FlashLock privacy policy

Who operates FlashLock

FlashLock is an Android app that combines flashcards with learning breaks while using selected apps and websites.

Operator: Flash Lock PTY LTD
Privacy and support contact: hello@flashlock.app
Effective date: 21 October 2026

Intended beta audience

The first FlashLock beta is intended for adult learners aged 18 and over. It is not designed or marketed for children.

Learning information on your phone

FlashLock keeps cards, decks, imported media, study history, progress, preferences, selected apps/websites and unfinished card drafts in the app's private storage. These are not automatically uploaded to the community library. You choose whether to submit a deck, export/share content or send feedback.

Android may back up or transfer the study database according to your device settings and the app's backup rules. Account preferences, feedback drafts and caches are excluded from the app's backup configuration. Database backup is limited to supported encrypted cloud-backup conditions or device transfer.

Deleting local cards, clearing app storage or uninstalling affects the app's local information on that device. It does not delete your community account, server records, exported files, other people's downloaded decks or an existing Android backup.

Accessibility, Usage Access and learning breaks

With your permission, FlashLock uses Accessibility and Usage Access to identify the foreground app and, in supported browsers, the visible address needed to match a website you selected. Matching and learning-break decisions take place on your phone. This interruption path does not upload screen contents, browser-page text or Accessibility events to FlashLock's community service.

Your chosen app/site rules and learning-break state are saved locally. FlashLock uses launcher-app information for the app picker and checks essential system handlers, such as Home, calling and keyboards, to avoid interrupting them.

You can change selected apps/sites in FlashLock or disable these permissions in Android Settings. Setup guidance uses the phone's make/model and Android version locally. The bundled setup video plays only when you choose it.

Community accounts and shared decks

You can browse the community library without creating a personal account. Uploading or reporting a deck requires a verified account. Account sign-in uses Google Firebase Authentication through email/password or Google sign-in. Authentication processes identifiers, email and security information. FlashLock also stores your chosen public username and account identifier.

Submitting a deck sends its selected card text, included images and metadata, such as title, description, category, language, difficulty, licence and attribution. Private submission records also contain your account identifier, account email, public username, timestamps, upload-check results and moderation status.

Google Firebase/Google Cloud handles service records, and Cloudflare R2 stores uploaded files and published deck files. Submitted content is checked and reviewed before publication.

Published card content, images, deck metadata and your public username can be seen by people using the library. Public metadata also includes an opaque publisher identifier. Your account email is not part of ordinary published deck metadata. Include only content you are entitled and willing to share. Removing a hosted deck cannot recall copies already downloaded or exported by other people.

A deck report sends the deck identifier, your account identifier, the reason you enter and a timestamp for private moderation. Reports are not public catalogue entries.

Upload review and restrictions

We may reject or restrict uploads for security or content-review reasons. Private restriction and administrator-review records contain the affected submission, account reference, reason, status and timestamps; access to those records is limited to authorized administrators. You can access your own submission record and its status. An upload restriction is not account deletion, and restoring upload access does not itself publish rejected content. Review history is kept for security, handling disputes and preventing repeated misuse; deletion requests are assessed with any necessary, explained retention exceptions.

Feedback and account-deletion requests

Sending feedback transmits your message, selected topic, optional reply email, app/version and Android-version information. It also includes a random installation identifier and submission reference. The server keeps an installation-identifier hash and verification/quota information to limit duplicates and abuse.

Feedback is private and available to authorized administrators through the private inbox. It is not published. Automatic feedback email forwarding is currently off. Unsent drafts remain locally for retry; the matching local draft is cleared after a confirmed successful submission.

In the updated app, Community account → Request account deletion sends a request for the signed-in account. A recorded request has a reference number and enters private administrator review. The case holds the authenticated account identifier, request reference/status, timestamps and available account/contact information. A verified account email may be included as a reply contact; an unverified account email is not treated as a verified reply address.

Submitting this request does not immediately delete the account or its data. Signing out or uninstalling is not an account-deletion request.

The account-deletion page explains the request process and its limits. Without installing the app, contact hello@flashlock.app. Do not send passwords, sign-in codes or access tokens.

Optional app-usage sharing

Share app usage is off by default. Turning it on enables Google Analytics for Firebase product events, including screen categories, setup/permission status, import outcomes/counts, review ratings, star/Undo events and speech timing/status.

The app's product-event API does not include card text, deck names, selected app names or browsing history. The Analytics SDK also handles app-instance identifiers and standard app/device/session information. Advertising-ID collection and advertising-personalization/storage consent are disabled in the reviewed beta configuration.

Turning sharing off disables subsequent product-analytics collection and resets local Analytics data/identifier. It does not itself erase information already received by the provider. Provider-held Analytics records may need separate handling when you request deletion; turning sharing off is not confirmation that those records have been erased.

Language identification, speech and external services

FlashLock uses bundled Google ML Kit language identification to choose a suitable speech language. Its input text and processing results remain on the device. ML Kit separately sends operational metrics to Google, including app/device information, per-installation identifiers, performance/error information and identified languages. That SDK telemetry is separate from Share app usage. See ML Kit's privacy explanation and Android SDK data disclosure.

When you ask FlashLock to read a card, its text is passed to your installed text-to-speech engine. FlashLock prefers available offline voices, but some voices need a network connection and may process the text through the speech provider. Check the selected engine and voice settings.

AI card creation prepares a prompt for you to copy into an AI service of your choice, then lets you paste the response. FlashLock does not automatically submit that prompt to an AI API. Information you deliberately paste into another service, export/share or open through an external link is handled by that destination.

Service security and providers

Online features use Firebase App Check with Google Play Integrity to help verify the app/device and limit misuse. The configured Google services process verification material; verification tokens accompany protected requests. Authentication and online services also process request/network information needed for operation and security. These functions are separate from optional product analytics. See Firebase's processing information.

The reviewed beta does not include Firebase Crashlytics or Google Play Billing. This does not imply that historical transaction records from older versions have been erased.

FlashLock uses app-private local storage, access controls for private service records and encrypted network connections. Those measures do not guarantee that any system is risk-free.

The community database is in Google's Sydney region. Google and Cloudflare may process information in other locations according to their services and terms; not all information is necessarily kept in Australia. See also Cloudflare's privacy policy.

Retention and deletion

Local cards and preferences stay until you remove them, clear app storage or uninstall, subject to separate backups and exported copies.

Account/profile and private submission information is kept to provide the account, process submissions and resolve related requests. The service currently has no fixed automatic-erasure schedule for these records or abandoned uploads. Expiry of an upload link does not mean its file has been deleted.

Feedback and moderation records are kept for support, review, dispute handling and prevention of repeated misuse. They are assessed when a relevant deletion request is received, rather than erased automatically at a fixed age.

Deletion requests are kept while being handled. Requests cover the authentication account, community profile and associated private service records and files. We review published material, other retained copies and any security or legal exception before confirming the outcome. A completion notice must distinguish what was removed from anything retained and explain why it is kept. A request receipt is not proof of completed deletion.

Completion can leave limited hashed safety/audit records needed to prevent deleted data being recreated and to record the completed operation. Hashes are not necessarily anonymous. Any retained account-related information must have a specific reason, considered during request review.

Hosted published decks, public attribution and revisions need separate review. Tell us if your request includes a published deck or its attribution. Account deletion does not automatically revoke a content licence and cannot recall copies downloaded or exported by other people. Local cards and Android backups require separate action on your device.

The current Google Cloud default service-log bucket has a 30-day retention setting; the required audit-log bucket has a locked 400-day setting. These settings do not describe every provider's logs or Analytics records. The community database currently has no scheduled Firestore backups and point-in-time recovery is disabled; Android device backups are separate.

Analytics records and other provider-held information follow the applicable provider settings and request processes. Turning a feature off is not proof that old provider data has disappeared. Contact us to request review of this information as part of a deletion request.

Questions and changes

Contact hello@flashlock.app to ask about your information, request correction or deletion, or raise a concern, including about a child's information. We may need proportionate information to confirm that a request concerns your account; we do not need your password or sign-in codes.

We will update this policy when our information practices change. The effective date identifies this version. An app-store audience or content rating does not change the data practices described here.