Privacy Policy
Effective November 18, 2026
WriteFlow is developed and operated by Juraj Gajdos, an independent developer based in the European Union ("I," "me," or "my"). This Privacy Policy explains how I collect, use, and protect your information when you use WriteFlow on iPhone, iPad, Mac, or an Android device — including the keyboard extension on iOS / iPadOS, the standalone app on macOS, and, on Android, an app and the WriteFlow AI Writing Assistant (the WriteFlow bubble), which uses Android's Accessibility service to work alongside any keyboard (collectively, the "Service").
This policy applies to all users worldwide and covers all three distribution channels: WriteFlow on the App Store (iOS / iPadOS), WriteFlow for Mac as a direct download from this website, and WriteFlow on Google Play (Android).
Where a section applies to some platforms and not others, the heading says so. Anything not marked applies everywhere.
1. Information I collect
1.1 Text input data
When you use an AI feature (Rewrite, Translate, Generate, or custom tiles), the text in your current text field is temporarily sent to a secure server for AI processing. This text is:
- Transmitted over HTTPS with TLS 1.2 or higher
- Processed in real time to generate AI suggestions
- Not stored, logged, or retained on any server after processing is complete
- Not used to train AI models
This applies identically on iOS, iPadOS, macOS, and Android. On Android, WriteFlow works through the WriteFlow AI Writing Assistant (the WriteFlow bubble), which appears next to the text field you tap in another app and works with any keyboard (see 2.4). There, text leaves your device only when you tap a prompt, Ask AI or Dictate in the WriteFlow window, and only the text you selected, or the text from the start of the field up to the cursor, is sent. It is never sent as a side effect of typing.
1.2 Voice input — dictation (macOS and Android only)
WriteFlow can dictate on macOS and on Android: you start a dictation, speak, and a cleaned-up transcript is inserted into whatever you were typing in. On macOS you start it with a keyboard shortcut; on Android you tap the WriteFlow AI Writing Assistant (the WriteFlow bubble) and then Dictate. Dictation is not part of the iOS or iPadOS apps, and those apps never request or use a microphone.
When you start a dictation:
- Audio is captured only between the moment you start the dictation and the moment it ends — either when you stop it yourself, or automatically after a fixed maximum length
- The recording is written to a temporary file on your own device — a cache location the system is free to reclaim — and deleted as soon as it has been sent, and also deleted if you cancel, if it times out, or if the app is closed mid-recording
- It is transmitted over HTTPS to the same secure server that handles text, and forwarded to OpenAI for transcription and a short clean-up pass that removes filler words and restores punctuation
- Neither the audio nor the transcript is stored, logged, or retained on any server after processing completes. When a transcription fails, the error is logged with the failure status only — never the audio and never any transcript
- Not used to train AI models
- The recording is never shared with any other app on your device, and never written anywhere another app could read it
The microphone is never opened unless you start a dictation yourself. There is no always-on listening, no wake word, and nothing is captured before you start or after you finish. See 2.3 for the macOS microphone permission and 2.5 for Android's.
1.3 User preferences (device-local)
The following preferences are stored locally on your device:
- Theme selection (light, dark, system)
- Tile configuration and custom presets
- Your custom prompts
- Haptic feedback preference (iOS and Android)
- Your preferred languages, if you chose any (Android)
- Whether the WriteFlow AI Writing Assistant (the WriteFlow bubble) is on, whether you accepted its disclosure (2.4), and where you last placed it (Android)
- iCloud sync preference (Apple platforms only)
- Privacy consent status
These never leave your device unless you enable iCloud Sync
(see 1.6). On iOS / iPadOS this data lives in the App Group
container shared between the host app and the keyboard extension.
On macOS it lives in standard UserDefaults. On Android
it lives in the app's own private SharedPreferences,
which no other app can read.
Data from the earlier Android keyboard. Versions of WriteFlow for Android before 1.5 included a keyboard, which kept a dictionary of the words you typed and a record of where you tended to touch each key, on your device only. WriteFlow 1.5 has no keyboard and keeps no learned words. The first time you open the app after updating to 1.5, it deletes that data from your device. None of it was ever uploaded.
Android backup. If you have Android's own Backup turned on in your system settings, Android may copy the app's settings (your prompts, your tile arrangement, your preferred languages, your haptic feedback choice, your recent Library searches and the usage counts shown on Home) into the backup held under your Google account, in the same way it does for other apps. The AI Writing Assistant keeps no text, so there is none to back up. That is Google's backup of your device, not a transfer to me, and I cannot read it. Four things are deliberately excluded from it: your signed-in session, the anonymous device identifier described in 1.8, the subscription records RevenueCat's software keeps on the device (1.5), and the AI Writing Assistant's state, including whether you accepted its disclosure, so that every device shows you the disclosure before the assistant can be turned on. A restored or transferred install therefore starts signed out and with fresh identifiers, rather than impersonating the device it came from. One subscription identifier can travel by a separate route that this backup setting does not cover, Google Block Store. That route is described under "Google Block Store" in 1.5.
1.4 Account information (when you sign in)
WriteFlow lets you sign in to use your Pro subscription on multiple devices. Sign-in is optional — the app works without an account, subject to the free-tier limit.
When you sign in, I collect and store:
- A Supabase user ID (an opaque UUID)
- The email address linked to your sign-in identity (whether you signed in with Apple, Google, or email)
- The timestamp of your sign-in
- The identity provider you used (Apple, Google, or email OTP)
On Android, you can sign in with Google or with an email one-time code. Apple sign-in is not offered on Android. Google sign-in goes through Android's own account picker; see Section 4.9 for what Google receives.
This data is stored at Supabase (see Section 4).
Deleting your account. You can ask for your WriteFlow account and the data tied to it to be deleted at any time: in the Android app under Settings → Account → Delete account, or by emailing starsync.dev@outlook.com from your account's address. The account deletion page explains both, and lists what is deleted and what may be kept.
1.5 Subscription information
If you purchase a WriteFlow Pro subscription, the following data is collected by the relevant payment processor and shared with RevenueCat (my entitlement-management provider):
- Subscription tier (Monthly, Six Months, or Yearly)
- Purchase status (active, expired, in grace period)
- Purchase and renewal timestamps
- Receipt or transaction identifier (no card details)
On iOS / iPadOS, payment is processed by Apple through the App Store. On macOS, payment is processed by Stripe (acting as merchant of record via Stripe Managed Payments) through RevenueCat Web Billing.
On Android, payment is processed by Google through
Google Play, and Google is the merchant of record. The app shows
the plans and prices that Google Play reports and opens Google
Play's own payment sheet. It confirms the result through RevenueCat,
using RevenueCat's software and Google's Play Billing Library inside
the app. You buy in the WriteFlow app; when the WriteFlow AI Writing
Assistant (the WriteFlow bubble) offers Pro, it opens the app's plans screen. The payment itself
happens in Google Play. RevenueCat links the purchase to the same
pro entitlement as a purchase on iOS or macOS,
so it unlocks Pro on your other devices once you sign in.
For an Android purchase, RevenueCat receives:
- the Google Play purchase token, with which RevenueCat looks up the order with Google;
- the plan purchased;
- the purchase and renewal times, and the price and currency;
- a RevenueCat app user ID. While you are signed out, this is a random anonymous identifier that RevenueCat's software creates on the device (it begins with
$RCAnonymousID). Once you sign in, it is your WriteFlow account ID.
If you buy while signed out and later sign in, the purchase moves to your account so that you can use it on your other devices.
Google Block Store (Android). While you are signed out on Android and your anonymous RevenueCat app user ID has a subscription attached, RevenueCat's software saves that ID in Google Block Store. Block Store is a small storage area that Google Play services keeps for each app. Google may include it in your Google account's backup and restore it when you set up a new device.
- Only that one identifier is stored. Nothing else about you or your purchase is stored there.
- It is stored only while you are signed out and the anonymous identifier has a subscription attached, whether you bought on this install or Google Play restored an earlier purchase to it. It is removed when you sign in on that device.
- On a later install, RevenueCat reads it back only while you are still signed out, and only when a purchase completes or purchases are restored. It then links the earlier anonymous purchase to the new install, so the purchase stays with you.
- Block Store is separate from the Android backup described in 1.3. The app's own backup exclusions do not apply to it.
- It is held by Google under Google's privacy policy, and I cannot read it.
Card numbers, billing addresses, and other payment-method details are handled exclusively by Apple, Stripe, or Google. I do not receive, store, or have any access to them, and on Android your Google account details are not passed to me either.
Purchase event history. Each notification RevenueCat sends about your subscription — a purchase, a renewal, a cancellation, an expiry — is recorded so that I have a record of billing history if a question arises. Each record holds the event type and time, the product purchased, which store it came from, the price and currency, the billing period type, the expiry date, and your account identifier. It contains no card details and nothing about your use of the app.
Devices on a Pro subscription. A Pro subscription may be used on up to six devices. To enforce that, I record for each device the anonymous device UUID, your account identifier, which platform it is (Mac, iPhone/iPad, or Android), and when it was first and last seen. No other information about the device is collected. If you sign in on a seventh device, the one you have not used for the longest is signed out to make room; you can sign it back in, which will displace a different one.
1.6 iCloud data
iCloud Sync is off unless you turn it on in Settings. While it is off, nothing leaves your device through iCloud.
If you switch it on, what syncs across your devices is:
- iOS / iPadOS: your tiles and their arrangement, and your theme and haptic preference
- macOS: your tiles and their arrangement, your custom prompts, and your theme
That is the whole of it. Your text, your dictation, your usage counts, and your account details are never put into iCloud. Sync travels through Apple's iCloud Key-Value Storage under whichever Apple ID is signed in to the device — which is separate from your WriteFlow account — and while it is there the data is governed by Apple's iCloud terms and privacy policy. I cannot read it.
iCloud Sync uses your macOS or iOS Apple ID, which is independent from your WriteFlow sign-in. You can have one without the other.
1.7 Purchase-funnel events (iOS / iPadOS only)
To understand whether the subscription flow actually works — how many people reach the paywall, and where they drop out — the iOS and iPadOS apps report a small, fixed set of events. This is first-party: there is no third-party analytics SDK in any WriteFlow app. The macOS app reports none of this.
The complete list of events is:
- The paywall was shown
- A plan was tapped (which of the three: monthly, six-month, yearly)
- The outcome of a purchase attempt (success, pending, cancelled, unverified, failed)
- The free daily limit was reached (at most once per day per device)
- The sign-in sheet was shown, and whether you signed in or skipped
Each event carries only its name, one short detail from the list above, the platform, and an identifier — your account ID if you are signed in, otherwise the anonymous device UUID. The server accepts only the event names listed above and rejects anything else, so these records cannot be widened to carry other information.
They contain no text you wrote, no prompt or tool you used, no audio, and no record of how often you use the AI features.
These events are kept for 90 days and then deleted automatically by a scheduled nightly job — I do not hold them indefinitely. What remains after that is a daily count per platform with no identifier attached to it, which cannot be traced back to you or your device. If you would rather not wait, email me and I will delete the records associated with your account or device.
1.8 Information I do NOT collect
- I do not collect keystrokes or typing patterns
- I do not collect passwords, credit card numbers, or other sensitive field data
- I do not collect contacts, photos, location, or advertising identifiers. The one device identifier I do use is an anonymous UUID generated by the app itself and never synced — stored in your device's keychain on Apple platforms, and in the app's private storage on Android. It is used to count your free daily allowance, to attribute the events in 1.7 when you are not signed in, and to recognise your devices against the Pro device limit in 1.5. It is not derived from your hardware and is not any of the identifiers Android exposes — not the Advertising ID, not the Android ID, not the IMEI, not the MAC address. It is not linked to your Apple ID or your Google account. Uninstalling the app, or clearing its data, discards it and the next launch generates an unrelated one. Subscriptions use one further identifier: the RevenueCat app user ID described in 1.5. On Android it is also random while you are signed out, and RevenueCat's software is configured not to collect the Advertising ID or any other device identifier
- I do not use any third-party analytics, crash reporting, advertising, or tracking SDK — the only events recorded are the purchase-funnel ones listed in 1.7. The Android app contains no such SDK either: no Firebase, no Crashlytics, no ad library. Its network dependencies are an HTTP client, used to call the endpoints named in 2.4, and, for subscriptions only, RevenueCat's software together with Google's Play Billing Library (1.5, 4.3)
- I do not collect the names of the apps you use WriteFlow in. A request carries the text you asked me to work on and nothing about where you were typing it. On Android, the WriteFlow AI Writing Assistant (the WriteFlow bubble) uses the app's name on your device only, to decide whether to show itself there
- I do not record which AI tools or prompts you use, or how many times you use them
- I do not collect any data when the keyboard, the app or the AI Writing Assistant is open without you triggering an AI feature
- I do not sell your personal information to anyone
2. Permissions
2.1 iOS / iPadOS — "Allow Full Access"
WriteFlow's keyboard extension requests "Allow Full Access" in iOS Settings. This permission is required solely to enable the keyboard to make network requests to the AI processing server. Without Full Access, AI features will not function and no data leaves your device.
With Full Access enabled:
- Text is only transmitted when you actively tap an AI tile
- The keyboard does not passively monitor or transmit what you type
- Network requests go only to my own backend, and only to these endpoints: the AI processing endpoint; a check of how much of your free daily allowance remains; the purchase-funnel events in 1.7; and, once when you first sign in, a one-off request that moves your existing daily usage count from your device to your new account. Nothing is sent to any other destination.
2.2 macOS — Accessibility permission
WriteFlow on macOS requests Accessibility access (System Settings → Privacy & Security → Accessibility). This permission is required solely to read your currently selected text and replace it with the AI-rewritten version, which is the core function of the app.
With Accessibility access:
- Text is only read when you actively trigger an AI feature (e.g., the global keyboard shortcut)
- The app does not passively monitor or log what you type
- It does not record screen contents or interact with other applications beyond the read/replace gesture you initiate
You can revoke Accessibility access at any time in System Settings. The app will continue to launch but AI features will stop working.
2.3 macOS — Microphone permission
WriteFlow on macOS asks for microphone access (System Settings → Privacy & Security → Microphone) the first time you use dictation. It is required solely to record the speech you are dictating.
- The microphone is opened only when you start a dictation, and closed as soon as it ends
- The app does not listen in the background, and cannot record while no dictation is running
- Nothing is captured before you press the shortcut or after the dictation finishes
Dictation is entirely optional. If you never use it you can leave the permission unasked or switch it off, and every other feature continues to work. You can revoke it at any time in System Settings; only dictation stops working.
The iOS and iPadOS apps do not request microphone access at all.
2.4 Android — the WriteFlow AI Writing Assistant (Accessibility service)
On Android, WriteFlow works through the WriteFlow AI Writing Assistant (the WriteFlow bubble), a small button that appears next to the text field you tap in another app, so you can use your prompts and dictation with any keyboard. It is off until you turn it on. It works through Android's Accessibility service. Before Android's Accessibility settings open, WriteFlow shows a screen that explains exactly what it does, and the service does nothing until you have agreed to it there. Android then asks you to confirm in its own words, as it does for every app that uses this service; that warning describes what such a service is able to do, and the list below is what WriteFlow does. WriteFlow is not an accessibility tool, and it uses this access for the AI Writing Assistant and its window and nothing else.
- To decide when to show the WriteFlow bubble, it checks only the field's type and settings (such as whether it is a password field or marked sensitive), its label, identifier and position, whether the same screen has a password field, whether a keyboard is open, and whether the phone is locked. It does not read the words you type to do this; while you type, it only notes how long the text is
- Tapping the WriteFlow bubble reads only where the text and cursor are in that field, so the window can be placed clear of them. The words are read only after you tap a prompt, Ask AI or Dictate in the WriteFlow window, and nothing else on your screen is ever read
- Only the text you selected, or the text from the start of the field up to the cursor, is sent, over the same encrypted connection as the rest of WriteFlow (1.1, 1.2). The rest of the field is not sent. The result is shown to you first and written into the field only when you confirm it. When you use Ask AI, the instruction you type or say is sent with that text, or on its own when the field is empty. The name of the app you are typing in is never sent
- While you type an instruction for Ask AI, the keyboard types into WriteFlow's own box; WriteFlow then puts the cursor back in your field
- Your text is not stored. While the WriteFlow window is open it keeps the part that was sent, your instruction and a fingerprint of the field, so it can check that nothing changed before it writes; both are discarded when the window closes. Text is never written to any log
- Dictation records only after you tap Dictate, and the microphone closes when the recording ends or the window closes. The audio goes to the WriteFlow transcription service as described in 1.2
- The WriteFlow bubble never appears, and no text is read, in password fields, in username and sign-in fields, in fields an app marks as sensitive, or in fields that look like a PIN, a one-time code or a card number. It also stays hidden on the lock screen and inside WriteFlow, except in WriteFlow's own practice fields described below
- The practice fields in onboarding and in Settings → Practice are WriteFlow's own text fields holding a sample message. The WriteFlow bubble works on them as in any other app: when you run a prompt there, the text you chose (the selection, or the text up to the cursor, with your Ask AI instruction) is sent to the WriteFlow AI service like any other prompt (1.1), marked as practice, up to 100 times per device. These tries are counted apart from your free daily prompts and never against your plan; the server keeps only a count of them for your anonymous device identifier, never the text. When you are offline or the tries are used up, Proofread shows a built-in example produced on your device and nothing is sent
- Dictation in those practice fields records only after you tap Dictate and is sent to the WriteFlow transcription service (1.2) with the same practice mark, counted from the same 100 tries. Until that part of the service is live, the recording is deleted on the device without being sent or transcribed and a sample sentence is inserted instead
- If an app does not accept the text directly, WriteFlow pastes it through the clipboard, marked as sensitive, and clears the clipboard afterwards. Android does not let it read what was on the clipboard before, so that earlier content is cleared, not restored, and WriteFlow tells you when this happens
- When its window would not fit above your keyboard, WriteFlow may hide the keyboard while the window is open and brings it back when the window closes
- The WriteFlow bubble and its window are drawn by the Accessibility service itself. WriteFlow does not ask for permission to display over other apps
You can turn it off at any time in WriteFlow → Settings → WriteFlow in other apps, or in Android Settings → Accessibility.
Network requests and permissions on Android.
- Network requests go only to my own backend, and only to these endpoints: the AI processing endpoint; the dictation transcription endpoint; a check of how much of your free daily allowance remains; sign-in; and, once when you first sign in, a check against the six-device Pro limit together with a one-off request that moves your existing daily usage count from your device to your new account. Apart from Google sign-in, if you choose it (4.9), the one other destination is subscriptions: to show prices, make a purchase, and check whether you have Pro, the app talks to Google Play (through Play Billing on your device) and to RevenueCat's servers (1.5, 4.3). Those requests carry the RevenueCat app user ID and the details RevenueCat's software needs to operate: the app and Android versions, the device brand and model, your language settings, and your Play Store country. They never carry text you typed. Nothing is sent to any other destination.
- Every request to my own backend carries, alongside the content you asked me to process: the anonymous device UUID from 1.8, your time-zone offset (used only to decide which local day a request counts against), the word "android", the app and Android version numbers, and the RevenueCat app user ID from 1.5, so that the server can check with RevenueCat whether you have Pro. It does not carry your name, your email unless you are signed in, any hardware identifier, or the name of the app you were typing in. If you chose languages under Settings → Preferred Languages, AI and dictation requests also carry the codes of those languages, so that the result stays in them; with Automatic detection, nothing about language is sent.
The Android app declares these permissions:
- Internet access, which is what makes the AI features possible at all.
- Google Play billing, which lets the app open Google Play's purchase sheet.
- Network state, which RevenueCat's software uses to tell whether the device is online.
- Biometric and fingerprint use, which are declared by Google's Credential Manager library, the software behind "Sign in with Google", for its own optional fingerprint or face confirmation of a saved credential. WriteFlow itself never asks for or uses your biometrics, and Android never passes biometric data to apps.
- Microphone, covered next.
Android grants all of these except the microphone at install time without prompting. There is no permission for contacts, location, storage, phone state, or installed-app queries, because nothing in the app needs one. The Accessibility service described above is not one of these permissions: it is a setting you switch on yourself, after the disclosure, and it adds no permission of its own.
2.5 Android — Microphone permission
WriteFlow on Android asks for microphone access the first time you start a dictation. It is required solely to record the speech you are dictating.
- The microphone is opened only when you start a dictation, and closed as soon as it ends — including when the WriteFlow window closes mid-dictation
- The app does not listen in the background, and cannot record while no dictation is running
- Nothing is captured before you tap Dictate or after the dictation finishes
- A recording has a hard maximum length enforced by the recorder itself, so a clip cannot run on unbounded even if something goes wrong
Android does not allow an Accessibility service to show a permission prompt directly, so the request is made by a small transparent screen that appears for a moment and then closes. That screen exists only to ask; it does nothing else.
Dictation is entirely optional. If you never use it you can leave the permission unasked or deny it, and every other feature continues to work. You can revoke it at any time in Android Settings → Apps → WriteFlow → Permissions; only dictation stops working.
3. How I use your information
Text submitted through AI features is used exclusively to:
- Generate rewritten, translated, or AI-composed text
- Return suggestions to your device in real time
Dictation audio (1.2) is used exclusively to:
- Produce a transcript of what you said
- Clean that transcript up — remove filler words, restore punctuation — before it is inserted
Account information (1.4) is used to:
- Authenticate you on the device
- Sync your Pro subscription entitlement across your devices
Subscription information (1.5) is used to:
- Verify whether you have an active Pro subscription
- Enable Pro features when entitled
Purchase-funnel events (1.7) are used exclusively to:
- Count how many people reach the paywall and complete or abandon a purchase
- Decide whether the subscription and sign-in flows need changing
I do not use any of this data for advertising, profiling, or cross-site tracking, and I do not analyse your writing or your use of the AI features.
4. Data sharing — sub-processors
I do not sell, rent, trade, or otherwise share your personal data with third parties for marketing, advertising, or profiling purposes.
To operate the Service I rely on a small number of sub-processors:
4.1 OpenAI — AI processing
- Provider: OpenAI, L.L.C. (San Francisco, CA, USA)
- Role: Generates the AI suggestion from your text, and on macOS and Android transcribes dictation audio and cleans up the resulting transcript
- Data sent: The text content you choose to process; on macOS and Android, dictation audio (1.2). Each request also carries a one-way hashed identifier derived from your account ID or anonymous device UUID — OpenAI requires a stable per-user identifier so that misuse can be attributed to an individual rather than to the whole account. It cannot be reversed to identify you, and it is not sent with any of your text.
- Storage: Processed in real time, with requests marked so that OpenAI does not retain them. With API usage, OpenAI does not use your data to train their models (per OpenAI's API data usage policy).
- Documentation: OpenAI Privacy Policy, API Data Usage Policy
4.2 Supabase — Backend infrastructure
- Provider: Supabase, Inc. (San Francisco, CA, USA)
- Role: Hosts the WriteFlow edge function that proxies AI requests to OpenAI, the user authentication system (Supabase Auth), and the database mirroring your subscription entitlement
- Data passing through: Your AI request text, and dictation audio on macOS and Android (both held only transiently in memory while the request is forwarded to OpenAI — not logged or retained); your account information (1.4); your subscription entitlement state mirrored from RevenueCat; the purchase-funnel events in 1.7
- Operational logs: For each AI request the backend writes one diagnostic line into Supabase's log system, so that I can tell whether subscription checks are working. It records the outcome of the entitlement check, the platform, the app version, and a one-way hash of your subscription identifier. It contains no text, audio, or transcript, and the hash cannot be reversed to identify you.
- Documentation: Supabase Privacy Policy
4.3 RevenueCat — Subscription management
- Provider: RevenueCat, Inc. (San Francisco, CA, USA)
- Role: Aggregates subscription state from Apple (App Store), Google (Google Play, for Android) and Stripe (RevenueCat Web Billing for macOS), surfaces a unified entitlement to the app, and notifies the backend on purchase events
- Android: RevenueCat also handles Google Play subscriptions. The Android app contains RevenueCat's software, which receives the purchase from Google Play, has RevenueCat confirm it with Google, and reports whether you have Pro. The same data is sent as on iOS, with a Google Play purchase token in place of an App Store receipt (1.5). On Android this software is configured not to collect the Advertising ID or other device identifiers. It may store one anonymous identifier in Google Block Store, as described in 1.5.
- Data sent: Your device or user identifier, transaction receipts or purchase tokens, subscription tier, purchase/renewal timestamps. No card details.
- Technical details sent by RevenueCat's software: app and operating-system versions, device model, language and store country, and, when RevenueCat enables it, diagnostics about the software's own operation, such as how long its requests took and which ones failed. These contain no text you wrote and nothing about how you use the AI features.
- Also sent when you sign in: your email address, and your full name if your identity provider supplied one. These are attached to your RevenueCat subscriber record so that a subscription can be recognised as belonging to a person rather than a bare UUID — which is what makes it possible for me to help when you write in about billing. They play no part in deciding whether you have Pro.
- Documentation: RevenueCat Privacy Policy
4.4 Apple — App Store payments (iOS / iPadOS only)
- Provider: Apple, Inc. (Cupertino, CA, USA)
- Role: Processes subscription payments and acts as merchant of record for in-app purchases on iOS / iPadOS
- Data shared: Whatever the App Store transaction normally entails (App Store account ID, payment method, country). I do not receive any of this directly.
- Documentation: Apple Privacy Policy
4.5 Stripe — Web payments (macOS only)
- Provider: Stripe Payments Europe, Ltd. (Dublin, Ireland) / Stripe, Inc. (San Francisco, CA, USA)
- Role: Processes subscription payments for the macOS direct-download app via RevenueCat Web Billing. Stripe acts as merchant of record under Stripe Managed Payments, meaning Stripe is responsible for VAT / sales-tax collection and remittance.
- Data shared: Card details, billing email, country, and any other information you enter on the Stripe Checkout page. I never see your card number. Stripe shares only a transaction identifier and status with RevenueCat and my backend.
- Documentation: Stripe Privacy Policy
4.6 Resend — Transactional email
- Provider: Resend (Wilmington, DE, USA)
- Role: Delivers sign-in OTP emails (and any other transactional email Supabase sends on my behalf)
- Data sent: Your email address and the email body (containing the one-time code or magic link)
- Documentation: Resend Privacy Policy
4.7 Apple iCloud — Optional cross-device sync
- Provider: Apple, Inc.
- Role: When you switch iCloud Sync on, syncs your tiles and theme between your Apple devices — plus your custom prompts on macOS, and your haptic preference on iOS. Nothing else. See 1.6
- Data shared: Tile configuration, custom prompts, theme preference
- Documentation: Apple iCloud Terms
4.8 Cloudflare — Website hosting and macOS auto-updates
- Provider: Cloudflare, Inc. (San Francisco, CA, USA)
- Role: Hosts writeflowapp.org and serves the macOS auto-update manifest (
appcast.xml) and DMG/ZIP artifacts to the Sparkle update framework inside the macOS app - Data exposed: Standard HTTP request metadata (IP address, User-Agent, timestamp) when your Mac checks for updates. Cloudflare may retain this in standard server logs.
- Documentation: Cloudflare Privacy Policy
4.9 Google — Sign-in, Google Play, and web fonts
- Provider: Google LLC (Mountain View, CA, USA)
- Role — sign-in: If, and only if, you choose "Sign in with Google", Google authenticates you and returns an identity token which is exchanged for a WriteFlow session. Choose Apple or an email code instead and Google receives nothing. On Android, Google sign-in uses Android's Credential Manager, which shows the Google accounts on the device for you to pick from — see 1.4.
- Data exposed by sign-in: Whatever Google's own sign-in flow involves, plus the fact that you signed in to WriteFlow. I receive your email address and, if you have one set, your name — see 1.4.
- Role — Google Play (Android only): Google Play distributes the Android app and delivers its updates. Installing, updating, and purchasing a subscription through Play are transactions between you and Google, under Google's own privacy policy. Google is the merchant of record for Android subscriptions (1.5). Google provides me with aggregate, non-identifying statistics in the Play Console: install and uninstall counts, crash and ANR reports gathered by the platform itself, and ratings and reviews. For a purchase, it also provides the order record that any Play developer receives. I do not receive your Google account identity.
- Role — Google Play Billing and Block Store (Android only): To show prices and complete a purchase, the app uses Google's Play Billing Library, which talks to the Google Play app on your device. RevenueCat's software may also store one anonymous identifier in Google Block Store (see 1.5). Beyond these and the optional sign-in above, the app sends nothing to Google.
- Role — web fonts: The pages of this website load a typeface from Google Fonts. Your browser therefore contacts Google when you visit, which exposes your IP address and User-Agent to Google. This affects the website only — the iOS, iPadOS, macOS, and Android apps do not load anything from Google.
- Documentation: Google Privacy Policy
No data is shared with any other third party.
5. Auto-updates (macOS only)
The macOS app uses the Sparkle update framework
to check for new versions and offer to install them. Periodically
(typically once per day on first launch), the app fetches
appcast.xml from
https://writeflowapp.org/dl/appcast.xml. This request
reveals to Cloudflare your IP address, User-Agent, and the fact
that you are running WriteFlow.
If a new version is available, Sparkle prompts you before downloading or installing anything. You can disable update checks in Settings.
The iOS / iPadOS app updates exclusively through Apple's App Store and does not include Sparkle. The Android app updates exclusively through Google Play and likewise contains no update framework of its own — it never contacts writeflowapp.org to check for a version, and Cloudflare therefore sees nothing from it.
6. Data retention
| Data | Where | Retention |
|---|---|---|
| Text submitted to AI features | OpenAI + Supabase Edge Function | Not retained. Discarded immediately after processing. |
| Dictation audio and transcripts (macOS and Android) | Your own device, then OpenAI + Supabase Edge Function | Not retained. The temporary file on your device is deleted as soon as it is sent, or on cancel, timeout, or app close; nothing is stored server-side. |
| Free-tier daily usage counter | Supabase | Deleted automatically after 7 days. A count only — no record of what you did. |
| Onboarding/Practice tries counter (Android) | Supabase | A count of prompt and dictation practice tries per anonymous device identifier, kept so the 100 tries are not reset. No record of the text or the audio. |
| Purchase-funnel events (1.7, iOS only) | Supabase | 90 days, then deleted automatically by a scheduled nightly job. You can also ask me to remove your records sooner. |
| Account information (Supabase Auth) | Supabase | Until you delete your account. Request deletion in the Android app or as described on the account deletion page. |
| Subscription state | RevenueCat + Supabase | Until you delete your account, or per RevenueCat / Apple / Google / Stripe statutory retention requirements (typically up to 7 years for tax/audit). |
| Anonymous RevenueCat ID in Google Block Store (Android, 1.5) | Google Play services on your device, and your Google account's backup | Only while signed out with a subscription attached to the anonymous ID, bought on that install or restored to it by Google Play. Removed when you sign in on that device; otherwise kept per Google's Block Store and backup retention. I have no access to it. |
| Purchase event history (1.5) | Supabase | Kept as billing history. Deleted with your account on request. |
| Pro device records (1.5) | Supabase | Until you sign the device out, it is displaced by the six-device limit, or you delete your account. |
| Operational request logs (4.2) | Supabase logs | Per Supabase's log retention for the project. Contains no text, audio, or transcript. |
| Email delivery logs | Resend | Per Resend's retention policy (typically 30 days). |
| Device-local preferences | Your device | Deleted when you uninstall, reset to defaults, or sign out. |
| Text read by the WriteFlow AI Writing Assistant (the WriteFlow bubble; Android, 2.4) | Your device, while the WriteFlow window is open | Discarded when the window closes. Never written to storage or to any log. |
| Android backup of app settings (1.3) | Your own Google account | Per Google's backup retention, and only if you have Android Backup on. Excludes your session, your device identifier, RevenueCat's on-device subscription records and the AI Writing Assistant's state. I have no access to it. |
| iCloud-synced preferences | Apple iCloud | Per Apple's iCloud retention. Disable iCloud Sync to stop. |
| Web traffic / update check logs | Cloudflare | Per Cloudflare's standard log retention. |
7. Data security
I implement appropriate technical measures to protect your data:
- All network communication uses HTTPS with TLS 1.2 or higher
- No persistent server-side storage of your AI text. It exists in transient memory only during the request.
- App-level data on iOS is sandboxed within Apple's security model; on macOS it lives inside the app sandbox and is signed and notarized by Apple; on Android it lives in the app's private storage, which Android's per-app sandbox keeps other apps out of
- On Android, your signed-in session is stored encrypted under a key held in the device's hardware-backed keystore, which cannot be exported. That is also why the session is left out of Android's backup: the ciphertext would be undecryptable anywhere else, so a restored install starts signed out rather than carrying a copy of your credentials
- The Android app permits no plaintext HTTP traffic in release builds; every request is HTTPS or it does not happen
- iCloud-synced data is encrypted by Apple in transit and at rest
- Supabase Auth credentials and API keys are managed via environment configuration; the iOS, macOS, and Android apps use a public anon key only
What this does and does not cover. Transit encryption protects your text from being intercepted on the network. It is not end-to-end encryption: the WriteFlow edge function and OpenAI's API briefly process your text as plaintext in memory to generate AI suggestions. No party other than you, my infrastructure, and OpenAI has access to the content, and none of it is persisted.
8. International data transfers
When you use an AI feature, your text is sent to servers operated by Supabase and OpenAI, both located in the United States. Account data sits at Supabase (US). Stripe payments are processed via Stripe's EU/US infrastructure; Apple App Store payments stay within Apple's infrastructure, and Google Play payments within Google's. Subscription records are held by RevenueCat (US).
If you are located outside the United States (including within the European Economic Area), this constitutes an international data transfer. Such transfers are protected by:
- Encryption in transit (HTTPS with TLS 1.2 or higher)
- The contractual obligations of OpenAI, Supabase, RevenueCat, Stripe, Resend, and Cloudflare to protect your data under their terms of service
- Standard contractual clauses (where applicable) and other safeguards in accordance with GDPR Articles 44–49
9. Legal basis for processing (EEA / UK users)
Under the General Data Protection Regulation (GDPR), I process your data on the following legal bases:
- Consent (Art. 6(1)(a)) — for AI text processing. You provide explicit consent through the in-app privacy consent screen before any data processing occurs. You may withdraw consent at any time by disabling Full Access (iOS), Accessibility access (macOS), or the WriteFlow AI Writing Assistant (the WriteFlow bubble) on Android.
- Contract performance (Art. 6(1)(b)) — for processing your text through AI features and for delivering your subscription.
- Legitimate interest (Art. 6(1)(f)) — for free-tier rate limiting and enforcing the Pro device limit (using an anonymous device UUID to prevent abuse); for the operational request logs in 4.2, which keep subscription checks working; for the purchase-funnel counts in 1.7, so that I can tell whether the upgrade screens function; and for delivering security-related transactional emails.
- Legal obligation (Art. 6(1)(c)) — for retention of subscription and payment records by Apple, Google, Stripe, and RevenueCat where required by tax or commercial law.
10. Your privacy rights
10.1 All users
Regardless of where you are located, you can:
- Stop AI data processing at any time by disabling Full Access (iOS), Accessibility access (macOS), or by turning off WriteFlow in other apps in the app's Settings or in Android Settings → Accessibility (Android)
- Delete local data by uninstalling the app or using "Reset to Defaults" in Settings. On Android, "Clear storage" in Android Settings → Apps → WriteFlow also removes the app's settings and the anonymous device identifier
- Revoke microphone access at any time — System Settings on macOS, Android Settings → Apps → WriteFlow → Permissions on Android — which stops dictation and nothing else
- Disable iCloud Sync in the app's settings to stop cross-device syncing
- Turn off Android Backup in your device settings if you do not want Google's backup to include the app's settings (see 1.3)
- Delete your WriteFlow account from the Android app (Settings → Account → Delete account) or by emailing starsync.dev@outlook.com, as described on the account deletion page. I will action the deletion within 30 days.
- Cancel your subscription at any time via your Apple ID Settings (iOS), your RevenueCat billing portal (macOS), or Google Play → Payments & subscriptions → Subscriptions (Android). Refunds for Android purchases are handled by Google under Google Play's refund policy; see the Terms of Use
- The anonymous RevenueCat identifier in Google Block Store (1.5) is removed when you sign in on that device. If you would rather not sign in, email me and I will delete the RevenueCat customer record it refers to. The identifier then refers to nothing
- Contact me with any privacy-related questions or requests at starsync.dev@outlook.com
10.2 European Economic Area, UK, and Swiss users (GDPR / UK GDPR)
You additionally have the right to:
- Access: Request confirmation of whether your personal data is being processed and obtain a copy of it
- Rectification: Request correction of inaccurate personal data
- Erasure: Request deletion of your personal data
- Restrict processing: Request restriction of processing in certain circumstances
- Data portability: Request your data in a structured, machine-readable format
- Object: Object to processing of your personal data
- Withdraw consent: At any time, without affecting the lawfulness of prior processing
- Lodge a complaint: With a supervisory authority in the EU member state of your habitual residence, place of work, or place of the alleged infringement
10.3 California users (CCPA / CPRA)
California residents have the right to:
- Know: Request disclosure of the categories and specific pieces of personal information collected
- Delete: Request deletion of your personal information
- Opt-out of sale: I do not sell personal information. No opt-out is necessary.
- Non-discrimination: You will not be discriminated against for exercising your privacy rights
Categories of personal information collected: Text input (only during active AI processing, not retained); audio recordings, on macOS and Android only and only while a dictation you started is running (transmitted for transcription, not retained — see 1.2); account information (email, name where your provider supplies one, Supabase user ID); subscription metadata and purchase event history (no card details); commercial information (which devices carry your subscription); internet activity (the purchase-funnel counts in 1.7 and the operational request logs in 4.2); device-local preferences (not transmitted); anonymous device UUID (rate limiting, device limit, and attributing 1.7 events before sign-in); RevenueCat app user ID (subscriptions, 1.5).
Categories of personal information sold: None.
Categories shared for cross-context behavioral advertising: None.
10.4 Brazilian users (LGPD)
Under the Lei Geral de Proteção de Dados (LGPD), you have rights of confirmation, access, correction, anonymization, portability, deletion, information about data sharing, and revocation of consent. Contact me to exercise any of these rights.
10.5 Other jurisdictions
If you are located in another jurisdiction with specific data protection rights, I will honor those rights to the extent required by applicable law. Contact me to exercise your rights.
11. Children's privacy
WriteFlow is not directed at children. The minimum age to use WriteFlow is:
- 16 years in the European Economic Area (in accordance with GDPR Article 8)
- 13 years in the United States (in accordance with COPPA)
- The minimum age required by local law in all other jurisdictions
I do not knowingly collect personal information from children under the applicable age. If you believe a child has provided personal data through the Service, please contact me and I will delete it promptly.
12. Do Not Track
WriteFlow does not track users across third-party websites or services, does not build advertising or behavioural profiles, and contains no third-party tracking SDK. The only events recorded are the purchase-funnel ones described in 1.7, which are first-party and never leave my own infrastructure. I do not respond to Do Not Track (DNT) browser signals, as no cross-site tracking occurs for them to apply to.
13. Changes to this policy
I may update this Privacy Policy from time to time. Changes will be reflected by updating the effective date above. For significant changes, I will provide notice through the app. Continued use of WriteFlow after changes constitutes acceptance of the updated policy.
14. Data controller and contact
The data controller responsible for your personal data is:
Juraj Gajdos
Email: starsync.dev@outlook.com
Location: European Union
If you are in the EEA and wish to lodge a complaint, you may contact the data protection authority in your country of residence. A list of EEA data protection authorities is available at edpb.europa.eu.