Draft. This text has not been reviewed by a lawyer and is not legal advice. Highlighted items in square brackets still need a decision or a real value before launch.
Privacy Policy
What personal data FollowUp Desk X handles, why, and what your rights are.
Last updated 12 October 2026
1. Who is responsible
Sebastian, trading as Scappi X Studios, Denmark, is the data controller for account data. Privacy requests go to support.scappix@gmail.com.
Roadmap content is normally about a game server, not about people. If you put personal details of others into it, you are the controller for that data and we process it on your behalf. [decide whether a data processing agreement is offered]
2. What we collect and why
| Data | Purpose | Legal basis (GDPR) |
|---|---|---|
| Email address and a hashed password | Creating your account and signing you in | Performance of a contract, Art. 6(1)(b) |
| Server name, server address and player page name | Labelling your workspace and, if you switch it on, your public page | Performance of a contract, Art. 6(1)(b) |
| Roadmap items, descriptions, steps and step notes you enter | Providing the service to you, and publishing the roadmap when your public page is on | Performance of a contract, Art. 6(1)(b) |
| Session cookies and technical logs kept by our providers (such as IP address and time of request) | Keeping you signed in, security and fault finding | Legitimate interests, Art. 6(1)(f), and strictly necessary storage |
| Staff email addresses an owner adds to a server | Giving those people access to that server’s roadmap when they sign in | Legitimate interests of the owner, Art. 6(1)(f) |
| Names an owner writes against steps | Showing the team who is doing what. Never shown to players | Processed on the owner’s instructions |
| A one-way hash of a visitor’s IP address, kept with each vote and each suggestion | Allowing one vote per item per visitor and limiting suggestions to three a day. The IP address itself is not stored | Legitimate interests, Art. 6(1)(f) |
| Suggestions players send, and the in-game name they may add | Passing ideas to the server’s team. Never shown to other players | Legitimate interests, Art. 6(1)(f) |
| A Discord webhook address an owner saves | Posting roadmap updates to the owner’s own Discord channel | Performance of a contract, Art. 6(1)(b) |
| If you buy Pro: your subscription status, the date the paid period ends, and the customer and subscription references Stripe gives us | Switching Pro on and off for your server and letting you manage the subscription | Performance of a contract, Art. 6(1)(b) |
| Card and payment details | Entered on Stripe’s own pages and handled by Stripe. We do not receive or store card numbers | Performance of a contract, Art. 6(1)(b) |
| If you connect a Minecraft server with the WhatsNextX plugin: the names and versions of plugins that were added, removed or updated, the number of installed plugins, the server software version, the time the plugin last contacted us, and the name, old value and new value of each setting that changed in the plugins’ settings files. Settings that look like passwords, keys or tokens are sent as “hidden”, and licence files and player data files are skipped. The owner can switch this off or leave plugins out | Listing changes for the server’s team, so they can add them to the roadmap. Shown to players only if the owner switches that on, and then without version numbers | Performance of a contract, Art. 6(1)(b) |
| Only if the owner switches it on in the plugin: the in-game names of staff who ran the admin commands the owner listed, with the command; LuckPerms permission changes with who made them; and the names in the operator list or whitelist when those files are watched | Showing the server’s team who changed what. Never shown to players. Staff should be told by the owner that this is logged | Legitimate interests of the owner, Art. 6(1)(f) |
| The email address of a player who subscribes to a server’s updates, and whether it was confirmed | Sending that server’s published updates. Only after the player confirmed by email; every email has an unsubscribe link that deletes the address | Consent, Art. 6(1)(a) |
| Comments players write on an update, with the in-game name they may add, and reactions | Showing approved comments and reaction counts on the changelog. A one-way hash of the IP address is kept with each to limit abuse | Legitimate interests, Art. 6(1)(f) |
| Release notes an owner chooses to have rewritten by AI | Sent to Anthropic to be rewritten and returned. Only the title and notes of that update, only when the owner presses the button | Performance of a contract, Art. 6(1)(b) |
| Saved versions of a connected server’s settings files: setting names and values, secrets replaced by a fingerprint | Comparing versions and finding differences between servers. The files themselves stay on the owner’s server | Performance of a contract, Art. 6(1)(b) |
| Ticks per second, memory use and the number of players online on a connected server | The performance chart for the server’s team. A count only, no names | Performance of a contract, Art. 6(1)(b) |
| A one-way hash of the server key that links the plugin to your server | Checking that reports really come from your server. The key itself is not stored | Performance of a contract, Art. 6(1)(b) |
| Your cookie choice | Remembering whether you allowed optional categories | Legal obligation and legitimate interests |
3. What is public
Nothing is public until you switch on the player page in Settings. When it is on, anyone with the link can see:
- your server name and server address;
- every roadmap item that is not marked dropped, with its title, description, category and status;
- the title, due date and done state of each step;
- your announcement, and vote counts if you have switched voting on;
- the updates you published to your changelog, with their notes and the roadmap items attached to them. They also appear in the RSS feed, in the widget you can embed on your own site, and in game;
- with Pro: the tagline, banner image and the Discord, website and store links you saved;
- with Pro, if you switched them on: reactions and approved comments on updates, and a status page showing whether each connected server is checking in. Comments are never public before your team approves them;
- if you switched on “Show recent server changes”: the names of plugins the WhatsNextX plugin reported as added, removed or updated, without version numbers.
A banner image is loaded by each visitor’s browser from the address you gave, so the host of that image can see the visitor’s IP address. Pick a host you trust.
The same information is available as a data feed at the page address followed by /feed.json, so a game plugin or a Discord bot can read it.
Step notes, step owners, dropped items, suggestions, your staff list, plugin version numbers, watched settings, your subscription and your email address are never shown. Switching the page off hides the page and the feed again at once.
4. What we do not do
- We do not sell personal data.
- We do not run analytics or advertising trackers at present. If that changes, they will only run with your consent.
- We do not collect anything about players who only view a public page, beyond the technical logs described above. Voting or sending a suggestion stores the hash described in the table.
5. Who processes data for us
- Supabase: database and authentication. Stores account data and everything you enter. [confirm the project region and sign Supabase’s data processing addendum]
- Stripe: payments for Pro, the same provider VanillaX uses. Stripe handles your card details; we never see them. We receive only a confirmation that a payment succeeded, the amount, and the references needed to keep the subscription in step.
- Anthropic: only when an owner uses AI rewriting. Receives the title and notes of that update. Based in the United States.
- Resend: only for servers with email subscribers. Receives the subscriber’s address and the update being sent. [confirm the provider, its region and its agreement]
- An owner’s own webhook address: if an owner adds an outgoing webhook, reported changes and published updates are sent to the address that owner chose.
- Discord: only if an owner saves a webhook address. Roadmap titles and statuses are then sent to that owner’s Discord channel. Discord is based in the United States.
- Web hosting: [not configured: web hosting provider]. Serves the application and may keep request logs.
Fonts are served from our own domain, not from a third party.
6. Transfers outside the EU/EEA
Whether data leaves the EU/EEA depends on the regions chosen for the providers above. [state the regions and the transfer mechanism, for example standard contractual clauses, once the providers are set up]
7. How long we keep data
- Account data and everything you have entered is kept while your account exists.
- Deleting your account in Settings removes your login, server details, public page, roadmap items and steps from the live database straight away.
- Copies in provider backups and logs are removed on the providers’ own schedules. [confirm backup and log retention periods]
- Records of payments are kept as long as bookkeeping law requires, also after an account is deleted. [confirm the retention period for accounting records]
- Reported server changes: the newest 500 per server are kept, or 5000 with Pro, until the account is deleted. Clearing the Inbox does not delete them; they stay in the timeline. Performance samples: the newest 600 per server.
- Inactive accounts: [decide whether and when inactive accounts are deleted]
8. Your rights
Under the GDPR you can ask to:
- see the personal data we hold about you and receive a copy;
- have incorrect data corrected;
- have your data deleted;
- restrict or object to processing based on legitimate interests;
- receive your data in a portable format;
- withdraw consent to optional cookies at any time, through Cookie preferences.
Write to support.scappix@gmail.com to use any of these rights. You can delete your account yourself in Settings. You also have the right to complain to a supervisory authority; in Denmark that is Datatilsynet.
If a public page on FollowUp Desk X shows personal details about you, contact the server’s owner first, or write to us and we will pass the request on.
9. Security
Access to data is restricted per account by database row-level security, connections are encrypted in transit, and passwords are stored only as hashes by the authentication provider. No system is perfectly secure; tell us at once if you suspect a problem.
10. Changes
We will update this page when our handling of personal data changes and revise the date at the top.