Updated: October 3, 2026
Privacy policy
How we use your data and how you can exercise your rights in Triverso.
1. Controller and contact
Triverso is a personal project of Iván Cárdenas, Venezuela. For privacy questions, contact [email protected].
2. Data we use
- Online play: nickname, avatar, guest, session and room identifiers, moves and match results. Your opponent can see your nickname, avatar, reactions and result.
- Optional account: Google and Firebase process the identity information needed to sign you in. Triverso associates your Firebase identifier with your account, profile name, avatar, language and time zone. We do not receive your Google password.
- Progress: participants, dates, results, match history and daily activity for statistics and streaks.
- Preferences: language, theme, sound, vibration and measurement options. Your device or browser stores preferences and the data needed to keep you signed in.
- Technical data: IP address when connecting, platform, version, requests and errors needed to provide the service, limit abuse and diagnose problems.
Practice matches are calculated on your device. If usage measurement is enabled, practice events may also be generated.
3. Purposes and providers
We use this data to provide the game, authenticate accounts, retain progress, restore connections, respond to requests and protect the service.
We use AWS Lightsail to host the server and database; Google/Firebase for authentication and, when enabled, measurement through Google Analytics; and Sentry for error diagnosis when configured. Support emails are handled through Gmail. These providers may process data outside Venezuela under their applicable terms and safeguards.
The current version has no purchases or ads. We do not sell your data or use Analytics events for advertising.
4. Measurement and diagnostics
You can change “Share usage statistics” in Settings. Measurement uses events about usage, game mode, language, duration and version; Google may use cookies or installation identifiers and technical data. Our own event parameters do not include your nickname, room codes or invitation links.
Turning this option off stops future usage measurement; it does not automatically erase information sent earlier. Sentry error reports and logs needed to operate the service are separate from Analytics. We apply filters to reduce session data and personal content in diagnostics.
These information pages do not include Analytics, Sentry, tracking cookies or external resources. HTTP requests needed to serve them may be processed by the hosting provider.
5. Retention
We retain your profile and progress while you keep your account and they are needed for those features, until you request deletion. Match results may remain in participants’ histories; when processing your deletion, we remove your identification or delete records that cannot be retained without identifying you.
Sessions, invitations and rooms have operational expiration periods. Expiration does not mean match history has been deleted. Technical and provider logs are retained according to active settings and the need for diagnostics, security and incident handling; you may ask about the retention that applies to your data.
When handling deletion, we review associated data in our systems and with providers. If backups exist, we restrict their use and prevent deleted data from being restored. If a legal obligation or justified security need requires retention, we will explain the reason, affected data and applicable period or criterion.
6. Your requests and deletion
You may request access, correction or deletion of your data through the privacy email. We verify ownership proportionately; we will never ask for your Google password or session tokens.
Requests are handled personally. We will update you on the process and confirm when it is complete. If an obligation prevents us from deleting part of the data, we will explain why. Signing out, switching guests or uninstalling the app does not by itself delete server data.
7. Security and audience
Public connections use HTTPS and WSS. We apply authentication, authorization and session access controls. No service can guarantee absolute protection.
Triverso is intended for a general audience, with particular attention to teenagers and young adults; the public-play pilot admits people aged 14 and over. If you are a minor, use the service with the authorization or supervision required in your country. If you are responsible for a minor and need to ask about or delete data, contact us.
8. Changes
We will publish updates on this page with their date. If the controller changes or our use of data changes substantially, we will provide notice as appropriate. Creating a company in the future does not mean your data has already been transferred to it.
Public-play pilot and protection
When the pilot is available, people aged 14 and over can find an opponent as a guest or with an account. We store your declared age band and the version and date of your acceptance of the rules; we do not ask for your date of birth. The declaration does not verify your identity or enable adult chat. Your opponent cannot see your age band. Online and searching indicators are approximate aggregate counts, without a public directory.
To recover searches and enforce blocks, we retain identity associations, accepted modes and assignments. To support reports, we retain recent encounters with identifiers, nicknames, avatars, mode and dates. A report contains its reason, any description you provide and an encounter copy obtained by the server. Your opponent does not receive the identity of the reporter.
The encounter record used for protection expires after 30 days; that period starts again when the encounter ends. Report evidence expires 90 days after receipt, unless a justified extension with an explicit expiry is recorded, up to 365 days after receipt. Moderation audit records expire after 180 days. These periods do not themselves delete progress history, identity associations, age declarations, acceptance of rules or blocks. You can request their review, correction or deletion through the privacy contact.