1.1 Registration and authentication
- Email: collected in plaintext, used for authentication, transactional communications, and service notifications. Legal basis: performance of contract.
- Password: never stored in plaintext or retained in memory beyond the hashing operation. Stored as an Argon2id hash with a random salt (64 MB memory, 4 threads, 32-byte key, PHC format). Legal basis: performance of contract.
- Google identifier (Google sub): collected upon sign-in via Google OAuth. Email and Google identifier stored in plaintext. No Google token is retained by Omiros. Legal basis: performance of contract.
1.2 Twitch data (OAuth connection)
Upon Twitch connection or integration, the following data is collected from the Twitch API and stored in Omiros's database:
- Twitch ID, login, display name, account type, broadcaster type, channel description, profile image URL, offline image URL, view count — stored in plaintext.
- Twitch access token and refresh token: encrypted via an additional AES-256-GCM layer applied by Omiros before storage, in addition to Twitch's native encryption. The encryption key is a private key managed by Omiros. These tokens are accessible only to Omiros's backend service for the purposes of operating the Service. Legal basis: performance of contract, OAuth consent.
The Twitch OAuth scopes requested vary according to the User's plan. The exhaustive list of permissions is presented to the User at each consent request before any authorisation is granted.
1.3 Public profile data (Bento Page)
- Display name, bio, social and sponsor links, custom modules, uploaded images and media — stored and displayed publicly according to the User's chosen settings. Legal basis: performance of contract, consent for public publication.
1.4 Connection and security data
- IP address: collected and stored in the database in INET format. Purposes: session management, rate limiting, detection of suspicious sessions, and potentially geoblocking in the future. Legal basis: legitimate interest (service security).
- Session data: technical information necessary for managing authentication sessions. Legal basis: performance of contract.
1.5 Technical data (logs)
- Error and activity logs are generated by the infrastructure (Render). These logs are used for debugging and maintenance purposes. They are not stored in Omiros's database and are subject to Render's retention policies.
1.6 Billing data
- Omiros retains technical Stripe identifiers (payment session ID, subscription ID, status, price ID). No banking data is stored by Omiros. The full billing history is accessible from the operator's Stripe dashboard. Legal basis: legal obligation (10-year accounting retention).
1.7 Discord integration data
- Discord server identifier (guild_id), announcement channel identifier, clips channel identifier, bot status, notification status, invitation date, secure technical invitation token. Legal basis: performance of contract, consent.