1. Who we are
This policy explains how Mestra Labs Pty Ltd (ABN 73 702 936 356) of Sydney, New South Wales, Australia ("Mestra", "we", "us") handles personal information.
Mestra is a service for businesses. It turns an advertising master in Adobe InDesign, Figma or Canva into every format a campaign needs, checks each one, publishes them to screens, runs screens and reports what played. This policy covers our website (withmestra.com), the web app (app.withmestra.com) and the Mestra apps for InDesign, Figma and Canva, and the Mestra Player, our app that runs your screens.
We handle personal information in line with the Australian Privacy Principles in the Privacy Act 1988 (Cth).
Questions? Email privacy@withmestra.com.
2. What we collect
Account information. Your name and email address. If you sign in with Google, Microsoft or a sign-in provider your organisation connects, the identifier that provider gives us for you. Your role in each organisation (owner, editor or reviewer). Your sessions and app sign-ins: we store a scrambled form (a hash) of each token, never the token itself, together with your browser's user agent and the times it was used. When you connect a design app, we record the approximate location of the sign-in (country, and later city), worked out by our network provider from your connection, and include it in a security email to you. We don't store your IP address.
Organisation information. Your organisation's name and members. Your brands, formats, format sets, campaigns and campaign copy, and uploaded logos. When you sign up, the domain of your email address (for example example.com.au), or a note that it's a free-mail address.
Your content. When you run Mestra, our apps read content from your master, such as text, layout and images. For a review, the app also sends a picture of the built format. Your content may include personal information if, for example, your copy names a person or an image shows one. If someone presses Save master, we also keep a copy of that master, as section 5 describes, and a new version of it each time you press Generate. We also store your exported files in the file library.
Reviews. When your team reviews a campaign on the web, we store the review: each round (a snapshot of every format), approvals and requests for changes, comments and pins, and anything you apply or export. Fonts you upload to a brand are stored too, and are limited to that brand. For each font upload we also keep a licence record: the name and email address of the person who confirmed the font's licence, when they confirmed it, and a fingerprint of the file. We keep it so we can answer a font owner's questions about how a font is licensed. A review can include personal information if, for example, your copy names a person or an image shows one.
Outside reviewers. If an owner or editor shares a review link with someone outside your organisation, we collect that person's name and email address, which we verify with a one-time code, and their comments and approvals. We store only a hash of the link's token. The one-time code is hashed and expires after 10 minutes. Requests for a code are checked with Cloudflare Turnstile and rate-limited.
Screen systems you connect. If an owner connects a screen system (a third-party service that manages your screens) to Mestra, we store the access token you give us, encrypted, along with who connected it and when, and the settings you make for it, such as which screens match which sizes. To show you your screens, we read details from that system: screens, frames, sizes, opening hours, online status, and what's booked and playing. If your organisation uses dynamic variants, we also use each screen's location (coordinates, city, state and postcode) and tags to choose a variant. The reason we record for a choice can name a value that decided it, such as a city or a time (see section 9). We keep what the system tells us about your screens: their names, time zones, locations, tags, players, sizes and identifiers, and the bookings and creatives on them, in your organisation's account. When someone publishes, we keep a record of it: who published, when, where it went, the dates, the result, and the file's size, type and a fingerprint of it, but not the artwork itself, and, for reserved screen time, which screens, times and dates were reserved, and until when. If an owner turns on play reports, the screen system can send us records of when your bookings played, or we read them from it. From each play record we keep the booking, the screen, the advertiser's name, the creative's name and each play's time and length, or, where the system only gives daily totals, the number of plays each day. We don't keep anything about people who see the screen. None of this is sent to our AI provider.
Screen monitoring. If your organisation runs Mestra screens, we collect each screen's health readings, play counts and events (section 9 says how long). We keep them in Mestra's monitoring service for your organisation, and show them only to your organisation. Mestra staff see screen health and events to run the service. Play records themselves are covered under "Mestra screens" below.
Mestra screens. If your organisation runs Mestra screens, an owner installs the Mestra Player on each screen's Windows PC and joins it to your organisation, either by typing in the code the screen shows or with an install key an owner makes. We then hold:
- The pairing. While a screen waits to be joined: its code (stored scrambled, valid for 10 minutes), its size and rotation, its time zone and the hardware details below.
- Keys. For each install key: its name, who made it, when, its last four characters, any expiry and expected number of screens, and how many times an ended key was tried. We keep only a one-way hash of the key. A screen's own key is also kept only as a hash.
- Each screen. The name an owner gives it, its site, when it joined and was last heard from, the Player's version, and whether it is online. Its display size, rotation and time zone. What it is showing and playing next, the size of its file cache, and any file that failed its check. What the PC can decode, and whether it can run HTML5 ads.
- Location. If an owner sets one, on a screen or its site: a place name, street address, suburb, state, postcode and map coordinates. If an owner uses place search, the text they type is sent to a map data provider to find matching places, and the place they pick fills in these details.
- The PC. The Windows edition and build number, how the Player is set as the PC's shell, and the PC maker and model as its BIOS names them. Its serial number, its hardware ID (the system UUID from the BIOS) and a hash of its TPM key, which we use to tell one screen from another and to detect tampering. Health readings: free disk space, memory, temperature, the clock's offset from ours, the web view's version and when the PC last started. The Player does not report the PC's host name, its IP address or the names of Windows accounts. We don't store the PC's IP address. Like every request, our logs keep only its network part. A log file an owner asks for can contain the name of the Windows account the Player runs under.
- What the screen did. Play records: which booking played, when (in the screen's local time), for how long, which file, and whether the panel was on. They contain nothing about people who see the screen. A short history of events (for example "came online", "restarted its window") and of commands an owner sent, with the user who sent each.
- Screen control. The hours, brightness, sound and power settings an owner sets, and, if an owner connects the Player to a display panel, the panel's settings, including the serial port or local network address (IP address and port) they enter, and the panel's latest report. If an owner runs Test panel, the exact messages the screen sent the panel and the panel's replies, for the latest run on each screen only.
- What owners ask of screens. Bookings (name, dates, times), the artwork sent to screens, the stop screen, and takedown requests with the reason the user types and who made them.
- Business contacts. If your organisation runs a network, the contacts you keep for each advertiser: name, email and company.
- Customers. If you name the advertisers you book screens for, or bring them across from a screen system you connect or from Mestra Network: each one's name, an optional category, and the loop rules you set for it. Shown to your organisation, and to Mestra support when you ask us to help. Kept until your organisation ends, or until you ask us to delete them.
- Screenshots. An owner can ask a screen for a screenshot, and can turn on automatic screenshots every 15, 30 or 60 minutes (off unless an owner turns them on). A screenshot is a picture of the PC's main monitor, which is whatever the screen is showing at that moment. The Player has no access to a camera, a microphone or any other screen. Screenshots are encrypted before they are stored, with your organisation's key.
- Log files. An owner can ask a screen for its log file. The Player keeps a short rolling log on the PC. It has keys and tokens removed. It is sent only when an owner asks. It is stored as it arrives, encrypted, and is not read by us or sent anywhere else.
Screenshots and log files are shown only to owners and editors in your organisation, in the web app. They can't be reached with an API key or a connected app, and Mestra staff can't see them through support access. What your screens report is shown to your organisation, and Mestra staff see screen health and events, with the organisation and screen identifiers, to run the service. Screenshots and log files are never sent to our AI provider.
On the screen's PC. The installer makes (or uses) a Windows account for the Player and signs it in automatically. Its password is made on the PC, kept in Windows' protected secret store, and never sent to us. If the PC already signed in automatically to another account, the installer keeps a copy of that account's sign-in details (its name and password) in the same protected store, only so the uninstaller can put them back, and removes the copy when it does. The copy is readable only by administrators and the system, and never leaves the PC. Files the screen plays are cached on the PC and removed if the screen is removed. The Player's own device key and log live in a folder only administrators and the system can change.
Project tools you connect. If an owner connects a project tool (a third-party service where your team writes briefs) to Mestra, we store the access token, encrypted, along with who connected it and when, and the settings you make for it, such as which lists hold briefs and which fields match which campaign details. When a brief is sent to Mestra, we read it from that tool: its title, description, fields and link. We keep the link, the title, the brief's description when you've allowed us to read it, the details we filled into the campaign and short notes on what needs a look.
Accounting systems you connect. If an owner connects an accounting system, we store its access token, encrypted, with who connected it and when, the organisation's name, currency, country and lock dates, the accounts and tax rates you choose, and a record of what we posted with the system's identifiers. We send it the tax invoices, receipts and credit notes of your card bookings (with their PDFs), the advertiser's name, email and tax number as a contact, the payments and refunds, fees, disputes, our fee invoice and your payouts. Depending on the integration we may read your accounts, tax rates and contacts to match them. It is your organisation's own provider, under its own terms, and isn't our sub-processor. None of this is sent to our AI provider.
Motion. When someone makes motion, we keep the motion brief, chat and versions, and the videos we render. They are encrypted and aren't written to our logs.
Ask Mestra. When you use Ask Mestra, the helper in the web apps, we keep your conversations: what you ask, the answers, and what it looked up to answer. They are encrypted, shown only to you, and aren't written to our logs. You can delete a conversation at any time.
API and connected apps. If an owner turns on the API and MCP server, we also keep:
- API keys: the key's name, who made it, its permissions, expiry and when it was last used. The key itself is stored only as a one-way hash.
- Connected apps: the app's name and address as it gives them, the permissions chosen, who connected it, and when it was last used.
- Sign-in consent records for connected apps.
Usage information.
- Run records: who started a run, when, the brand, campaign and app used, and each format's status and flags. These hold no artwork or copy.
- A usage ledger: a record of each AI request (model, token counts, timing, outcome and cost), with no content.
- An audit log: sign-ins and changes, recording who did what and when. It never holds content or tokens. It holds an email address only where an outside reviewer approves something, which is recorded by name and email address.
- The audit log also records approvals, uses of Apply, review links created and revoked, and approvals made on someone's behalf.
- Operational logs: request lines (method, path with sensitive parts removed, status and timing), with no content. Logs record only a shortened form of your IP address (the network part, not the full address).
Sign-up and anti-abuse information.
- When you sign up, an automated check (Cloudflare Turnstile) confirms you're human, and we use your IP address for a short time to apply rate limits.
- To stop repeat free trials, we keep one-way fingerprints of your work domain, your email address and, if you add a card, the card, and of the network your sign-up came from. They can't be turned back into the domain, address, card or IP address. They are kept indefinitely, including after your organisation is deleted, and used only to enforce one trial each.
Billing information (through Stripe). If your organisation subscribes or adds a card, Stripe collects the billing contact's name, email and address, any tax ID, and card details. If your organisation has a written contract and is billed by invoice, we give Stripe the billing contact's name, invoice email address and postal address (and any tax ID), so Stripe can issue the invoices, send them and collect payment. Card details are entered only on Stripe's pages and never reach Mestra. We never store a card number, its last four digits or its expiry date. We keep Stripe's reference numbers, your subscription status, the invoice amounts, due dates and whether each invoice is paid, and the card-fingerprint hash described above.
Support emails. If you email support@withmestra.com, privacy@withmestra.com or security@withmestra.com, we keep your email address, your message and our reply.
Website enquiries. If you use a form on our website (for example "Talk to us"), we collect your name, email address, company, role and message, and the country your request came from (worked out from your IP address, which we don't keep).
Website analytics. Our website uses Cloudflare Web Analytics, which counts visits and pages viewed without cookies and doesn't track you across other sites.
Cookies.
- The web app uses a session cookie to keep you signed in. It's first-party and essential: the app can't work without it.
- If you sign in with Google or Microsoft, a short-lived cookie keeps that sign-in secure.
- Cloudflare, which delivers and protects our app and website, sees your IP address when you connect. Its Turnstile check, on sign-up and on our website forms, and when an outside reviewer asks for a one-time code, may set its own cookie or storage for that check.
- The web app also keeps two small items in your browser's storage: the page to return to after you sign in, and which notices you've dismissed. Our design-app plugins keep a sign-in token in the app's own storage.
- We don't use advertising or cross-site tracking cookies.
We don't ask for sensitive information (such as health or political information) and you shouldn't put it into Mestra.
3. How we collect it
We collect personal information:
- from you, when you sign up, use Mestra, contact us or fill in a form on our website;
- from your organisation, when an owner invites you (they give us your email address and role) or a member starts runs that include your information;
- from the Mestra apps, which send us the structure of a master while a format is being built;
- through the API and MCP server, when your systems or connected apps send us information;
- automatically, through the session cookie, logs, the audit log and analytics;
- from your organisation or its authorised contact, when we set up your contract (the invoice contact's name, email address and address);
- from Stripe, about the status of your payments, invoices and subscription;
- from Google or Microsoft, if you choose to sign in with them;
- from outside reviewers, who give us their name, email address and comments when they open a review link.
You can deal with us without giving your name only for general website enquiries. To use Mestra, we need your email address.
4. Why we use it
We use personal information to:
- provide Mestra: create accounts, sign you in, build and review formats, and deliver files;
- run your organisation: invites, roles, settings and the file library;
- run trials; bill for subscriptions, and invoice customers on a written contract, including through Stripe;
- enforce our trial rules and limits, and prevent fraud and abuse. Some of these checks are automated: for example, whether a domain, email address or card has already had a trial decides whether a new trial can start;
- keep Mestra secure, investigate incidents and keep the audit log;
- send service emails, such as sign-in links, trial reminders, billing notices, read-only and deletion warnings, and security notices;
- run your screens: show your artwork on them, check they are on and playing, switch them on and off, and let your team see and fix a screen that has a problem.
- answer support requests and website enquiries;
- understand how Mestra and our website are used, mostly from counts with no content, so we can improve them;
- meet our legal obligations, such as tax records.
We also use personal information to run reviews: to show your team each round and what changed between rounds, to record approvals and comments, to send review notices, and to let outside reviewers see and comment on the one campaign a link covers.
We don't sell personal information, and we don't use it for advertising.
If one person at your organisation's domain already has Mestra and you ask to join, we email that organisation's owners your name and email address so they can invite you. We never show you their names or addresses.
5. AI processing
Mestra uses an AI model to build and review formats, to answer questions in Ask Mestra, and to help diagnose faults on Mestra screens. Our AI provider is Anthropic, PBC, and the processing happens in the United States. More detail is on our sub-processors page.
For each request we send:
- content from your designs and comments, such as text, layout and images;
- your format and brand settings;
- if an owner allows it, the text of a brief sent from a connected project tool, to fill in the campaign. We don't keep the AI's reply, only the details it helped fill in.
- for Ask Mestra, your conversation, your name, role and organisation's name, the page you are on, and whatever it looks up in your organisation to answer. It can look up only what you can see yourself.
- for a screen fault, the fault's code and how it was handled: what the screen tried, whether it recovered, and how many screens have the same fault. No screen names, screenshots or log files.
What Mestra keeps. We don't store our prompts or the AI's replies after the request finishes, with three exceptions: layout review passes, described below, screen fault diagnoses, kept for up to 90 days, and Ask Mestra conversations, described in section 2. We keep the layout plan of each built size, encrypted, so your team can change it and draw it again in the web app. It is deleted with that size. We keep two things from each build so your team can review, change and export it later in the web app: the layout of each finished size and the images it uses (not your original files). We also keep the AI's review notes on each format. For each layout review pass, we keep the AI's replies and working notes. We use these to investigate and improve layout quality. Only Mestra staff can read them, for that purpose, and each read is logged. A review keeps each round's layouts and images in the same way. The motion brief, chat and versions are kept too, as section 2 describes. Section 9 says how long.
Saved masters. When someone presses Save master in the InDesign, Figma or Canva app, we keep a copy of that master, encrypted. We use a saved master to build sizes and to show it in the web app. Masters that an advertiser saves through a network are kept in the same way. When you press Generate, we also save the master as a new version if it changed. We delete an older version once no kept run uses it. The latest version stays until the master is deleted. Section 9 says how long.
What Anthropic keeps.
- Anthropic deletes API inputs and outputs within 30 days by default.
- Content flagged for a usage-policy breach may be kept for up to 2 years, and classification scores for up to 7 years, or longer where the law requires.
- Under Anthropic's commercial terms, customer content isn't used to train its models.
We don't claim zero data retention at our AI provider.
6. Who we share it with
We share personal information only as this policy describes.
Within your organisation. Members can see each other's names, email addresses and roles, and who started each run. Owners see billing details and usage.
Mestra screens. Owners and editors see their organisation's screens (including each PC's maker, model and serial number), plays, health and events. Owners also see install keys, panel settings and profiles, and can send a screen commands. An API key or connected app can read the screen list, plays and takedowns, within the permissions chosen when it was connected (see "Apps and agents you connect"). Screenshots and log files are for owners and editors only, in the web app. Members with the reviewer role don't see them. Support access can see a screen's health and history but not its screenshots or logs. Nothing about your screens is shared outside Mestra other than with the sub-processors in the table below and with any monitoring destination your organisation connects (below). If an owner turns on install key notices, we email the organisation's owners when an ended install key is tried, when screens join too fast, or when a key may have been read. Windows and its web view runtime are Microsoft's: the PC talks to Microsoft for Windows updates under your organisation's own terms with Microsoft, and Microsoft isn't our sub-processor.
Outside reviewers. A person with a review link sees only the one campaign the link covers, and only the comments and approvals on it. They see the names of people who commented on that campaign, but not your member list, other campaigns, brands or billing.
Screen systems you connect. A screen system you connect is a provider your organisation chooses and uses under its own agreement with that provider. It isn't our sub-processor. When someone in your organisation publishes, we send that system the finished artwork they choose, with the campaign name, brand code, size, start and end dates, times and days, purchase type and the screens it's booked on. The system keeps it under its own terms. If your organisation runs a screen network on Mestra, a request for screen time can also reserve that time in the system, with no artwork, until the request is approved, withdrawn or the reservation runs out. If an owner turns on play reports, depending on the integration we may also create a campaign there for each of your campaigns, with its name and dates, so the system can report plays. Mestra never deletes anything in that system and never changes bookings it didn't make. This also applies to motion: when someone publishes a motion video, we send the video file, with the campaign name, brand, size, length and booking details, as we do for still artwork.
Data feeds you connect. If an owner turns on data feeds, we send the web address they enter to their own feed, with a screen's postcode, city or coordinates filled in when the address asks for them, and with the keys they give us. That feed is your organisation's own service, under its own terms. It isn't our sub-processor. We keep your keys, encrypted, and the feed's last answer for a short time, and delete them when the feed is deleted or data feeds are turned off. None of this is sent to our AI provider.
Campaign map. When someone on a network's portal chooses an area for a campaign, their browser loads the street map from OpenFreeMap. OpenFreeMap sees their IP address and the part of the map they look at. We send it nothing else, and the address they search for is not sent to it.
Monitoring destinations you connect. If an owner adds a monitoring destination, we send it your organisation's screen telemetry: each screen's status, health readings, play counts and events, with its name and site. We keep the destination's address and keys, encrypted, and delete them when the owner deletes the destination or turns screens off. That destination is your organisation's own provider, under its own terms. It isn't our sub-processor.
Project tools you connect. A project tool you connect is a provider your organisation chooses and uses under its own agreement with that provider. It isn't our sub-processor. If an owner allows it, we post short comments on a brief, each with a link to Mestra. They don't contain the brief's text or the AI's replies. Mestra never changes a brief's title, description or fields.
Apps and agents you connect. An AI assistant, agent, automation platform or other app that your organisation connects to Mestra, with an API key or by signing in through it, is a provider your organisation chooses and uses under its own agreement with that provider. It isn't our sub-processor. When it's used, we send it what it asks for, within the permissions chosen when it was connected. That can include members' names on comments and runs, review comments, campaign details and run results. What the app and its provider keep, and how they use it, including for training their models, is governed by your organisation's terms with that provider.
Our sub-processors. These providers process personal information for us to run Mestra:
| Provider | What they do | Where |
|---|---|---|
| Fly.io, Inc. | Runs the Mestra application server (including the service your screens talk to), our own log server and the monitoring service for your screens; operational logs (Fly.io keeps its own copy 7 days; our log server keeps them 90 days) | Server in Sydney, Australia. Log storage location not published: United States or elsewhere. |
| Neon, LLC (part of Databricks, Inc.) | Database: accounts, settings, logos, run records, usage, audit log, reviews, outside reviewers and screens (their details, settings, plays and history) | Sydney, Australia (AWS) |
| Cloudflare, Inc. | Network security and delivery, file storage (R2, including operational log storage and a 1-year log archive, and screen artwork, screenshots and screen log files), delivery of your screens' traffic, website hosting and analytics, sign-up checks (Turnstile), review-link code checks and review files | Global network. File storage uses an Oceania location hint, which Cloudflare describes as best effort, not a guarantee. |
| Anthropic, PBC | AI processing (section 5) | United States |
| Postmark (AC PM LLC) | Sending service emails, including review notices, one-time codes and install key notices | United States |
| Stripe Payments Australia Pty Ltd | Payments, subscriptions, invoices and tax | United States and other countries |
Stripe. We use Stripe Payments Australia Pty Ltd and its affiliates to process subscription payments and to issue and collect invoices for customers on a written contract. For payment processing on our behalf, Stripe acts as our processor (service provider). Stripe also acts as an independent controller for its own purposes, including fraud prevention, regulatory compliance and product improvement, under the Stripe Privacy Policy.
Card payments to a screen network. When a business pays a screen network by card on that network's booking portal, the payment is made to the network's own Stripe account, under the network's own agreement with Stripe. For those payments Stripe acts for the network, not for Mestra. Card details are entered only on Stripe's pages and never reach Mestra. From Stripe we receive each payment's status, amount, fees and references, which we use to issue the network's receipts, tax invoices and credit notes and its monthly statement.
The current list, with more detail, is at withmestra.com/trust/subprocessors. We give at least 30 days' notice before adding or replacing a sub-processor that handles customer data. To be told about changes, email privacy@withmestra.com.
Mailbox provider. Emails you send to our support, privacy and security addresses are delivered to our Microsoft 365 mailbox, which stores mail in Australia.
Others, only when needed.
- Professional advisers, such as lawyers and accountants, who must keep it confidential.
- Our AI provider (Anthropic), if we need to investigate possible misuse under its usage policy, sharing only what that investigation needs.
- Police, regulators or courts, where the law requires or allows it.
- A buyer or successor of all or part of our business, who must handle it under this policy.
7. Overseas disclosure
Some personal information is sent to, or stored by, providers outside Australia:
| Country | Who | What |
|---|---|---|
| United States | Anthropic | Your content during AI processing (section 5) |
| United States | Postmark | Your name and email address, and the content of service emails, including outside reviewers' email addresses and one-time codes |
| United States and other countries | Stripe, and its affiliates and sub-processors | Billing contact details, tax ID and card details |
| United States and other countries | Cloudflare | Traffic as it passes through Cloudflare's global network |
| United States or elsewhere | Fly.io | Operational logs |
| Wherever its data partners operate | Our map data provider's data partners | The text typed into place search, with account details removed |
Our service and database run in Sydney, and stored files use an Oceania location hint. We choose providers with published security practices and data processing terms, and we take reasonable steps to make sure they handle personal information consistently with the APPs.
8. Storage and security
We take reasonable steps to protect personal information from misuse, interference, loss, and unauthorised access, change or disclosure. These include:
- HTTPS for all traffic, and encrypted connections between our server and its providers;
- library files encrypted by us before they're stored, with a separate key for each organisation;
- screenshots and log files from screens encrypted by us before they're stored, with your organisation's own key, shown only in the web app and never through the API;
- screens' own keys and install keys stored only as hashes, and screens that join with an install key held inert until an owner names them.
- storing only hashes of sign-in links, sessions and app tokens;
- every request limited to one organisation, with owner, editor and reviewer roles;
- multi-factor authentication on our hosting and infrastructure accounts;
- support access limited to Mestra staff, time-limited, with a recorded reason, and visible to owners on the Activity page;
- an audit log that can't be edited.
A review link carries a random token, and we store only its hash. A link expires after 30 days unless the owner or editor who creates it sets a longer period (up to 90 days), can be revoked at any time, and covers one campaign. Link pages aren't indexed by search engines. Downloads are off unless they're turned on for that link. Review files are encrypted by us before they're stored.
More detail is on our trust site, withmestra.com/trust. Our security policies were adopted on 4 October 2026 and are available on request.
9. How long we keep it
| Information | How long |
|---|---|
| Working data and plans sent by the apps | Not stored after the request finishes, except saved masters, built layouts, images, AI review notes, layout review passes and screen fault diagnoses below. Anthropic's retention is in section 5. |
| Saved masters | Kept until someone deletes the master or its brand, or your organisation's content is deleted. For a network's advertiser, until that advertiser is deleted from the network. Encrypted. Counts toward your cloud storage. |
| Master versions | A new version is saved when a master has changed since the last Generate. An older version is deleted once no kept run uses it. The latest version stays until the master is deleted. Encrypted. |
| AI review notes | Kept with their run or review for the library retention period, then deleted. If an owner shortens the retention period, run notes are deleted straight away and review notes within the hour. Deleting the run, review or brand, or closing the account, deletes them too. Encrypted, visible to people in your organisation, and never shown to outside reviewers. |
| Layout review passes (the AI's replies and working notes) | Kept for the same period as AI review notes, then deleted, and deleted in the same way if an owner shortens the retention period, or the run, review or brand is deleted or the account is closed. Encrypted with your organisation's own key. Not shown in the apps: only Mestra staff can read them, to investigate layout quality, and each read is logged. |
| Ask Mestra conversations | The library retention period after the conversation was last used, then deleted. Deleted sooner if you delete the conversation, or your organisation's content is deleted. Encrypted, and shown only to the person who had the conversation. |
| Screen fault diagnoses | Up to 90 days, then deleted. |
| Ask Mestra notes | What Ask Mestra keeps so it knows your organisation next time: short notes saved for the organisation (visible to the organisation's owners, who can edit and remove them) or for one person (visible only to that person, and removed when they leave the organisation). Kept until they are removed, or the organisation is deleted. Encrypted. Notes can't hold contact details, card numbers or secrets. |
| Ask Mestra documents (files an owner adds) | The file and the text read from it: kept until an owner removes it, or the organisation is deleted. Encrypted, shown only to the organisation's owners, and read by Ask Mestra for people in that organisation. The text of a document is sent to our AI provider when it is read and when Ask Mestra uses it to answer. |
| Built layouts and images | Kept with their run for the library retention period, then deleted. Deleted straight away if an owner shortens the retention period, or deletes the run, brand or organisation. Encrypted. |
| Reviews (rounds, snapshots, images, comments, pins, approvals) | The library retention period after the review's last activity (a round, comment or approval). The library retention period is 90 days unless an owner chooses 30 days or 1 year in the app, or Keep everything, which has no time limit. Deleted with the campaign or organisation. |
| Review exports | Deleted 7 days after they're made, whatever the library retention. Encrypted. |
| Outside reviewers (email address, name, comments) and review links | Kept with the review. A link expires after 30 days by default (up to 90) and can be revoked sooner. One-time codes expire after 10 minutes. |
| Fonts uploaded to a brand | Until deleted, or until their brand or organisation is deleted |
| Font licence records (who confirmed a font's licence, when, and a fingerprint of the file) | 2 years after the font is removed, including after the organisation is deleted |
| Screen telemetry (health readings, play counts and events from Mestra screens) | Health readings and play counts: 90 days. Events: searchable for 30 days, then kept in an archive for 1 year. Deleted when your organisation turns screens off or leaves. |
| Monitoring destinations (address and settings) | Until the owner deletes the destination or your organisation turns screens off. Encrypted. |
| Monitoring destination keys | Deleted with the destination, or when your organisation turns screens off. Encrypted. |
| Screenshots from Mestra screens (asked for by an owner) | 30 days after we receive them, then deleted. Encrypted. Not counted toward your cloud storage. |
| Automatic screenshots (if an owner turns them on) | 7 days after we receive them, then deleted. Encrypted. |
| Screen log files (sent when an owner asks) | 30 days after we receive them, then deleted. Encrypted. |
| Screen history (events such as "came online", and commands sent, with the user who sent them) | 90 days, then deleted. |
| A screen's latest health report and status | Only the latest is kept. It is replaced by the next report. |
| Test panel results (messages to a panel and its replies) | Only the latest run on each screen, replaced by the next. Deleted with the screen. |
| Pairing codes and details of a screen waiting to join | The code is valid for 10 minutes. The record is deleted when the screen collects its key, or when the next screen starts pairing after the code has expired. |
| Screens (name, site, hardware details, serial number, settings and last report) | Until your organisation is deleted. Removing a screen or switching screens off keeps its record (name, site, hardware details, serial number) as history and forgets its keys; screenshots, logs and health reports are deleted as above; settings and the last report go with the screen's keys. |
| Install keys (name, hint, who made it, counts) | Until an owner turns screens off or the organisation is deleted. A revoked key's record is kept until then. The key itself is kept only as a hash. |
| Play records from Mestra screens | Until your organisation is deleted. Removing a screen or switching screens off does not delete its past plays. |
| Bookings, artwork and takedown requests for Mestra screens | Bookings and takedown requests: until your organisation is deleted. Artwork files: until screens are switched off; the record of each file (size, type, fingerprint) stays. |
| Panel-off records (Mestra screens) | Times a screen's panel was off while a booking was due: until the organisation is deleted. Never counted as plays. |
| Panel settings and panel profiles | Settings: with the screen. Profiles an owner saves: every version is kept, even after an owner deletes the profile, until screens are switched off or the organisation is deleted. |
| On the PC: device log | The latest 5 files of up to 2 MB each, on the PC only. The oldest is overwritten. |
| On the PC: copy of the previous automatic sign-in | On the PC only, until the Player is uninstalled. The uninstaller puts it back and deletes the copy. |
| Account (name, email) | While you're a member of an organisation. Removing you from an organisation doesn't delete your account. Ask us to delete it, or it's deleted when you no longer belong to any organisation and the last one is deleted. |
| Sessions | Up to 30 days of use. Expired or revoked sessions are deleted 30 days later. |
| Sign-in links and app sign-in codes | Deleted 24 hours after use or expiry |
| App sign-ins | Expire after 90 days without use |
| Approximate location of a design-app sign-in | Up to 7 days, then deleted. A copy stays in the security email we sent you. |
| Organisation settings, campaign copy and logos | Until you delete them, or your organisation is deleted |
| Library files | The library retention period: 90 days unless an owner chooses 30 days or 1 year. Then deleted. An owner can choose Keep everything instead: files are then kept until you delete them or the account is closed. |
| Accounting connection | Until an owner disconnects it or turns it off, then deleted straight away. The record of what was posted: until the organisation is deleted. |
| Motion briefs, chat messages and versions | Kept for the library retention period, then deleted. Deleted straight away if the motion is deleted. |
| Motion videos and posters | As for motion briefs. A video sent to a review is kept for as long as that review. |
| Run records and usage ledger | For the life of your organisation. After deletion, the usage and billing ledgers are kept only as anonymous counts. |
| Screen-system connection (encrypted token, settings, screen links and sizes) | Encrypted token and settings: until an owner disconnects it or turns it off, or the organisation is deleted. Then deleted straight away. Screen links and sizes: until the organisation is deleted. Disconnecting doesn't cancel the token in the screen system itself: revoke it there too. |
| Play records from a screen system | Until the organisation is deleted. Turning play reports off, disconnecting or turning the system off stops new records but keeps the ones we already have. |
| Details read from a screen system | Names, time zones, locations, tags, players, sizes and identifiers: until the organisation is deleted. We note when each was last seen. |
| Data feeds (address, encrypted keys, the fields you choose) | Until an owner deletes the feed or turns data feeds off, or the organisation is deleted. Then they're deleted straight away. The feed's last answer is kept in memory only, for a short time. |
| Which variant each booking got (dynamic variants) | For each choice we keep the campaign, the table version, the variant chosen, the booking and size, and the reasons, which can name a value that decided it, such as a city or a time. Kept for the period an owner chooses in Settings: 30 days, 90 days, 1 year or until deleted (the default). Deleted by themselves when older, and deleted if the organisation is deleted. |
| Publish records | Until the organisation is deleted. The audit log keeps identifiers and counts of publishing for 1 year, as for other changes. |
| Project-tool connection (encrypted token and settings) | Until an owner disconnects it or turns it off, or the organisation is deleted. Then it's deleted straight away. Disconnecting doesn't cancel Mestra's access in the tool itself: remove it there too. |
| Briefs received (link, title, details filled in, notes) | Until the organisation is deleted. Campaigns made from briefs keep their link to the brief. |
| Comments waiting to be posted to a project tool | Deleted 30 days after they're posted or give up. Deleted straight away if comments are turned off, the tool is disconnected, or the organisation is deleted. |
| Reserved screen time | Until the organisation is deleted. |
| Business contacts (networks) | Until the network is deleted or the person asks us to remove them; taking a contact off a list keeps it. |
| Revoked or expired API keys | The record is kept, without the key, as part of the audit log, for the audit log's retention (1 year) |
| Connected apps | Deleted when someone disconnects the app, when the member who connected it leaves, or when an owner turns the API off |
| Unused app registrations | Deleted after 30 days |
| App sign-in requests | Expire after 20 minutes |
| Audit log | 1 year |
| Operational logs | 90 days on our own log server, plus a 1-year archive in Cloudflare R2. Fly.io keeps its own copy for 7 days |
| Sign-up domain | Until your organisation is deleted |
| Trial hashes (domain, email, card, network) | Kept indefinitely, including after your organisation is deleted, to enforce one trial each. They don't show the underlying details in readable form. |
| Stripe event records | 30 days |
| Billing records at Stripe (customer and invoices) | Kept by Stripe after your organisation is deleted, for Australian tax records |
| Database backups | Up to 7 days after deletion |
| Website enquiries | 12 months, or until the enquirer becomes a customer |
| Support emails | 2 years after the last contact |
When an organisation stops paying. If a trial ends without a subscription, a subscription ends, a card-paid invoice is 14 days unpaid, or a contract invoice is unpaid 30 days after its due date (Terms, clause 14.1), the organisation becomes read-only. We keep its data for 60 days, and email its owners about 7 days before we delete it. Then we delete its brands, campaigns, formats, settings, logos, run records, library files, invites, app sign-ins and memberships, and any member who no longer belongs to an organisation.
10. Access and correction
You can ask to see the personal information we hold about you, or ask us to correct it, by emailing privacy@withmestra.com.
- You can update your own name in the app. Owners can change members' roles.
- We'll check your identity before we act.
- We don't charge for a request.
- We'll respond within a reasonable time. If we refuse, we'll tell you why in writing, unless that would be unreasonable, and how to complain.
11. Deletion and export
Deleting.
- Owners and editors can delete settings, logos and library files in the app at any time.
- Owners can remove members and revoke app sign-ins.
- Owners can revoke any review link, and whoever created a link can revoke it, at any time. Deleting a campaign or an organisation deletes its reviews, comments and outside reviewers' details, except audit log entries, which we keep for 1 year. Deleting a brand or an organisation deletes the fonts uploaded to that brand.
- To delete your own account, or your whole organisation sooner than the 60-day process in section 9, email privacy@withmestra.com. We'll confirm the request with an owner before deleting an organisation.
- We may keep information we need for tax, legal or security reasons, as section 9 describes.
Exporting.
- Your editable outputs stay in your design tool and folders.
- Library files can be downloaded one at a time or a run at a time as a zip.
- Files you apply or export from a review can be downloaded in the app.
- Brand, format and campaign settings can be read in the app or through the API.
- For a copy of your account or audit records, email privacy@withmestra.com.
12. Marketing
We only send emails about your account and the service. We don't send marketing emails unless you've opted in, and every marketing email will have an unsubscribe link.
13. Children
Mestra is a business service. It isn't directed at children, and users must be at least 18. We don't knowingly collect personal information from children. If you think we have, email privacy@withmestra.com and we'll delete it.
14. Complaints
If you have a complaint about how we've handled your personal information:
- Tell us first. Email privacy@withmestra.com with the details. We'll acknowledge it, look into it, and reply in writing within a reasonable time.
- If you're not satisfied, you can also contact the Office of the Australian Information Commissioner (OAIC): oaic.gov.au, phone 1300 363 992.
15. Data breaches
We treat the Notifiable Data Breaches scheme in the Privacy Act as applying to us. If we suspect a data breach:
- we assess it promptly, within 30 days at most;
- if it's likely to cause serious harm, we notify the OAIC and the people affected as soon as practicable;
- we tell affected customers' owners without undue delay, and aim to do so within 72 hours of confirming an incident that affects their data, whether or not the law requires it;
- we post updates at status.withmestra.com where customers are affected.
To report a security issue, email security@withmestra.com.
16. Changes to this policy
We may update this policy, for example when our service or providers change. We'll post the new version here with a new date. If a change materially affects how we handle your personal information, we'll email organisation owners before it takes effect.
17. Contact
Mestra Labs Pty Ltd (ABN 73 702 936 356), Sydney NSW, Australia.
- Privacy: privacy@withmestra.com
- Security: security@withmestra.com
- Support: support@withmestra.com
Our service emails come from an address that doesn't accept replies, so please use the addresses above.
