Privacy policy for the Flowdots app
Last updated: 4 November 2026.
About this policy
This policy explains how the Flowdots iOS app handles personal data. Flowdots is intended for teenagers aged 13 and over and adults. Features may differ between app versions. This policy covers the app. Visits to the website and the website contact form are covered by the separate Website Privacy Policy.
The controller responsible for this processing is Sam Armbrust, Nijmegen, the Netherlands. For privacy questions and requests, email support@flowdots.nl.
Some data stays on your device. Other data is stored on Flowdots servers or processed by service providers such as Apple and Google. Below, we explain what this data is and how it is used.
Privacy at a glance
- Flowdots uses account, progress and transaction data to make your game, Daily and Hint Coins work.
- Some data stays on your device; other data is stored on our servers.
- Apple processes data for Apple features; Google does so for ads and consent choices.
- The app requests tracking permission through Apple and ad privacy choices through Google. Declining does not stop all technical data processing.
- You can request access to your data through support@flowdots.nl and delete an existing account in Account Details. Some necessary evidence may be retained afterwards.
Your account and Sign in with Apple
You can play Flow without signing in with Apple. Server features such as your Hint Coin wallet may create a guest account. A guest account also has account and Player IDs and is therefore not anonymous. The server stores account status, sessions and a link that allows purchases to be associated with the correct account.
Sign in with Apple lets you link your account for authentication and recovery on other devices. Apple supplies identification and verification data for this purpose. Flowdots verifies it on the server and stores the Apple account link and an encrypted authorization token. Sign-in credentials are kept in secure storage on your device.
The app asks Apple for permission to receive your name. If Apple provides name components, the app creates up to two initials for the local account display. This name and these initials are not included in the account sign-in request sent to Flowdots servers. Flowdots does not request your email address through Sign in with Apple. Information you provide to support is covered by the separate support processing described below.
An Apple-linked account is required for purchases and participation in the official Daily. Signing out ends your local session and clears the local account cache; it does not delete your online account or all your local game progress.
Flow and saved progress
On your device, Flowdots stores information including completed puzzles, stars, best swipe counts, mastery, hints used, your current position, tutorial status and preferences. Local Daily Flow history and recovery or synchronization data may also be stored on the device. The account cache may contain your identifiers, last known balance, hint unlocks and initials.
If your Apple-linked Flowdots account already has Flow progress stored on Flowdots servers, you can choose to import it into iCloud. After signing in, you can review the available progress and decide whether to combine it with your existing progress. The original server copy is retained according to our data retention policy. Hint Coins, purchases, and rewards are managed separately and are not affected by this import.
When iCloud is available, this version synchronizes Flow and previously saved local daily puzzle progress through private CloudKit storage in the iCloud account used by iOS. This includes puzzle progress, history and the metadata needed for safe merging and recovery. Native iCloud synchronization does not require a Flowdots wallet login. Linking an Apple sign-in to a Flowdots account is a separate action used for account services and importing earlier server progress. Hint Coin balances, purchases, competitive Daily results and telemetry are not part of these progress snapshots.
Official Daily, Game Center and fair play
The official Daily uses the server for start times, gameplay validation, scores, results, rankings and rewards. This involves processing account and edition identifiers, game actions such as swipes, undo and reset, durations, attempt status, and validation and result data. This is needed to resume attempts, verify results, prevent unfair use and handle rewards correctly.
The app may process account, Game Center and security data before you press Start. The official Daily may be temporarily unavailable.
Game Center supplies game- and team-scoped player identifiers and signed data that the server uses to verify your identity. If you allow access to friends, the app may read their Game Center identifiers and display names. Identifiers and temporary references are sent to the server for friends rankings; display names stay on the device.
Rankings use Flowdots aliases. On your device, a permitted Game Center friend name may replace an alias. Your Sign in with Apple name and account initials are not used as a public ranking name.
Apple App Attest helps check that requests come from a valid app. Flowdots processes information including key registrations, signed proofs, temporary security challenges, counters and verification outcomes. This security mechanism does not give Flowdots access to your photos, messages or other general device content.
Gameplay validation and score and reward calculations are automated. Contact support if you think a result or its handling is incorrect.
Hint Coins, purchases and rewards
Flowdots servers keep track of your Hint Coin balance and store associated account-linked transactions, credits and spending, reward claims, hint unlocks, and purchase and refund status. The app keeps a local cache; the server determines the valid balance.
Apple processes payment for an in-app purchase. Flowdots receives and verifies information including transaction references, product identifiers, purchase environment, account association, and purchase or refund status. Flowdots does not receive payment card details from Apple. Restoring and rechecking purchases takes the purchase type and existing transactions into account. Choosing “Restore purchases” alone does not grant a new Coin purchase for a consumable purchase that has already been processed.
For a rewarded ad, the server creates a temporary reward reference. The app passes this reference to Google. Hint Coins are granted only after Google's signed server confirmation has been verified. A failed, blocked or unverified ad does not produce a completed reward.
After account deletion, minimal purchase, refund, transaction and reward evidence may still be needed. For example, it prevents an old purchase or ad request from granting Coins again. This evidence is not necessarily anonymous and may remain linked to a deleted account reference.
Ads and your privacy choices
Flowdots uses Google AdMob for optional rewarded ads and Google's User Messaging Platform, UMP, for regional privacy choices. Flowdots does not ask for your date of birth or age category and does not use Apple Declared Age Range. The app therefore does not independently establish whether a player is a minor or an adult.
At the first actual app launch, iOS may request tracking permission once the app is active and can display the system prompt. An existing iOS choice or system restriction may mean that no prompt appears. Flowdots does not try to force you to make a choice again. You can later change the available tracking setting in iOS Settings. Tracking permission is not required for normal play or purchases.
The Google privacy flow starts when you open the Store. The app requests current consent information and displays a Google message if needed. Privacy Options is available when Google indicates that you need this option. No ad is requested before the consent check permits ad requests. A refusal may still permit a more limited ad route; it is not general consent to personalized ads.
The app permits the tracking and ad personalization route only when both iOS tracking permission and the applicable regional Google signals allow it. Without that combination, the app selects the more restricted Limited Ads settings and disables Google's publisher ID and publisher personalization settings. Flowdots does not use an alternative identifier of its own to bypass a refusal of tracking permission. An ad may also be entirely unavailable.
Limited Ads does not mean that all data processing stops or that the ad is anonymous. According to Google, data including IP addresses, limited device or storage information, ad events, and security and fraud prevention signals may still be needed. Non-personalized ads are likewise not automatically free of identifiers or data sharing.
Google's ad SDK may process information including device identifiers, approximate location derived from an IP address, ad and interaction data, and performance, crash and diagnostic data. Use depends on the region, choices, ad route and ad partners involved. Google may process data for ad delivery, measurement, analytics and security, or share it with relevant partners. See Google's Privacy Policy and the information in Google's privacy dialogs. This policy does not promise that Flowdots can inspect all internal processing by Google or ad buyers.
Notifications
If you allow notifications, Apple and Flowdots servers may process a push registration. The server associates an encrypted push token with your account and session and processes information including language, app build, registration expiry and delivery status. This is used to deliver app notifications to the correct installation and investigate delivery problems. Apple handles delivery through its push service.
You can disable notifications in iOS Settings. Notification permission is separate from ad tracking. Account deletion or session expiry may make a registration unusable; this does not mean that every earlier delivery record is immediately erased.
Gameplay and technical information
Flowdots records game and usage events locally to study functionality, usability and stability. Examples include session and game-round identifiers, timestamps, app version, language, puzzle context, swipes, resets, hints and completions. The former beta reporting, Participant ID display and manual export/translation feedback feature are no longer available. This does not disable the shared event recording.
Automatic upload to Flowdots servers depends on a separate configuration. If upload is enabled, selected events are sent with a random installation identifier, session and event identifiers, and permitted version and gameplay fields. This is pseudonymous data, not a guarantee of anonymity.
This automatic first-party upload does not contain Flowdots account or Player IDs, Apple sign-in credentials, purchase identifiers, IDFA, IDFV or free-text translation notes. The upload flow described here is not linked to the Commerce account database and is not intended for third-party ad tracking. The ad SDK has a separate data flow, as described above.
The beta erase button is no longer available. Removing this interface does not erase previously stored local events, installation identifiers, uploaded data or previously shared exports. Existing local data has not been automatically erased as a result.
The server and service providers may process technical request information such as IP addresses, timestamps, errors and security information. This supports operation and security of the service and investigation of faults. An ad privacy choice is not consent to every other kind of processing.
Support
When you contact support, we receive the contact details, message and any attachments you provide. A Player ID may be needed to locate an account problem. Do not share passwords, tokens, payment card details or unnecessary information about others.
Support email and messages are processed through Apple iCloud Mail; the website form uses Netlify Forms. Diagnostic or playtest exports you provide may also become support data. Account deletion does not automatically delete this correspondence. The website policy explains the website form separately.
How long is data kept?
We retain data for the purposes described, taking recovery, unresolved issues, legal obligations and prevention of duplicate transactions into account.
Current implementation: the retention policy and additional cleanup software have been established and tested. However, the new automatic cleanup for data including Daily evidence and extended account and transaction context has not yet been enabled. The periods below for that data are conditions and policy targets; they are not proof that every relevant record is automatically deleted on that date. Existing account deletion and other existing cleanup routines are separate. You can ask us to review your data and submit a deletion request.
- Local progress and preferences
- Until you reset it or remove it from the device. Deleting an account or the app does not automatically erase other copies or provider data.
- Uploaded playtest data
- Existing cleanup uses 90 days from receipt for events and from the last receipt for sessions/installations; for an unused installation, from creation. New activity may keep sessions/installations for longer. Exports are not covered by this period.
- Daily actions, snapshots and finish details
- Policy: 30 days after final gameplay verification and closure of review, provided the edition and earned rewards have been correctly settled. Uncertain requests, open matters and unpaid entitlements remain protected. This new automatic cleanup is not yet active.
- Abandoned Daily attempts
- Policy: 30 days after the later of edition close or the relevant attempt update, only after explicit safe-closure review and with no uncertain finish, claim or other protected dependency. Not automatically active.
- Daily explanation, result and reward audit
- Policy: 24 calendar months from the latest relevant completion, gameplay verification, reward settlement or review closure, subject to the same safety conditions. Minimal evidence against duplicate processing and duplicate rewards is excluded. Not automatically active.
- Redundant account and session context
- Policy: redundant metadata becomes eligible for minimization after 30 days under safe conditions; a session must also have expired. Expired sign-in keys become eligible for one-way redaction at review. The original expiry date continues to apply to any restricted sign-in key for resubmitting a deletion request; session access is valid for a maximum of 180 days. Expiry of access is not proof of physical deletion. New automatic minimization is not active.
- Extended financial and reward context
- Policy: 24 calendar months for each individual context record, from the later relevant action, associated refund/reversal or first account deletion. An unrelated purchase or login does not extend this period. Only redundant context is eligible; not automatically the entire wallet, purchase or transaction. New automatic minimization is not active.
- Minimal purchase, refund, balance, request and duplicate-processing evidence
- For as long as the relevant old requests can still be accepted or a specific obligation or open matter requires the evidence. There is no general fixed end date for this yet. The policy requires at least an annual review of necessity; this is not an automatic extension or a claim that the first full review has already been completed.
- Tax records
- Only data genuinely needed for financial administration follows the applicable statutory retention requirement. This does not make every Hint Coin, ad reference or Player ID a tax record. The exact subset of tax records and applicable exceptions still need to be confirmed against the actual administration.
- App Attest and Game Center security
- Existing policy: single-use App Attest challenges for a maximum of 7 days, with cleanup targeting day 6; active key evidence for as long as the key is needed; revoked key evidence for 30 days unless a relevant review remains open. Expired unused Game Center link challenges have a period of 7 days from issue; this additional cleanup is not yet active.
- Operational context linkable to individuals
- Policy: 90 days for redundant operational audit/role context and closed exception metadata, while retaining minimal necessary authorization evidence and specific open matters. New automatic minimization is not active. Separate technical incident exports: 30 days after actual incident closure, unless a recorded exception is needed. Export cleanup is manual; the inventory of all copies and closure dates is not yet complete.
- Push registrations and delivery data
- Registrations expire after 30 days unless renewed. Existing cleanup of delivery records targets 30 days after the message expires. Disabling notifications does not immediately erase all earlier delivery data.
- Support messages and attachments
- At the first monthly manual review after 12 calendar months have passed since the last relevant contact, unless a justified exception is needed. No automatic support deletion.
Where cleanup exists, it runs in bounded steps; faults and backlogs can delay it. A recorded exception must be reassessed and is not a justification for keeping everything indefinitely. Fraud prevention is not in itself a statutory retention obligation.
Separate recovery and log windows apply to the Cloudflare products used: Workers Logs on the Paid plan has a 7-day window, and D1 Time Travel has a 30-day recovery window. No separate in-house Logpush/R2 server backup archive has been configured. This does not describe all Cloudflare security data or manually retained copies. Account deletion does not immediately erase earlier recovery history.
Deleting your account
In the intended release, you can delete an existing guest account as well as an Apple-linked account in Account Details, with confirmation. You do not have to sign in with Apple first to delete a guest account. If no online account exists yet, the app does not create one just to delete it.
After successful processing, your account access and the relevant sessions are terminated. Apple authorization is revoked where applicable. Account-linked Apple associations, protected Flow copies, hint unlocks and designated claim data are deleted. The app cleans up local account and session data after deletion is confirmed; if an error occurs, information may be needed for a safe retry.
For the official Daily, Game Center links and verification data, App Attest keys and temporary security challenges are deleted, ranking eligibility is withdrawn and identifying references are replaced. This does not automatically delete every attempt, action, result, validation or reward.
Active ad reward sessions are invalidated. A late or repeated Google server confirmation must not grant new Coins to the deleted account. Minimal purchase, refund, wallet, request, account-deletion and duplicate-processing evidence may remain for the purposes described above. This data may still be traceable to a deleted account reference.
Deleting your Flowdots account does not remove the separate progress copy in your iCloud account. Local game progress, separate telemetry, files already shared, support correspondence and data held by Apple or Google have their own lifecycles. Account deletion does not promise complete erasure by every party involved. For an additional request, email support@flowdots.nl.
Service providers, sharing and international processing
Apple provides services including Sign in with Apple, private iCloud/CloudKit progress storage, payments, Game Center, App Attest, push and support email. Cloudflare provides Flowdots servers, databases and server-side notification processing. Google provides ads and consent software; Netlify provides the website and website form. Each service receives data associated with the relevant processing.
Other players can see the ranking information described above. Authorized support staff and Flowdots server administrators can access the data needed to manage the service, resolve problems and handle requests. Google and relevant ad partners may process data as described in the advertising section.
Processing may take place outside the European Economic Area, including in the United States. A transfer must rely on an applicable European adequacy decision or other valid safeguards, such as the European Commission's standard contractual clauses. The EU–US Data Privacy Framework applies only to transfers covered by the relevant US recipient's certification; it is not a general approval of all processing by that service provider.
Apple describes standard contractual clauses for international transfers of personal data collected in the EEA in its privacy policy. Google, Cloudflare and Netlify also describe transfer mechanisms, whose applicability depends on the service, recipient and agreements. This does not promise exclusively European storage or fully verified coverage for every data flow. You can email support@flowdots.nl to ask about relevant recipients and request information or a copy of the applicable safeguards. See Apple, Google, Cloudflare and Netlify.
Why do we process this data?
The GDPR recognizes different grounds for using personal data. Below, we explain which ground applies to each purpose. Requesting a service does not give general consent to other uses of your data.
- Account, sign-in, requested server features, Flow recovery and official Daily participation
- Performance of the contract for the service you request, only for the data needed for that service. This includes necessary progress, actions, results and the associated ranking feature.
- Hint Coins, purchases, restores and refunds
- Performance of the requested purchase, balance and recovery features. Minimal evidence against duplicate credits or reprocessing also serves our legitimate interest in correct transactions and handling disputes. Only genuinely mandatory financial administration is subject to a statutory retention obligation.
- App Attest, security, fraud prevention and game integrity
- Our legitimate interest in protecting accounts, fair participation and transactions. We must balance necessity against your privacy, paying particular attention to minors. This is not a general statutory retention obligation.
- Necessary technical diagnosis
- Our legitimate interest in investigating faults and keeping the service secure and reliable, using as little data as possible. Additional playtest analysis and product improvement do not automatically fall under the game contract or this necessary diagnosis. An appropriate legal basis must be established in advance and, where needed, consent obtained.
- Support and account deletion
- Necessary service relating to your account or purchase is covered by performance of the contract. We handle other ordinary support questions based on our legitimate interest in helping you. Assessing and responding to GDPR rights requests is done to meet our legal obligations.
- Ads and privacy choices
- Where required, valid consent is needed for ad personalization, tracking and non-essential storage or access on your device. Limited ad delivery and necessary security or fraud processing require a separate assessment; Limited Ads does not automatically mean that consent is never needed.
Apple ATT is permission for tracking under Apple's rules. Google UMP records regional choices about purposes and parties. Neither is, by itself, a general GDPR legal basis or proof that a minor can independently give legally valid consent. Choosing “legitimate interest” in a form does not replace our own assessment of necessity and interests. Where the rules for storage or access on a device require consent, legitimate interest cannot replace that consent.
The target audience and App Store age rating of 13+ do not determine the age at which you can independently consent. In the Netherlands, processing based on consent for children under 16 generally requires consent from a parent or legal guardian; other countries may have different limits. The current app does not ask for a date of birth or age category and does not establish parental consent through ATT or UMP. You can ask us about this at support@flowdots.nl.
Your privacy rights
Where the GDPR applies, you can request access to, correction, erasure or restriction of your personal data. Depending on the processing and legal basis, you can request data portability or object, including to processing based on legitimate interests. You can withdraw consent you have given; this does not retrospectively make earlier lawful use unlawful.
Email support@flowdots.nl. We may ask for proportionate information to verify your identity and locate the correct data. We normally respond within one month. If the GDPR allows an extension, we will let you know within that first month. Rights and exceptions are subject to the legal conditions.
You can complain to the supervisory authority in the country where you live or work, or where the possible infringement took place. In the Netherlands, this is the Autoriteit Persoonsgegevens.