Privacy policy

Last updated 10 October 2026

The short version
  • Without an account, your drawings stay in your browser. We never receive them.
  • With an account, we store your email address, a scrambled (hashed) form of your password, and a copy of your pages so they can sync between your devices.
  • No adverts or visitor tracking. We count blog actions and editor usage in anonymous daily totals and never sell your data.
  • You can delete your account, and its cloud copy, at any time from the app.

Who we are

epicdraw ("we", "us") is the diagram editor at epicdraw.app. We are the data controller for the personal data described here. Contact us at support@epicdraw.app about anything in this policy.

Using epicdraw without an account

You can use every drawing feature without an account. Your pages, pictures, recovery copies and settings are saved by your own browser on your own device (in its IndexedDB and local storage), and a copy of the app is kept in your browser's offline cache. This data is not sent to us and we cannot see it, recover it or delete it for you. Clearing your browser's site data removes it, so download a backup for anything you want to keep.

Like any website, loading epicdraw means your browser connects to our hosting provider, Cloudflare. Cloudflare processes your IP address and basic request details to deliver the site and protect it from attacks. See "Hosting and logs" below.

What we collect if you create an account

DataWhyLawful basis
Email addressTo identify your account and let you sign inContract: providing the sync service you asked for
Password, stored only as a salted PBKDF2 hashTo check it is you when you sign in. We cannot read your password.Contract
Your pages (the workspace you sync), including any pictures you addedTo keep a cloud copy and sync it to your other devicesContract
Sign-in sessions (a random token, stored hashed, with created and expiry times)To keep you signed in for up to 30 daysContract
Account creation time, when you were last active, last sync time, count of recent failed sign-insTo run the service, understand how many accounts are in use, and protect accounts from password guessingLegitimate interests: running and securing the service
Pages you choose to share as a link, their settings (including a hashed link password), when they were shared and how many times they were openedTo show the page to people you send the link toContract
Changes viewers make to the interactive parts of a link set to "shared with everyone"So everyone with that link sees the same ticks, votes and card movesContract (for the link owner)
Password-reset links (stored hashed, valid for one hour)To let you choose a new password by emailContract
IP address, brieflyTo limit how often sign-in and sign-up can be triedLegitimate interests: preventing abuse

We only email you when you ask for a password reset. We don't send marketing. An account does not require a name; reviewers can choose a display name for comments, and we do not look at the content of your pages except where needed to keep the service running, to deal with a problem you report, or where the law requires it.

AI assistant connections (MCP)

Before an assistant edits or restores a page, we save its previous version privately for recovery. We retain the ten most recent versions across your account, until replaced by newer versions or removed when you delete your account. Creation request identifiers and content hashes are retained until account deletion to prevent duplicate pages when an assistant retries. Consumed refresh-token hashes are retained for the connection's remaining lifetime to detect reuse and revoke compromised connections.

This optional feature requires an account. When you connect an assistant, we store its registered name and callback addresses, your chosen permissions, connection time, and hashed access and refresh tokens. Tokens allow access only to your account’s synced diagrams. You can choose read-only access or also allow diagram creation and editing.

The assistant receives the diagrams it reads, including text, notes and pictures, and may send edits back to Epicdraw if you allowed editing. Its provider’s data policies apply to the content it receives. Your Epicdraw password is not sent to the assistant. Connecting does not publish diagrams or allow the assistant to manage your account.

You can disconnect an assistant from the Account panel at any time. This stops future access but cannot remove copies already received by the assistant. Access tokens last one hour; refresh tokens allow the connection to continue for up to 30 days. Temporary connection requests expire after ten minutes and single-use authorization codes after five minutes. Changing or resetting your password disconnects assistants; deleting your account also removes its connections.

Review comments

When you post on a shared page, we store your chosen display name, text, shape or canvas anchor, creation time, replies and resolved status to provide the review feature you requested. Comments are visible to everyone who can open the link. Names are chosen by reviewers and are not verified. Account emails and reviewer identifiers are not displayed.

We associate feedback with your account identifier if signed in, or a random identifier for that link otherwise, so you can resolve your threads. Feedback remains until the owner deletes the link or account. Turning comments off hides it from reviewers but retains it for the owner. To request removal, contact the link owner or support@epicdraw.app. Drawing backups do not include comments.

Cookies and browser storage

We set ed_session after you sign in. It is strictly necessary to keep you signed in, is limited to our sync API, cannot be read by page scripts, and expires after 30 days or when you sign out. Because it is strictly necessary, we do not ask for consent. We use no advertising, analytics or third-party cookies.

Anonymous content measurement

We also count editor openings and whether someone makes a saved content change during that opening. Each reload or new tab counts as a new session. Totals are grouped by UTC date, action and whether the editor was opened signed in or signed out; no account or visitor identifier is included. These are session counts, not unique people. Shared-link viewers are excluded. The browser sends at most two requests per editor opening, without cookies or a referrer, and keeps the measurement flags only in memory. Offline visits, blocked requests and privacy opt-outs may be missing.

We count blog views, template starts, clicks on account invitations and successful account creation from an article. We store only a daily total for each article and action, using UTC dates. These are event counts, not unique visitor counts. We do not store visitor identifiers, account IDs, email addresses, individual event histories or fingerprinting data in these totals.

An article label can pass in the link to the editor and stays in memory for that page only. We do not save it in cookies or local storage. We respect Do Not Track and Global Privacy Control signals. Measurement requests use the same Cloudflare infrastructure as the site; IP addresses may be used briefly for rate limiting, as with account security, but are not stored in the measurement table. Totals cannot reconstruct a person's browsing history.

If you open a password-protected share link and enter the right password, we set a strictly necessary cookie, ed_share_<link>, so you aren't asked again for 30 days. It only works for that link.

When you comment without signing in, ed_reviewer_<link> remembers your threads so you can resolve or reopen them. This strictly necessary cookie is limited to that link’s API, cannot be read by page scripts and expires after 30 days. Your display name is remembered in local storage on this device.

The app also uses your browser's storage to save your work, to remember sync progress, and to keep your own taps on share links set to "just for themselves". This stays on your device.

Who processes your data for us

We do not sell or rent personal data. In addition to these service providers, pages are sent to AI assistants you explicitly connect, according to the permissions you choose, and to viewers of share links you create. Otherwise we share personal data only where the law requires it.

Hosting and logs

Cloudflare processes connection data (such as IP address, browser type and the pages requested) to serve and secure the site. We do not use this to build profiles of visitors. Our own error logs may briefly include technical details of failed requests, but never passwords or page contents.

How long we keep it

Security

All traffic uses HTTPS. Passwords are salted and hashed, session tokens are stored only in hashed form, cross-site requests to the API are blocked, and repeated failed sign-ins temporarily lock the account. No system is perfectly secure, so please use a password you don't use anywhere else.

Your rights

Under UK data protection law (the UK GDPR and the Data Protection Act 2018), you can ask us to:

Email support@epicdraw.app and we'll reply within one month. If you're unhappy with how we handle your data, you can complain to the Information Commissioner's Office at ico.org.uk, but we'd appreciate the chance to sort it out first.

Children

Anyone can use epicdraw without an account. Accounts are for people aged 13 or over. If you believe a child under 13 has created an account, contact us and we will delete it.

Changes to this policy

If we change how we handle personal data, we'll update this page and the date at the top. If a change materially affects account holders, we'll tell you in the app before it takes effect.