Trust and security

When you use Meles, you're the controller of your users' data and Meles is your processor: we process it only on your instructions, under our data processing agreement. For your own team's accounts, Meles is the controller, as our privacy notice explains.

Where your data lives

In the United States. Our servers, database and file storage run at DigitalOcean in New York, error reports and performance traces are stored by Sentry, and logs, metrics and traces by Grafana Cloud, both in the United States.

Your users' browsers fetch our script and your campaigns' settings from DigitalOcean's content delivery network, which runs on Cloudflare's network worldwide and may set Cloudflare's bot-management cookie, __cf_bm. What your users send back goes to our servers in New York, which we run, and reach, from Australia.

Security measures

Each measure says what shows it. Our code and its tests are private: ask at privacy@meles.app and we'll share the evidence with you under the DPA.

  • Hosted in the United States

    The application, its database and its file storage run at DigitalOcean in New York (nyc3). Error reports and performance traces are stored by Sentry, and logs, metrics and traces by Grafana Cloud, both in the United States.

    Shown by: Declared in our infrastructure code, which is the only way anything is created.

  • Encrypted in transit and at rest

    Every page and API call is served over HTTPS, with HSTS. The managed database encrypts its storage and its connections.

    Shown by: The web server's configuration, and the database's terms, checked when it was chosen on 2026-09-20.

  • The application can't read a table

    The application's database role may only run reviewed stored routines, each scoped to one organisation. It can't read or change a table directly, so one customer's request can't reach another's data.

    Shown by: Checked on every change by the database's guardrail tests.

  • Keys are hashed, scoped and revocable

    Secret API keys are stored only as hashes, carry only the scopes they were given, and can be revoked at once. Every site requires that each user a page identifies is vouched for by your server, with an HMAC of their ID.

    Shown by: Tested through the API and the MCP server on every change.

  • Sign-in through WorkOS

    Dashboard sign-in is WorkOS AuthKit's. Meles keeps no passwords, and its session cookie is HttpOnly, Secure and SameSite. Each member can turn on two-factor sign-in with an authenticator app.

    Shown by: Our requirements, the session's and two-factor sign-in's tests, and a sign-in with a code on WorkOS's staging environment, which production used until 2026-10-26.

  • Nobody configures a server by hand

    Servers are configured only by our deployment pipeline, from code in our repository. Emergency access opens a temporary window that closes itself.

    Shown by: The pipeline configures the server after every infrastructure change, and every release passes its health gate.

  • Backups, and a restore we've rehearsed

    The database is backed up daily and can be restored to any moment in the last 7 days. A full restore was rehearsed on 2026-09-26 and was online in about 6 minutes.

    Shown by: The restore runbook's rehearsal log.

  • Monitored, with alerts that page

    The API is checked every minute from outside DigitalOcean, and an outage pages the founder's phone. Every new error is reported.

    Shown by: Each alert was drilled, with its timings recorded.

  • Error reports and traces carry only our internal IDs

    Error reports and performance traces leave out users, IP addresses, cookies, headers, query strings and request bodies, and a trace is named for its route, never the address requested. Our embeddable script sends nothing to an error tracker.

    Shown by: Tests send requests full of personal data and fail if any of it reaches a report or a trace.

  • Logs hold internal IDs only

    Our logs never hold a name, an email address or anything a person typed: only our own internal ID numbers. They're kept for 14 days at Grafana Cloud, and on our servers until our next release.

    Shown by: Tested on every change, for every kind of request.

  • Delete and export a person's data

    You can delete or export everything Meles stores about one of your users, through the API or the MCP server. After a restore from backup, our runbook replays every deletion.

    Shown by: Tested across every table that holds a person's data.

  • A breach runbook, walked

    How we find, contain and assess a breach, and how we tell you about it.

    Shown by: Walked on 2026-10-03 as a desk exercise by Claude, an AI assistant; the founder walks it next.

  • Logs kept for a stated period

    Logs kept for 14 days at Grafana Cloud, searchable across releases, as well as on our servers until the next release.

    Shown by: The switch that sends them, on since 7 October 2026, and a test that fails if a log line or a trace leaves with anything personal in it.

  • A retention window for raw events

    Raw events and impressions are deleted once they're 180 days old, a month at a time; webhook and Slack delivery logs 30 days after their last attempt. Responses and answers are kept until you delete them.

    Shown by: A daily job does it; tests plant old months and check it deletes them and keeps any month not yet fully counted in your results.

  • Your whole organisation, exported or deleted

    An export of everything Meles's database holds of your organisation, and its deletion at the end of the service: its rows in every table, its site configs on the CDN, its export files, its customer record at Stripe (invoices stay, as tax law requires) and its organisation at WorkOS. The export made just before the deletion goes within a day. Keys, webhook URLs and signing secrets are left out of the export.

    Shown by: The export reads every table that holds an organisation's rows from the database itself, so a new table is in it the day it lands; a test fails the build if a new table has no deletion, and tests seed every table, delete one organisation and check another is untouched.

Planned security measures

What we don't have yet

How long we keep data

Sub-processors

What each vendor receives. Only DigitalOcean (with Cloudflare, which carries its CDN), Sentry and Grafana Labs get your users' data; the others handle your team's accounts, our email, billing, domain and visits to this site.

  • 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

Changes. We tell your organisation's Owners by email 30 days before a new sub-processor starts, and you can object.

Destinations you connect aren't our sub-processors. A Slack connection sends a campaign's name, its scores and its open-text answers to the channel you choose, and a webhook sends the events you subscribe it to, to the address you give. They go where you send them, under your own terms with Slack or the receiver.

The data processing agreement

Our DPA is part of our terms, so accepting them accepts it. It includes the EU standard contractual clauses and the UK Addendum for transfers out of the EU and the UK. If you need a countersigned copy, email privacy@meles.app.

If something goes wrong

If a breach affects your data, we email your organisation's Owners without undue delay, and within 72 hours of finding it: what happened, which data, what we've done and what you may need to do. We keep a record of every breach, however small.

To report a vulnerability or a suspected breach, email privacy@meles.app.