Privacy Policy
This policy explains the personal data Pixel Dice handles when providing its website, games, applications, accounts, online functions, support and optional features.
1. Controller and contact
The controller is IVAN MORALES VICENTE Y OTROS SOCIEDAD CIVIL, tax ID J93919835, based in Bilbao, Spain, trading as Pixel Dice Studio. The general and privacy contact is hola@pixeldice.studio.
2. Data we may handle
| Category | Examples | When |
|---|---|---|
| Account and identity | Apple/Google ID, email if shared, internal ID, linked providers and public name | When creating or linking an account |
| Gameplay | Progress, inventory, syncable settings, room, decisions, results, ranking and matchmaking state | When playing or using cloud/multiplayer |
| Technical and security | IP, version, platform, random installation ID, error codes, limited events and push token | When connecting, protecting or diagnosing |
| Purchases | Store, product, transaction ID, state, entitlement and evidence hash | When purchasing or restoring |
| Communications | Email, enquiry content and response | When you contact us |
| AI features | Game variables, public names or pseudonyms, user-entered game-related text and generated content | When the application offers and uses the feature |
3. Purposes and legal bases
Accepting the Terms does not mean consenting to all processing. The policy is acknowledged as information; optional consents are requested separately.
| Purpose | Main basis |
|---|---|
| Create accounts, save progress, run games, matchmaking, rankings, restoration and requested support | Performance of the contract or steps you request |
| Generate requested AI content, manage push permission or other clearly optional features | Performance of the requested feature; consent where required for permissions or other features and capable of withdrawal |
| Security, antifraud, abuse prevention and limited diagnostics | Legitimate interests in protecting users and Services, balanced against their rights |
| Accounting, tax, claims and compliance | Legal obligation or establishment/defence of claims |
4. Accounts, stores and purchases
Apple or Google authenticates the user and provides an identifier, authentication state and, if the user shares it, minimum data such as email. We do not receive the password.
Apple App Store and Google Play process payments, payment methods, billing and store requests. Pixel Dice receives minimum evidence to verify a product, grant entitlements, restore purchases and handle fraud or refunds. We do not store full card numbers.
5. Providers and recipients
We use only the providers needed for an active feature. Not every application uses the same AI providers; the relevant annex identifies the feature, data categories and communication route that apply.
| Provider | Function | Possible data |
|---|---|---|
| Apple | Distribution, IAP, authentication and notifications where applicable | Identifier, purchase, device and push token |
| Distribution, IAP and authentication | Identifier, purchase and technical data | |
| Cloudflare | CDN, security, media or configured storage | IP, request, resource and security logs |
| Railway | API or backend hosting | Account, gameplay and minimum logs depending on the Service |
| Supabase | Authentication, database, synchronization and backend functions | Account, progress, verified purchases and limited technical events |
| Firebase / Google Cloud | Authentication, progress, real-time rooms, leaderboards, functions, protection and analytics | Identifier, profile and image, progress, purchases, room, game state, device and technical logs |
| Generative AI providers (OpenAI, Groq or others identified in the annex) | Narrative, comments or other text when the application offers the feature | Game variables, public names or pseudonyms, decisions, results and game-related text as described in the annex; never passwords |
6. International transfers
Some providers may handle data outside the European Economic Area. Where GDPR applies, a transfer will take place only under a valid mechanism, such as an adequacy decision, Standard Contractual Clauses or another applicable safeguard, together with any necessary supplementary measures.
We do not claim all data remains in the European Union. Annexes and contextual notices will be updated if a provider, region or purpose changes materially.
7. Retention
There is no general rule allowing every account, game or backup to be kept for years. Each retention needs a real purpose and period.
| Data | Period or criterion |
|---|---|
| Account, sessions and progress | While the account exists or until a valid deletion request is completed |
| Temporary rooms and games | For the game and short technical window stated in the annex or game configuration |
| Ordinary logs and diagnostics | 30-day target |
| Fraud or security evidence | Up to 90 days unless an open incident or claim justifies additional blocking |
| AI-feature data | Pixel Dice retains it only for the period and purposes stated in the applicable annex. Provider retention depends on the service and configuration. Guarantees such as `store: false` or Zero Data Retention are prerequisites where the annex requires them; the provider may retain security or abuse logs for up to 30 days where applicable |
| Operational backups | Until overwritten in the provider's documented cycle, without returning deleted data to production |
| Minimum commercial/accounting evidence | Blocked or pseudonymized for up to six years where required for commercial, tax, fraud or claim purposes |
| Support | While handling the enquiry and then only as needed for obligations or claims |
9. Children
Accounts and online features are intended for people aged 16 or over. We do not use the Services to profile or advertise to children.
AI features are subject to the same age-16-or-over requirement. If Pixel Dice later designs a Service for children, it will publish specific rules, checks and controls before processing their data.
10. Rights and complaints
Where applicable, you may request access, correction, erasure, restriction, portability or objection, and withdraw consent without affecting prior lawfulness. Email hola@pixeldice.studio and identify the Service and account without sending passwords, tokens or unnecessary documents.
We may request proportionate verification so we do not disclose or delete another person's data. You may also complain to the Spanish Data Protection Agency or the authority in your country.
11. Security and incidents
We use minimization, access controls, encryption in transit, game separation, server-side credentials and content-free logs. No measure eliminates all risk.
Passwords, OAuth tokens, full receipts, emails, provider identifiers, prompts, AI results and complete snapshots must not appear in ordinary telemetry. If an incident occurs, we will investigate, limit harm and notify where required by law.
12. Account and data deletion
Global deletion removes identity, sessions and linked progress from all games, except minimum pseudonymized commercial evidence or data blocked for a specific duty or claim. Some Services also let you delete only that game's progress.
Account deletion does not automatically refund previous purchases; refund requests are made to Apple or Google where applicable. Data held only on a device must be removed in the app or by uninstalling it as explained in the guide.
13. Versions and changes
Each policy identifies its version and date. We will communicate material changes by a proportionate method. Updating this information does not by itself require renewed contractual acceptance.
We will request new consent if the purpose, data, provider or period of a consent-based feature changes materially. Evidence of Terms acceptance, acknowledgement of this policy and optional consents remain separate.
Optional studio communications
When you voluntarily subscribe, we process your email address, language and evidence of your request, confirmation and withdrawal to send Pixel Dice Studio news, beta invitations and launches. This subscription is independent of your account and acceptance of the terms. It is based on your consent and requires email confirmation.
If you join the Pixel Dice Studio Lab from labs.pixeldice.studio, joining includes these communications: we use the verified email of your Pixel Dice account, keep the text you accepted when joining as evidence and send you a welcome email with instructions for testing the games. You can unsubscribe from the newsletter at any time without leaving the Lab.
We use Resend to confirm addresses, manage contacts, send emails and handle unsubscribes. We use Cloudflare Turnstile to protect the form against abuse. These providers may process the data needed to provide their services under the international transfer safeguards described in this policy.
We retain your address and evidence while you remain subscribed. Unconfirmed requests expire after 24 hours. Unsubscribing stops updates immediately; we then retain your address and evidence for five years after you unsubscribe, restricted to documenting consent and withdrawal and addressing potential liabilities, without using them for campaigns. After that period, an automated process deletes the list data from our database and Resend.
You can unsubscribe from any update without signing in or affecting your games. Deleting a game account does not automatically withdraw this independent subscription. To request erasure of mailing-list data or exercise your rights, use the contact details in this policy.
14. Information by Service
Annex A · Omerta
Handles public name, player code or token, room, decisions, results, matchmaking, push subscription and limited analytics/diagnostic events. Rooms are cleaned after completion or inactivity under backend configuration; the current target is a short one-to-two-day window for finished or inactive games.
When generation through Groq is enabled, it will receive variables, public names, decisions and results for bot comments, summaries or narrative. It will not receive passwords. The integration will be enabled only after the available retention limits, including Zero Data Retention where applicable, and the necessary transfer safeguards have been configured. Groq may retain exceptional reliability or abuse logs for up to 30 days.
Annex B · Malas Artes
Handles room, public name, role, inventory, encounters, decisions, score, matchmaking, push and diagnostics where enabled. Values and payments in the game are fiction, not real financial data.
Games are held for the session and a short technical window for reconnection, support, security and automatic cleanup.
Annex C · Blade Burst
Stores much progress and settings locally. With backend enabled, it may handle anonymous or linked identity, progress, checkpoints, sync queue, scores, leaderboards, diagnostic codes and purchase entitlements.
Account deletion removes identifiable progress. Minimum pseudonymized purchase evidence may remain for restoration, fraud or legal duties. Settings and active games never synchronized remain only on the device.
Annex D · Triq
Triq uses Google Firebase for authentication, cloud progress, multiplayer rooms, daily leaderboards, server-side functions, abuse protection and usage analytics. Firebase Realtime Database stores profiles linked to the user identifier—including name, profile image and title—campaign progress, records and streaks, offers and purchases, daily leaderboards and room data including code, state, players, presence, last activity and results.
Profiles and leaderboards may be shown to other authenticated users; progress, records, offers and purchases are accessible only to their owner. Rooms become subject to deletion after at least seven days without activity through an automated daily process. This period does not apply to account, progress, purchase or leaderboard data. Triq does not use AI features.
Annex E · Blood Scribe
Installed packs, content snapshots, games and books remain local unless a feature expressly says otherwise. Official or imported packs may contain fictional names and text.
The AI narrative is optional, off by default, and Blood Scribe remains fully usable without it. When the user requests it, the app sends only game variables, public names or pseudonyms and user-entered game-related text over an encrypted connection through an ephemeral Pixel Dice proxy. It does not send email addresses, passwords or OAuth identifiers.
The integration will be enabled only if the proxy does not write the content or result to disk, databases, queues, logs, traces or backups and OpenAI has optional storage disabled (`store: false` or equivalent). Pixel Dice will not voluntarily opt into training. OpenAI may retain abuse-monitoring logs for up to 30 days.
The narrative returns to the device and is integrated into a local book that the user may delete or share for personal use. This version does not cloud-sync or automatically publish books or narratives.
Annex F · Neko Snack
When online functions are enabled, Neko Snack handles the account and progress needed for cloud synchronization. The public social leaderboard shows only the chosen display name and score; it never exposes the account or provider UID. 1v1 rooms are private and membership is authorized without revealing provider identity to the opponent.
Room, presence and reconnection data is retained only for the game and the configured technical reconnection and cleanup window. Cloud progress and scores are retained while needed to provide those functions or until the user deletes progress or the account, except for minimum evidence required for security or legal duties.
Deleting progress removes Neko Snack progress and linked scores without itself deleting the account. Deleting the account removes the linked identity and progress under the general deletion process; data that was never synchronized remains on the device and must be deleted there.
If future purchases are enabled in Apple App Store or Google Play, Pixel Dice will verify the product identifier and minimum technical purchase evidence with the store before granting restorable entitlements. It will not publish that evidence or retain the full token or receipt where a pseudonymized reference is sufficient, except where legally required or needed for fraud prevention.
Neko Snack is the current commercial name of the Service with the stable technical identifier gato_nevera. This naming change does not by itself alter rights, data, purposes, scope or retention.
Annex G · Croma
Croma stores gameplay progress, records, campaign state, preferences and other local settings on the device. When account and synchronization features are enabled, it may handle the account identifier, visible name and progress needed to maintain a cloud copy.
Leaderboards, challenges and online rooms, when enabled, may handle the visible name, room, presence, game configuration, results, scores and limited connection and diagnostic data. Online features may remain disabled during internal testing.
Promotional codes and verified purchases may handle the entered code, granted entitlements, product identifier and the minimum technical evidence needed to verify or restore a purchase. Pixel Dice avoids retaining full tokens or receipts where a pseudonymized reference is sufficient, except where legally required or needed for fraud prevention.
Notifications and error reporting are enabled only when configured. Croma does not use generative AI features. Data that is never synchronized remains on the device and must be deleted there; account deletion follows the general process described on this site.
If you have any questions, email hola@pixeldice.studio