Privacy
Short version: the site works without an account, stores as little as possible when you have one, and you can export or delete everything at any time.
If you never sign in
Your collection and your saved teams live in your browser's local storage and nowhere else. They are not sent anywhere, and we cannot see them. Clearing your site data deletes them — so export a copy if it matters to you.
The team builder's share link is not an exception. The whole team is packed into the part of the URL after the #, which browsers never send to a server. We do not see those links, cannot count them, and could not take one down if we wanted to.
If you sign in
Signing in with Discord or Google is optional and exists only to sync across devices.
What is stored
- An account id issued by our database
- Your email address and display name, as supplied by Discord or Google
- Your collection: which forms you have marked, and when
- Your collection profile names and any server region you set
- Your saved teams, so they stay in step across your devices
- Any team you publish — see below
What is not
- No password. Sign-in is delegated, so there is nothing to leak.
- No Discord or Google contacts, servers, friends or activity.
- No advertising identifiers, and your collection is never used for advertising.
- Nothing is sold or shared with third parties.
If you publish a team
Publishing is a separate, deliberate act: nothing you build is public until you press Publish. What goes on the page is the team's name, its four slots and their notes, your notes, and the credit you type in — nothing else. Your email, your account id and your collection are not part of it and are not readable by anyone visiting the page.
What is published is a snapshot. Editing the team afterwards — or syncing it between your devices — does not change the page; it stays on the version you published until you press Update the page. So a team you are still experimenting with is not quietly going public a change at a time.
A published page is genuinely public: anyone with the link can read it, it is listed on Published teams, and search engines may index it. Treat the credit field as a public name, not a private one.
Taking it down. “Take it offline” on the team builder makes the page 404 again and delists it. Deleting the team removes the stored row entirely. Neither can reach copies other people have already made or pages that have already been cached elsewhere — that is true of anything published anywhere, and is the reason publishing asks first.
Getting your data out
The collection page exports everything as JSON, signed in or not. It imports the same file, so you can move between browsers without an account.
Deleting it
- Local copy: “Clear collection” on the collection page, or clear site data.
- Account and cloud copy: “Delete account” on the collection page. It removes the account and everything attached to it — including any published team pages — immediately and irreversibly. Your browser copy is left alone.
- Signing out is not deletion — it leaves both copies intact.
Who processes it
Hosting is Vercel; accounts and the database are Supabase. Sign-in is handled by Discord or Google, whose own privacy policies apply to the account you sign in with. Data is stored in the region the database was created in.
Access is enforced at the database with row-level security: every row is readable and writable only by the account that owns it.
Analytics
Aggregate page-view analytics may be used to understand which pages are useful. It records no cookies and no cross-site identifiers, and is never joined to your collection or your account.
Children
Accounts are not intended for children under 13, or under 16 in regions where that is the threshold for consent. The site is fully usable without an account at any age.
Contact and changes
This is an unofficial fan project, not affiliated with Pawprint Studio. For anything privacy-related, or to request deletion if the in-app button is not working for you, open an issue on the project repository.
Last updated 2026-09-08. Material changes will be noted here; the page history is public in the repository.