Privacy Policy for Flashadelic

Last updated: November 18, 2026

Canonical version: https://flashadelic.com/privacy/

This Privacy Policy describes how Yauhen Bahdanovich, a self-employed individual based in the Republic of Belarus ("I," "me," or the "Developer"), processes personal data in connection with the Flashadelic app for iPhone and iPad (the "App"). On the App Store the App is listed as "Flash Cards: Create With AI."

Where I determine the purposes and means of processing, I am the data controller or operator under applicable data-protection law. Questions and requests may be sent to help@flashadelic.com.

This Privacy Policy is a notice. It does not replace separate consent where applicable law requires consent.

The App does not require an account. There is no sign-up, username, or social-media login.

1. Scope

This Privacy Policy applies to personal data processed through the App and to messages sent to me about the App.

Apple, Google, Cloudflare, OpenRouter, SiliconFlow, and Postale.io may also process information under their own terms and privacy policies. This Privacy Policy describes my use of those services. It does not govern processing that those companies carry out independently for their own purposes.

2. Cards and Photos

The App stores the folders, cards, and photos a user creates. The front of a card is text. The back may be text, a photo, or both. A photo is taken with the camera or chosen from the photo library when the operating system asks for permission and the user grants it.

These records stay on the device. If iCloud is enabled for the App, they may sync through Apple iCloud and CloudKit to the user's other devices on the same Apple ID. Local App data may also be included in an iCloud device backup or a computer backup, according to the user's backup settings.

I do not operate a server that receives cards or photos, and I do not read them. Cards and photos are not sent to Firebase Analytics or Firebase Crashlytics.

A card remains until the user deletes it. Deleting a card or folder deletes the active App copy and propagates the deletion through CloudKit according to Apple's synchronization behavior. Uninstalling the App removes its active on-device data. Synced data or backup copies may remain until the user deletes them or Apple removes them under its retention rules.

3. Writing the Back of a Card

The user can type the back of a card, or ask the App to write the back from the front.

When the user asks the App to write the back, the text on the front is sent to a service I operate on Cloudflare, together with the App Store storefront country. The service sends that text to a language-model provider so the provider can return a short answer. The provider is OpenRouter, which uses Google, or SiliconFlow's international service. Which provider handles a request can depend on where the request comes from. In some places the feature is unavailable.

The provider receives the front of the card. It does not receive the storefront country, the photos, the other cards, the user's name, or the Apple ID. The front of a card is whatever the user typed. A user should not ask the App to write a back from text they would not want that provider to receive.

I do not keep the card text, and I do not read it. The service records the country and which provider handled the request. That record does not include the card text or the IP address. I do not export it. When Cloudflare stores it in Workers Logs, Cloudflare keeps it for at most 7 days. The service uses the IP address to limit repeated requests during a 60-second window, and it does not write the IP address into that record. I do not add the card text or the IP address to Firebase.

OpenRouter, Google, SiliconFlow, and Cloudflare describe their own handling of information they receive:

4. Support

When a user writes to me, I receive the sender's email address, the message, any attachments the sender chooses to include, and ordinary email-routing metadata. My email is hosted by Postale.io.

I use these messages to answer the user, investigate reported problems, and maintain the App.

I consider a conversation resolved when I send a final response or, following my response, the user does not reply for 30 days. I delete the conversation, its attachments, and copies in the active mailbox and Trash six months after resolution. Residual copies may remain temporarily in Postale.io backups and are removed under the provider's backup-retention process.

Information may be retained longer only where reasonably necessary to comply with law, resolve an active dispute, or establish, exercise, or defend legal claims.

5. Firebase Analytics and Firebase Crashlytics

The App uses Firebase Analytics and Firebase Crashlytics, both provided by Google. These services initialize automatically when the App launches. The App does not provide an in-App control to disable their collection or reset the Firebase app-instance identifier.

Firebase Analytics

Firebase Analytics may process:

I use this information in aggregate to understand which screens and controls are used and to improve the App. The App has no account-level user identifier. I do not configure Analytics events to include names, email addresses, card text, or photos.

Firebase Crashlytics

Firebase Crashlytics may process:

I use Crashlytics to identify, investigate, and correct crashes and reliability problems. A failed request to write the back of a card may be recorded as an error status code. I do not configure Crashlytics to receive card text or photos.

Advertising and retention

Firebase is not used for advertising or cross-app tracking. The App does not use the Apple advertising identifier (IDFA).

Firebase Analytics user-level and event-level data may be retained for up to 14 months after the most recent activity. New activity may restart the user-level retention period. Aggregated reports that no longer identify an app instance may be retained longer.

Google states that Firebase Crashlytics retains crash stack traces and associated installation identifiers for 90 days before beginning removal from live and backup systems. Google may retain service and security data under its own retention rules.

Additional information is available in the Google Privacy Policy and in Privacy and Security in Firebase.

6. Purchases

In-app purchases are processed by Apple. I do not receive full payment-card details. The App receives purchase or subscription status from Apple to provide paid features. Firebase Analytics may record the purchase-event information described in Section 5. Refunds and billing are handled by Apple.

7. Purposes and Legal Bases

Where the European Union General Data Protection Regulation ("GDPR") or United Kingdom GDPR applies, I rely on the following legal bases:

For processing governed by the laws of Belarus, I rely on the agreement or action requested by the user, consent where required, and other grounds permitted by the Law of the Republic of Belarus No. 99-Z "On Personal Data Protection."

Where processing is based on consent, consent may be withdrawn at any time without affecting processing already carried out lawfully before withdrawal.

8. Recipients and Disclosure

I may disclose information to the following recipients for the stated purposes:

Service providers process data under their terms, contractual commitments, and applicable law. I do not sell or rent personal data or share it for cross-context behavioral advertising.

9. International Processing and Transfers

I am based in the Republic of Belarus and access support messages and Firebase information from Belarus. Belarus has not been recognized by the European Union or the United Kingdom as providing an adequate level of data protection.

Apple, Google, Cloudflare, OpenRouter, SiliconFlow, and Postale.io may process information in the United States, Singapore, France, countries in the European Economic Area, and other countries in which they or their service providers operate. Cloudflare, Inc. is based in the United States. OpenRouter states that personal data may be transferred to its servers in the United States. SiliconFlow's international service is operated by SILICONFLOW LABS PTE. LTD. in Singapore. Postale.io states that it uses Amazon Web Services infrastructure in France and the United States.

Where applicable, providers may rely on adequacy decisions, data-protection frameworks, standard contractual clauses, or other lawful transfer mechanisms made available under their terms. Their locations and mechanisms may change.

For purposes of Belarusian law, use of foreign cloud, email, analytics, and language-model services may constitute a cross-border transfer. A destination may not provide the level of protection recognized under Belarusian law. Risks may include different privacy rules, access by foreign authorities, and more limited rights or remedies.

Users should not send a support message if they do not want that message processed in Belarus or by the foreign providers identified above.

10. Retention Summary

Unless a longer period is required by law or for an active legal claim:

11. Rights and Requests

Depending on applicable law, a person may have the right to:

Cards and photos are controlled by the user through the App, iCloud, and device settings. Deleting a card removes its active App record. Users may manage iCloud data and backups through Apple settings.

Because the App has no account, Firebase identifiers are not linked to an email address or identity known to me. I may be unable to locate a particular Firebase record from an email request. I do not keep the card text, and the language-model providers do not receive the user's email address, so I cannot locate a particular card text from an email request. Uninstalling the App stops future collection from that installation. It does not immediately delete information already sent to Google or to a language-model provider.

Requests concerning data I control may be sent to help@flashadelic.com. I may request information reasonably necessary to verify the requester and locate the relevant records, and I will respond within the period required by applicable law.

Residents of Belarus may complain to the National Personal Data Protection Centre of the Republic of Belarus. Individuals in the EEA or the United Kingdom may complain to the supervisory authority where they live or work.

The App does not make decisions that produce legal or similarly significant effects solely through automated processing. I do not sell personal data, including as "sale" or "sharing" is defined by applicable United States state privacy laws.

12. Children

Flashadelic is a general-audience study app with an App Store age rating of 13+. It is not directed to children under 13.

The App does not request a date of birth, and Firebase does not provide me with the user's age. People under 13 must not send support messages. A parent or guardian who believes a child has sent personal information to me may request deletion at help@flashadelic.com.

13. Security

I use reasonable technical and organizational measures appropriate to the information processed, including limiting access to service accounts and relying on security controls provided by Apple, Google, Cloudflare, OpenRouter, SiliconFlow, and Postale.io. Postale.io states that it uses encrypted transport and encryption at rest.

No method of storage or transmission is completely secure. Ordinary email is not an appropriate channel for card text or photos that are unnecessary for support. Users should review attachments and remove anything they do not wish to send.

14. Changes to this Privacy Policy

I may amend this Privacy Policy to reflect changes in the App, service providers, or applicable law. The "Last updated" date identifies the current version. If a change materially expands processing that requires consent, I will request new consent where required.

The current version is published at https://flashadelic.com/privacy/.

15. Contact

Yauhen Bahdanovich Self-employed developer of Flashadelic Republic of Belarus Email: help@flashadelic.com