Skip to content
Trustample
Privacy by architecture

Trust & security

You upload recordings of real conversations — the most sensitive data there is. This page describes, precisely, how that data is protected. Every claim here is traceable to our Privacy Policy and to the implementation itself.

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 — files, transcripts, 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 — buttons in the product, not 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 removes everything — files, transcripts, usage records and profile — permanently.

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 — no training

We never use your files or transcripts to train AI models of our own. Transcription runs on Deepgram and AI features on Anthropic Claude; we configure these providers' 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 Paddle as merchant of record. Card details never touch our servers — we store only your plan and Paddle subscription references. Webhook messages from Paddle are cryptographically verified before any account change.

Infrastructure

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

  • Vercel — application hosting and CDN
  • Supabase — PostgreSQL database, authentication and encrypted file storage
  • Deepgram — speech-to-text processing
  • Anthropic — AI features (summaries, chat, translation)
  • Paddle — payments and taxes (merchant of record)
  • Inngest — background job processing with automatic retries
  • Upstash — rate limiting; Sentry — 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 — the repository is scanned before every release.

Where your data is processed

Our providers operate primarily on infrastructure in the United States, so your content is stored and processed there and may transit other regions where these providers operate. Each provider handles data under its own terms and safeguards, described in its privacy documentation.

Questions or security reports

Security concerns, vulnerability reports or privacy questions: info@trustample.com. We aim to respond within 48 hours. See also our Privacy Policy and Terms of Service.

Chat with us