Chat Like Gen Z privacy policy

1. Messages and conversion records

When you request an encode or decode, the text you enter goes through an authenticated Firebase Cloud Function to Google Gemini for a generated answer. For encode, the request can also include your chosen writing style and optional age range, identity and pronouns. Decode does not send those preferences. Google processes the request to produce the answer. AI answers can be inaccurate.

The Firebase wallet stores a conversion operation under your account identifier. Its record contains the request ID, status, timing information, a fingerprint derived from the submitted text and preferences, and the generated result on success. The current operation record does not save the plaintext input, but the input is transmitted to the backend and AI service. The fingerprint helps prevent a request ID being reused for different content. We do not claim that conversion text is processed only on your device or that no message data is stored.

2. Information on your device

The app saves your writing profile locally, including any age range, identity, pronouns and style you select. It also uses local storage for a pending conversion request and the most recent completed input and result, so an interrupted request can be recovered without charging twice. A pending request can include your message and encode preferences. Reward-test state may also be kept locally while a reward is being checked.

Clearing the app’s storage or uninstalling it removes app-managed local data on that device. Text you copy or share goes to the destination you choose; that destination’s privacy practices then apply. Device backups may retain copies under your device or backup-provider settings.

3. Accounts, wallet and recovery

You can start without Google sign-in. Firebase Authentication creates an anonymous account identifier, shown in the app as a Support ID, so a remote wallet can track your conversion balance. A new guest wallet starts with 10 conversions; successful new conversions use one, while failed or cancelled requests return their reserved credit. Uninstalling an unlinked guest account can mean losing access to its balance, but does not itself delete server data.

You may link a Google account to preserve or recover a wallet. Firebase Authentication then receives account details such as your Google identifier, email and basic profile information. If that Google account already has a wallet, restoring it switches to that wallet; balances are not combined. Google sign-in is required before test-pack checkout, not for free conversions. Firebase App Check, using Android integrity signals, helps protect backend requests from abuse. It does not make submitted text end-to-end encrypted.

4. Rewarded ads and privacy choices

The test build offers optional Google AdMob rewarded ads. A verified completed ad is intended to add three conversions after our server checks Google’s signed confirmation. The app also has demo ads that add no credits. Owned-unit ad completion and the full consent flow have not yet been verified on the test phone; live public ads are disabled.

Google’s Mobile Ads SDK and User Messaging Platform (UMP) can process IP address, device or advertising identifiers, approximate location inferred from IP, ad interactions and diagnostics for ad delivery, measurement, security and consent management. The test configuration requests non-personalized, G-rated ads and applies under-age treatment to selected age groups. It does not request precise location. The app requests consent where required before loading ads and offers Settings → Ad privacy choices when a privacy-options form is required and available. A Console consent message still needs configuration and testing. See Google’s Privacy Policy.

5. Google Play test purchases

Google Play test billing offers consumable packs of 100, 200 or 300 conversions to approved internal testers. There are no public live sales in this version. The app sends product and purchase identifiers to our backend, which checks the purchase and account association with Google Play before adding credits. We store wallet balances, grant records and billing-account mappings to reconcile purchases and avoid duplicate credits. Google Play handles payment; AppCrazy Labs does not receive your full payment-card details. Google controls its own purchase history. No subscription, lifetime Pro or RevenueCat service is used for this app.

6. Purposes and service providers

We use the information above to produce conversions, personalize encodes, recover results and balances, verify credits and test purchases, prevent misuse, respond to support and comply with legal obligations. Relevant providers are Google Firebase (Authentication, Cloud Functions, Firestore and App Check), Google Gemini through Vertex AI, Google AdMob and UMP for test ads, Google Play for test billing, and our email provider when you contact support. We may also disclose information when legally required. We do not use a separate analytics or crash-reporting SDK in the inspected test build.

If you contact us, we receive your email address, message and any attachments you choose to send. Please do not email passwords, payment-card details or sensitive message text. See also Google’s privacy information for its services.

7. Retention and deletion

Server conversion results and the fingerprint derived from submitted content expire seven days after creation. The backend stops returning expired results and removes them on access. An hourly cleanup job also removes expired results and fingerprints; physical cleanup can be delayed by retries, outages or a processing backlog. This is not a promise that every physical copy disappears exactly at seven days. Active requests are allowed to settle or time out safely before cleanup. Minimal request IDs, status and timing metadata remain with the wallet until account deletion to prevent old retries from spending a conversion again. This mechanism does not use Firestore TTL to delete entire conversion records.

Firebase account, wallet, linked Google identity, billing mappings and active-account credit records remain while the account exists. Expired reward tickets are cleaned after an additional day for reconciliation. Your latest input/result and writing profile can remain on your device until replaced or cleared; the server's seven-day rule does not erase local copies, screenshots, shared text or device backups.

In internal build 8 and later, use Settings → Delete account & data. Confirm Google sign-in again if linked, then confirm permanent deletion. The server closes the account immediately, blocks new wallet writes, removes the Firebase Auth account and Google link, wallet, conversion records, billing mappings and reward tickets. Interrupted cleanup retries hourly. This also removes unused purchased conversions and does not request a Google Play refund. The Google account itself is not deleted. The app clears app-managed personal data on the requesting phone and attempts to revoke its Google sign-in access. Other/offline devices and backups may need local cleanup or removal through their own settings.

After deletion, transaction-token digests with pack/reward type, amount, timing and reversal status, but without your Firebase account ID, email, Google identity or messages, remain for 180 days to prevent duplicate credits and reconcile refunds. A hashed account-deletion receipt remains for 90 days to block stale requests and record completion. Hourly cleanup removes these records after their retention deadlines, subject to the same operational delays. These are the current test app's operational retention periods, not a claim that a law requires this duration. Google Play controls its own purchase history. The configured Cloud Logging buckets retain default operational logs for 30 days and required audit logs for 400 days; the required-audit bucket is locked. These platform logs are separate from app wallet data and are not erased by account deletion. Data held by Google, Gemini, AdMob and our email provider follow their separate retention practices.

You can also request deletion without signing in through theChat Like Gen Z data-deletion page. Support verifies ownership before processing; knowing a Support ID alone is not enough. Email requests are reviewed manually and sending one does not immediately delete an account. Support correspondence is separate from the automated account cleanup; ask for its deletion too if desired. We will explain any specific legal hold before retaining requested correspondence. No fixed support completion time is promised.

Depending on your location, you may have rights to access, correct or delete personal information, or object to or restrict processing. Email udawat.sidhanshu@gmail.com with your Support ID if you have it. We may ask for limited information to verify ownership before acting on a request.

8. Security and international processing

Backend requests use encrypted connections, Firebase Authentication and App Check; the app cannot directly edit the server wallet. This limits some risks but does not guarantee absolute security. Submitted text is visible to the backend and AI service for processing, so it is not end-to-end encrypted. Google services and our email provider may process information outside your country, including the United States, subject to their policies and applicable safeguards.

9. Children and changes

Chat Like Gen Z is not directed at children under 13. Its profile includes a 13–17 age range, so some users may be teenagers. If you believe a child under 13 has supplied personal information, contact us so we can investigate.

We may revise this policy when the app, providers or test configuration change. The new version will appear here with an updated date. For privacy questions, contact Sidhanshu Udawat at udawat.sidhanshu@gmail.com.