NoteFlow Privacy Policy

Last updated: 25 October 2026

Effective date: 25 October 2026

NoteFlow is a note-taking application. This policy explains how information is handled when you use its local features, optional Google Drive synchronization, Premium purchases, crash reporting, and support services. References to "we" mean the developer operating NoteFlow, as identified in its app-store listing.

Privacy contact: noteflowhelp@gmail.com.

For processing whose purposes and means we determine, the store-listed developer is the data controller. Google and the app store also handle information for their own services under their applicable terms and privacy notices. Having no separate NoteFlow note-storage server does not mean that no personal information is processed by the app's service integrations.

Related document: Terms of Use.

1. The essentials

• Notes are primarily stored on your device. Connecting Google Drive enables synchronization with your own Google account; it is optional.
• Premium purchases are processed by the app store and verified through RevenueCat. You do not need to create a separate NoteFlow account.
• Firebase Crashlytics automatically processes technical crash information to help us diagnose problems in the production app, for both free and Premium users.
• Some fonts may be downloaded from Google when they are not already bundled or cached.
• We do not sell personal information or use your notes or Google Drive information for advertising, cross-app tracking, or training AI models.

The app can contain personal or sensitive information that you choose to write in your notes. Consider what you store, where you export it, and who can access your device or Google account.

2. Information stored on your device

NoteFlow stores note titles, rich-text content, a derived search index, folders, labels, colors, pinning preferences, creation and modification dates, trash information, and reminder settings. It also stores app preferences, purchase-access cache entries, and technical synchronization records.

This information supports editing, search, organization, reminders, widgets, local backup, and synchronization. We do not operate a separate NoteFlow server that receives your note library for these features.

Local backups are exported to the location or service you choose through your device's file interface. These files can contain the full exported note library and are not password-encrypted by NoteFlow. A recipient or service you share a backup with handles that copy under its own practices.

Your operating system may separately back up or transfer app data depending on your device settings. Such operating-system services are distinct from NoteFlow's Google Drive synchronization.

3. Optional Google Drive synchronization

When you connect Google Drive, NoteFlow uses Google's authorization flow. NoteFlow does not ask for or receive your Google password. Google manages the authorization grant; the app uses access credentials supplied through Google's SDK to make authorized requests.

NoteFlow requests the drive.appdata permission. This lets it manage its own application-specific data in your Google Drive account, not browse arbitrary personal Drive documents. Synchronization files are stored in Drive's application-data area and are not published as public files by NoteFlow.

The app accesses your Drive account identifier, email address, and, when returned, display name. These identify the selected account, show connection details, and prevent one account's data from accidentally being mixed with another's. Some connection and dataset-binding information is kept locally.

Synchronized data includes notes and their formatting, folders, labels, relevant reminder and note attributes, and technical metadata such as record IDs, app-generated installation IDs, version counters, timestamps, checksums, and deletion markers. These records let your devices exchange changes and handle conflicts and deletions. Device-specific widget configurations and notification pin selections are not a promise of cross-device synchronization.

Synchronization is not real-time collaborative editing. It may run when the app starts, when you connect an account, when you request synchronization, and through operating-system background tasks. Network conditions and device restrictions can delay it. Conflicts can produce an additional copy of a note.

NoteFlow uses Google API information only for the disclosed, user-facing synchronization functions. Its handling and transfers of this information must comply with the Google API Services User Data Policy, including the Limited Use rules. We do not send your Drive note contents to RevenueCat for purchase verification or intentionally attach them to crash reports. We do not routinely read the contents of your Drive library. If you choose to send specific content to support, we use that content to handle your request.

Disconnecting Drive stops future synchronization from that installation; it does not automatically delete existing Drive files or local notes. You can also revoke NoteFlow's access through your Google account. Other connected devices must be disconnected separately.

To remove the cloud copy, disconnect all devices first, then use Google Drive's application-management settings, where available, to delete NoteFlow's hidden application data. Deleting only the cloud copy while a device remains connected can allow that device to upload its local library again.

4. Purchases and RevenueCat

The app store processes payments. NoteFlow and its developer do not receive your full payment-card number or Google account password.

RevenueCat processes information needed to verify purchases and manage Premium access: an app-generated customer identifier, product and transaction identifiers, store purchase tokens or receipts, purchase history, entitlement status, subscription dates, and technical app/device information. Service requests also expose ordinary network information, such as an IP address, to the receiving service. Purchase records and associated service metrics help operate and understand the purchase service.

The purchase SDK can connect when the app starts, before you make a purchase, to initialize its customer record and check existing access. An app-generated customer ID does not directly contain your name, but can link service requests and purchases to the same installation or customer. It is not a promise of irreversible anonymization. RevenueCat can also derive a country from store transactions or a connection's IP address and record first/last connection times; its customer-profile documentation states that the IP address is discarded after the country is determined.

The current integration uses RevenueCat-generated customer IDs. NoteFlow does not intentionally supply your note contents, Drive library, or Drive email address as RevenueCat customer attributes. Purchase status is also cached on your device to support access when temporarily offline.

RevenueCat acts as a service provider for the purchase integration. See its Privacy Policy. Your app store separately handles your store account, payment information, refunds, and subscription management.

5. Crash reporting

The production app uses Google's Firebase Crashlytics to diagnose crashes and improve stability. Reports can include stack traces, exception information, app and operating-system versions, device characteristics, and Crashlytics/Firebase installation identifiers. These identifiers can distinguish installations; we do not describe crash reporting as containing no personal data.

Automatic crash reporting is enabled without a separate in-app opt-in screen, and the current version has no switch to disable it. It does not depend on connecting Drive or buying Premium. This describes the current configuration; accepting the Terms of Use or this policy is not treated as separate consent.

We do not intentionally add note contents, complete backups, or authorization tokens to crash reports. Technical error messages can nevertheless contain contextual information. Reports are used for troubleshooting and reliability, not to profile the contents of your notes.

Firebase's published retention policy states that Crashlytics begins removing crash traces and associated identifiers from live and backup systems after 90 days. See Firebase privacy information for current details and Google-controlled processing.

6. Fonts, support, and external pages

If a selected font is not bundled or already cached, the app may download a font file from Google's font servers. The server receives the request and ordinary network information, such as your IP address. The font request does not intentionally include your note text. Downloaded fonts can be cached on your device.

When you contact support, we receive your email address and what you choose to send. A bug-report draft may contain your app version, Android version, and device model. Purchase-recovery drafts may include a RevenueCat customer ID. You decide whether to send the draft and attach a receipt or other material. Do not send passwords, access tokens, payment-card details, or unrelated sensitive notes.

Opening a privacy, terms, store, or other external link sends you to a third-party page. That page's operator, including GitHub if it hosts these documents, handles website requests, cookies, and access logs under its own privacy practices.

The app can ask Google Play to display its native rating/review prompt. Eligibility dates and session counters are kept on your device. NoteFlow does not receive the review text through that integration; if you submit a review, Google Play handles it under its own terms and privacy practices.

7. Purposes and legal grounds

Where applicable law requires a legal basis, the purposes and relevant grounds are:

• Requested features and paid access: processing necessary to provide the service you request or perform our agreement, including optional Drive synchronization and purchase verification/restoration. The app can be used for local notes without connecting Drive. Declining the processing needed to verify a purchase can prevent us from establishing the associated Premium access.
• Reliability and security: limited technical diagnostics to find crashes, fix defects, and protect the app and purchase service. Where permitted, this relies on our legitimate interests in maintaining a reliable and secure service, subject to necessity and balancing against your rights. This ground does not override any separate requirement for prior consent to device access, data collection, or international transfers under applicable law.
• Support: information you choose to send is used to answer your request, perform a relevant purchase/service agreement, or pursue our legitimate interests in resolving questions and defending claims, as applicable. We do not use support messages for unsolicited promotional mailing lists.
• Legal obligations: records or disclosures required by applicable law, where such an obligation applies.

A Google permission grant does not replace a separate consent that applicable privacy law may require. This policy explains processing; it does not itself create a legal basis or turn automatic diagnostics into consent-based collection.

Accepting the Terms or using the app does not constitute blanket consent to every form of data processing. Consent-based processing requires the consent and withdrawal mechanisms required by applicable law.

8. Service providers and international processing

Google provides Drive, authorization, font delivery, and Firebase services. RevenueCat provides purchase verification and entitlement management. The app store and email providers also process information for their respective services. We disclose information when legally required or necessary to protect the service and address security issues, only to the extent allowed by applicable law and Google's rules for Google API information.

These providers may process information outside your country, including in the United States. Applicable contractual and legal safeguards must be in place where required. Contact us for information about relevant processing arrangements and safeguards. Installing the app alone is not treated as consent to an international transfer where a separate legal mechanism or consent is required.

Google publishes Firebase Data Processing and Security Terms, and RevenueCat publishes a Data Processing Addendum, including provisions for applicable European/UK transfers. These documents describe the providers' contractual arrangements; their existence is not a statement that every transfer route is authorized under every country's law. You can ask the privacy contact about the safeguard applicable to a particular processing operation and how to obtain relevant information or a copy where required.

Provider information: Google Privacy Policy, Firebase privacy information, and RevenueCat Privacy Policy.

9. Retention and deletion

• Local library and preferences: retained while present in the installation. Deleting content, clearing app storage, or uninstalling removes local copies subject to device and operating-system backup behavior. Exported backups and cloud copies are not automatically removed.
• Trash: notes moved to trash can remain until permanently deleted. The app cleans notes older than 30 days during startup; removal is not guaranteed at an exact clock time while the app is closed. Other devices receive deletion changes only after synchronization.
• Synchronization metadata: deletion markers and version information can outlast the deleted note to prevent an offline device from restoring it. Permanently deleted records are represented without their note-content payload in current sync data, but previous cloud generations, conflict copies, exports, or disconnected devices can retain content. There is no general fixed expiry for all synchronization metadata.
• Technical Drive generations: the app normally retains up to three recent snapshot generations after successful publication. Cleanup is best-effort; network failures can leave additional files. They are not a user-facing version-history or guaranteed recovery service.
• Purchase information: retained as needed to verify and restore access and handle payment-related obligations, disputes, and permitted security needs. Store records and service-provider retention are separate from deleting the app. You can request deletion of developer-controlled RevenueCat records.
• Support: retained for handling the request, necessary follow-up, and applicable legal or dispute needs; unrelated material should not be retained longer than necessary. Crashlytics retention is described above.

For a complete cleanup of your note copies, consider every connected device, Drive application data, exported backups, operating-system backups, and any conflict copies. Disconnect devices before deleting the cloud library. We cannot remotely erase copies held only on a device or an export you control.

Email support for access, correction, or deletion requests involving information we or our service providers hold for NoteFlow. We may request proportionate information to locate and verify the relevant record. Deleting purchase-service records does not cancel a store subscription or delete the store's payment records; cancel subscriptions separately through the store. A later restore or store synchronization can recreate necessary purchase-verification records.

For a privacy request, describe what you want to access, correct, export, delete, or object to. Include only information reasonably needed to locate the record, such as the app/platform and, for a purchase-service request, your app customer ID if available. Do not send your entire note library, passwords, full card details, or identity documents unless a specific, proportionate verification need has been explained. We do not require you to create a NoteFlow account to submit a request. If a technical report cannot reasonably be linked to you with the information available, we will explain that limitation.

10. Security and your choices

Service requests use encrypted HTTPS transport. Local app storage uses the operating system's application protections. NoteFlow does not currently add its own password-based encryption to local backups or end-to-end encryption to Drive snapshots. A checksum verifies data integrity; it is not encryption. No storage or transmission method can be guaranteed completely secure.

You can choose not to connect Drive, disconnect it, revoke its Google authorization, manage device permissions, export your data, and contact support about privacy requests. Widgets, reminders, and notification pins may show note text on your home screen or lock screen according to your device settings.

Depending on applicable law, you may have rights to access, correct, erase, or receive your data; restrict or object to processing; withdraw consent; and complain to a data-protection authority. Some requests are subject to identity verification and lawful retention exceptions. Contact support to exercise applicable rights; we respond within the time limits required by the relevant law.

For requests governed by Turkey's KVKK, we respond as soon as possible and within 30 days. For GDPR/UK GDPR requests, we respond without undue delay and normally within one month; where the law permits an extension for complexity or the number of requests, we explain the reason within that first month. Requests are normally free; any legally permitted fee or refusal must be explained. You may object to legitimate-interest processing; we assess the request under applicable law. A support request is not an immediate technical switch that stops future automatic crash reports from your installation.

We do not use your notes for advertising profiles or make decisions about you based solely on automated processing that produce legal or similarly significant effects. Statutory rights and complaint routes remain available regardless of whether you use free or Premium features.

11. Children and policy changes

NoteFlow is not directed specifically to children. If you believe a child has provided personal information to our support or service providers in a way that requires parental consent, contact us so we can investigate and take appropriate steps. The app-store age rating is not itself a statement of contractual capacity or privacy consent.

We will update this policy when our practices change. Material changes require appropriate notice, and new consent when required by law or Google's API rules. The date above identifies the latest revision. Privacy questions can be sent to noteflowhelp@gmail.com.