Fortune Fragments – Privacy Policy

Fortune Fragments (“the app”) is developed by Andrii Kadygrob. This policy describes what information the app collects, how it is used, and your choices. We comply with applicable privacy laws in Ukraine and globally. If you do not agree with this policy, please do not use the app.

1. Information we collect

1.1 Crash and diagnostic data

The app integrates Firebase Crashlytics to detect and fix crashes. When a crash occurs, Crashlytics automatically collects data such as:

• an installation‑specific UUID to deduplicate crashes;
• the Firebase installation ID and session ID;
• timestamp of the crash;
• the app’s bundle identifier, version and build number;
• device information (model, operating system version, CPU architecture, memory and disk size, whether the device is rooted/jail‑broken);
• stack traces of the running threads and any thrown exception.

Crashlytics uses this information to associate crashes with a project, send alerts to the developer and help debug issues. Crash data (including Crashlytics installation UUIDs and Firebase installation IDs) is retained for 90 days before removal from live and backup systems.

1.2 Advertising data

The app displays ads using the Google Mobile Ads SDK (AdMob). The SDK collects and shares certain data automatically for advertising, analytics and fraud prevention, including:

• IP address – used to derive approximate location;
• User interactions – information about app launches, taps and video views;
• Diagnostic information – crash logs, app launch time, hang rate and energy usage;
• Device and account identifiers – such as the Android advertising ID and app‑set ID.

All data collected by AdMob is encrypted in transit using Transport Layer Security (TLS). You can reset or delete the advertising ID from your device’s settings. If you are in the European Economic Area or another region that requires consent, the app can display a consent dialog before personalizing ads.

1.3 In‑app purchase data

The app uses RevenueCat via the purchases_flutter plugin to handle subscriptions and in‑app purchases. RevenueCat collects the following data:

• Purchase history – receipts and transaction identifiers required to verify purchases and manage entitlements;
• Locale and currency code – used for price localisation;
• Device identifiers – used if you enable integrations that utilise advertising identifiers.

RevenueCat encrypts data in transit and stores only the information necessary to fulfil your purchase. RevenueCat does not collect users’ location, contacts, photos or browsing history.

1.4 Local preferences

The app may store limited user preferences (such as language, settings and progress) in shared preferences on your device. This data remains on your device and is not transmitted to our servers or any third party.

1.5 Other information

We do not collect personal identifiers (such as name, email address or phone number) or sensitive personal data. The app does not request access to your contacts, calendar, photos, camera, microphone or precise location.

2. How we use the information

• diagnose and fix crashes, monitor app performance and improve stability;
• display and personalise ads (where allowed by user consent);
• process payments, verify subscriptions and provide access to premium content;
• understand how users interact with the app in order to improve user experience;
• comply with legal obligations and defend against legal claims.

We do not sell your data or use it to build marketing profiles.

3. Data sharing and third parties

We share information with third‑party service providers only to the extent necessary to provide core functionality:

These providers process data on our behalf under contractual obligations that require them to protect your information.

4. Data retention

We retain crash logs and diagnostic data for up to 90 days. Advertising and purchase data are stored by Google and RevenueCat for as long as necessary to deliver services and comply with legal obligations. Local preferences are stored on your device until you delete the app or clear its data.

5. Security

We take reasonable steps to protect your information. All communications with our third‑party services use HTTPS/TLS encryption. Firebase services, AdMob and RevenueCat employ industry‑standard security measures to prevent unauthorised access, including logical isolation of customer data, access logging and restricted personnel access. However, no method of transmission or storage is completely secure and we cannot guarantee absolute security.

6. Your rights and choices

• Consent for personalised ads: In regions where consent is required, the app can present a consent dialog allowing you to choose whether to receive personalised ads. You can change your preference at any time via the app’s settings.
• Advertising ID: You can reset or delete your advertising identifier through your device’s privacy settings. If you opt out of personalized ads, the app will request non‑personalized ads from AdMob.
• Access or delete purchase data: If you want to view or delete purchase history, use the contact form below. RevenueCat allows us to delete customer data upon request.
• Crash reporting opt‑out: If you prefer not to share crash data, you can disable crash reporting in the app’s settings (if available).
• Uninstalling the app: You can stop all data collection by uninstalling the app.

7. Children’s privacy

The app is not directed at children under the age of 13. We do not knowingly collect personal data from children. If you believe a child has provided us with personal information, please contact us so we can delete it.

8. International data transfers

The third‑party services we use may process data in any country where they or their agents operate. By using the app, you consent to the transfer of your data to countries that may have different data protection laws than your country of residence.

9. Changes to this policy

We may update this privacy policy from time to time. Changes will be posted in the app and, if significant, we will notify you through the app or via other channels. The date at the top of this policy indicates when it was last updated.

10. Contact us

For questions or requests about this privacy policy or your data, use the contact form.

This page is provided for convenience and may link to third‑party documentation owned by their respective providers.