Privacy Policy
Last updated 12 September 2026.
The clauses below are real, but some details have deliberately not been filled in, because inventing them would be worse than leaving them blank. Until they are supplied, treat this page as a draft.
entityName— The legal entity a customer is contracting with — a registered company name, or your trading name if you are operating as a sole trader.companyNumber— The company registration number, if a company exists. Omit entirely if you are a sole trader.businessAddress— A business address to publish. A registered office or mailbox service is the usual answer; a home address is not required and should not be used.governingLaw— Which country's law governs the terms, and whose courts hear a dispute. Almost certainly England and Wales given the Stripe account, but that is your decision rather than an inference.supervisoryAuthority— The data protection authority customers may complain to — the ICO for the UK. Needed for the privacy policy to be complete under UK GDPR.
Who is responsible
[legal entity — to be supplied], of [business address — to be supplied], is the controller of the personal data described here. Contact admin@rspsbot.com about any of it.
What we collect
When you make an account
You sign in with Discord. We receive and store your Discord account identifier, your email address and your display name. We never see or store a password — there is not one.
How you found us
When you first arrive we record the page you landed on, the site that referred you, and any campaign parameters in the link. If you go on to make an account, that is stored against it so we can tell which channels bring people. It is kept as it was on the first visit and is not updated to follow you around; we also keep the most recent equivalent values separately. It is not used to build a profile or to target you individually.
When you use the client
The client signs in as your account and holds a session. We store which machine it is running on (a device name and a fingerprint that identifies the installation, not you), the client version, the operating system family, when the session started and when it was last heard from.
Diagnostics
The client sends events about what it is doing — a script started, a script stopped, an error and its stack trace. These carry the script, its version, the server it was run against, and the account and session they came from. They exist so faults can be found and fixed.
Payments
Payments are processed by Stripe. We never see or store your card details. We keep the Stripe customer and subscription identifiers, what you bought and when, so your account knows what it is entitled to.
If you write to us
The support form stores the email address you give, your subject and message, and which page you were on — so we can answer.
Why we are allowed to
- To provide what you asked for — your account, your entitlements, your sessions and your payments. Without this data the product cannot work.
- Our legitimate interests — diagnostics to keep it working, and attribution to understand where users come from, both kept to what is necessary.
- Legal obligation — records of payments, which tax law requires us to keep.
Who else sees it
Supabase hosts the database and handles authentication. Vercel hosts the website. Cloudflare R2 stores the downloadable files. Stripe processes payments. Discord provides sign-in. Each of them only handles what they need for their part. We do not sell personal data, and we do not share it for advertising.
How long it is kept
- Account details, for as long as the account exists.
- Sessions and device records, while they are current and for a short period afterwards.
- Diagnostic events, which are purged automatically on a schedule.
- Payment records, for as long as tax law requires.
- Support messages, until the matter is resolved and a reasonable period after.
Cookies and analytics
We set what is needed to keep you signed in. We do not use advertising cookies and we do not run third-party advertising trackers. The attribution described above is stored on your own device until you make an account, at which point it moves to your account record and is cleared.
Your rights
You can ask for a copy of your data, ask for it to be corrected, ask for it to be deleted, object to our use of it, or ask us to restrict it. Write to admin@rspsbot.com and we will answer within a month.
If you are not satisfied, you may complain to [supervisory authority — to be supplied].
Children
This service is not intended for anybody under 16, and we do not knowingly collect data from them. If you believe we have, tell us and it will be deleted.
Changes
Any update is reflected in the date at the top. See also the terms of service and the refund policy.