Privacy Policy

Last updated 19 August 2026

Mayah records your meetings. That is an unusual amount of trust to ask for, so this policy is written to be specific rather than reassuring. Where something might read two ways, we have chosen the reading that is less flattering to us.

The short version

• Raw audio and screen images never leave your Mac. They are captured, transcribed and stored locally, and are never uploaded to Mayah.
• Transcripts and derived data do reach Mayah’s servers on the paid tier, and Mayah staff can read them. See below — this is the part most people assume works the other way.
• Mayah is private from your employer, not from Mayah. We do not integrate with employer admin consoles, we do not report your usage to anyone, and nothing about Mayah appears in your company’s device or SaaS management tooling.
• AI processing uses your own API key. Your prompts go directly from your Mac to the AI provider you configured. They do not pass through us.

What stays on your device

Meeting audio, screen captures, and your connected-service credentials are stored on your Mac — audio and images on local disk, credentials in the macOS keychain via Electron’s safeStorage. None of these are transmitted to Mayah at any time, on any tier.

What Mayah can see

On the paid tier, your meeting transcripts and everything derived from them — summaries, cards, extracted entities, corrections, and the memory Mayah builds about your work — are synced to our servers so that features like the mobile app can answer questions when your laptop is closed.

This data is stored in readable form. It is encrypted in transit and at rest, but we hold the keys, and Mayah engineers can read it. We do this deliberately: diagnosing why an answer was wrong requires seeing the material it was drawn from. We considered end-to-end encryption and chose not to build it, because it would prevent the product from being debugged and improved. If that trade is not acceptable to you, Mayah is not the right tool, and we would rather tell you here than bury it.

What we do with it

We use your content to operate the service, to diagnose faults, and to improve Mayah’s accuracy. During the current research preview, content may be used to evaluate and improve the system in text form only, after automated substitution of names and identifiers. Raw audio is never used for this.

We do not sell your data, we do not use it for advertising, and we do not share it with your employer.

Your controls

• Delete any individual meeting and everything derived from it.
• Turn off cloud sync entirely and run Mayah fully locally.
• Request a copy of what we hold about you, or ask us to delete all of it, by emailing hello@mayah.app.

Recording consent is your responsibility

Recording laws differ by state and country, and in many places every participant must consent before a conversation is recorded. Mayah gives you the technical ability to record; it does not give you the legal right to. You are responsible for obtaining whatever consent applies to your meetings, and for complying with your employer’s own policies.

Who else is involved

We use Stripe for payments (Stripe receives your billing details; we never see your full card number), Vercel for hosting, and Neon for our database. Your AI provider receives your prompts directly under your own API key and their terms, not ours.

Where your data lives

Mayah is operated from Australia by BUI Group Pty Ltd. Our hosting and database providers may store data outside Australia, including in the United States.

Complaints

Email hello@mayah.app and we will respond within 30 days. If you are not satisfied with our response you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.