Privacy
What we store, and what we don't.
This describes what the software actually does. Where something depends on how a particular deployment is configured, it says so rather than promising more than the code delivers.
Your entry lists stay in your browser
These all happen on your device and are never sent to a server:
- names you type or paste
- spreadsheet and CSV files you import — the file is read locally and not uploaded
- wheel titles, themes, weights and spin settings
- choosing the winner
- saved wheels and recent picks, kept in this browser’s local storage
- the Entry List ID, calculated locally
- the proof video, composed and encoded in your browser
There is no account, so there is nothing tying any of it to you. Clearing your site data removes saved wheels and history permanently — we have no copy to restore.
Payments
Proof purchases go through Stripe Checkout. Card details are entered on Stripe’s hosted page and never reach Spinnza. Stripe processes that payment as its own controller; their privacy policy covers it.
When you buy a proof spin, we store a purchase record containing:
- an opaque purchase id and the Stripe session and payment intent ids
- status, amount, currency, and when it was created, expires and was used
- how many recording attempts have been made
- a random reference your browser generated before checkout, so an unused purchase can be recovered without an account
That record contains nothing about the draw — no entrant names, no list, no title, no Entry List ID. Nothing about your entries is put into Stripe metadata either. Purchase records are kept for accounting and refunds; unused entitlements expire after 7 days.
Analytics
We count what happens, not who it happened to. Events are things like spin_completed, xlsx_imported or payment_completed, with a small set of numeric or fixed-value properties: how many entries were in the draw, how many winners, which format was exported, which error code occurred.
The server only accepts a fixed list of property names, none of which holds free text, so entrant names cannot travel there even by accident. There are no advertising or cross-site tracking cookies set by Spinnza itself.
IP addresses
Server endpoints that cost something — creating a checkout session, admin login, contact messages — are rate limited using an IP-derived key held in memory. It is not written to a database and does not persist beyond the server process. Your hosting provider and CDN keep their own request logs, which are outside Spinnza’s control.
Advertising
The free pages may show advertising. Where a deployment enables Google AdSense, Google sets its own cookies and processes data under its own policies, and a consent tool appropriate to your region is required. With no ad configuration present, no advertising script is loaded at all.
Contact and feedback
If you send a message we store what you wrote, the topic, and your email address if you gave one, so we can reply.
Children
Spinnza is a general-purpose tool with no account and no profile. Where a teacher uses it with a class list, those names stay in the browser on that device and are never transmitted to us.
Your choices
- Clear saved wheels and history from the tool, or by clearing site data.
- Ask us to delete a purchase record at support@spinnza.com, once any refund window has passed.