Privacy

We keep as little as we can get away with, and everything we do keep has a reason you can read below.

Last changed:

Who is responsible

The controller of your personal data is Adam Jurica, which runs the STYGION project from the Czech Republic. Processing follows the General Data Protection Regulation and Czech data protection law.

For anything about privacy, write to [email protected].

We have not appointed a data protection officer; our processing is not of a kind that requires one.

What we collect

If you are only reading

Your choice of language is stored in a cookie so the site does not switch back on you. Nothing else is written to your browser and nothing is measured. The server keeps an ordinary access log: the time, the address requested, the browser, and the IP address it came from.

If you write to us

A message sent from the feedback button carries what you typed and the details listed in the preview before you send: product, page, version, system, browser and language. An image or a capture of your screen goes only if you attach it yourself. Nothing else leaves your device.

If you make an account

A STYGION ID is created through somebody else — Discord, Microsoft, GitHub or Google. We take your identifier there, the name you present, and your email address. We store no passwords at all, so there is nothing here to steal.

Why we are allowed to

  • Language and running the site — legitimate interest in the site working. Without that cookie you would land back in English after every click.
  • Server logs — legitimate interest in security and in being able to trace an outage or an attack.
  • Feedback and tickets — doing the thing you asked us to do.
  • Accounts — performing the service you signed up for.

None of it rests on consent, because none of it is tracking. If we ever start measuring traffic we will ask first, and refusing will be as easy as agreeing.

How long we keep it

Language cookie
A year, or until you clear your browser.
Server logs
Thirty days at most, then deleted.
Tickets and feedback
While the thing is open, then two years so we can pick up the thread.
Account
As long as you have one. Deleting it takes its content with it.

Who else sees it

We do not sell personal data and we do not hand it to anybody for marketing. It is seen by the people on the team who need it to do the work, and by the providers without which the service would not run. When you pay for anything we offer, the payment is processed by Stripe — they handle the money and we receive a confirmation and whatever you chose to tell us about yourself. The rest keep the parts running that you can see: server hosting, protection against attacks, and email delivery — the list is kept current, so if a provider changes, this sentence changes with it. All of them act on our instructions and under contract.

When you sign in through Discord, Microsoft, GitHub or Google, what they do at their end is governed by their own policies. We transfer data outside the European Economic Area only where there is an adequacy decision or standard contractual clauses covering it.

What you can ask for

You can find out what we hold, get a readable copy of it, have it corrected, restricted or deleted, and object to anything we do on legitimate interest. Most of that you can do yourself in your account without writing to anyone: export your data, and delete the account.

If something looks wrong, tell us first — we will fix it faster than anybody else can. You can also complain to the supervisory authority, which is the Czech Office for Personal Data Protection.

Children

The services are not aimed at children under fifteen and we do not knowingly create accounts for them. If we find out an account belongs to a child below that age without a parent's consent, we delete it.

Changes

When the processing changes, this text changes with it and the date at the top moves. We announce anything substantial before it takes effect, here and on Discord.

What the browser stores is set out on the cookies page. The rules for using the services are in the terms.