Trust Center

You should be able to check every safety claim.

Buyer records, chats, papers, and checks move across markets and channels. This page says what is live, what is in a contract, and what is still planned.

Contact security Request a DPA

Encryption

TLS 1.2+ in transit · AES-256 at rest

Live

Tenant isolation

Scoped at the database and API boundary

Live

Model training

Excluded on provider API tiers

Contractual

Fairshift SOC 2 Type II

Certified infrastructure in use today

Planned

SOC 2 Type II

Planned · SOC 2 certified infra

GDPR

Export + erasure endpoints

DPDP Act

Aligned data practices

TLS 1.2+ · AES-256

Encryption in transit + at rest

Commitments

Six commitments, every tenant.

Honest about what is in place today, and what is on the roadmap. We publish what we have, not what we hope.

Tenant isolation

We keep each customer's data apart. Safety checks stop accounts from reading each other's chats, leads, or settings.

Encryption

Fairshift protects moving data with TLS 1.2+ and stored data with AES-256. Secrets such as email passwords are stored as coded text. Keys stay separate for each system area.

Audit trail

For key records, a change and its log must save together. If either fails, neither is saved. The log shows if a person, AI, or other process made the change. Newer tables are being added to the same check.

Role-scoped access

Owners, admins, members, viewers, and trade show staff get different rights. The API checks each role. Only owners can delete key data. SSO and SAML are planned for large customers.

AI model safety

We choose plans where model providers agree not to train their base models on customer data. We will list any provider that does not give this promise.

Compliance roadmap

GDPR export and deletion endpoints live. DPA available on request. Our infrastructure providers hold SOC 2 and ISO 27001 today; Fairshift's own SOC 2 Type II is planned. We publish what we have, not what we hope.

Audit trail

Every core write, recorded in the same transaction.

Attributable and insert-only. The audit log is not a side channel: for core entities, the change and its activity row are one transaction. If the log fails, the write fails.

Recorded fields

Actor (human, AI agent, or automation, with display label), action in entity.verb form, target entity, context snapshot, correlation ID for fan-out writes, UTC timestamp.

Coverage

All writes to core CRM entities: leads, conversations, messages, deals, campaigns, sequences, calls, personas, mailboxes, deployments, knowledge docs. Newer operational tables (orders, tasks, accounts) are being brought under the same gate.

Tamper resistance

Insert-only by design. The application write path has no update or delete on log rows, and retries are idempotent: a duplicate write returns the original log row instead of minting a second one.

Retention

Retained for the lifetime of your workspace. Full JSON export available through the GDPR export endpoint or on request.

AI attribution

AI-initiated writes record structured reasoning (trigger, policy, confidence, narrative) plus a snapshot of the inputs at decision time, so automated actions can be reviewed after the fact.

Access control

Roles enforced at the API, not by convention.

Every person gets a role with set rights. Trade show staff have separate roles. Only owners can delete key data. No role gets access to everything by default.

Owner

Full control of the tenant, including billing, team, and destructive actions. Account deletion requires the owner role, an explicit confirmation phrase, and is rate-limited.

Admin

Manages team members, personas, evals, and integrations. Cannot delete the tenant.

Member

Day-to-day operations: conversations, leads, pipeline, quotes, campaigns. Cannot manage users or billing.

Viewer

Read-only inspection access for auditors, analysts, and stakeholders.

Operator roles

Parallel expo roles (vendor, floor, organiser) scoped to event surfaces. They sit outside the tenant hierarchy and never inherit tenant-wide rights.

SSO and SAML

On the enterprise roadmap. Today: email and password sign-in with JWT sessions and rate-limited auth endpoints.

Residency

Data lives in Singapore. Stated plainly.

Stored customer data sits in one AWS area in Singapore. It is managed through Supabase. We will only list more areas after they are live.

Primary storage

AWS ap-southeast-1 (Singapore), via Supabase: Postgres, auth, and file storage. Encrypted at rest with AES-256.

Application compute

API on Railway (Google Cloud, USA). Frontends served from Vercel's global edge network. TLS 1.2+ on every hop.

AI inference

US-hosted model providers (Anthropic, OpenAI, Google) on API tiers that contractually exclude customer data from model training.

Additional regions

EU and India residency are on the roadmap and will be offered through enterprise contracts as regions come online. No region is claimed before it exists.

Cross-border transfers

Documented in the DPA, available on request. Standard Contractual Clauses incorporated where GDPR requires them.

Right to delete

GDPR Article 17 supported. Owner-initiated deletion wipes the tenant across both schemas; confirmed within 30 days. Sub-processor cascade on contract.

Subprocessors

Providers we may use, listed for the record.

GDPR rules require this list. These are the service providers Fairshift may use now. The list can change. Last updated July 2026.

Provider

Role

Data handled

Region

Anthropic

Reasoning, drafting, multilingual handling

Conversation content, customer context

USA

OpenAI

Reasoning and drafting

Conversation content, customer context

USA

Google

Reasoning and multimodal

Conversation content, multimedia

USA

Retell / Vapi

Voice rails (inbound + outbound calls)

Call audio, transcripts

USA

Anam AI

Video avatar rendering

Session audio, video frames

USA / EU

KIE.ai

Image and video generation

Asset prompts, generated media

USA

Apollo / Clay

Lead data enrichment

Company and contact data

USA

Smartlead / Instantly

Email warming

Sender-mailbox metadata

USA / EU

Lovable / v0

Landing page generation

Campaign briefs, generated pages

USA / EU

Gamma

Deck generation

Deck briefs, generated content

USA

Perplexity / Exa

Research

Research queries

USA

Amazon Web Services

Database and storage infrastructure (via Supabase)

All customer data at rest

Singapore (ap-southeast-1)

Vercel

Edge hosting for marketing and app

Static assets, session tokens

Multi-region

Railway

API hosting and compute

All customer data in transit

USA (Google Cloud)

Supabase

Primary database and auth

Account and operational data

Singapore (AWS ap-southeast-1)

Twilio

SMS delivery, phone numbers

Message content, phone metadata

Multi-region

Meta (WhatsApp Business)

WhatsApp message delivery

Message content, phone numbers

Multi-region

Stripe

Billing and payment processing

Billing info, payment methods

USA / EU

Audits, DPAs, security reviews.

We show safety teams how Fairshift is built. We share DPAs and answer rule questions in writing. Contact us directly.

Contact security Privacy policy