This policy explains what data the FSON site may use, why it is needed, and how a user can manage it.
The project may use data entered by the user: email address, login name, support-tier information, and support-related requests.
It may also use page visit information, actions on the site, and general device parameters when needed for safety and stable site work.
Data is used for account access, support tiers, communication with the user, site protection, and improvement of the user path.
The project does not use data for goals unrelated to site work and FSON growth.
Data is stored only to the extent necessary for project work and user actions.
The project takes reasonable protection measures and limits access to such data where needed.
Data may be transferred to third parties only when needed for live user scenarios after launch, or when required by law.
Before live scenarios are connected, the matching screens may exist only as prepared visual states.
A user may request clarification, update, or deletion of their data within the limits compatible with project work and applicable requirements.
The current contact route for data questions will appear together with the launch of account space and paid tiers.
The same backend session is used by the site, launcher, and OAuth sign-in.
Or continue with
Google and Discord can be linked to this same local account.
Free
₽250 / month
₽500 / month
₽1000 / month
For now, you can review what the tier includes and return to the list. Real checkout will open later.
The site is already prepared for this path. For now, you can browse the project, download the launcher, and choose a support tier.
The button is already in its final place. Once the file is published, the download path will open without rebuilding the site.
The page already shows the tiers and what they include. Real payment will be added later without breaking the user path.
Once checkout goes live, this is where a calm waiting state will appear without feeling broken.
After payment goes live, this is where the clean success state will appear.
If something goes wrong, this is where the honest non-empty fallback state will appear.