Privacy policy
Last updated: not set
NOT YET REVIEWED. This page is a structure, not a
finished policy. The headings are the ones payment processors expect, but
the wording is yours to write and should be checked by someone qualified
before you take money. Nothing here is legal advice.
What we collect
You already have most of this written. Section 7D of your licensing plan and clause 5 of the beta licence describe exactly what the app sends when someone registers: email address, password, machine code, and stage. Clause 6 lists what is never transmitted.
PLACEHOLDER — Restate that here in plain language, plus anything the
website itself collects - account email, payment details handled by the
processor, and any server logs.
What we never collect
PLACEHOLDER — This is a genuine selling point for you and worth stating
prominently. Clause 6 of the beta licence already lists it - your work,
your files, your keystrokes.
Why we hold it
PLACEHOLDER — Tie each item to a reason: the email address identifies the
account, the machine code binds the licence to a computer, and so on.
Payment information
PLACEHOLDER — Name your processor (Stripe, Paddle or Gumroad) and state
that card details go to them and never reach your server. Link their
privacy policy.
How long we keep it
PLACEHOLDER — Note that the issued-licence ledger is permanent by design -
it is how a reinstall gets the same licence back without spending a seat.
Who else sees it
PLACEHOLDER — Your hosting provider, your payment processor, and your
email provider. Name them.
Your rights
PLACEHOLDER — How someone asks for a copy of their data, corrects it, or
asks for deletion - and what deletion means when the licence ledger has to
stay intact.
Cookies
PLACEHOLDER — This site sets one session cookie when you sign in, and
nothing else. No analytics or tracking at present - say so if it stays that
way.
Contact
Questions about this policy: contact us.