Legal

Privacy Policy

Effective November 9, 2026

1. Operator and scope

WordPoise is independently developed and operated by Debartha Chakraborty , based in Bengaluru, Karnataka, India. This policy explains how WordPoise handles information when you use its mobile apps and public website. For privacy questions, contact support@wordpoise.com .

2. Age, family-friendly play, and local-only experience

WordPoise is a family-friendly word puzzle game, primarily suited to ages 9 and above; younger children may enjoy local play with appropriate guidance. For the first release, under-18 players are intended to have local-only Daily Journey, Practice, and progress. Online accounts, Google Sign-In, cloud synchronization, and online Duels are intended for adults aged 18 or older. Available features depend on the app version and whether they have been released.

For the first mobile release, WordPoise is being designed to use a neutral age assessment before enabling online accounts. The assessment helps determine which features may be offered; it is not independent proof of age. No Firebase account is needed for local-only play, and online account features are intended only for adults.

Local-only play is designed to keep puzzle progress on the device without requiring online authentication, personalized advertising, or online interaction with other players. Website visits and contact emails can still generate ordinary technical or correspondence records. Parents and guardians may contact support@wordpoise.com about privacy or local data. WordPoise does not offer parent-managed online child accounts in its first release.

3. Information we process

The information processed depends on whether you play locally or enable eligible online functionality. It can include:

An anonymous Firebase account is not anonymous in every privacy-law sense: it has a Firebase UID and may be associated with a WordPoise account and gameplay information. WordPoise does not use hardware identifiers or advertising identifiers as account IDs.

How we use information

We use information to operate the game and website, maintain eligible online accounts, preserve gameplay progress where supported, secure the service, address support and deletion requests, and meet legal obligations. The public website does not include advertising, analytics, or marketing-tracking scripts. Infrastructure providers may generate operational request records. WordPoise does not use player profiles for targeted advertising.

4. Google Sign-In and Firebase Authentication

Google Sign-In is intended for eligible adult online accounts. Authentication uses the basic openid , email , and profile permissions. Google and Firebase Authentication may receive, process, or retain your Google account identifier, email address, profile name, profile picture, Firebase UID, and authentication/session information needed to sign you in. WordPoise does not request access to your Gmail messages, Google Drive files, contacts, or other Google account content.

When a player enables an online account, the WordPoise backend uses a verified Firebase UID to associate gameplay with an internal WordPoise account. Your WordPoise display name and built-in avatar are separate from your Google profile. The intended application database stores the account identifier, WordPoise profile, and relevant gameplay records, but not independently saved Google OAuth access or refresh tokens. Authentication SDKs may securely maintain credentials on your device. Authentication tokens should not be included in support messages.

You can use local play without connecting Google. If you choose to sign in, Google and Firebase process information under their applicable policies as well as the practices described here.

5. Local information

Local play can store puzzle sessions, guesses, results, game history, statistics, appearance preferences, eligibility preferences, and other settings needed for the app on the device. Local data may be removed through supported in-app controls when available, by clearing app data, or by uninstalling the app, subject to operating-system backups and device settings. Local-only data is not promised to be recoverable across devices.

6. Eligible online gameplay

For adult online accounts, WordPoise may process relevant gameplay information through its backend to operate Daily Journey, account synchronization, Duels, statistics, and account integrity. Limited match information, such as a player’s WordPoise display name, avatar, game activity, and match result, may be visible to an opponent as needed to operate a Duel. WordPoise does not offer unrestricted chat or public social profiles.

7. Service providers

WordPoise uses or relies on the following service providers for the functions described in this policy: Firebase Authentication and Google for authentication; Google Cloud, including Cloud Run, for backend operations and Firebase Hosting for website delivery; Neon PostgreSQL for the application database; Porkbun for domain management and support-email forwarding; and the support mailbox destination service for correspondence. These providers may process information to provide their services. We may also disclose information where required by law or necessary to protect WordPoise, players, or the public.

8. Retention

We generally keep active online account information and associated gameplay records while the account exists, unless deletion, legal requirements, or a justified security need calls for a different period. Local gameplay stays on the device until it is cleared or removed through supported app or operating-system behavior. We do not plan to delete anonymous online accounts solely because they have been inactive.

Our retention targets are 30 days for configurable application logs and database backups, 180 days after resolution for support correspondence, and 90 days for minimal deletion audit records and completed merge records when no longer needed. Actual retention can vary where cloud providers impose different schedules or where security or legal obligations require limited additional retention. Some provider-managed logs and backups cannot follow these targets. We retain identity-related security records only as long as justified for protecting accounts and preventing misuse.

9. Privacy requests and account deletion

Contact support@wordpoise.com to request access to, correction of, or deletion of your information, to get help with account access, or to raise a privacy concern. Available rights and response requirements depend on applicable law. We may need to verify your identity or account ownership safely before acting; a Firebase UID alone is not proof of ownership. Never email passwords, ID tokens, or other authentication secrets.

See Account Deletion for instructions on requesting deletion by email and for any in-app deletion option when available. Once a request has been verified, we aim to restrict access promptly and complete ordinary account deletion within 30 calendar days, subject to applicable law and legitimate retention exceptions. Backup copies may remain until the applicable backup cycle expires.

10. Security and international processing

WordPoise uses reasonable measures intended to protect information appropriate to the service. No online service can guarantee absolute security. We do not promise a particular encryption method, certification, or zero-risk outcome.

The application backend and database currently selected for WordPoise are in Frankfurt, Germany: Google Cloud Run ( europe-west3 ) and Neon PostgreSQL. Firebase Authentication processes authentication information in the United States. Firebase Hosting, Google, Porkbun, and the email provider receiving support messages may process information in other countries. The public website is globally accessible; the initial intended mobile distribution is India and the United States. Hosting infrastructure in Germany does not mean that all personal information is kept within the European Union.

11. Changes to this policy

We may update this policy as WordPoise changes or legal requirements evolve. We will post the updated version here and revise its effective date. We will provide additional notice for significant changes when required by applicable law.