← FLUXION INTERACTIVE

Privacy Notice

Last updated 19 October 2026

This explains what personal data Fluxion Interactive collects, why, and what you can do about it. It covers this website and the Developer Portal used by the studio's team.

The short version. The public website collects nothing. If you contribute to a project, we hold your name, email, work records and payment details because we need them to credit and pay you. If you record voice lines for us, we hold those recordings for the game they were made for. We don't sell anything to anyone, and we don't run advertising or analytics trackers.

Who is responsible

Fluxion Interactive is a sole trader business operating under the professional name Flux Saloris, based in the United Kingdom. For data protection purposes, Fluxion Interactive is the data controller.

To contact us about anything in this notice, email contact@fluxioninteractive.net.

Visiting the public website

Browsing the public pages does not require an account and we do not set analytics or advertising cookies. Our hosting provider, Cloudflare, processes technical connection information such as IP addresses in order to deliver the site securely and to block attacks. That processing is necessary for the service to work and to keep it safe.

Everything the pages show — text, images and fonts — is served from this site's own address, so reading them does not make your browser contact any other company. The site remembers your light or dark theme choice in your own browser; that never leaves it. The studio's announcements (the megaphone in the corner, and the Announcements section of the homepage) are fetched from this site without cookies, and nothing about who is reading them is recorded; your browser keeps only the number of the newest announcement it has shown you, so it can say when there is something new. That never leaves it either. During a special event (Halloween, say), the pages ask this site which event is showing — again without cookies, and the answer is the same for everyone — and your browser keeps that answer so the next page opens in the right colours, along with whether you paused the moving decorations and the date the homepage's welcome screen last played, so it plays at most once a day. None of that leaves your browser, and none of it is about you. When a link to the site is shared, apps such as Discord fetch the homepage to make a preview; the site tells them apart by the name their software sends, only so the edge of that preview can be drawn in the right colour, and keeps nothing. In the Developer Portal your browser also remembers your seasonal-theme choice, so the page opens in it, and, for the chat, whether it is open, where you put it and how big, which conversation you were in, whether pop-up previews are on, and the number of the newest message it has popped up for each conversation — never what anyone wrote. That never leaves it either, and signing out clears the conversation and the numbers.

If you open a signing link (as a contributor's substitute — see the table below), the page takes the secret part of the link out of the address bar as soon as it has read it, so it is not left in your history or on your screen, and keeps it only in that browser tab so a reload still works. Closing the tab forgets it.

If you contribute to a project

Contributors have an account on the Developer Portal. We hold the following:

WhatWhyHow long
Name or handle, email address To identify your account and contact you about work While you contribute, then 6 years
Password (stored only as an irreversible hash) To let you sign in. It cannot be read back by anyone, including us Until your account is closed
Profile picture and display colour, if you set them, and your choice of look (light or dark, and whether special events show in the portal) So your work is identifiable on shared boards, and the portal looks the way you chose on every device Until you change or remove them
Record of tickets claimed and completed To calculate contribution shares under your agreement 6 years, as the payment record
Two cookies set when you sign in: one keeps you signed in (it expires after 3 hours idle), and one marks your browser as one you have used before Security. The second lets you sign in even while someone else is guessing at your password, because browsers without it are held back Session: until you sign out or it expires. Browser marker: 400 days
A third cookie, set when the sign-in screen opens: a random marker for that browser Security. If a browser gets the password wrong too many times, the block can follow the browser and not only its internet connection 400 days
Wrong passwords on the sign-in screen: the address tried, the time, the IP address, the approximate place and network provider that address belongs to (as reported by our hosting provider, Cloudflare), and the type of browser and device. A browser and address blocked from signing in after too many, and when the block was lifted Security — to tell the studio someone may be trying to get into an account, and to stop them. We never record the password that was typed About 13 months (400 days), then deleted automatically. A block stays until it is lifted, and is then kept for 400 days
The roles you hold on the team, and any role you apply for: your reason and any links you add to your work To decide which work you can pick up, and so the studio can consider your application While you are on the team; both are deleted when you are taken off it
Files you hand in on a ticket, with your name, the file's name and size, and when you handed it in; and, if you open or download a file the studio has made available to you, a record of that So the studio receives and can use your work. Everyone on the ticket sees each file listed, but only the studio and anyone it employs full-time can open or download it — not other contributors, and not you once it is handed in, so keep your own copy. Every time someone other than the studio opens a file, it is recorded For as long as the studio uses the work. Once your work is in the game, the studio keeps it in the game's own version-control system on the studio's computer, with private backup copies kept with Cloudflare, for as long as the game is kept; it may then remove the copy on this site. A file the studio removes from this site, or that is on a ticket that is deleted, is erased from it at once. The record of who opened a file is kept with the activity log (about 13 months). If a file holds your personal data — a recording of your voice, for example — you can still ask for a copy of it
Comments you leave on a design document So the studio can read and act on your feedback Until you or the studio delete them
Messages you post in the team chat — in the team channel, a game's channel, or a direct message — with your name and when you posted them, and when you last read each conversation So the team can talk while it works. A channel is read by everyone it is for, and by the studio. A direct message is read only by the two people in it: the studio sees one only if one of you reports it, and then only the reported message and up to three before it. The newest line of a conversation is shown to the people who can read it — in the chat's list and, unless you turn them off, in a pop-up beside the chat bubble; it is worked out when it is shown and not stored anywhere else. The Announcements channel is different: only the studio and team leads post in it, and what is posted there is also published on the public website — a team lead's post signed “Fluxion Interactive”, never with their name. Who posted each one is kept in the activity log, and the studio is notified, with the start of the post, when a team lead posts one. The studio can hide an announcement from the website without deleting it, take one down, or pause announcements altogether — for instance if a team lead's account may have been misused — and every such step is logged. Files cannot be sent in the chat — work is handed in through its ticket 12 months, then deleted automatically. A message you delete is erased at once. If you leave the team, what you wrote stays until its 12 months are up
A message you report in the chat: a copy of it (and, for a direct message, of up to three messages before it), your name and the reason you give So the studio can deal with a message that should not be there, and show what it acted on 12 months
When you last took part: the date of your latest ticket move, comment, note, chat message, ticket request or role application (signing in and profile changes are not counted) Your agreement asks that you do not go silent for long. If 30 days pass with nothing, the studio checks in with you in writing before anything else happens Worked out from the records above when the roster is opened; not stored separately
Sign-in times and IP addresses in the activity log, including failed and held sign-ins Security — detecting unauthorised access to accounts, and being able to show afterwards what happened About 13 months (400 days), then deleted automatically
Payment details you enter in the Developer Portal — the name on the account and its sort code and account number, IBAN, or the other way you ask to be paid — your VAT number if you are registered, and when you last changed them To pay you what you are owed, and to issue your statements correctly. They are stored encrypted, and no one but you and the studio can see them: you see them masked, and every time the studio looks at them it is logged. Payments wait three days after a change, so anyone who got into your account could not quietly redirect your money; you and the studio are told of every change While you are owed anything or might be, then 6 years for tax records; at once if you remove them and nothing is owed
A statement for each payment made to you: the payment, the months it covered, how your share of each was worked out, and your VAT position Your agreement entitles you to one (clause 7.8), and it is part of the tax records 6 years after the end of the tax year the payment was made in
The name you choose to be credited under — your handle, another name, or none To credit your work as your agreement promises. Only that name, and the roles on your finished work, are published — under each game you worked on, on the public website and in the game's credits. Choose “none” and nothing about you is published For as long as the game is credited, including after you leave; you can change it at any time in the portal
Work offered to you by name, and your answer, with any reason you give for declining So you can choose which work to take on, and the studio knows The offer: until you answer, or a week. Your answer: in the ticket's history, and the activity log (about 13 months)
The payment log and the studio's bank statements, which show your name, the amounts paid to you and the payment reference, and the working kept with each pay run: each month's figures, your points and how your share was worked out To prove what was paid, match payments to what was owed, and keep the tax records the law requires 6 years after the end of the tax year the payment was made in
Right to work check records, if we check your right to work in the UK: a copy of the document you show us, or the result of an online check, and the date Legal obligation — the rules on preventing illegal working, which from 1 October 2026 can apply to individual contractors as well as employees While you work with us, then 2 years
Agreements you have signed, and the record of signing: the legal name you typed, the date and time, your IP address, your browser's identifier, a fingerprint of the exact document version, a drawn mark if you added one, and the name you had chosen to be credited under and your VAT number at the time To prove what was agreed, by whom and when. A signature nobody can verify afterwards is not worth having, for either of us Kept permanently — see below
Voice recordings, if you perform lines for a game — every take you send, and the scripts and direction we send you To make and promote the game you recorded for. We never use a recording to identify you, and never to train, clone or generate a synthetic voice Lines used in a game: for as long as that game is available. Takes we did not use: only for that game's production, never for anything else
Requests to check your statements, the date, any note you add, and what the check found To answer the check within the 30 days your agreement allows, and to prove we did 6 years, with the payment records they relate to
If your agreement ends: how and when it ended. If it was ended for cause, the part of the agreement relied on and the date the notice was sent — never the details of an allegation. If your access was paused while something was looked into, the dates To pay you correctly for the months that follow, and to establish or defend any legal claim about how it ended 6 years after the agreement ends
If you decline an agreement in the Developer Portal: your name and email, which agreement and version, when, and the reason you give if you give one. Unless you have a separate agreement with us that carries on, your account, picture, roles and notices are deleted at the same moment, and any open ticket requests are closed; your work, points and payments are kept as in the rows above So the studio knows the invitation was declined and what it did; if you had signed before, it is also your notice to leave, and the record of when your agreement ended The note of the decline: 12 months. If it ended an agreement, the record of how it ended is kept as in the row above
If you sign as a contributor's substitute, through a signing link: your name, handle and email address, the contributor you stand in for, the tickets and start date, and the record of signing — the legal name you typed, that you confirmed you are 18 or over and agreed, the date and time, your IP address, your browser's identifier and a fingerprint of the exact agreement. You do not get an account, and nothing else is kept about you To prove that the work you did for the ticket belongs to the studio and that you agreed to keep its information confidential — which is all a substitute's agreement does The record of signing: permanently, like every signature record (see below). The link itself stops working once used, or after 14 days
Postal address for service, if you provide one Only for formal legal notice, as set out in your agreement While the agreement is in force, then 6 years

Why we are allowed to hold it

Signature records are permanent, and that is deliberate

Everything else in the table above can be corrected or deleted on request. Signature records cannot. They are the evidence that an agreement was made, and a record that can be quietly edited or removed afterwards would be no evidence at all — which would cut against you as much as against the studio.

So the system is built so that they can only be added to, never altered or erased. Superseding an agreement with a new version leaves the old signature standing beside it rather than replacing it. If you ask us to delete your data, we will delete everything we are not required or entitled to keep, and we will tell you plainly that the signature records are staying and why. UK data protection law allows this where records are needed for the establishment, exercise or defence of legal claims.

You can read any agreement you have signed at any time, and download a certificate of your own signing record, from the Agreements section of the Developer Portal. If you signed through a signing link, the page you signed on gave you your record to keep; for another copy, email contact@fluxioninteractive.net.

Who else sees it

We do not sell personal data and we do not share it for marketing. It is handled by:

Other contributors on a project can see your display name, avatar, colour and the tickets you hold. They cannot see your email address, bank details or address.

Where your data goes

Some of these providers are based outside the United Kingdom, or store data outside it — Cloudflare is a United States company. That means some of your personal data is transferred out of the UK.

Where it is, we rely on the safeguards in each provider's own data processing terms — the UK International Data Transfer Addendum, or the UK extension to the EU Standard Contractual Clauses — which are the transfer mechanisms UK law recognises. We do not transfer personal data to any provider that does not offer one. If you would like to see the specific terms we rely on for any provider, email us and we will send them.

Cookies

The Developer Portal sets two cookies when you sign in: one keeps you signed in, and one marks your browser as one you have used before, so your account stays usable even while somebody else is guessing at its password. A third is set when its sign-in screen opens: a random marker for that browser, so that if it gets the password wrong too many times the block can follow the browser and not only its connection. All three are strictly necessary for the service to work securely, so they do not require consent. Each holds a random identifier and nothing about you. The public pages set no cookies of ours, and we do not use analytics, advertising or tracking cookies anywhere on this site.

Your rights

Under UK data protection law you can ask us to:

Email us and we will respond within one month. There is no charge.

Complaining

You have the right to complain to us about how we have handled your personal data. Email contact@fluxioninteractive.net, or raise it any other way you reach the studio — there is no form to fill in. We will acknowledge your complaint within 30 days, look into it, keep you told how it is going, and tell you the outcome without undue delay.

You can also complain to the Information Commissioner's Office at ico.org.uk. Complaining to us first is not required, but it is usually the quickest way to put something right.

Changes

If this notice changes materially we will tell contributors directly rather than relying on you noticing the date at the top.