Privacy Policy
Effective 21 October 2026
Shot Canvas is a collaborative canvas for people and agents, on the web and in the iPhone app (and its App Clip). Shot Canvas is made by Derainged LLC ("we"), which is responsible for your data. This policy says what we collect, why, who else handles it, how long we keep it, and how to delete it. Questions: support@shotcanvas.io.
Canvases on your own computer
A canvas you make on the website without signing in stays in your browser, or as files on your computer through the local helper. We don't receive it. Nothing below applies to it until you share it, except the usage events described under "Product usage".
What we collect
- Your account: your email address and name, and an account ID. If you sign in with Apple or Google, we get the name and email they give us (with Apple, that can be a private relay address).
- What you make and share: shared canvases and their pages, layers, images and files, their saved versions, comments and replies, folders, who you share with and their roles, and the invitations you send (with the email addresses you type).
- Activity on shared canvases: who changed what and when (the History), when you last looked at a canvas (for "new" counts), your notifications and their read state, and requests to open a canvas.
- Your device, in the app: a push notification token, if you allow notifications, and the app's version.
- Your browser, if you turn on browser notifications: the push address and keys your browser gives us for them, and its name and version. We send each notification encrypted for that browser.
- Reports: when you report a canvas, the reason, your note and who sent it.
- Connections you make: if you connect an AI agent or import from Figma, the access grant for that connection.
- Product usage: a few events: when you sign up, and when a canvas is opened, shared or changed (by you or by an agent). Each event carries the canvas's ID, never its contents. It also carries a random ID for your browser or device, your account ID, email and name once you sign in, your device and browser type, and the rough location your IP address suggests. These events come from the website, the local helper, the app and the agents server.
- App performance: Apple’s daily MetricKit aggregates in the full iPhone app: launch and resume durations, hangs, animation hitch ratios, memory use and termination counts. We send only numeric summaries to Mixpanel to find performance problems, never raw diagnostic payloads, stacks, canvas contents or task text.
- Agent tool performance: which built-in tool and fixed action were called, how long it took, whether it succeeded, failed, was cancelled or interrupted, a unique MCP session ID, and your account ID when known. These events come from the local helper through an open canvas window and from the cloud agents server. We do not send tool arguments, results, error text or conversation contents.
- Server process performance: periodic memory measurements for processes on our cloud agents server, with process and server-instance IDs, process type, and the account, MCP session, agent-slot and canvas IDs associated with them where known. We also record process starts and stops, exit reasons, session initialization times, process reuse and whether a saved place was supplied on reconnect, plus numeric counts and sizes for active sessions, calls, shared tool catalogues and temporary copied-layer storage. These measurements never include the contents of that storage. Shared infrastructure is recorded separately. For the server's headless browser windows and its renders drawn without one, we record how long each took to start and stayed open or ran, its memory use, which agent tool needed it, which tools used it, and coded reasons why a browser window was needed (such as a built-in layer type the server cannot draw yet). We do not collect a list of processes on your computer, process command lines or file paths.
- Support chat: if you chat with us from the website or the app, your messages, the email address and name you give (or your account's, once you sign in), and your browser or device type and rough location, so we can answer you.
- TestFlight requests: if you request access to the iOS beta, we email your address to our team so we can send you an invitation. It stays in our inbox until your request is handled, or you ask us to delete it.
We don't use advertising, we don't track you across other companies' apps or websites, we don't sell your data, and the app has no advertising SDKs.
Why
Only to run Shot Canvas: to sign you in, keep and sync shared canvases, show the people and agents working on them, send the emails and notifications you ask for, let you search your canvases, keep the service secure, and review reports of content that breaks our Terms. We use product usage events only to understand how Shot Canvas is used, so we can improve it, and support chats only to help you.
Who else handles it
These companies run parts of the service for us, and handle your data only to do so:
- Supabase: accounts and sign-in, the database, and file storage.
- Fly.io: the servers that sync shared canvases and that agents connect to.
- Vercel: the website.
- Resend: emails (sign-in codes, invitations, and TestFlight signup requests).
- Apple: Sign in with Apple, and push notifications on iPhone.
- Your browser's push service (Google, Mozilla, Apple or Microsoft, depending on your browser): delivers the browser notifications you turn on; it sees only encrypted messages.
- Google: Sign in with Google, if you use it.
- Mixpanel: product usage events, agent tool timing, server process performance measurements and daily app performance summaries.
- Crisp: the support chat.
Each of them is bound to protect your data at least as well as this policy does.
AI agents
Shot Canvas doesn't send your canvases to an AI company on its own. You can choose to connect an AI agent, such as Claude, ChatGPT, Codex or Cursor. A connected agent works as you. It can read and change the canvases you can open, including their comments and the names of the people on them. What it reads goes to that agent's company, under your agreement with them. From the app, "Send to agent" opens that agent with a message and a link to the canvas, which you can see first. You can remove an agent's access at any time.
Who can see your canvases
A shared canvas is seen by the people you invite, the people in its folder, anyone using its link while the link is open, and the agents those people connect. Comments show your name.
How long we keep it
We keep your account and shared canvases until you delete them. A canvas you delete goes to Trash first, where you can restore it. Saved versions are kept while their canvas is. Reports are kept for as long as we need them to deal with abuse.
Deleting your account
In the app, open your account (your picture) and tap Delete account. You can also email support@shotcanvas.io from your account's address. Deleting your account removes your account, the canvases and folders you own (for everyone they're shared with), your memberships, devices, notifications, requests and reports. If you signed in with Apple, it also revokes Shot Canvas's access to your Apple ID. Canvases other people own stay with them, and the comments you left on them stay there too. Deleted data leaves our live systems at once and our backups within 30 days.
Your choices and rights
You can turn off notifications (or set quiet hours, or mute a canvas), change who a canvas is shared with, remove an agent's access, and download your canvases. You can ask us for a copy of your data, or to correct or delete it, at support@shotcanvas.io. Where a law such as the GDPR applies, we rely on our contract with you to provide the service, and you can also complain to your data protection authority.
Children
Shot Canvas isn't meant for children under 13, and we don't knowingly collect their data.
Changes
If we change this policy, we'll update this page and its date, and tell you in the app or by email if the change matters.