Trust & security

Encryption

All traffic is encrypted in transit with TLS, and every response carries HTTP Strict Transport Security so browsers refuse unencrypted connections. Files and database records are encrypted at rest by our storage and database provider.

Data isolation

Access control is enforced at the database layer, not just in application code: PostgreSQL Row Level Security policies ensure each account can only ever read or modify its own rows, meaning files, transcripts and usage records. Storage follows the same rule: files live in per-user folders inside a private bucket, and the storage policies only permit access to the folder matching the requesting account.

As defense-in-depth, application queries additionally scope by the authenticated user's ID, so even a policy misconfiguration would not expose another customer's data.

Data deletion

Deletion is self-serve and immediate, with buttons in the product rather than a support queue:

• Uploaded audio/video is deleted automatically 30 days after upload (a nightly job with automatic retries and failure alerting).
• Any file or transcript can be deleted instantly at any time.
• Account deletion permanently removes everything: files, transcripts, usage records and profile.

Paranoid Mode

For sensitive recordings, Paranoid Mode deletes the uploaded audio file permanently the moment transcription succeeds. The recording, the most sensitive artifact, exists on our systems only for the minutes transcription takes. The transcript remains yours to keep or delete. Precisely what it does and doesn't do is documented in the Privacy Policy.

AI processing without training

We never use your files or transcripts to train AI models of our own. Transcription and AI features run on established third-party providers, and we configure their training opt-outs so your content is not used to train their models under their current API terms. Your content is sent to them only to fulfil the specific request you make, and never to any other third party.

Payments

Payments are processed by a third-party payment provider acting as merchant of record. Card details never touch our servers; we store only your plan and the provider's subscription references. Webhook messages from the provider are cryptographically verified before any account change.

Infrastructure

Trustample runs on established, audited providers rather than self-managed servers:

• Application hosting and global CDN
• Managed PostgreSQL database, authentication and encrypted file storage
• Speech-to-text processing
• AI features (summaries, chat, translation)
• Payments and taxes, via a merchant of record
• Background job processing with automatic retries
• Rate limiting and error monitoring

Application security

Every response carries security headers (X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, HSTS). All API endpoints authenticate the caller and verify resource ownership. Upload, transcription and AI endpoints are rate-limited. Secrets live in environment configuration, never in code, and the repository is scanned before every release.

Where your data is processed

Your account, uploaded files and transcripts are stored and processed on infrastructure located in the United States. The third-party services we rely on for transcription and AI features are US-based and receive your content only to fulfil the specific request you make, never for any other purpose.

Operational services such as rate limiting and error monitoring hold only technical metadata, never your files or transcripts. Each provider handles data under its own terms and safeguards, described in its privacy documentation.