Where your data lives, who can see it, how long it’s kept, and what processes it. No marketing language — this is the same page we’d walk your InfoSec or audit team through.
Mayetik runs on Railway’s managed infrastructure, backed by a dedicated PostgreSQL database — not a shared multi-vendor stack. Files respondents upload are held separately, in a private cloud storage bucket with no public access (see below). All traffic to and from Mayetik is encrypted in transit (TLS). Data at rest sits on encrypted infrastructure-provider storage. We don’t currently hold a formal certification (SOC 2, ISO 27001) for this infrastructure — we’ll say that plainly rather than imply otherwise, and formal certification is on our roadmap as we grow.
Access is role-based and enforced on every request, not just in the UI:
Every meaningful action — session created, invitation sent, brief generated, role changed, knowledge queried or exported — is written to an append-only log with who, what, and when. Nothing in that log can be edited or deleted through the product. Org and project admins can view their own scoped history at any time.
Responses are sent to OpenAI’s API to generate briefs, transcribe voice input, and build search embeddings. Per OpenAI’s API data usage policy, data submitted through the API is not used to train their models by default. Email delivery (invitations, magic links, notifications) is handled by our transactional email provider. Files respondents upload, and our encrypted database backups, are stored with a cloud storage provider. Our infrastructure provider hosts the application and its database. Those are the parties that hold or process customer data — we don’t sell, share, or otherwise use it beyond delivering the product. A full sub-processor list, naming each one, is available on request.
A file attached to an answer is never given a public address. It is stored in a private bucket, and an answer records a reference to it rather than a link. Every read goes through Mayetik, which checks who is asking — the respondent who uploaded it, an admin of that project or organization — before issuing a link that works for five minutes and cannot be reused afterwards. Someone who obtains that link later, or who is not entitled to the file, gets nothing. When an organization is deleted, its files are removed from storage as well as from the database.
Responses, briefs, and audit history are retained for the life of your organization’s account — we don’t auto-delete data on a fixed schedule today. An org owner can request deletion of a specific project, interview, or the entire account at any time by contacting hello@mayetik.com. Deletion removes the data from the live system, including any uploaded files, promptly. Encrypted backups are a deliberate exception: they are held under a retention lock for 30 days, which prevents them being altered or deleted in the ordinary course — that is what makes them useful after a mistake or an attack — so a copy persists there until it expires, within 30 days of the request. Backups are encrypted before they leave our systems, with a key our storage provider does not hold.
Responses, briefs, and syntheses export as CSV, JSON, or Markdown at any time — nothing is locked in. This matters for evidence packs, legal or IC review, and simply not being dependent on us to hold your own records.