CueArrena Privacy Policy

Effective: 2026-09-06  ·  Last updated: 2026-09-06  ·  Applies to: the CueArrena mobile app, dev.cuearrena.com, and the CueArrena real-time game platform

This policy explains what personal data the CueArrena game platform collects from you, why we collect it, how we use and share it, and the rights you have over it. It covers the CueArrena mobile app for players, the developer portal at dev.cuearrena.com, and the real-time servers that host live games.

1. Who we are

"CueArrena", "we", "us", or "our" refers to the operator of the CueArrena platform, reachable at privacy@cuearr.com. CueArrena is a scan-based multiplayer game platform built on top of the CueArr QR-code system. We are based in Canada and host our services in Microsoft Azure's Canada Central region.

For the purposes of privacy law, we are the data controller for information collected about you as a player of the CueArrena app and as a developer using the CueArrena portal. Where we process data on behalf of a third-party game developer (see §8), we act as their data processor.

2. What this policy covers

This policy applies to:

• The CueArrena mobile app for Android and iOS (game player experience).
• The CueArrena developer portal at dev.cuearrena.com.
• The CueArrena real-time servers that host live game instances.
• Push notifications, transactional emails, and account management flows tied to your CueArrena / CueArr account.

It does not cover:

• The CueArr product ecosystem at cuearr.com — see the separate CueArr privacy policy.
• Individual games built by third-party developers on our platform — see §8 for how those interact with your data.
• Third-party sites, apps, or services that CueArrena or its developers may link to.

3. What data we collect

Our design principle is collect only what a scan-based multiplayer game needs to run — data is processed for the game and discarded when the game ends. We do not build long-term behavioural profiles.

3.1 Account data

• Email address and (optionally) a display name / username — supplied at sign-up. Your CueArrena login is the same as your CueArr account; both apps read from a single account record.
• Password hash — never stored in plaintext; stored as a bcrypt-family hash.
• Multi-factor authentication (MFA) secrets if you enable MFA — encrypted at rest with a key held separately from the database.
• Authentication tokens (JWTs) issued to your device for the duration of a session. Stored on your device in the OS secure keystore (Android Keystore / iOS Keychain).

3.2 Profile data

• Avatar photo, if you upload one (see §6).
• App preferences: sound-effect on/off, vibration on/off, push notifications on/off, default CueArr selected for gaming, distance units.
• Friends list: links between your CueArrena account and the CueArr accounts of players you have added as friends (surfaced from cuearr.com).

3.3 Device & technical data

• Push notification device token issued by Firebase Cloud Messaging on Android and Apple Push Notification service on iOS, so we can deliver "you got tagged" and "game ended" alerts.
• Device OS + app version — for compatibility gating and crash triage.
• IP address — recorded in short-lived server logs for abuse mitigation and security investigations.

3.4 Gameplay data

• Which game instances you join, when, and when you leave.
• Scans you perform — the CueArr you scanned, the timestamp, and (when the game requires it for anti-cheat) your approximate location at scan time.
• Chat messages you send inside a game.
• Script-managed per-player fields — game scripts (whether ours or a third-party developer's) may write role, score, immunity state, and similar values against your player record for the duration of an instance.

4. Location data

Some games use location for gameplay reasons — a game may define a physical geofence that players must stay inside, or require a scan location to be within a certain distance of the CueArr being scanned (anti-cheat).

The CueArrena app requests location in one of two levels; you choose which to grant via the OS system prompt, and you can change your mind at any time in the CueArrena app's Preferences or your device's Settings.

• While Using the App — the default. Position is collected only while the app is open on screen; stops the moment you close or background it.
• Always — only for games that declare a need for it (for example a hide-and-seek game that needs the hider's position to keep updating while their phone is in their pocket). We show you why the game needs it before you're asked to grant.

• Location is never collected outside an active game session.
• Location precision is used at the resolution the game requires (typically ~10-50 meters) and is not combined with any advertising identifier or sold.
• You can revoke location access at any time; games that require location will simply reject the actions that need it.

5. Camera & scan data

CueArrena requires camera access to scan physical CueArr QR codes during a game. The camera is used only while the in-app scanner is open. We do not record video, capture stills, or retain the camera stream — the QR is decoded on-device and only the resulting scan token is sent to our servers.

6. Avatar photos

You may optionally upload a photo, or generate an avatar, to be used as your icon in games. If you do:

• Uploaded photos are resized server-side to a maximum of 512×512 pixels, re-encoded as JPEG, and stored on our CDN. EXIF metadata (device model, GPS coordinates, capture timestamps) is stripped during re-encoding.
• Your avatar URL is derived from your user ID and is public in the same sense that most social-app avatars are — anyone who can see you in a shared game has your player ID and can fetch the image directly.
• You can replace or delete your avatar at any time from the app's Settings screen. Deletion removes both the CDN file and the database record.

7. Data inside a game session

During a live game your device connects to a real-time server that runs the game's logic. The following data flows across that connection:

• Your player ID, display name, and avatar URL are broadcast to the other players in the same game instance so they can see who's playing.
• Actions you perform (scan, button press, chat, text input, in-game photo capture) are sent to the game server, which applies them to the game state.
• The game server projects a per-player view of the game state and sends it to you and the other players; entries intended only for one player (private toasts, hidden roles managed via server-only state) are stripped from every other player's projection.

When you leave a game, per-player data the script stored in server-only ("private") state is cleared. Public state may persist for the lifetime of that game instance.

8. Third-party developer games

CueArrena is an open platform: independent developers can publish games that other players join. When you join a developer's game:

• The developer's game script sees the same per-player data the CueArrena runtime sees: player ID, display name, avatar URL, and any actions you perform within their game.
• Scripts run inside a hardened per-instance sandbox with strict limits on memory, CPU time, and network access. They cannot read your email, your friends list, your device token, your IP, or data from any game session other than their own.
• Developers can send in-game push notifications to their instances' players via CueArrena's broadcast API. The notification content is written by the developer.
• Developer scripts declare the OS permissions they need (for example "always location") via a template setting. The CueArrena app shows you the dev's own explanation before firing any OS prompt so you can decide with context.

For data that a developer's script chooses to store during your session, we act as the developer's data processor. If you need to exercise rights specifically over that data, contact us at privacy@cuearr.com and we will route your request to the responsible developer.

9. Doubloons (in-app currency)

CueArrena has an optional in-app currency called doubloons, used to make private-instance games or buy in-game shop items published by game developers.

• Wallet ledger — every credit and debit is recorded with a source ("welcome bonus", "game_award", "private_instance", ...) plus a timestamp, so you can see where doubloons came from and went. Kept for the life of your account plus 7 years for financial audit.
• Doubloons have no cash value and are not redeemable for cash. See the Terms & Conditions for the full doubloons policy.

10. Why we collect it & legal bases

Under the EU GDPR / UK GDPR, we rely on the following legal bases:

• Contract — account data, gameplay data, and device tokens are needed to provide the service you asked us to provide (letting you play games on CueArrena).
• Legitimate interest — anti-cheat logs, abuse-mitigation IP logging, and security telemetry, balanced against your reasonable expectations of a fair game.
• Consent — for location access (granted via OS permission), for push notifications where the OS requires consent, and for optional avatar upload.
• Legal obligation — where we are required to retain records (e.g. financial or compliance).

11. Sub-processors & sharing

We share data only with the parties needed to operate the service:

• Microsoft Azure (Canada Central) — hosts our application servers, databases, and CDN origin.
• Google Firebase Cloud Messaging — delivers push notifications to Android devices.
• Apple Push Notification service — delivers push notifications to iOS devices.
• Mailjet (a Sinch company) — sends transactional emails such as email verification and password reset.

We do not sell or rent personal data to any party, we do not use it for advertising, and we do not share it with any party not listed above except when compelled by valid legal process, in which case we limit disclosure to what the process actually requires.

12. How long we keep data

• Account data — for as long as your account is active. When you delete your account, we delete or anonymize account data within 30 days, except records we are legally required to retain (see below).
• Gameplay data — game instances are disposed after they end or after idle timeout. Public state is deleted with the instance. Aggregated / anonymized play statistics may be retained indefinitely.
• Location data — only in-memory during the active game session; the anti-cheat scan log retains a coarse location stamp for up to 30 days for dispute resolution and is then purged.
• Chat messages — for the lifetime of the game instance in which they were sent.
• Server logs containing IP addresses — up to 30 days, then rotated out.
• Financial records (wallet ledger, purchases) — 7 years, per applicable tax and accounting requirements.

13. Security

• All traffic between your device and our servers uses HTTPS / WSS with TLS. Real-time game connections use WebSockets exclusively (no long-polling fallback) so authentication tokens never appear in URLs.
• JWT access tokens on your device are stored in the OS-provided secure keystore (Android Keystore / iOS Keychain), not in plaintext preferences.
• Passwords are stored as bcrypt-family hashes; the plaintext is never persisted.
• MFA secrets are stored encrypted at rest with a key held in the runtime environment (not in the database).
• Sensitive server-side secrets (database credentials, JWT signing keys, third-party API keys) are held in environment variables that are only readable by the application process.
• Third-party game scripts run in a per-instance V8 isolate with strict memory, CPU-time, and network limits so a misbehaving or hostile script cannot exfiltrate data or affect other games.
• Data at rest is stored on encrypted volumes in Microsoft Azure Canada Central.

No system is 100% secure. If you believe your account has been compromised, contact security@cuearr.com.

14. Your rights

Depending on where you live you may have some or all of the following rights over your personal data:

• Access — request a copy of what we hold about you.
• Correction — ask us to correct inaccurate data.
• Deletion — ask us to delete your data ("right to be forgotten"). See §15 for the in-app deletion flow.
• Portability — receive your data in a structured, machine-readable format.
• Objection — object to certain kinds of processing (e.g. legitimate-interest-based).
• Withdraw consent — for any processing we do on the basis of your consent, at any time.
• Complain — to your local data protection authority (in the EU, your national DPA; in the UK, the ICO; in Canada, the Office of the Privacy Commissioner; in California, the California Privacy Protection Agency).

To exercise any of these rights, email privacy@cuearr.com from the email address on your CueArrena account. We respond within 30 days; verification requirements may apply.

California residents under CCPA / CPRA also have the right to know what categories of personal information we collect, from whom, and for what purpose (all disclosed above), and the right not to be discriminated against for exercising these rights.

15. Deleting your account

You can delete your account at any time. Because your CueArrena login is the same login as your CueArr account, deletion is handled once and removes access to both:

• In the CueArrena mobile app, open Settings → Preferences and tap Delete account. You'll be walked through the confirmation flow and asked to re-enter your password.
• You can also delete directly at cuearr.com/account/delete.

When you confirm, we mark your account for deletion and remove or anonymize your personal data across CueArrena and CueArr within 30 days. Aggregated / anonymized statistics that no longer identify you may be retained. Records we are legally required to keep (see §12) are held for their statutory retention period and then deleted.

16. International transfers

Our primary data storage is in Canada. Sub-processors listed in §11 may process data in other countries (for example, Firebase may route push notifications through Google infrastructure in multiple regions). Where required, we rely on the receiving party's compliance framework (adequacy decisions, Standard Contractual Clauses, or equivalent) to ensure your data continues to receive protection consistent with this policy.

17. Children

CueArrena is not directed at children under 13. We do not knowingly collect personal information from anyone under 13. If you are a parent or guardian and believe your child has provided us with personal information, contact privacy@cuearr.com and we will delete the information promptly.

Where local law requires a higher minimum age (e.g. some EU member states set the digital-consent age at 16 under GDPR), that local minimum applies.

18. Cookies & local storage

The CueArrena mobile app does not use cookies. It stores your authentication token in the OS secure keystore and non-sensitive preferences in the app's local storage sandbox.

The developer portal at dev.cuearrena.com uses first-party session cookies strictly necessary to keep you logged in and to protect against CSRF. It does not set marketing, analytics, or cross-site tracking cookies.

19. Push notifications

We send push notifications for gameplay events such as being tagged in a game, a game you're in ending, or a broadcast message from a game's developer. To do so we register your device with Firebase Cloud Messaging (Android) or the Apple Push Notification service (iOS), which returns a device token that we store against your user account.

You can disable push at any time from your device's OS settings or from the CueArrena app's Preferences. Disabling push does not affect your ability to play games.

20. Tracking & advertising

CueArrena does not use any third-party analytics or advertising SDKs. We do not collect the iOS Advertising Identifier (IDFA), the Android Advertising ID, or any equivalent cross-app tracking identifier. We do not display ads, and we do not participate in any cross-service tracking or data-broker network.

21. Changes to this policy

We may update this policy from time to time. Material changes will be surfaced in the app on next launch and, where we have your email on file, communicated by email at least 14 days before they take effect. The Last updated date at the top of this page reflects the most recent revision. Previous versions are available on request.

22. Contact

Questions, requests, or concerns about this policy or the data we hold:

• Email (privacy): privacy@cuearr.com
• Email (security): security@cuearr.com
• Web: cuearrena.com  ·  cuearr.com  ·  dev.cuearrena.com