Privacy notice
Last updated 15 November 2026
This notice may change; the date above says when it last did.
This notice covers this website, the Meles waitlist, and the Meles product for the people who sign in to it. If you answered a survey or saw an announcement inside another company's product, that company decides what happens to your data, and Meles processes it for them: see If you use one of our customers' products.
Who we are
Meles is run by Meles Labs Pty Ltd (ACN 703 542 483), a company registered in Australia, which is the controller of the personal data described here, except where this notice says Meles processes it for a customer. To reach it about your data, email privacy@meles.app.
The website and the waitlist
What we collect
If you joined the waitlist, whose form closed on 31 October 2026, what you gave us (deleted 1 November 2026):
- your email address;
- your two answers: what you use today, and what you want first;
- where you came from: the campaign tags in the link you followed (the
utm_parameters), the address of the page that linked to us without its query, and the page you signed up on; - when you confirmed.
This site sets no cookies and stores nothing in your browser. To count visits, every page loads Cloudflare Web Analytics, which reads your browser's details and how fast the page loads and answers your clicks, never what you type, and sends them, with the page's address and referrer, to Cloudflare. It stores nothing to recognise you by, and doesn't run if your browser sends Global Privacy Control or Do Not Track. Our emails don't track you.
Why, and on what basis
- Until 31 October 2026, to send the confirmation email, and to decide what to build first from your answers. One note followed, in November 2026, to say Meles had opened as a free beta instead. The basis was your consent, which you gave by confirming, and could withdraw at any time.
- Until 31 October 2026, to stop the form being abused. The server that took sign-ups kept your IP address in memory for ten minutes to limit repeated attempts, and never wrote it to disk. The basis was our legitimate interest in keeping the service working and not emailing people who didn't ask.
- To know which pages are read and how fast they load, Cloudflare Web Analytics counts page views. The basis is our legitimate interest in improving the site. To object, turn on Global Privacy Control or Do Not Track.
We don't sell your data, share it for advertising, or use it for anything else.
The Meles dashboard
What we collect
When you sign in to Meles, or someone invites you to their organisation:
- your name, email address and sign-in sessions, and your authenticator app's key if you turn on two-factor sign-in, which WorkOS holds for us; if you sign in with Google, Google tells WorkOS who you are;
- your organisations, your role and the terms you accepted in each, and your last sign-in;
- for one you made, the campaign tags and site our Start free link carried, kept in your tab until then;
- if invited, your email address on the invitation, until 30 days after it's accepted, revoked or lapses;
- during the beta, if we've admitted you by name, your email address on our list of those people, which we keep at GitHub and remove at launch or when you ask;
- the API keys you make: their names, scopes and when each was last used, never the keys themselves;
- how you use the dashboard, through Meles itself: our internal ID number for you, your role, your organisation's plan and age, the dashboard pages you open, which of our surveys and announcements you were shown, and your answers if you answer one. It runs in Meles's cookieless mode, so it keeps its ID in your browser tab only; the network that serves its script may set Cloudflare's bot-management cookie,
__cf_bm; and our servers keep your IP address in memory, with that tab's ID, until about an hour after your last request, to tell people from scripts, never writing it to disk or a log; - if you pay, the billing details you give Stripe, which Stripe holds; Meles keeps only Stripe's reference.
Why, and on what basis
- To give you and your organisation the service you signed up for: sign-in, your organisation's members, keys and billing, and, if you're an Owner, the notices the terms and the data processing agreement promise you by email; and to see if an account or organisation is unused. The basis is our contract with you or your organisation.
- To send an invitation someone asked us to send, and to exempt people we admitted by name from the beta's cap on new organisations. The basis is our legitimate interest in running the beta, and an inviter's in adding members.
- To learn how the dashboard is used and ask you about it there, with Meles, keep scripts out of those figures, and count which links bring new organisations. The basis is our legitimate interest in improving the service.
- To keep invoices as tax law requires. The basis is that legal obligation.
If you use one of our customers' products
Our customers put Meles in their products to ask their users questions and show them announcements. What Meles holds about you there, such as the ID the product gave you, what you did in it, your answers and, until about an hour after your last visit, your IP address, which tells people from scripts, it holds for that company, which is the controller: Meles is its processor, under our data processing agreement. To see, correct or delete it, ask the company whose product it was; if you write to us, we'll tell you who to ask, and we act on their instruction.
Who processes it for us
Each of these vendors receives some of the data above, and works under its own data processing terms.
DigitalOcean
- What for
- Hosting: our servers, database, backups and file storage, and the network that delivers our script and your campaigns' settings
- What it receives
- Everything Meles holds
- Where
- The United States (New York)
- Transfers from the EEA and the UK
- Certified to the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Framework, with the EU standard contractual clauses and the UK Addendum as the fallback
- Its data processing terms
- DigitalOcean's DPA
Sentry
- What for
- Error reports from our servers and dashboard, performance traces from our servers, and uptime checks
- What it receives
- Our internal ID numbers in error reports and traces: never a name, an email address or an answer
- Where
- The United States
- Transfers from the EEA and the UK
- Certified to the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Framework, with the EU standard contractual clauses and the UK Addendum as the fallback
- Its data processing terms
- Sentry's DPA
Resend
- What for
- Sends our email: invitations to join an organisation, notices to an organisation's owners and admins, and a warning before we delete an unused account
- What it receives
- Invitees', owners', admins' and unused accounts' email addresses, and the emails we send them, a waitlist sign-up's confirmation among them until 30 November 2026
- Where
- The United States
- Transfers from the EEA and the UK
- The EU standard contractual clauses and the UK Addendum; certified to the EU-U.S. Data Privacy Framework
- Its data processing terms
- Resend's DPA
Cloudflare
- What for
- Our domain's DNS, our status page, and counting visits to this site
- What it receives
- The details of each visit to our status page, which Cloudflare logs for 3 days; and, for each page of this site you view, its address and the site that linked to it, both without their query, your browser, operating system, device type and country, how fast the page loaded and answered your clicks and typing, with which part of the page it was but never what you typed, and an ID made up for that one page view, kept for six months. Cloudflare receives your IP address with each, and says it doesn't use it to fingerprint you
- Where
- Cloudflare's network of data centres, worldwide
- Transfers from the EEA and the UK
- Certified to the EU-U.S. Data Privacy Framework and its UK Extension; the EU standard contractual clauses and the UK Addendum for any other transfer
- Its data processing terms
- Cloudflare's DPA
Google
- What for
- Our mailbox: email you send to hello@, privacy@ or support@meles.app, our replies, the one note we sent the waitlist's sign-ups, and the notices we send an organisation's Owners
- What it receives
- Your email address and name as your email shows them, and what you write; an Owner's email address, for those notices
- Where
- Google's data centres, worldwide
- Transfers from the EEA and the UK
- Certified to the EU-U.S. Data Privacy Framework and its UK Extension, with standard contractual clauses as the fallback
- Its data processing terms
- Google's DPA
WorkOS
- What for
- Dashboard sign-in
- What it receives
- Your team's names, email addresses and sign-in sessions, and the authenticator-app key of anyone who turns on two-factor sign-in
- Where
- The United States
- Transfers from the EEA and the UK
- The EU standard contractual clauses and the UK Addendum
- Its data processing terms
- WorkOS's DPA
GitHub
- What for
- Holds the email addresses admitted to the private beta by name
- What it receives
- Those email addresses
- Where
- The United States, among other places
- Transfers from the EEA and the UK
- Certified to the EU-U.S. Data Privacy Framework; the EU standard contractual clauses
- Its data processing terms
- GitHub's DPA
Stripe
- What for
- Billing: checkout, subscriptions and invoices
- What it receives
- Your billing contact's details and payment method
- Where
- The United States, and Stripe's affiliates and sub-processors elsewhere
- Transfers from the EEA and the UK
- Certified to the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Framework, with the EU standard contractual clauses and the UK Addendum as the fallback
- Its data processing terms
- Stripe's DPA
Grafana Labs
- What for
- Monitoring: our servers' logs, metrics and performance traces, kept for 14 days, and the alerts on them
- What it receives
- Our internal ID numbers in log lines and traces: never a name, an email address or an answer
- Where
- The United States
- Transfers from the EEA and the UK
- Certified to the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Framework
- Its data processing terms
- Grafana Labs's DPA
Our trust page has the same list, with how we protect the data and how we'd tell you about a breach.
How long we keep it
- A sign-up you never confirmed was never kept: the confirmation link carried your details, encrypted, and no longer works.
- After you confirmed, until we deleted the whole list, with the record of anyone who unsubscribed, on 1 November 2026. Resend keeps the confirmation email it sent you 30 days, so none is left after 30 November 2026.
- Before then, we deleted any sign-up on request, with the record that they had opted out.
- The pages you view, counted by Cloudflare: six months, and after 7 days only a sample of about one in ten.
- Mail to hello@, privacy@ or support@meles.app (your address, name and words), used only to answer you, or tell you when there's room in the beta if you ask, our replies, the one note we sent the waitlist, and the notices we send Owners: until no longer needed or you ask us to delete it; Google, our mail host, then erases it in 180 days.
- Your dashboard account, until you ask us to delete it, or two years after you last sign in or an API key you made is used, a month after we email you (an Owner's waits until they own no organisation). Backups expire in 7 days.
- Our servers' logs record what happened, with our own internal ID numbers and never your name, email address or anything you told us. Grafana Labs, our monitoring provider, keeps them 14 days in the United States; our servers keep them until our next release, and never more than about 30 MB per server.
- Error reports and traces, with only those internal ID numbers: 30 days at Sentry, 14 at Grafana Labs.
- The dashboard pages you open and the surveys you were shown, 180 days; your ID number, role, plan and organisation age, and your answers, until you ask us to delete them.
Your rights
You can ask for a copy of your data, have it corrected or deleted, restrict or object to how we use it, receive it in a portable form, or withdraw your consent, which doesn't undo what we did before. To do any of these, email privacy@meles.app and we'll reply within a month.
A dashboard account needs an email address to sign in with, making an organisation needs its terms accepted, and paying needs the billing details Stripe asks for: without them we can't provide that part of the service. We make no decisions about you based solely on automated processing that have legal or similarly significant effects (GDPR Article 22). We run Meles from Australia, which has no EU adequacy decision: we, the controller, are there, and reach your data from there, while the vendors above store it.
You can also complain to your data protection authority: in the UK, the Information Commissioner's Office; in the EU, the authority in your country; in Australia, the Office of the Australian Information Commissioner.
Changes
If this notice changes, the date at the top changes with it, and we'll tell the people who use Meles about anything material.