Security

In Stemma, each company's product data is kept apart from every other company's, and every change is traceable. Here is how. Updated 2026-11-17.

Company data stays separate

Every table belongs to a company workspace, and the database itself checks on every request that the user has access to that workspace. One company's records cannot be linked to another's, even by a faulty request. Automated tests check this on every change.

Roles and approval

Roles are owner, admin, editor and viewer. A product reaches webshops, partners or datasheets only after it is approved, and editing an approved product sends it back for review. Every change is kept in the history: who, what and when.

Sign-in

Two-factor sign-in with an authenticator app is built in. An organization can require it for owners and admins, and can require sign-in with the company's Google account.

Files and sharing

Images, videos and documents are private and downloaded through short-lived signed links. A shared datasheet link is personal to each recipient, expires and can be withdrawn; we store only a hash of it.

Integrations

API keys and webhook secrets are shown once and stored only as hashes. Webhooks are signed.

Support access

Stemma support can open your workspace only through a time-limited support session with a recorded reason, visible to your admins. Support cannot change members, API keys or sharing.

Where data is kept

Data is stored in Europe. All connections are encrypted (HTTPS) and our providers encrypt stored data.

Sub-processorPurposeLocation
SupabaseDatabase and sign-inIreland (AWS eu-west-1)
CloudflareFile storage, website and DNSEurope (R2 storage); global network for delivery
ResendSending emails your company starts (datasheets)Ireland (eu-west-1)
LovableApplication hosting during early accessProvider infrastructure; being replaced by our own accounts

Report a security issue

Email [email protected]. We reply within one working day.