Skip to content
SINAD iconSINADERP · Commerce · Accounting
PlatformProductsPricingResourcesCompany
Sign inBuild my plan
Subprocessors

Subprocessors

This page identifies core third-party processors or infrastructure providers that may handle personal data for the hosted service, depending on the tenant's enabled features.

Last updated

April 10, 2026

Core hosted-service providers

The following providers may process limited categories of personal data on our behalf as part of the hosted service:

  • Supabase: authentication, hosted database, storage, session handling, and related platform infrastructure for workspace data and uploaded files.
  • Meta Platforms services / WhatsApp Business Platform: message transport, delivery events, and related identifiers when WhatsApp features are enabled for a tenant.
  • Stripe: subscription billing, checkout, payment event reconciliation, and related billing identifiers when external billing or checkout is enabled.

Stay in the loop

Get product updates and new features

SINAD icon

SINAD

ERP · Commerce · Accounting

Sinad Core is the ERP foundation. Add Commerce, Factory, Product Specs, the AI Agent, and capacity packs as you grow.

info@larateks.com+90 (552) 636-34-00sinad.app

SINAD. Core ERP that grows with product add-ons.

Products

Sinad CoreSinad CommerceSinad FactorySinad Design (Beta)Sinad AI AgentPricingPlan Builder

Resources & Company

BlogCase studiesAboutContactSign in

Legal

Legal Center

Customer-configured or optional integrations

Some tenants may enable optional channels or external business workflows that depend on customer-configured providers. Where the customer selects, controls, or connects such a provider, the customer is also responsible for validating that provider's legal suitability for its own use case and obtaining any required permissions or notices.

Scope limitation

Not every subprocessor applies to every tenant or every user. Data shared with a provider should be limited to what is reasonably necessary for the feature being used, such as authentication, storage, billing, or WhatsApp delivery.

Change management

We may update this list when service architecture, billing flows, or communication channels materially change. The effective version and update date shown on this page should be used for legal reference and version tracking.

Questions or objections

Questions about this list may be sent to info@larateks.com. Contractual customers who require a stricter signed processor schedule should address that requirement through their commercial onboarding or data-processing addendum workflow.