Trust & security

Security posture.

v0.2-draft · last reviewed 2026-11-13

We're pre-SOC2 and honest about it. Here's what's in place, what's roadmapped, and the gaps; no date is set for any of them. This page has not been reviewed by a lawyer.

§AEncryption

Traffic to api.travelminds.ai and travelminds.ai is served over HTTPS through Cloudflare. API keys and passwords are stored as Argon2id hashes; only the key's prefix (used for revocation lookup) is stored in cleartext.

The database runs in a Docker container on our own server in India, with its data in a Docker volume on that machine. Google sign-in tokens for the MCP connector are stored on the same server in a file store that is not encrypted.

§BAccess control

API keys follow the tmai_live_<prefix>.<secret> format. The prefix is publicly visible (used in dashboard + revocation UI); the secret is never recoverable after issue. The data endpoints read through the tmaiv2_api Postgres role, which cannot bypass row-level security. Account, billing, usage tracking and the Concierge use a separate administrative role that does bypass row-level security.

The service runs on our own server, which takes outside traffic only through a Cloudflare Tunnel. GAP — B.2.a GAP — B.2.b A centralised personnel offboarding checklist and rotation policy are on the §F roadmap; no date is set.

Customer-side key permissions are coarse-grained today (every issued tmai_live_* key has full read of the tenant's licensed surface). GAP — B.4 Per-key scoping is on the §F roadmap; no date is set.

§CLicense posture

Every commercial-table row in TravelMindsAI carries a license_tag. The registry classifies sources as commercial-OK (Apache-2.0, CC0, CC-BY-4.0, ODbL, and others; the public list at /v1/licenses has 50 entries, 41 of them cleared for commercial use, as of 14 November 2026) or not cleared (non-commercial, default-deny, unclear-pending-review). For the data endpoints, a Postgres row-level security policy hides every row whose license has not passed our filter. Plan options, such as CC BY-SA content, are applied in the gateway code. The same filter is not a per-tenant whitelist: it applies to every account alike.

Data endpoint rows carry their license tag inline.

What the licences require of you is on the licence page; the live list is at /v1/licenses.

§EInfrastructure

Our server takes outside traffic only through a Cloudflare Tunnel. Its service ports, including the database, are bound to 127.0.0.1, so none is reachable from the internet.

Background ingestion (the W-numbered ETL fleet) runs on the same server as the live service. The data endpoints read the published tables through the row-level security policy described in §C.

An on-prem package is possible by contract; none has been built or deployed for a customer.

§GSub-processors

The current list of Approved Sub-processors lives at /legal/sub-processors. Categories include LLM inference (Anthropic, when the trip planner is switched on), billing (anticipated: Paddle outside India, Razorpay in India), website hosting, edge and tunnel (Cloudflare), sign-in for the MCP connector (Google), page assets (Google Fonts, unpkg, CARTO), source hosting (GitHub), and transactional email (Resend when it is configured, otherwise an SMTP service).

A machine-readable JSON list is published at /legal/sub-processors.json for change-watch automation.

§DAudit & monitoring

Application and gateway logs are kept in Docker's log files on our server, capped at 100 MB per container, with the oldest entries overwritten. GAP — D.1.a Shipping those logs to a separate, tamper-evident store is on the roadmap; no date is set. GAP — D.1.b A SIEM / log-analytics platform: no date is set. GAP — D.2 Customer-self-service audit-log download: no date is set.

We're transparent that this is the lowest-maturity area of the posture.

§HIncident response

Report security issues to [email protected]. The DPDP grievance channel is [email protected].

§FRoadmap of [GAP] items

Every GAP marker on this page corresponds to a row below.

Gap IDDescriptionTarget
C.2Off-site backup with documented retentionNo date is set.
C.3DR runbook with RTO / RPO commitmentsNo date is set.
D.1.aAudit-log shipping to tamper-evident storeNo date is set.
D.1.bSIEM or log analytics platformNo date is set.
D.2Customer-self-service audit-log downloadNo date is set.
A.3Concierge query PII redaction at gatewayNo date is set.
B.2.bDocumented offboarding checklistNo date is set.
B.4Per-key scopingNo date is set.

Updates ship as a new version pill at the top of this page.

§IDocuments

Direct links to the contractual artifacts referenced above:

If your procurement needs a questionnaire, write to [email protected].

§JContact

Security reports / questionnaires:  [email protected]

DPDP grievance officer (India):  [email protected]

General:  [email protected]