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:

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:

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:

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:

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):

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:

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.

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:

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:

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

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:

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:

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.

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.

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.

The Android app declares these permissions:

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.

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:

Dictation audio (1.2) is used exclusively to:

Account information (1.4) is used to:

Subscription information (1.5) is used to:

Purchase-funnel events (1.7) are used exclusively to:

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

4.2 Supabase — Backend infrastructure

4.3 RevenueCat — Subscription management

4.4 Apple — App Store payments (iOS / iPadOS only)

4.5 Stripe — Web payments (macOS only)

4.6 Resend — Transactional email

4.7 Apple iCloud — Optional cross-device sync

4.8 Cloudflare — Website hosting and macOS auto-updates

4.9 Google — Sign-in, Google Play, and web fonts

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

DataWhereRetention
Text submitted to AI featuresOpenAI + Supabase Edge FunctionNot retained. Discarded immediately after processing.
Dictation audio and transcripts (macOS and Android)Your own device, then OpenAI + Supabase Edge FunctionNot 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 counterSupabaseDeleted automatically after 7 days. A count only — no record of what you did.
Onboarding/Practice tries counter (Android)SupabaseA 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)Supabase90 days, then deleted automatically by a scheduled nightly job. You can also ask me to remove your records sooner.
Account information (Supabase Auth)SupabaseUntil you delete your account. Request deletion in the Android app or as described on the account deletion page.
Subscription stateRevenueCat + SupabaseUntil 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 backupOnly 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)SupabaseKept as billing history. Deleted with your account on request.
Pro device records (1.5)SupabaseUntil you sign the device out, it is displaced by the six-device limit, or you delete your account.
Operational request logs (4.2)Supabase logsPer Supabase's log retention for the project. Contains no text, audio, or transcript.
Email delivery logsResendPer Resend's retention policy (typically 30 days).
Device-local preferencesYour deviceDeleted 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 openDiscarded when the window closes. Never written to storage or to any log.
Android backup of app settings (1.3)Your own Google accountPer 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 preferencesApple iCloudPer Apple's iCloud retention. Disable iCloud Sync to stop.
Web traffic / update check logsCloudflarePer Cloudflare's standard log retention.

7. Data security

I implement appropriate technical measures to protect your data:

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:

9. Legal basis for processing (EEA / UK users)

Under the General Data Protection Regulation (GDPR), I process your data on the following legal bases:

10. Your privacy rights

10.1 All users

Regardless of where you are located, you can:

10.2 European Economic Area, UK, and Swiss users (GDPR / UK GDPR)

You additionally have the right to:

10.3 California users (CCPA / CPRA)

California residents have the right to:

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:

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.