Privacy Policy

Who is responsible

The controller of your personal data is Trisgram s.r.o., Zbrojnická 229/1, 301 00 Plzeň, company ID 10735917 ("we", "us").

You can reach us about anything in this policy at [email protected].

What we collect

Account data: your username, e-mail address and sign-in records from your Trisgram account.

Store data: the games in your library, purchases (the order, game, amount, currency and its status) and product keys you redeem, play sessions and play time, reviews and the games you follow. Each play session is recorded with the platform, the game’s version, a random ID of the device it ran on and, in the Trisgine Play app, a label naming the app and the operating system, such as “Trisgine Play (Windows)”, so the store can tell you on which device a game is already running. The device ID also goes into the licence a game receives, so that the licence works on that device only. The people who run a game see platforms and versions only counted across all its players. We record play sessions and play time for every game you start through the store or the Trisgine Play app, whatever you choose about game data; a game played in the browser without signing in is recorded under that browser’s random ID (play.deviceId). Your card details go to Stripe, our payment provider, and never reach us.

Game data: error and crash reports from the games you play and, only if you allow it, hardware and system details and usage statistics, as the next section describes.

Developer data: the companies and groups you belong to and what you publish through them, such as game pages, builds and news.

Technical data: your IP address, browser and request logs, kept to run and secure the service.

Data from games

Games built on the Trisgine runtime or with the Trisgine SDK can report how they run, in the browser player, in the Trisgine Play app and in desktop builds. There are three kinds of report:

Error and crash reports: the error, where in the game’s code it happened, the game, its version and build, the platform and engine, and the time and play session it happened in. File paths in the error message and in the list of code locations are shortened so that they do not show your user folder. An error report also carries the last steps the game recorded before the error (at most 50, such as “opened the inventory”) and labels its developer attached to the report (at most 32, such as the level being played). These are limited in size, and e-mail addresses and your user folder are removed from them as from the error message.

Crash dumps: a crash may add a crash dump, a copy of part of the game’s memory at the moment it failed. A dump can contain whatever the game held in memory then, which may include personal data such as text you typed, names shown in the game or file paths, and it is not shortened or filtered. Only the game’s developer and we can download a crash dump, to find the cause of the crash, and we delete it after 30 days.

Hardware and system details, only if you allow them: processor model and number of cores, memory, graphics card, its driver and memory, operating system and version, screen size and scale, and language. These details never include serial numbers, network (MAC) addresses, IP addresses, or your device’s or user name.

Usage statistics, only if you allow them: the events a game’s developer chose to count through the Trisgine SDK, such as a level finished. Play sessions and play time are not part of them: the store records those whatever you choose, as described under Store data.

Reports do not include your Trisgram account ID, and we remove e-mail addresses and your user folder from their text; a game’s own messages and crash dumps can still contain what the game showed or held, such as names. Each game knows you under a pseudonymous player ID, different in every game, that only we can link to your account. The player ID keeps your account out of the game, its reports and its tokens. It does not hide you from the game’s developer completely: the people who run a game in the store also see which Trisgram accounts own it, redeemed its keys or reviewed it, because they need that to sell and give access to the game, and in some cases they could connect that with a player ID. Our terms forbid them to try.

You choose under Settings → Privacy & data, for all games or, on a game’s store page, for that one game. A change reaches your games from their next session, within an hour. A game played without a Trisgram account sends error and crash reports only, never hardware and system details or usage statistics; such a game may offer its own switch to turn error reports off.

Connected social accounts

If you are a developer and connect a social account (Facebook Pages and Instagram professional accounts today; other networks later), the network sends us the account's or Page's ID and name and an access token for the permissions you grant.

We store the posts you publish through us, where each one was published and its status on each network.

To show reactions in one feed we fetch the reactions and comments on those posts, including the public name of the person reacting and the text of their comment.

We use this only to publish what you ask us to publish and to show you the reactions. We never post without your action, never sell this data and never use it for advertising.

Why we use it

To provide the store and your account, including the games you buy and the play sessions and play time we record (performance of a contract).

To show the people who run a game in the store statistics about how it is played, counted across all its players and naming no account (our legitimate interest, and that of each game’s developer, in knowing how games are played).

To receive error and crash reports from games and pass them to each game’s developer so that faults get fixed (our legitimate interest, and that of each game’s developer, in games that work; you can object at any time by turning error reports off in Settings).

To receive hardware and system details and usage statistics from games (your consent, which you withdraw by turning them off in Settings).

To turn older game reports into anonymous statistics before we delete them (our legitimate interest in knowing which faults and devices matter; the statistics are built so that individual players cannot be picked out of them).

To connect and publish to your social accounts and show their reactions (your consent, which you withdraw by disconnecting the account).

To keep the service secure and fix faults (our legitimate interest).

To meet accounting and other legal obligations (legal obligation).

Who we share it with

Our hosting and infrastructure providers, who process data only on our instructions. Among them is Cloudflare, which delivers the site and carries game reports to us.

Stripe, which processes the payment when you buy a game and receives what you enter on its payment page, such as your card details. Stripe handles payment data under its own privacy policy.

The developer of a game you play. It receives that game’s reports under a pseudonymous player ID, different in every game, that only we can link to your account, and the people who run the game in the store see which Trisgram accounts own it, redeemed its keys or reviewed it. They also see statistics made from the play sessions of all the game’s players, whether those turned usage statistics on or not: players per day, session lengths, play time, hours of the day, platforms and versions, naming no account. Each developer is a separate controller of the data it receives, responsible for its own use of it. Our terms allow it to use the data only to run, fix and improve its game and forbid it to try to find out who is behind a player ID.

The social networks you publish to, which receive the content you send them and handle it under their own privacy policies.

Authorities, where the law requires it. We do not sell personal data.

How long we keep it

Account and store data for as long as your account exists, and afterwards only as long as the law requires.

Game error reports, hardware and system details and usage statistics for 90 days, crash dumps for 30 days. After that we keep only anonymous statistics made from them, such as how many play sessions met a given error on a given kind of graphics card. They hold no player ID, session, device, IP address or message text, they count by day and build, and any group of fewer than 5 play sessions is left out or merged. They are designed so that individual players cannot be picked out of them.

Your choices about game data and their history, which prove what you agreed to and when, for as long as your account exists.

The record of which player ID belongs to which account number, holding only the game, the player ID and the account number: while your account exists, so that reports, choices and requests under a player ID reach the right account. We delete it together with your account; your orders carry the account number themselves and do not need it.

A connected social account’s token, posts and fetched reactions until you disconnect the account, remove our app from the network or ask us to delete them; then we delete them within 30 days.

Request logs for a limited period needed for security.

Where your data is stored

Our own services that hold your account, store data and game reports run on servers in the European Union.

Some of the providers and recipients named above are outside it; the next section says when data leaves the European Union and how it is protected.

Transfers outside the European Union

Cloudflare, a company in the USA, runs a global network, so the site’s traffic and game reports may pass through its data centres outside the European Union.

Stripe processes payment data in the USA as well as in the European Union.

These transfers rest on the EU–US Data Privacy Framework, where the provider is certified under it, or on the European Commission’s standard contractual clauses in the provider’s data processing terms.

A game’s developer may be established outside the European Union, and that game’s reports then reach the country where the developer is. Our terms set the same duties for every developer, wherever it is.

You can ask us at [email protected] which safeguards apply and for a copy of them.

Cookies and browser storage

We set no advertising, analytics or tracking cookies, so the store asks for no cookie consent. It keeps only what it needs to work, in your browser:

accessToken, refreshToken and user (local storage): your sign-in session, until you sign out.

trisgram-session (IndexedDB): the sign-in tokens already used, so several open tabs do not sign each other out. Deleted when you sign out.

locale (local storage): the language you chose.

myCompany.last (local storage): the company or group the Developer section last opened.

play.deviceId (local storage): a random ID for this browser, so a play session on another device can be told apart.

social.connectReturn (session storage): where to return after connecting a social account; gone when the tab closes.

Cloudflare, which delivers the site, may set a strictly necessary security cookie to protect it from attacks.

A game page's trailer shows a picture loaded from YouTube. The YouTube player (youtube-nocookie.com) loads only when you press play, and YouTube may then store data in your browser under its own privacy policy.

If we ever add anything that is not strictly necessary, we will ask for your consent first.

Your rights

You may ask for access to your data, its correction, erasure or restriction, object to its processing, ask for a copy in a portable format and withdraw consent at any time. Write to [email protected].

You can see and change your choices about game data at any time under Settings → Privacy & data. Turning one off applies from the game’s next session, within an hour; withdrawing consent does not make earlier processing unlawful.

To have your Trisgram account or your game data deleted, write to [email protected]. We do it within one month of your request: we delete the game reports sent under each game’s player ID and your choices about game data. Each player ID is worked out from your Trisgram account number, and the store keeps a record of which player ID belongs to which account number. Deleting your account deletes that record too. The account number itself stays on the records we must keep by law, such as your orders, for as long as How long we keep it says. Anonymous statistics already made from the reports remain; they are built so that individual players cannot be picked out of them.

You may also complain to a data protection authority; in the Czech Republic that is the Office for Personal Data Protection (Úřad pro ochranu osobních údajů, uoou.gov.cz).

The Data Deletion page explains how to remove our app from Facebook and have your social data deleted.

Children

In the Czech Republic you can give consent to the processing of your data yourself from the age of 15; elsewhere in the European Union that age is between 13 and 16, as the law of your country sets it. If you are younger, hardware and system details and usage statistics may be turned on only by your parent or guardian or with their agreement.

When you allow them in the store, it asks you to confirm that you are old enough to agree yourself or that your parent or guardian agrees. It does not check your age in any other way.

Error reports do not rest on consent, and a parent or guardian can turn them off in Settings as well. If we learn that a choice was made for a younger child without that agreement, we turn it off.

Changes

We will publish any change to this policy on this page with a new date, and tell you in the store when a change matters to you.