privacy
privacy policy.
what palletism stores, who processes it, and how to get a copy or delete it.
last updated
what we collect
free needs no card. if you buy hobby, dodo payments takes your payment details at checkout; we never see or store your card. you can browse without an account, but our hosting and security providers still see technical request data such as ip addresses, urls and browser details.
- account: your email and whether it’s verified, account id, display name, profile picture or avatar seed, sign-in sessions and their times. neon auth may record the ip address and browser of each session. sign-in codes expire, but the record of a code may not be erased right away.
- google sign-in, if you use it: google shares your account id, email, name and profile picture with neon auth, which manages the link. we never see your google password, and we don’t ask for your mail or files.
- profile, saves and votes: your handle if you set one, the images and packs you save, and your votes, with dates.
- feedback, if you send it: the title, description and optional screenshot you send with the feedback button, the page you sent it from and its status. signed in, it’s tied to your account, shown in your profile and deleted with it. signed out, it has no account attached and only we can see it, so don’t put personal details in it. screenshots are stored privately; only we and, when you were signed in, you can open them.
- mcp: key names and prefixes, a hash instead of the key itself, when each key was made, used, expires or was revoked, daily call counts and your plan. we don’t keep your searches or the responses as history.
- support and security: emails you send us, how we confirmed it was you, what we did, and admin audit records with the account id, action, time and reason.
- billing, if you buy hobby: dodo’s customer and subscription ids, plan, status, period dates, cancellation and discount history, and webhook ids, types and times. we don’t store card details or raw billing webhooks, and free accounts don’t need any of this.
cookies and browser storage
neon auth uses session cookies to keep you signed in. admins also get a secure, http-only session cookie on palletism; regular users don’t.
to keep tabs in sync, the sign-in code uses the browser-storage key better-auth.message. we limit it to a timestamp and an instruction to refresh your session, not an account, email or token payload, and we clear older entries when sign-in starts. deleting your account can’t reach your devices, so sign out and clear site data on the ones you use.
we don’t run ads or ad trackers.
analytics and logs
we may use cloudflare web analytics to count page views, referrers, browser and device types, and page speed. cloudflare says it doesn’t use cookies or browser storage or follow you across sites. it drops query strings, but page paths can be counted, so don’t put personal details in a url.
we keep error logs to fix problems. they use fixed event names and error types, not request bodies, passwords or keys, and query strings are hidden. as our host, cloudflare also handles platform and request data. we don’t use session replay or outside error-tracking services, and we send other sites only our domain as the referrer.
why we use it
to run sign-in, saves, votes, settings and mcp access, to enforce limits, answer support, keep the service secure and stop abuse, and to run hobby billing. we don’t sell your data or use it to train models.
the only automatic emails we send are sign-in codes. no newsletters. agents and image tools you use alongside palletism are separate services with their own terms.
who processes it
- neon: the database, sign-in and image storage, run from aws us-east-2. image files, including originals, are public by address, not private storage.
- google: sign-in if you choose it, and the inbox that receives support mail through cloudflare email routing.
- resend: may deliver sign-in code emails for neon auth, which passes it your address and the message.
- cloudflare: hosts the site and mcp server, handles security and rate limits by account id or ip address, stores mcp keys, counts and plans, and keeps logs, analytics and short-term recovery history.
- dodo payments: the merchant of record for hobby. at checkout it collects your email, name, billing address and payment details, works out tax and sends receipts, under its own privacy policy. it sends us back the ids, plan and status listed above, never your card. free accounts never reach dodo. if an account has billing, deleting it may mean looking you up at dodo by email and cancelling open subscriptions first. support can delete a verified never-billed account without contacting dodo. dodo keeps its own payment records under its own terms, and deleting your palletism account doesn’t erase them.
these providers may process data in other countries and use their own subprocessors.
getting a copy of your data
email contact@palletism.art. we’ll confirm it’s you before sharing anything. if you’ve lost access to your email, tell us and we’ll find another way to check. never send passwords, sign-in codes or card details.
the export is a json file with your account details and avatar, handle, saves, votes, any subscription summary, active mcp key details and up to 30 days of usage. it doesn’t include key secrets or hashes, session or oauth tokens, revoked-key metadata, security or admin audits, support emails, backups or records held by providers. ask if you want any of those, or if something needs correcting.
you can change your name, avatar and handle in settings. email changes go through support.
deleting your account
email contact@palletism.art. once we’ve confirmed it’s you, support deletes the account. if it may have billing, we first check dodo and cancel any open subscription; if that check fails, nothing is deleted until support sorts it out, as there is no automatic retry queue. a verified never-billed account is deleted without a dodo check.
deletion removes your mcp keys, usage and plan, saves, votes, handle, subscription and billing-event rows, any admin access, and your sign-in account. some things stay:
- the deleted account id and time, so requests already in flight can’t bring it back.
- security and support audit entries, and support emails.
- anonymous counts, such as early-bird places, and records that stop late billing events from being processed twice.
- copies held by our providers in logs, recovery history, mailboxes and backups, until they expire.
deleting your account doesn’t waive any rights from an earlier purchase.
how long we keep data
we keep account data while your account exists. expired sign-in codes and keys stop working, but their records aren’t necessarily erased right away. old mcp key records and admin audits have no set end date.
mcp usage counts are cleared after about 35 days. cleanup runs when the service gets traffic, so after idle periods older counts can stay a little longer. the export shows the last 30 days.
cloudflare keeps up to 30 days of recovery history for stored mcp data, and resend says it keeps email logs for 30 days. neon and cloudflare log windows depend on our plan.
contact
to ask for a copy, a correction, deletion or help with any other privacy right, email contact@palletism.art. nothing here limits your rights under the law where you live. if we change this policy, we’ll update the date at the top.
provider details: neon email delivery, resend retention and cloudflare recovery history.