Mason

Policies · Last updated 16 November 2026

Privacy Policy

What we collect about you when you visit masondata.ai, sign in to Mason Cloud or use the mason command with it; why we collect it; who we share it with; how long we keep it; and what you can ask of us.

1. Who we are

Mason is made by TMD Technology Limited, trading as Embeddable (“we”, “us”, “our”), a company registered in England and Wales under number 13856879, whose registered office is at International House, 142 Cromwell Road, London SW7 4EF, United Kingdom. We are the controller of the personal data this policy describes.

Our contact for anything to do with personal data is Henry Marshall, COO: harry@embeddable.com.

2. What this policy covers

This policy applies to:

It does not apply to:

3. Your data, and the data you sync

When you create a replica, Mason copies the tables and columns you choose from your Postgres database onto a machine we run for you, and answers queries over that copy. That copy, the results it serves, the log of the queries it answers and the error records that come from it are Customer Data. You decide what goes into it. We process it only on your instructions, as your processor, under our Data Processing Addendum (the “DPA”). This policy does not govern Customer Data, except that sections 7 and 8 say where it lives and how long it is kept, because those facts matter to you.

Everything else we hold about you is account data: your account, your sign-ins, the way your replicas are configured, your messages to us. We decide how that is processed, so we are its controller, and this policy is about it.

4. What we collect

When you sign up and sign in

We do not receive or store a password. WorkOS runs the sign-in and sends us the profile of who signed in; we keep only the email address and the fact that it was verified.

When you sign in from the command line

mason login asks the Service for a code and sends the name of your machine. We record that name, the IP address the request came from (to limit how many codes one address may ask for), and when the code was approved. The login token it gives you is kept on your machine, in ~/.config/mason/credentials.json; we keep only a hash of it. A login lasts 30 days, or until you run mason logout. Every request the command makes to the Service identifies itself as mason-cli with its version.

When you create and run a replica

When you open a replica’s page

A replica’s own page opens through the Service under a one-use ticket that becomes a page key. We keep hashes of both, when the page was opened and when it was last used. The page’s content comes from your replica and is relayed, not stored.

When a page’s script fails

If a script on one of the app’s pages fails in your browser, the browser reports the failure to us: the page’s route, which of our files it was in, the line, and the error’s name. Never the error’s message, nor anything you typed. The report goes into the control plane’s logs. We limit these reports per address, in memory, and the address is not stored.

When you contact us

The contact page in the Service emails your message to us, with your email address as the reply address and a note of the page you came from. We keep the message in our mailbox. The Service itself keeps only a keyed digest of the text for a day, so that one message is never sent twice. If you email us directly, we keep that email too.

Incident and diagnostic records

When a sync or a statement on your replica fails, or a statement is slow, your replica’s machine reports it to us. We keep these reports for 14 days in a log group of their own, encrypted with its own key: the statement with its values replaced by placeholders, Mason’s error message (which can include a row’s values), a slow statement’s plan, each synced table’s columns and types, and the structure of each deployed project. Only a named operator’s AWS sign-in and our diagnostics workflow can decrypt them, and each decryption is recorded. These records can contain Customer Data, so the DPA governs them; they are described here so that you know they exist.

Service logs, metrics and internal reports

When you visit masondata.ai

The website is a set of static pages served by Vercel. We run no analytics on it and set no cookies. Vercel, as our host, sees the usual request data (your IP address, browser and the page requested) and keeps request logs for a short time. The home page serves its own fonts. The page at /apply/ and the test pages under /lp/ load fonts from Google Fonts, so your browser sends Google the request. The /apply/ page also links to an application form hosted by Typeform; what you enter there is governed by Typeform’s privacy policy and comes to us as a submission.

GitHub

If you open an issue, discussion or pull request on github.com/embeddable-hq/mason-data, GitHub’s terms and privacy policy govern it, and what you post there is public.

5. Why we use it, and on what basis

PurposeWhat we useLegal basis
To provide the Service: sign you in, create and run your replicas, run your deploys and commands, answer the mason commandAccount, sign-in and login records, replica configuration, check records, deploy state, tokensPerformance of our contract with you
To keep the Service secure and prevent abuse: limit sign-in codes and check runs per address, keep the audit log, enforce address allowlists and sign-up limits, raise alarmsIP addresses, device names, check records, audit log, metricsOur legitimate interest in running a secure service
To find and fix faults, and to support youIncident and diagnostic records, service logs, your messages to usPerformance of our contract; our legitimate interest in a reliable service
To understand how the Service is usedCounts per organisation, the daily summaryOur legitimate interest in improving the Service
To tell you things you need to know: changes to our terms, prices or subprocessors, the end of a trial, an incident that affects youYour email addressPerformance of our contract; our legal obligations
To comply with the law and protect our rightsWhatever the obligation or claim requiresLegal obligation; legitimate interests

We may email you about Mason itself. We do not send advertising, and we never sell personal data or share it for advertising.

6. Who we share it with

These providers process account data for us, on our instructions:

Those of them that process Customer Data are listed, with what each receives, at masondata.ai/policies/subprocessors, and the DPA says how we tell you of a change.

We may also disclose personal data where the law requires it, to establish or defend legal claims, to protect the security of the Service or the safety of any person, or, if our business or the Service is sold or merged, to the buyer, who takes on this policy’s obligations.

7. Where it is processed

We are in the United Kingdom. The Service runs in Amazon Web Services’ eu-west-1 region in Ireland and nowhere else: your replica, the control plane, its database, logs and secrets are all there. Customer Data leaves that region only as the subprocessor list says: a replica’s incident records, read on a GitHub-hosted machine or encrypted to a Claude session, both in the United States, and only when we are investigating a fault.

Account data reaches WorkOS in the United States when you sign in, and our own mailboxes when we email you or you email us.

Where personal data leaves the United Kingdom or the European Economic Area, we rely on an adequacy decision (the EEA and the United Kingdom recognise each other) or, for providers in the United States, on the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, or the UK Extension to the EU–US Data Privacy Framework where the provider is certified under it.

8. How long we keep it

WhatKept
Your account: email address, organisation name, sign-in records, replica records, audit logUntil you ask us to close your account. Within 30 days of that we replace what identifies you in our records, as section 11 describes.
Session cookie12 hours, or until you sign out
Command-line logins (device name, hashed token)30 days, or until you sign out
Sign-in codes from the command line, with the requesting IP addressAn hour or more after the code expires: expired codes are cleared on the next sign-in request
CI tokens (name, scopes, hashed token)Until they expire or you revoke them
Records of our checks of your database (host address, port, database and user name, outcome)30 days; a failed check, one day
Messages you send from the contact pageIn our mailbox until your account is erased; the Service’s digest of each, one day
The daily summary email to our teamIn our mailbox; deleted when your account is erased
Control plane and check-function logs, naming organisations and replicasOne month
Usage counts by organisation (metrics)15 months, which is how long AWS keeps metrics
Backups of the control plane’s databaseOne day
Website request logs at VercelA short period set by Vercel
Customer Data (governed by the DPA)
Your synced data on a replicaUntil you delete the replica. Deletion destroys the machine, its encrypted volume and its secret. There are no backups or snapshots: a replica that is lost is recreated and synced again.
Mason’s own log of the queries your replica answered (the SQL, the user, timing, rows, and the plan of a slow statement)7 days, on the replica’s volume, so it goes with the replica
Incident and diagnostic records (section 4)14 days, which can outlive the replica by up to 14 days

9. Cookies

app.masondata.ai sets two cookies, both ours, both marked HttpOnly and Secure, and both needed for the Service to work:

masondata.ai sets no cookies. Neither site uses analytics, advertising or third-party cookies, so there is nothing to consent to and no cookie banner. We do not track you across other sites, so there is nothing for a “Do Not Track” signal to change.

10. Security

Each replica runs on a machine of its own, in a private network, reachable only through its own load balancer, with TLS and a password on every connection and only from the addresses you allow. Your database’s credentials are held in AWS Secrets Manager, readable only by your replica’s machine. Tokens are stored as hashes, our audit log refuses to store anything shaped like a secret, and only our continuous-integration system deploys the Service, under short-lived credentials. The DPA’s Exhibit B describes these measures in full.

If we learn of a breach of security affecting your personal data, we will tell you without undue delay and, where feasible, within 72 hours of becoming aware of it, with what we know and what we are doing. To report a vulnerability, see SECURITY.md.

11. Your rights

Under the UK GDPR and, where it applies, the EU GDPR, you can ask us to:

Email harry@embeddable.com and we will answer within a month. You can also complain to the Information Commissioner’s Office at ico.org.uk, or to the data protection authority where you live.

Closing your account. Delete your replicas first, so that each one’s replication slot is dropped on your database and its machine, volume and secret are destroyed. Then ask us to close the account. Within 30 days we replace your email address and your organisation’s name in our records with placeholders, delete the records of our checks of your database and the messages that hold your email, and keep the audit log with those identifiers replaced. Database backups overwrite within a day, and incident records expire within 14 days.

If your data is in someone else’s replica. If you are a customer or user of an organisation that uses the Service, that organisation decides what it syncs, and your request should go to it. If you contact us instead, we will pass your request to that organisation and help it respond.

12. Business use only

The Service is for organisations. You sign up with a work email address, on behalf of the organisation whose database you connect, and you must be at least 18. We do not knowingly collect personal data from children.

13. Changes to this policy

When we change this policy we post the new version here with its date. If a change materially affects how we use your personal data, we email account holders at least 30 days before it takes effect, unless the law requires the change sooner.

14. How to contact us

Henry Marshall, COO
TMD Technology Limited, trading as Embeddable
International House, 142 Cromwell Road, London SW7 4EF, United Kingdom
harry@embeddable.com