Merid
Terms Open Merid

Privacy Policy

What we collect, and why.

Effective 23 August 2026

Merid is an architecture whiteboard you design with your AI. This policy explains what information we handle when you use usemerid.com and the app at app.usemerid.com (together, the "Service"), where it lives, and the control you have over it. We've tried to write it the way we'd want to read it. "Merid", "we" and "us" mean the operator of the Service.

1. Information we collect

Account information

You sign in with Google. We don't run password accounts. When you sign in we receive your name, email address and Google account identifier from Google, via Amazon Cognito, and we use them to create and recognise your account, show who you are to your collaborators, and send you service email (for example, an invitation you've been sent). We never see your Google password.

Your content

Everything you create in Merid is your content: projects, sheets, the nodes and connections in them, layouts, comments and review threads, proposals from connected AI tools, and the edit history that records who changed what and when. We store it so the Service works — so your sheets are there when you come back, so the people you share with can see them, and so your AI tools can read and propose changes to them when you connect them.

Collaboration and presence

While you have a shared sheet open, other members of that project can see that you're there (your name or initials, and a colour) and which elements you currently have selected. This is live only — we keep a short-lived connection record so the feature works, and it's removed when you leave or expires within hours.

Billing

Payments are handled by Stripe. If you subscribe to Pro, Stripe collects your card details on its own hosted pages; we never receive or store your card number. We keep your Stripe customer and subscription identifiers and your subscription status so we can unlock Pro features.

AI tool connections

When you connect an AI tool (for example, a coding agent) to Merid over MCP, you either create an API token or authorise the tool through OAuth. We store those tokens and credentials so the connection works, record which tool acted on your sheets in the edit history, and let you revoke any token at any time from the app.

Usage and technical data

Like most web services, our servers log requests (IP address, browser type, the pages and API endpoints used, timestamps) for security, abuse prevention and debugging. Our marketing site at usemerid.com and the app use Google Analytics to understand how people find us and which features they use — events like "created a project" or "exported a sheet", tied to a pseudonymous id. Your diagram content, names and email addresses are never sent to it.

2. What we don't do

  • We don't sell your information, and we don't share it with advertisers.
  • We don't send your content to AI models ourselves. Merid is the canvas your AI works on, not an AI provider. Your content is only read by an AI tool when you connect one, and that tool's handling of it is governed by its own provider's terms.
  • We don't train models on your content.

3. How we use information

  • To provide, maintain and improve the Service.
  • To let you share with and collaborate alongside the people you choose.
  • To process subscriptions and send billing-related notices.
  • To keep the Service secure — detecting abuse, rate limiting, investigating incidents.
  • To answer your questions when you contact us.

4. Sharing and who can see your content

You decide who sees what:

  • Project members you invite by email can view, comment on or edit the sheets in that project according to the role you give them.
  • Share links let anyone who has the link view a project without an account. Treat them like you'd treat a link to any private document.
  • Rendered images that your AI tools generate are served from expiring, signed links and mask content outside the sheet's own project.

Beyond that, we share information only with the service providers that run the Service on our behalf (below), when the law requires it, or to protect the rights and safety of Merid and its users.

5. Service providers

  • Amazon Web Services — hosting, storage and backups (US-East region).
  • Amazon Cognito and Google — sign-in.
  • Stripe — payments and subscription management.
  • Google Analytics — usage analytics (page views and feature events; no content).

6. Where your data lives and how it's protected

Your data is stored in the United States on AWS. It is encrypted in transit (TLS) and at rest, access is limited to what the Service needs to operate, and we keep point-in-time backups so we can recover from mistakes and failures. No system is perfectly secure, but we treat your architecture as the sensitive information it is.

7. Retention and deletion

We keep your content for as long as your account exists. When you delete a sheet or project it's removed from the app, and copies in backups age out within roughly 35 days. If you want your account and everything in it deleted, email us (below) and we'll do it; shared projects you own will become unavailable to the people you shared them with. Server logs are kept for a limited period and then deleted.

8. Your choices and rights

You can edit or delete your content in the app at any time, revoke AI tool tokens, leave projects, and cancel a subscription through the billing portal. Depending on where you live, you may have rights to access, correct, export or delete your personal information, or to object to or restrict how we use it. Email us and we'll help — we don't need you to fill in a form.

9. Cookies and browser storage

The app stores your sign-in session in your browser's local storage so you stay signed in; that's strictly necessary for the Service to work. Google Analytics uses cookies; your browser's settings and Google's opt-out tools control those.

10. Children

Merid is not directed at children under 13, and we don't knowingly collect information from them. If you believe a child has created an account, contact us and we'll remove it.

11. Changes to this policy

If we change this policy in a way that matters, we'll update the date at the top and, for significant changes, let you know in the app or by email. Continuing to use the Service after a change means you accept the updated policy.

12. Contact

Questions, requests, or anything that worries you: support@usemerid.com.

Merid — architecture diagrams, designed with AI
Home Request a feature Report a bug Privacy Terms