Flowrish privacy policy

Effective date: 5 May 2020 · Updated 5 November 2026

This policy explains how Neurone IoT handles information in Flowrish, its optional modules, companion web planner and website. Contact us at neurone.iot@gmail.com with privacy questions or deletion requests.

Your planning records

The Android application stores tasks, roles, goals, schedules, reminders, labels, notes and task check-in responses on your device. Core planning does not require an account. Information you enter can be sensitive; choose what you record and which optional connections you enable.

The web planner stores your workspace in this browser's local database (IndexedDB). Core planning, habit statistics and natural-language task recognition are processed locally on your phone or in your browser. Task text is not sent to an AI service for recognition. Clearing site data or uninstalling can remove local records, so keep a backup. This does not mean that the application makes no network requests: optional phone sync, Google Drive backups, calendar connections, purchases and the Android diagnostics described below use their respective services.

Optional modules and permissions

• FitFlow — health and energy: step counts, activity goals, workout plans and logs, and body measurements you enter are used to display your activity and estimates. Activity recognition enables the phone's step sensor when you choose step tracking. Background step tracking uses a foreground service. These features provide general wellness tools, not medical diagnosis or treatment.
• FocusFlow — balance and focus: focus sessions and voluntary mood, stress and reflection responses support your own tracking.
• MoneyFlow and FIFlow — expenses and financial independence: accounts, balances, spending, income, bills, debt records, savings, investments and forecast assumptions are used for record keeping and calculations. The application does not execute banking or investment transactions.
• Transaction capture: if enabled and permitted, SMS and notification access lets the application identify financial transaction messages and prepare entries for your review. This can expose message content, senders, amounts and account references to the application. Processing is performed on the phone; access can be revoked in Android settings.
• Calendar, files and camera: optional calendar access displays device calendar events. File selection supports import, export, attachments and receipts. Camera access supports available scanning workflows. The application uses only the access you grant for the selected feature.
• Notifications and alarms: notification, alarm and foreground-service permissions support reminders, ongoing tracking and device connections. Availability depends on Android settings.

Backups, exports and connected devices

If you connect Google Drive, the application uses your Google account information and authorization to upload and restore backups in your Drive. Backups can contain the records included in the backup. Exported files are stored or shared at the destination you choose. Google operates its services under its own privacy policy.

The companion web planner can pair with your phone and exchange supported records over your local network. The paired browser can read and change the records exposed by the connection. The local connection uses HTTP with application-level AES-GCM encryption for record requests and responses. Network addresses and connection metadata remain visible to the local network. Use pairing only with devices and networks you trust, and stop the connection when it is no longer needed. Browser storage and exports may retain copies independently of the phone.

Usage information and diagnostics

The browser planner offers optional Firebase usage analytics after you choose Allow analytics. You can turn this off in Settings; browser Do Not Track and Global Privacy Control are respected. We measure which planner and Space screens are used, successful task saves and completions, and broad technical error categories. These custom web events exclude task text, search text, record identifiers, financial amounts, health values, check-in responses, raw error messages and stack traces. The browser client disables advertising personalization and automatic enhanced web measurement. Firebase may still process technical device, installation, session and connection information when analytics is enabled.

The Android application integrates Google Analytics for Firebase and Firebase Crashlytics. These services process app interactions, screen and feature usage, installation or device identifiers, device and operating-system information, purchase-related events, and crash or diagnostic information to help understand usage and investigate failures. Network requests also expose connection information such as an IP address to the receiving service. Google Analytics for Firebase derives approximate location from masked IP addresses and collects advertising identifiers by default. Analytics is not a copy of your full planning database; event parameters and error details may contain contextual information. These services operate independently of optional Drive backups.

The current application does not display advertising. It contains Google advertising and legacy consent components, which may contact Google to obtain consent information. See Firebase privacy information and Google's privacy policy for details about their processing and controls.

Membership and purchases

Google Play processes Android membership purchases and payments. The application receives purchase status and purchase identifiers to verify and restore access. We do not receive your full payment-card details from Google Play. Subscription cancellation and billing records are managed through Google Play.

Website updates and support

If you request product updates on the website, we store the email address and optional preferences you submit using Firebase services so we can provide the requested updates. You can ask us to stop updates and delete the registration by contacting the address above. Messages you send to support are processed to respond to your request. Hosting and service providers may process connection and operational logs when delivering the website.

Recipients and purposes

Information leaves your device when you choose backups, exports, sharing or device pairing, and through the service integrations described above. Relevant recipients include your chosen destinations, Google Play, Google Drive, Firebase and Google service providers. Their infrastructure may process information outside your country. The application does not publish your private records to a social feed.

Retention, deletion and choices

Local records remain until you delete them, clear application storage or uninstall the application. Exported files, browser records and cloud backups are separate copies and may remain after uninstalling; remove those copies at their destinations when you no longer need them. Disconnecting an account does not necessarily erase existing backups. You can revoke Android permissions and Google account access through their respective settings.

Support correspondence and website registrations are retained for their stated purposes; contact us to request deletion. Diagnostics, analytics and payment records are subject to the applicable service's retention controls and any records that must be kept for legitimate operational or legal purposes. Include enough information for us to locate a request, but do not send passwords, full payment details or unnecessary health or financial records. We may need to verify a deletion request. We cannot remotely delete files stored only on your device or copies you shared with another recipient.

Audience and changes

The application is intended for general users aged 13 and older and is not designed for children under 13. We will update this page when the described practices change. The date above identifies the latest revision.