Best on desktop — the editor needs a wider screen. Try ERDone on your laptop.

Privacy Policy

Effective July 21, 2026

Summary

ERDone is designed to hold as little personal data as possible. Your diagram contents live in your own Git repository or your browser’s local storage — not on our servers. We store account metadata (your provider ID and email), your repository connection settings, and your subscription state. We never sell your data.

1. Information We Collect

We collect only what we need to provide and bill for the Service:

  • Account data. When you sign in via an OAuth identity provider, we receive a stable user ID, email address, and (where you’ve made them public) display name and avatar URL.
  • Repository connection. If you connect a Git repository, we store the repository identifier and the access token issued by your Git host. The token is used only to read and write your diagram files at your direction.
  • Subscription state. Your tier (Free, Pro, or Team), status (trialing, active, canceled, past-due), trial end date, and (for paying customers) the Lemon Squeezy customer and subscription identifiers needed to link your subscription to your account. We do not receive or store payment-card data — that lives only with Lemon Squeezy.
  • Diagrams. Free-tier diagrams stay in your browser’s local storage. Paid-tier diagrams are saved as files in your Git repository. We do not transmit, copy, or analyze the contents of your diagrams on our servers.
  • Usage analytics. We use PostHog to understand how the Service is used. This records product events (e.g. features used, errors) and web-performance metrics, and a sampled subset of session replays with form inputs masked. Once you sign in, analytics is associated with your account ID; PostHog also processes your IP address and approximate location. Analytics is disabled entirely until we configure it, and we do not sell this data.
  • Advertising attribution. For visitors in the United States who arrive from a Google ad, we store ad-click identifiers (such as gclid) and campaign parameters (UTM values) in a first-party cookie so we can measure which campaigns lead to signups. Where enabled, a signup-conversion signal and the ad-click identifier are shared with Google Ads. This applies to US visitors only; outside the US, no advertising attribution runs.

2. How We Use Information

  • To operate the Service and authenticate your account.
  • To process subscriptions and bill you correctly through Lemon Squeezy.
  • To respond to support requests you send to support@erdone.net.
  • To send transactional emails about your account or subscription. We do not send marketing emails.
  • To detect and prevent abuse of the Service.

3. Data Subprocessors

We rely on the following third-party services to operate ERDone. Each is bound by its own privacy policy and applicable data processing agreements, and each is located in the United States; for users outside the US, using the Service involves transferring data to the US under the safeguards these providers maintain. We keep this list current and will post material changes here before a new subprocessor begins processing personal data.

Subprocessor Purpose Location Policy
Supabase, Inc. Authentication, database (account, subscription, and connection metadata), and Edge Function / webhook hosting. Data encrypted at rest and in transit. United States link
Vercel, Inc. Web hosting, CDN, and edge routing for erdone.net United States link
PostHog, Inc. Product analytics and session replay. Records usage events and a sampled subset of session recordings (form inputs masked); associates activity with your account ID and processes IP address and approximate location. United States link
Resend (Plus Five Five, Inc.) Transactional email delivery (welcome, team invite, account notices) United States link
Lemon Squeezy, Inc. Payment processing (Merchant of Record) United States link
GitHub, Inc. OAuth identity provider; repository storage for users who connect a GitHub repo United States link
Google LLC (Google Ads) Advertising conversion measurement for US visitors who arrive from a Google ad. Receives a signup-conversion signal and ad-click identifier; only when this integration is enabled. United States link

4. Cookies and Local Storage

We use cookies and browser local storage to keep you signed in, remember your UI preferences, and (on the Free tier) store your diagrams locally. PostHog sets cookies to measure product usage and session replays. For US visitors arriving from a Google ad, a first-party cookie stores ad-click and campaign identifiers for conversion measurement (see “Advertising attribution” above); this does not run outside the US. We do not use cookies to serve third-party ads to you.

5. Data Retention

We retain your account data for as long as your account is active. If you delete your account, we remove your profile and subscription records within 30 days, except where retention is required for legal, tax, or accounting purposes. Diagrams stored in your own Git repository are unaffected — they remain in your repository under your control.

6. Your Rights

Depending on where you live, you may have the right to access, correct, delete, or export your personal data; to object to or restrict certain processing; or to withdraw consent. To exercise any of these rights, email support@erdone.net. We’ll respond within 30 days.

California residents have additional rights under the California Consumer Privacy Act (CCPA), and EU/UK residents have rights under the GDPR / UK-GDPR. We do not sell personal information.

7. Children

The Service is not directed to children under 13 (or under the age of consent in your jurisdiction), and we do not knowingly collect data from them. If you believe a child has provided us information, email us and we’ll delete it.

8. Security

We take reasonable measures to protect the data we hold, including: encryption in transit (TLS) and at rest; row-level security so each account can reach only its own records; storage of third-party credentials (such as your Git access token) as encrypted secrets, used only at your direction; scoped, least-privilege access for our backend services; and authentication delegated to your OAuth provider, so we never receive or store your password. No system is perfectly secure; we encourage you to use a strong password and two-factor authentication on your OAuth provider and to keep your account credentials confidential.

Security incidents. If we become aware of a breach affecting your personal data, we will investigate, take steps to contain it, and notify affected users and, where applicable, the relevant authorities without undue delay and within the timeframes required by law.

9. Changes to This Policy

We may update this Privacy Policy. Material changes will be announced via the Service or by email at least 14 days before they take effect.

10. Contact

Privacy questions and data-rights requests: support@erdone.net.