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.
- Affiliate account
- Only if you apply to the affiliate programme: your referral code, the website and note you sent with the application, your payout method, payout email and any payout details, your commission rate, and who reviewed the application and when.
- To decide on your application, to credit the sales you refer, and to know where to send your money.
- Commissions and payouts
- For each sale an affiliate referred: which order it was, the sale value before tax, the rate, the commission, and whether it came from a link or a coupon. For each payout: the amount, the commissions it covered, where it was sent and any transaction reference. An affiliate sees the date and value of the sales they referred, never who the buyer was.
- They are financial records, and they are how an affiliate’s earnings are worked out.
- 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 keep you signed in, 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.
One more cookie, px71_analytics, remembers whether you accepted or declined analytics. It lasts a year and holds nothing else.
If you arrive through an affiliate’s link, we set px71_ref. It holds only that affiliate’s code, cannot be read by JavaScript, and lasts 90 days, so that if you buy in that time the affiliate who sent you is credited. A later affiliate link replaces it. It is set without asking and is never used for anything else. Your price is the same either way.
We use Google Analytics to see which pages are visited and where visitors come from. It is off until you accept it in the banner. If you accept, Google sets _ga cookies that last up to two years. If you decline, no analytics cookie is set and any existing ones are removed. Advertising features are always off, and there is no advertising pixel.
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.
- Affiliate payout services
- PayPal, Wise, Stripe, or the service an affiliate names. Each sees only the payout details that affiliate gave us and the amount we send.
- Google Analytics
- Visit statistics, only if you accept analytics. Sees the pages you view, your browser and an approximate location.
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. Commissions and payouts are kept on the same basis. 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.
If you are an affiliate, write to us before deleting your account so we can settle what you are owed and remove your payout details.
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.