Legal
Privacy
This page lists every category of data we store, why it exists, and who else can see it. If something is not on this page, we do not collect it.
What we store
- Your account
- Email address, name, and a bcrypt hash of your password. We never store the password itself and cannot read it. Also whether your email is verified, your role, and the time you last signed in.
- To let you sign in and to attach your purchases to you. Buying without signing up creates this from the email address you pay with.
- Sign-in sessions
- A hash of each refresh token, the browser user agent, and the IP address the session was created from. The plain token is never stored.
- To keep you signed in, to show you where you are signed in, and to end a session you no longer recognise.
- Verification and reset tokens
- A hash of each token, its type, and when it expires or was used.
- To verify an email address and to reset a forgotten password. They delete themselves when they expire.
- Orders
- The Stripe session and payment identifiers, what was bought, the amount, the currency, any coupon used, and the status. Card numbers never reach us; Stripe holds those.
- They are financial records, and they are how your access is justified.
- Licences
- Which templates you own, the licence key, and when it was issued or revoked.
- To decide what you may download.
- Downloads
- Which template you downloaded and when, with the IP address and browser user agent at the time.
- To enforce the daily download limit and to spot a licence being shared at scale.
- Reviews
- Your rating and text, shown with your name once approved.
- To let other buyers see what owners think. Your email is never shown.
- Newsletter
- Your email address and where you subscribed from, only if you asked to be added.
- To tell you when a template ships. Never added without you ticking the box.
- Contact messages
- Your name, email and message.
- To reply to you.
- Admin actions
- What an administrator changed, when, and from which IP address.
- So a change to your order or licence can be traced to a person.
Cookies
Two, both strictly necessary and both unreadable by JavaScript: px71_access lasts fifteen minutes and px71_refresh lasts thirty days. They exist only to keep you signed in.
There is no analytics, no advertising pixel and no third-party tracker on this site, which is why there is no consent banner. If that ever changes, this page changes with it and anything non-essential will ask first.
Who else sees it
- Stripe
- Payments and tax. Sees your email, name and card details. We never see the card.
- MongoDB Atlas
- The database. Holds everything in the table above.
- Cloudflare R2
- File storage. Holds the template files, not personal data.
- Resend
- Email delivery. Sees your email address and the message we send you.
- Upstash
- Rate limiting. Sees a truncated hash of your IP address, never the address.
- Sentry
- Error reporting. Request bodies, cookies and headers are scrubbed before sending.
- Vercel
- Hosting. Sees requests as any web host does.
We do not sell your data, and we do not share it with anyone not on that list.
How long we keep it
Verification and reset tokens delete themselves when they expire. Sessions expire after thirty days. Orders and licences are kept for as long as the law requires financial records to be kept, because they are the proof behind your access. Everything else is kept while your account exists.
Deleting your account
You can delete it from settings. Your email, name, avatar and password are erased, and every session and token is destroyed. The IP address and browser on your download history are cleared, keeping only the counts.
Orders and licences survive, attached to an anonymised identifier, because they are financial records we are required to keep. A deleted account cannot sign in and cannot be re-registered on the same email without us stepping in.
Asking us about it
Write through the contact form to see what we hold about you, correct it, or ask for it to be removed.