Mestra builds every format a campaign needs from approved advertising masters, checks each one, publishes them to screens, runs screens and reports what played. This page describes how the service is built and run today. Where something is planned rather than in place, we say so.
Hosting and data residency
The service and database run in Sydney. Library files are stored in Cloudflare R2 with an Oceania location hint, which Cloudflare describes as best effort. Some data is processed or held overseas, as listed below and on the sub-processors page.
| Data | Where it lives |
|---|---|
| Application server | Fly.io, Sydney |
| Database | Neon Postgres on AWS ap-southeast-2, Sydney. Holds accounts, settings, run records, usage and the audit log. |
| Library files | Cloudflare R2 with an Oceania location hint. Cloudflare describes location hints as best effort, not a guarantee. |
| Review rounds | Descriptions and pictures of each size, the images and brand fonts they use, and exports: Cloudflare R2 with an Oceania location hint, encrypted by Mestra. Comments, approvals and review links: Neon Postgres, Sydney. |
| Traffic in transit | Cloudflare's global network |
| AI processing | United States |
| Place search | AWS ap-southeast-2, Sydney. Searches may be answered by its map data partners outside Australia, with account details removed. |
| Sign-in and notice email | Postmark, United States |
| Payments | Stripe, United States and other countries. |
| Operational logs | Our own log server in Sydney (Fly.io), searchable for 90 days, with a 1-year archive in Cloudflare R2 (Oceania location hint). Fly.io also keeps its own copy for 7 days. IP addresses are shortened to the network. |
Encryption
- In transit: public traffic is HTTPS only (TLS 1.2 or later, with HSTS). Connections between our service and its database, file storage, AI provider and email service are also encrypted.
- Library files are encrypted by Mestra before they're stored, with a separate key for each organisation. Our storage provider only ever holds encrypted data. How long files are kept is under Retention and deletion.
- Review files (descriptions and pictures of each size, images, exports and brand fonts) are encrypted the same way as library files. A brand's fonts are only used to render that brand's work.
- Database: other records rely on the database provider's encryption at rest.
- Sign-in tokens: sessions, sign-in links and app tokens are random, and only their hashes are stored.
Access control
- Roles: people join your organisation as owner, editor or reviewer. Every request is scoped to one organisation, and removing someone or changing their role ends their sessions in that organisation at once.
- Sign-in: with an emailed link, Google or Microsoft (work and school accounts). Enterprise customers can also use their organisation’s own sign-in provider. An emailed link works once and expires after 15 minutes.
- Design apps: InDesign, Figma and Canva connect through a browser approval.
- Audit log: sign-ins, membership and configuration changes and staff actions are recorded.
- Staff access: Mestra staff can view your organisation only with permission, to help with a support request. Each session, its reason and every change made are recorded in your audit log, and owners can see them on the Activity page.
- Review links: a link carries a random token, and we store only its hash. A link covers one campaign for one brand, expires after 30 days by default (the owner or editor who creates it can set up to 90) and can be revoked at any time. Outside reviewers confirm their email address with a one-time code that works for 10 minutes, is rate-limited and is protected by Turnstile. Review pages aren't indexed by search engines and don't send referrer headers. Downloads are off unless they're turned on for that link.
- Vendor accounts: multi-factor authentication is on for every hosting and infrastructure account.
AI processing and data use
Our AI provider is Anthropic. Each request sends it content from your designs and comments, such as text, layout and images, with your format and brand settings. For a screen fault, it gets the fault's code and how it was handled, with no screen names, screenshots or log files. Anthropic processes this in the United States.
Mestra doesn't store its prompts or the AI's replies, apart from layout review passes and screen fault diagnoses (kept up to 90 days). What it keeps from each build, and for how long, is under Retention and deletion. Review notes are visible to people in your organisation and never to outside reviewers. Anthropic deletes API inputs and outputs within 30 days by default. Content flagged for a usage-policy violation may be kept for up to 2 years (classification scores up to 7 years), or longer where the law requires. Under Anthropic's commercial terms, customer content isn't used to train models. Mestra doesn't claim zero data retention.
Retention and deletion
- To lay out a format, Mestra reads your master. Mestra doesn't keep the artwork or copy it reads from your master beyond what is described here. It keeps each built size's layout and images for your retention period, 90 days unless an owner chooses 30 days or 1 year, so you can review, change and export the run later. Settings you enter, such as campaign copy and logos, are kept until you delete them. If a trial or subscription ends, or an invoice is 14 days unpaid, your organisation becomes read-only. Unless you subscribe or pay the overdue invoice within 60 days, its content and settings are then deleted, and we keep only what our Privacy Policy describes. Exported files in the file library are kept for your retention period and then deleted. An owner can instead choose Keep everything, and files are then kept until you delete them or close the account. Files kept this way still count toward your cloud storage.
- Each built size's layout and images are kept encrypted. Mestra also keeps each built size's layout plan, encrypted, so the size can be changed and drawn again, and deletes it with that size.
- When someone presses Save master in the InDesign, Figma or Canva app, Mestra keeps a copy of that master, encrypted. It is used to build sizes and shown in the web app, and it counts toward your cloud storage. It is kept until someone deletes the master or its brand, or your organisation's content is deleted. A network's advertisers' saved masters are kept the same way and deleted when the advertiser is deleted from the network. When you press Generate, Mestra also saves the master as a new version if it changed, and people in your organisation can see and compare versions in the web app. An older version is deleted once no kept run uses it. The latest version stays until the master is deleted.
- Run records and usage counts are kept for the life of the organisation. The audit log is kept for one year.
- Review rounds and comments are kept for your organisation's library retention period after the review's last activity, then deleted, unless an owner has chosen Keep everything. Review exports are deleted 7 days after they're made, whatever the retention. Approvals and applied changes stay in the audit log for one year.
- AI review notes and layout review pass records (the AI's replies and working notes) are kept for the library retention period, encrypted (layout review pass records with your organisation's own key), and deleted if you shorten the retention period (run notes straight away, review notes within the hour), or delete the run, review or brand, or close your account. Mestra uses layout review pass records to investigate and improve layout quality. Only Mestra staff can read them, for that purpose, and each read is logged.
- Owners and editors can delete settings, logos and library files at any time.
Data-handling details are available on request: email privacy@withmestra.com.
Breach notification
If a security incident affects your data, we'll tell you without undue delay, aiming for 72 hours from confirming it.
Data requests
Organisation owners can ask us to export or delete their organisation's data at any time: email privacy@withmestra.com.
Monitoring and status
UptimeRobot checks the service every 60 seconds, including sign-in. Live status and incident updates are at status.withmestra.com. Request logs carry no customer content. Mestra runs in a single region. Enterprise agreements include a service level. Other plans don't have one.
Engineering practice
Every change runs automated tests and vulnerability scans. Security-sensitive designs are reviewed before release.
Certifications
Mestra has no SOC 2 or ISO 27001 certification yet, and no independent audit or penetration test. Our security pack and completed security questionnaire answers are available on request.
Security policies
Our security policies: Information security, Access control, Change management, Backup and recovery, Incident response, Vendor management and Vulnerability disclosure. Adopted October 2026 and reviewed every year. Copies are available on request: email security@withmestra.com. Vulnerability disclosure is public, below.

Reporting a security issue
If you think you've found a vulnerability, email security@withmestra.com. We'll reply within two business days. Our security.txt has the machine-readable details.
- Include what you found and where, steps to reproduce it, and the impact you expect. Encrypt sensitive details with our PGP key (fingerprint DEEB 19CE 4D4F 6669 FDAF 90D3 4B1D 3CFE B08D E03D, at /.well-known/pgp-key.txt). Please don't send customer data you've accessed: describe it instead.
- In scope: app.withmestra.com, the Mestra apps and withmestra.com. Don't test admin.withmestra.com or status.withmestra.com, and no denial-of-service, load testing or social engineering.
- Testing rules: use only accounts and organisations you own (ask us for a test organisation if you need one). Don't access, change or keep other customers' data: if you reach any, stop and tell us. Don't degrade the service for others.
- Timing: give us a reasonable time to fix the issue before you disclose it. Our target is 90 days, or sooner by agreement.
- Our commitments: we'll acknowledge your report, keep you updated, tell you when it's fixed and credit you if you'd like. We won't pursue legal action against good-faith research that follows this policy. We don't currently offer paid bounties.
Incident contact
Report a security incident to security@withmestra.com. Updates are posted at status.withmestra.com.
