Security & Trust

This page describes controls that the platform implements today and is explicit about what is planned or in preparation. It is not a contractual commitment; contractual terms are in your Order Form, DPA and BAA.

At a glance

Data isolation, by plan

• Starter and Professional run on a shared SKIFIN-operated Azure host. Each tenant has a logically separate database and separate storage containers; Professional can have a dedicated Cosmos DB account. Compute is shared.
• Private (bring your own cloud) is deployed into the customer's own Azure subscription, in a dedicated resource group, under the customer's billing account. In that plan, Customer Data stays in the customer's subscription, apart from the AI model calls described below.
• Enterprise is a managed dedicated environment operated by SKIFIN.

Vendor operator access to tenant data planes is restricted to defined operator permissions, and impersonation sessions are time-boxed and audited.

Encryption

• In transit: TLS for browser-to-API and service-to-service traffic.
• At rest: Microsoft-managed keys by default. Customer-managed keys (Azure Key Vault) are available on Private and Enterprise. The public demo environment uses Microsoft-managed keys.

Access controls

• Role-based access control with least privilege. A grant-subset guard stops users from granting permissions they do not hold, and last-admin protection keeps at least one enabled administrator per tenant.
• Email invitations with single-use links valid for 72 hours; session revocation.
• Account lockout after 10 failed sign-ins in 15 minutes (15-minute lock) and rate limiting on the API.
• Optional TOTP two-factor authentication with single-use recovery codes. It is opt-in per user; enforcement for all users in a tenant is not yet available.
• Single sign-on with Microsoft Entra ID on eligible plans; optional Google sign-in.
• Passwords are hashed; access tokens are short-lived.

Audit logging

The platform records audit events for user, role, group, two-factor and lockout changes, and for data access, modification and deletion. Events include user ID, action, resource identifier, client IP address, user agent and timestamp. They do not include document content, and a PHI-masking filter is applied to logs.

Audit logs are written to write-once (WORM) blob storage with a 7-year retention policy. The policy is not yet locked, so it is not currently tamper-proof at the storage level.

AI data handling

• Azure OpenAI (GPT-4.1, gpt-4o-mini, text-embedding-3-small) is used under Microsoft's enterprise data terms. Our AI models are hosted on Microsoft Azure, so prompts and outputs are processed within Azure and are not used by Microsoft to train its models. Microsoft's standard Azure abuse monitoring applies unless an exemption has been approved for a deployment; stricter handling can be agreed per customer.
• Mistral document OCR runs as a Mistral model deployed on Azure AI Foundry, in the Azure region of the deployment. It is not Mistral AI's own service.
• SKIFIN does not train or fine-tune models on customer data. Corrections are reused as examples only within the same tenant.
• AI outputs can be wrong; human-in-the-loop review is available.

Compliance status

By region

Regulators do not certify vendors, and compliance remains the customer's responsibility. This table shows what the platform is designed to help customers meet in each region, and where data can be located. Where AI processing runs depends on the deployment and is stated in the Order Form.

Resilience and testing

• Backups: Cosmos DB periodic backup, about 7 days; worst-case recovery point 4 hours.
• Disaster recovery: a DR plan is documented; the first drill is scheduled.
• Penetration testing: an independent third-party test is planned. We will publish a summary when one is complete.
• Vulnerability management: dependency and container image scanning in the build pipeline.
• Secrets: stored in Azure Key Vault (soft delete 90 days).

Data deletion

Administrators can delete documents and user data in the application. After termination, Customer Data is deleted 30 days after the account ends, with a deletion attestation on request; backups expire on their normal cycle. On Private deployments, the customer can also remove the resource group in its own subscription. See the retention table.

Incident response

We notify affected customers of confirmed personal data breaches without undue delay, targeting within 48 hours of confirmation, and support the customer's own regulatory deadlines. For deployments in India, covered incidents are reported to CERT-In within 6 hours. Support response targets are set in the SLA where an Order Form includes one.

Subprocessors

See the Subprocessors page for the current list. We give 30 days' notice of changes.

Contact

For security questions, vulnerability reports, BAA or DPA requests: contact@skifin.com, subject "Security / Compliance". Related: Privacy Policy · Terms of Service · Acceptable Use Policy