Privacy Policy

1. Overview

GolpoTwist is a Bengali interactive storytelling app developed by Md Nazmul Haque Arif, operating under the name arifz (“we”, “us”). This policy explains local storage, advertising, purchases, diagnostics and your choices. The Android package is xyz.arifz.golpotwist. You do not need a developer-operated account. Some features work offline after their content is downloaded; ads, purchases and downloads use online services.

2. Information stored on your device

The app stores story progress, save slots, choices, unlocked endings, diamond balances, purchase-related records and reading, audio, reminder and privacy preferences in private app storage. This supports continuing stories, delivering purchases and remembering your settings. We do not operate a cloud account or a server for synchronizing your saved stories.

3. Advertising and consent

GolpoTwist uses Google AdMob and Google’s User Messaging Platform. The advertising SDK may process IP addresses (which can indicate approximate location), device and advertising identifiers (including advertising ID and app set ID), app interactions, ad views and clicks, and diagnostic information to deliver and measure ads and prevent fraud. Personalized advertising depends on your consent, region and Google settings; non-personalized ads can still process data. Where offered, use Settings → advertising and privacy options to review or change advertising consent. Android also provides advertising privacy controls. Advertising consent is separate from the analytics switch. App set ID is used for essential purposes such as analytics and fraud prevention, not ad personalization or ad measurement; we do not combine it with personal information or other device identifiers for advertising purposes.

The Remove Ads purchase removes the placements described in the store. Optional rewarded ads remain available, and the advertising SDK may prepare them in advance. Buying Remove Ads does not by itself switch off analytics or all advertising-SDK processing.

4. Analytics and crash reports

When enabled, Firebase Analytics and Firebase Crashlytics process app/device information, app-instance or installation identifiers, usage events and crash diagnostics to understand usage and improve reliability. Events include story and chapter identifiers, starts and completions, premium-choice use, endings reached or shared, downloads and errors, and purchase outcomes. These records are not necessarily anonymous merely because they do not include your name. The app does not deliberately send story text or a personal account profile in its custom events. Analytics advertising-ID collection and analytics advertising-personalization signals are disabled in the app configuration.

5. Your analytics choice

On a fresh installation, analytics storage consent and automatic crash-report uploads default to denied/off. The app uses SIM country, network country or device locale to decide whether to ask for analytics consent in the EEA, United Kingdom and Switzerland; it also asks if the country cannot be determined. Elsewhere, the current app may enable analytics and crash reporting unless you decline. This country check does not use GPS and may not reflect your physical location.

Change the usage-information switch in Settings (গোপনীয়তা → বেনামী ব্যবহারের তথ্য পাঠাও) at any time. Turning it off sets analytics storage consent to denied and disables automatic crash-report uploads. This is not a guarantee of zero network traffic: Google's consent mode can send limited consent and measurement signals without stored analytics identifiers. Previously transmitted data is not automatically deleted. Crash reports can remain locally queued and may be uploaded if reporting is later enabled. Saved consent choices can persist between launches.

Declining analytics does not prevent reading stories. Advertising consent is controlled separately. See Google's explanation of consent mode.

6. Purchases and Google Play

Google Play Billing handles payment for digital products. Google processes payment/account information under its own policies; we do not receive your payment-card details through the app. The app processes product identifiers, purchase tokens, purchase status and entitlement information to deliver purchases and avoid duplicate credits. Google Play Asset Delivery handles media downloads and may process device, app and delivery information. Google Play may retain transaction records independently of app deletion.

7. Permissions, reminders and sharing

Internet and network-state access support online features. Optional notification permission enables reminders about unfinished stories; you can disable reminders in the app or Android settings. When you choose to share an ending, Android sends the selected share content to the destination you choose. That destination handles the content under its own policy. The app does not require access to contacts, microphone, camera or precise device location for storytelling. Included service libraries also use advertising/attribution permissions and background-work permissions for advertising measurement, uploads and content delivery; these do not grant access to your contacts or precise location.

8. Backup, retention and deletion

Story databases and preferences are included in Android backup and device-transfer rules. Whether copies are made or restored depends on your device and backup settings; the backup provider processes those copies. Local records remain until removed or app storage is cleared. To remove local data, use Android Settings → Apps → GolpoTwist → Storage → Clear storage/data, or uninstall. This can permanently remove progress and consumable diamond balances. Manage existing backups separately with your backup provider. Clearing app storage does not erase Google Play transactions, previously shared content or previously transmitted SDK records.

Google states that Crashlytics retains crash traces and associated installation identifiers for 90 days before beginning removal from live and backup systems. Analytics user/event retention follows the project's configured retention controls; aggregated reporting can follow different retention rules. Advertising and Play transaction records follow Google's applicable retention policies. There is no single retention period covering every service. See Firebase retention information and Analytics retention controls. Contact us for deletion requests concerning information we hold; do not send purchase tokens or payment details.

9. Recipients, security and international processing

Google and its service providers process information for advertising, analytics, crash reporting, purchases and delivery. Data may be processed outside your country under their applicable safeguards and terms. We do not sell your saved story records. Advertising services may use information for ad delivery and measurement as described above. We may disclose information we actually hold when legally required or necessary to protect rights and prevent abuse. Android app isolation and service-provider transport protections help protect information, but no storage or transmission method is completely secure.

10. Support and your rights

For processing that we determine, the responsible provider is Md Nazmul Haque Arif (arifz), Bangladesh. Our postal address and contact phone are in the provider information. Email [email protected] for privacy questions or requests. If you contact us, we receive your address, message and attachments, and our email provider processes them. We retain correspondence as needed to answer, resolve follow-up and meet applicable legal obligations. Depending on applicable law, you may request access, correction or deletion, object to processing or withdraw consent, and complain to your local data-protection authority. We cannot identify or remotely delete your local saves through an app account, because no such account exists. For SDK records, we may need limited information to locate a record and may need to direct you to Google's privacy controls; we will explain any identification or legal-retention limits instead of promising deletion of records we cannot identify. Withdrawing consent does not invalidate processing that was lawful before withdrawal.

11. Children and age suitability

Story themes and age suitability vary; consult the Google Play content rating and story descriptions. We do not knowingly seek personal information from children under the age at which parental consent is required by applicable law. Parents or guardians concerned about information sent to us should contact us. A store content rating does not itself provide parental consent for data processing.

12. Third-party policies and this website

See the Google Privacy Policy, Google advertising information and Firebase privacy information. Visiting this page sends ordinary request information, such as your IP address and browser information, to the website hosting infrastructure. This page contains no advertising or analytics scripts.

13. Grounds for processing

Where data-protection law requires a legal basis, we process information necessary to supply requested features, purchases and support to perform our agreement with you; use consent for optional processing where required; and use legitimate interests, subject to your rights, for security, fraud prevention and handling support or legal claims. We also process information where necessary to meet legal obligations. Legitimate interests do not replace consent where consent is legally required. Google explains its own processing grounds in its privacy policy.

14. Policy updates

We may update this policy when the app or its practices change. The revision date appears above. We will provide additional notice or request consent when applicable law requires it.