Legal
Privacy Policy
Last Updated: November 21, 2026
BBMM Technologies Inc., operating as Flowo from Halifax, Nova Scotia, Canada, protects your privacy through data minimization, encrypted local storage, and clear choices about optional analytics: in the app, usage analytics tied to your installation runs only with your consent; setup milestone counts (stored without an identifier), subscription events and service metrics are handled as section 2 describes; and on flowoapp.com analytics follows the rules for your region in section 6A. This policy explains what the Flowo app and flowoapp.com process, why, and the choices available to you. Questions and privacy requests can be sent to privacy@flowoapp.com.
1. Who We Are and Scope
BBMM Technologies Inc. (NS Registry ID 4825550) is the controller for personal information processed by Flowo and this website. BBMM Technologies Inc. 1800 Argyle St, Unit 801 Halifax, Nova Scotia, B3J 3N8, Canada Privacy contact: privacy@flowoapp.com This policy applies to the Flowo mobile application, our marketing website at flowoapp.com, early-access forms, and support communications.
2. What the App Processes
Flowo is free to download. Flowo Pro is an optional auto-renewing subscription or one-time purchase sold through the Apple App Store and Google Play. The store processes the payment, and Flowo never receives your card details. The Flowo app does not include session replay. • Purchases and Pro access: RevenueCat processes Flowo Pro purchases for us as a service provider. It receives the random installation identifier described under Device security, which Flowo uses as the RevenueCat app user ID; App Store receipt and transaction data, including the product, purchase, renewal, expiration and refund dates; device type, operating system and similar technical details; and when the app last checked your subscription. Flowo does not send RevenueCat your name, planning content, or advertising identifiers, and sends it an email address only if you give one (see Contact email). When Pro starts, renews, changes or ends, RevenueCat notifies the Flowo API, which records the plan status against the same installation identifier. RevenueCat also keeps a few labels the app sets on that record: the paid feature you used most in the last 14 days, so the offer you see fits how you use Flowo; a referral code you redeemed; and, in versions that ask, how you found Flowo. Only while you consent to analytics, the app adds two more: where this copy of the app came from (the App Store, Google Play, TestFlight, or elsewhere, such as a developer build), so our subscription reports can leave out test installs; and the random installation identifier that your app usage analytics events carry, so the subscription events described below appear under the same Amplitude user. Withdrawing consent removes both. • Subscription analytics: RevenueCat may send Amplitude, our analytics provider, events about your purchase: a trial starting, a purchase, renewal, cancellation, billing problem, expiration or refund, and when the purchase screen is shown or closed. They carry the product, price, currency, store and dates, keyed to the installation identifier, and never your planning content. If you gave a contact email, RevenueCat may attach it as a one-way hash; we hide that field in Amplitude and do not use it. We use them to measure subscription retention and revenue, which we treat as a legitimate interest, so they are sent whether or not you turn on app analytics. You can ask privacy@flowoapp.com to delete them. • Contact email: From version 1.0.7, Settings has an optional Email field, so we can get in touch to answer your questions and tell you about offers. If you fill it in, the app keeps it in encrypted local storage on your device and sends it to RevenueCat, which keeps it on the customer record for your installation, whether or not you turn on analytics. That is how the Flowo team sees it and can write to you. Clearing the field removes it from RevenueCat, and so does Delete App & Device Data. Versions 1.0.6 and earlier asked for the same optional email on the "Where did you find Flowo?" screen and sent it to RevenueCat too. Version 1.0.7 removes that screen. • Local planning content: Tasks, schedules, habits, notes, Brain Dump items, preferences, and related planning state are stored in encrypted local storage on your device. Flowo does not maintain a centralized cloud database containing your tasks. • Device security: Flowo creates a random, app-scoped installation identifier and sends device-attestation evidence, security counters, quota use, and token metadata to authenticate the installation and prevent abuse. This is not an email or login account. • User-invoked cloud features: When you request generative assistance, only the content needed for that request is sent over an encrypted connection to the Flowo API and processed using Amazon Bedrock. Voice features ask for separate just-in-time permission before recording or uploading audio and may use Amazon Transcribe before a generative request. Flowo does not use this content to train models or store it as a centralized copy of your planning database. AWS publishes separate service terms and data-protection commitments for these services. • Photos of paper notes: You can photograph up to 10 pages of paper notes with the camera in the app so Flowo can turn them into tasks. The photos are sent only after you open the camera yourself, and only if you have allowed Flowo to share content with its cloud AI (Claude), which the app asks once. The scanner only takes new photos and cannot pick pictures from your photo library. On iPhone, Apple's VisionKit document camera finds the page on the device. On Android, the scanning screen is Google's ML Kit document scanner, delivered by Google Play services: it processes the page on the device and does not send the photo to Google, but it sends Google metrics about how the scanner performs and is used, such as the device model, app version and error codes. The app then uploads the photos over TLS to Flowo's encrypted Amazon S3 storage in Canada (ca-central-1). Anthropic's Claude model reads them through Amazon Bedrock in the United States, and the text it reads comes back to the app, where you can correct it before it is sorted like typed text. Flowo deletes the uploaded photos as soon as they have been read; section 7 says how long a photo or its text may otherwise remain. Flowo does not use the photos or their text to train models. • On-device processing: Semantic search and embeddings run on your device through Core ML on iOS or TensorFlow Lite on supported platforms. Raw text and embedding vectors used by those features remain on the device. • App usage analytics, only after you consent: Flowo sends Amplitude events about how the app is used, so we can measure usage, retention, and how long people keep using each feature. Events cover the screens you open, the features you use (for example creating a task, habit or plan, capturing a Brain Dump and its type of media, replanning, or using the assistant), onboarding steps, the purchase screen and its outcome, notifications you open, sessions and app opens, with counts, durations and settings. They never include the text, titles, notes, recordings or photos you enter. Each event carries a random installation identifier, the app version, platform and operating system version, plus a few properties: days since install, Pro status, the app's language and whether the app came from a store or a test build. The app switches off IP address, location, device model, carrier and advertising identifiers in Amplitude. With the same consent, Amplitude can show in-app tips, and versions 1.0.7 and earlier also send similar content-free telemetry to TelemetryDeck; later versions do not. Flowo does not ship a crash-reporting SDK, and these services are not used for cross-app tracking. • Install attribution, only after you consent: on iOS the app passes RevenueCat Apple's AdServices attribution token, and on Android the Google Play install referrer, so we can see which Apple Ads campaign or which of our own store links led to the install. Neither uses an advertising identifier, and the app does not ask for App Tracking Transparency permission. • Service metrics: The Flowo API counts requests, response times and errors, and for each AI request records the feature, model, token counts, latency, cost, the names of the in-app tools the assistant used, and whether it failed. These records never contain prompts, transcripts, replies, or the words of your tasks and notes. Request metrics always share one identifier with every other installation. AI request records do too unless you consent to analytics. With consent, the app also sends the Flowo API the random installation identifier that your app usage analytics events carry. The API passes it to Amplitude with the AI request records and does not store it, so the records appear under the same Amplitude user as those events and we can see how the assistant is used alongside the rest of the app. If the app does not send that identifier, as older versions do not, the records instead carry a pseudonym derived from the installation identifier described under Device security, which cannot be linked back to it without a key kept on our server. When you answer the analytics question on the welcome screen, the app also tells the Flowo API whether you chose Share or Don't share; the server checks the installation's authentication token, then counts these answers by platform and stores them with no identifier, so we know what share of people agree to analytics. In the European Economic Area, the United Kingdom, Switzerland and Canada, only Share is counted. • Setup milestones: After you answer the analytics question on the welcome screen, the app tells the Flowo API, once each, when this installation first reaches a setup milestone: finishing setup, creating its first task, event or habit after setup, completing its first task, and opening the app on the day after your answer and again on the seventh day. Each message carries only the milestone and the app version. The API checks the installation's authentication token to prevent abuse and to limit how often a milestone can be sent; it does not store the token or the installation identifier with the count, and passes Amplitude only the milestone, the platform, the app version and the environment, under one identifier shared by every installation and without your installation identifier or IP address, so we can see where people stop in their first week, including people who do not share analytics. The API holds them, like the answers to the analytics question, and passes them to Amplitude once a day, all dated to that day, so their time does not point to an installation. We keep these counts in de-identified form and do not attempt to re-identify them or link them back to an installation. To send each milestone only once, the app keeps the date of your answer and the list of milestones already sent on your device. In the European Economic Area, the United Kingdom, Switzerland and Canada (judged by your App Store or Google Play country; if the store does not name one, the app treats you as being there), the app stores and sends them only with your analytics consent, and withdrawing it stops them.
3. What the Website Processes
• Early-access, quiz, and contact forms: If you submit a form, we process the fields you choose to provide, such as your name, email address, role, use case, message, or optional quiz answers and outcome. When you finish the quiz at flowoapp.com/start/, your answers and result are saved anonymously, with the kind of device (iPhone, Android or computer) and the campaign tags of the link that brought you, and no name, email address or other identifier. Form submissions are stored through our Supabase project so we can manage access requests and respond. • Research sign-up: If you sign up at flowoapp.com/research/ to talk with us about planning with ADHD, we process your answers to the sign-up questions, including whether you have ADHD, which we treat as health information, plus your country and age band, the languages you can speak, your email address and the link that brought you. We use them only to decide whether to invite you, to arrange a call and to understand the problem we are working on. They are stored with Cloudflare in the United States, and Cal.com handles booking a call. A call is recorded only if you agree at its start. If you are under 18, or say you do not have ADHD, we keep only an anonymous count. • Support messenger: Zendesk does not load until you select Support. If you open it, Zendesk processes the messages and contact details you choose to provide plus technical data needed to deliver and secure the conversation. Do not send task text, passwords, payment-card data, or health information through support. • Consent preferences: We store your choices, and the rules and region (country and region code) they were made under, so the site can respect them. See section 6A. • Optional website analytics: Where your choice or the rules for your region allow it (section 6A), Amplitude receives page views and clicks on links and buttons, used to understand site performance. On the quiz at flowoapp.com/start/, Amplitude also receives each answer you choose and your result, linked to its random device identifier, so we can see where people stop. Amplitude never receives your name or email address from this website. Session recordings by Microsoft Clarity are a separate choice and stay off unless you turn them on. • Ask Ondi: If you ask Ondi, the website's AI assistant, a question, the text of the conversation is sent to Anthropic to write the answer. Our server does not store it. • Optional marketing measurement: Where your choice or the rules for your region allow it (section 6A), the Meta Pixel loads and Meta receives the pages you view on this site, when you press an App Store or Google Play button, the campaign tags in the link that brought you here, and standard browser data such as IP address and user agent. On the quiz at flowoapp.com/start/, Meta receives only whether you started or finished it, never your answers. Meta sets its own cookies (_fbp, _fbc) and may combine this with information it holds about you under its own privacy policy. We use it only to measure which of our ads bring visitors. The same events go to two pixels: Flowo's own and one used by our advertising agency while our ads run from its ad account. It stays off until you turn it on, in every region (section 6A), never runs inside the Flowo app, and never receives planning content, form answers or email addresses. • Technical delivery data: Hosting, DNS, security, and network providers may process standard request information such as IP address, browser type, timestamps, and requested URLs to deliver and protect the site.
4. Why We Process Data
We process data only for defined purposes: to provide an app feature you request, including a cloud feature you invoke (performance of a contract); to respond to early-access, privacy, or support requests (consent, legitimate interests, or steps requested before a contract); and to authenticate installations, enforce security controls, prevent abuse, and diagnose faults (performance of a contract and legitimate interests). Voice upload requires the separate choice shown before recording. In the app, usage analytics tied to your installation and install attribution run only with consent, to understand how Flowo is used, which features people return to, and which campaigns bring them. Subscription analytics, service metrics and setup milestones (section 2) run on legitimate interests: measuring subscription retention and revenue, seeing where new users stop, and keeping the service reliable and affordable. In the European Economic Area, the United Kingdom, Switzerland and Canada, setup milestones are sent only with consent. On flowoapp.com, it runs as described in section 6A: in Canada outside Quebec and in most US states it starts with a notice and you can turn it off at any time; elsewhere it waits for your choice. Local personalization does not send its planning data to us. Research sign-ups, including the health information in them, are processed with the consent you give on the form, which you can withdraw at any time. Flowo does not sell personal information, use planning content for advertising, track app users across other apps or websites, or use your content to train models. On this website, Meta ad measurement runs only as described in section 6A. Some US state laws may treat it as "sharing" or a "sale", and you can opt out of it at any time.
5. Service Providers
We use providers only for specific operating purposes: • Amazon Web Services, Amazon Bedrock, Amazon Transcribe, and Amazon S3 — Flowo API infrastructure and request-scoped processing for user-invoked generative, voice, or paper-note photo features, including short-term storage of those photos in Canada. • Amplitude — content-free app usage analytics and in-app tips with consent, subscription events from RevenueCat, AI request metadata, counts of analytics-question answers and setup milestones from the Flowo API, and website analytics under the rules in section 6A, including the answers given in the quiz at flowoapp.com/start/. • Google (Google Analytics and Google Tag Manager) — website analytics under the rules in section 6A. Not part of the Flowo app. • Microsoft Clarity — heatmaps and session recordings of flowoapp.com, with form fields masked, and a report of which AI assistants cite the site, only after a visitor turns on Session recordings. Microsoft sets its own cookies on clarity.ms and bing.com. It is not part of the Flowo app. • TelemetryDeck — in app versions 1.0.7 and earlier, consented, content-free product telemetry and performance signals; Flowo does not send it crash reports. • Apple platform services — Keychain, speech recognition, App Attest, the VisionKit document camera, and other operating-system functions needed for requested device features and security. • Google Play services (ML Kit document scanner) — on Android, the screen that scans paper notes. It works on the device and sends Google metrics about the scanner's performance and use, not the photos. • Zendesk — support messaging only after a visitor selects Support. • Anthropic — answers to questions asked in Ask Ondi on flowoapp.com, through the Claude API. • Meta Platforms — website ad measurement through the Meta Pixel (Flowo's pixel and our advertising agency's pixel), as described in section 6A. • Apple App Store — payment processing, subscription management, and refunds for in-app purchases. • RevenueCat — Flowo Pro purchase and entitlement processing using the installation identifier, App Store transaction data and basic device information, the optional contact email you give in the app, plan-status notifications to the Flowo API, subscription events sent to Amplitude, and, with consent, install attribution and where the app was installed from. • Supabase — website email sign-up, feedback, contact, and anonymous quiz results. • Resend and Google Workspace — delivery and handling of support or form-related email. • Cloudflare — hosting, content delivery, DNS, and security for flowoapp.com, and Cloudflare Web Analytics: aggregate page-view counts that set no cookie and store nothing on the device. • Cloudflare D1 — storage of research sign-ups, in the United States. • Cal.com — booking research calls. • Telegram — internal alerts that a research sign-up needs review, carrying only a participant code, never your answers or email address. • GitHub Pages and Fastly — a standby copy of the website. Each current provider processes data under its own terms and applicable data-protection obligations. We do not authorize providers to use planning content for advertising or model training. Contact privacy@flowoapp.com for the current provider and transfer-mechanism register.
6. Your Consent and Controls
App usage analytics tied to your installation and install attribution are off until you consent. Subscription analytics and service metrics (section 2) do not depend on that choice. Outside the European Economic Area, the United Kingdom, Switzerland and Canada, neither do the count of answers to the analytics question and setup milestones (section 2); in those countries only Share is counted, and milestones are sent only with consent; you can ask privacy@flowoapp.com to delete the subscription events tied to your installation. Voice upload asks for a separate choice before recording; generative text features run only when you invoke them. Photos of paper notes are sent only when you take them in the app and have allowed Flowo to share content with its cloud AI. You may change or withdraw optional analytics in the app, and withdrawal applies to future processing. You can export supported local records, use Delete App & Device Data to erase app-owned local records and identifiers, and remove locally stored content by deleting the app. On this website, analytics, session recordings and marketing measurement are separate choices. Which of them run before you choose depends on your region (section 6A). Cookie settings, or Your Privacy Choices in the US, at the bottom of every page lets you change or withdraw any of them at any time. Website choices expire after 180 days or when this policy version changes.
6A. Cookies and Similar Technologies by Region
This website applies different rules for optional technologies depending on where you appear to be. Cloudflare, our host, derives your country and region from your connection; the site keeps only the country and region code, for the visit and in your saved choice, and never your IP address. Location from an IP address can be wrong, so you can change every choice yourself with Cookie settings or Your Privacy Choices at the bottom of every page. • European Economic Area, United Kingdom, Switzerland, Brazil, Quebec, Washington, Nevada, Connecticut, and any other or unknown location: nothing optional runs until you choose. Accept all, Reject all and Settings are offered side by side. • Canada outside Quebec: website analytics (Amplitude and Google Analytics, described below) runs with a notice and a one-click opt-out. Marketing measurement stays off unless you turn it on. • Other US states: website analytics (Amplitude and Google Analytics, described below) runs with a notice, and Your Privacy Choices lets you turn it off. Meta ad measurement stays off unless you turn it on. • Everywhere: session recordings (Microsoft Clarity) stay off unless you turn them on. Strictly necessary storage, such as your saved choice and the security and delivery of the site, is always on. Global Privacy Control. If your browser sends Global Privacy Control, we treat it as a request to opt out of the sale or sharing of your personal information and of targeted advertising, in every region. The Meta Pixel and session recordings stay off in that browser, and Your Privacy Choices shows "Opt-out preference signal honored". A Do Not Track signal turns off every optional technology. Do Not Sell or Share My Personal Information. Flowo does not sell personal information for money. When Meta ad measurement runs on this website, some US state laws, including California's, may treat it as "sharing" for cross-context behavioral advertising or as a "sale". You can opt out at any time with Your Privacy Choices, or by turning on Global Privacy Control. We do not knowingly sell or share the personal information of consumers under 16. Canada and Quebec. Outside Quebec, we rely on implied consent, with notice and an easy opt-out, only for website analytics, and we ask for express consent before any marketing measurement. In Quebec, technologies that can identify, locate or profile you stay off until you turn them on, and the choice is offered in French. In the app, Canada is one of the countries where setup milestones and the count of answers to the analytics question are sent only with your analytics consent (section 2). Cookies, storage and providers on this website: • flowo-consent-v2 (local storage, this site): your choices and the rules and region they were made under. 180 days, or until this policy changes. Strictly necessary. • flowo-geo (session storage, this site): your country and region code for this visit. Cleared when you close the tab. Strictly necessary. • Cloudflare Web Analytics: aggregate page-view counts on every page. Sets no cookie and stores nothing on your device. • Amplitude (cookies AMP_* and AMP_MKTG_*, about 1 year; local storage amplitude.*): Analytics. On the quiz, it also receives each answer you choose and your result. • Google Analytics, loaded through Google Tag Manager (cookies _ga and _ga_*, about 13 months): Analytics. Google Tag Manager itself loads only once Analytics or Marketing is on. Google Analytics receives page views and a few named events, such as quiz steps and store button presses, and never your quiz answers. Google signals and ad personalization are off, and Google's advertising features receive nothing unless Marketing is on. • Microsoft Clarity (cookies _clck, up to 1 year, and _clsk, 1 day, on this site; Microsoft's own cookies such as MUID, MR, SM, ANONCHK and CLID on clarity.ms, and MUID, MR and SRM_B on bing.com): Session recordings. • Meta Pixel (cookie _fbp, about 90 days; _fbc when you arrive from a Meta ad): Marketing. The same events go to two pixels: Flowo's own (ID 4441183756145061) and one used by our advertising agency while our ads run from its ad account (ID 1421721209904217). • Zendesk: loads only when you select Support or ask Ask Ondi for a person, and then stores what it needs to run that conversation. • Anthropic: when you ask Ondi, the website's AI assistant, a question, the text of the conversation goes to Anthropic's API to write the answer. Ask Ondi sets no cookie, and our server does not store the conversation. Please do not share health details with it.
6B. Témoins et technologies similaires selon la région (français)
Ce site applique des règles différentes aux technologies facultatives selon l'endroit où vous semblez vous trouver. Cloudflare, notre hébergeur, déduit votre pays et votre région de votre connexion; le site ne conserve que le code du pays et de la région, pour la visite et dans votre choix enregistré, jamais votre adresse IP. La localisation par adresse IP peut se tromper : vous pouvez donc modifier chaque choix vous-même avec « Paramètres des cookies » ou « Vos choix en matière de confidentialité », en bas de chaque page. • Espace économique européen, Royaume-Uni, Suisse, Brésil, Québec, Washington, Nevada, Connecticut et tout autre lieu, connu ou non : aucune technologie facultative ne fonctionne avant votre choix. « Tout accepter », « Tout refuser » et « Préférences » sont présentés côte à côte. • Canada hors Québec : la mesure d'audience (Amplitude et Google Analytics) fonctionne avec un avis et un refus en un clic. La mesure publicitaire reste désactivée sauf si vous l'activez. • Autres États américains : la mesure d'audience (Amplitude et Google Analytics) fonctionne avec un avis, et « Vos choix en matière de confidentialité » permet de la désactiver. La mesure publicitaire de Meta reste désactivée sauf si vous l'activez. • Partout : les enregistrements de session (Microsoft Clarity) restent désactivés sauf si vous les activez. Le stockage strictement nécessaire, comme votre choix enregistré ainsi que la sécurité et la diffusion du site, est toujours actif. Québec. Les technologies qui permettent de vous identifier, de vous localiser ou d'effectuer votre profilage restent désactivées tant que vous ne les activez pas, et le choix vous est présenté en français. Vous pouvez retirer votre consentement à tout moment, aussi facilement que vous l'avez donné. Canada hors Québec. Nous nous fondons sur un consentement implicite, avec avis et refus facile, uniquement pour la mesure d'audience, et nous demandons un consentement exprès avant toute mesure publicitaire. Dans l'application, le Canada fait partie des pays où les jalons de configuration et le décompte des réponses à la question sur l'analyse ne sont envoyés qu'avec votre consentement à l'analyse (section 2). Global Privacy Control. Si votre navigateur envoie le signal Global Privacy Control, nous le traitons comme une demande de refus de la vente ou du partage de vos renseignements personnels et de la publicité ciblée, dans toutes les régions : le pixel Meta et les enregistrements de session restent désactivés. Un signal Do Not Track désactive toutes les technologies facultatives. Témoins (cookies) et fournisseurs : flowo-consent-v2 et flowo-geo (ce site, strictement nécessaires); Cloudflare Web Analytics (statistiques globales, aucun témoin); Amplitude (mesure d'audience, y compris vos réponses au quiz de flowoapp.com/start/ et le résultat); Google Analytics, chargé par Google Tag Manager (mesure d'audience, jamais vos réponses au quiz); Microsoft Clarity (enregistrements de session, avec des témoins de Microsoft sur clarity.ms et bing.com); pixel Meta (mesure publicitaire : le pixel de Flowo et celui de notre agence de publicité); Zendesk (uniquement si vous ouvrez le soutien); Anthropic (réponses d'Ask Ondi). Les durées et le détail figurent à la section 6A. En cas de divergence, la version anglaise prévaut.
7. Retention and Deletion
Local planning content remains on your device until you delete it, use the erasure workflow, or remove the app. Flowo does not retain user-invoked cloud content as a task database; limited request, security, and provider records may remain only for service delivery, abuse prevention, incident investigation, and legal claims under the applicable operational schedule. Uploaded photos of paper notes are deleted as soon as they have been read. A photo that is not read, because the reading failed on our side or the upload was cancelled or refused, is deleted automatically within about two days; after a failure on our side it is kept so you can try again without photographing the pages again. The text read from the pages stays with that import for up to a day, so the app can show it later, and is then deleted automatically, usually within a few more days. Backups of the Flowo API database keep it for up to 35 days. App usage and website analytics records follow the configured provider retention period and are no longer collected after consent is withdrawn. Subscription events, service metrics and setup milestones follow the same provider retention period. Setup milestones are stored with no identifier, so they cannot be found or deleted for one installation; Delete App & Device Data erases the milestone record on your device. Device-authentication, security, and revocation records are kept while needed to operate or protect an installation and are periodically reviewed. The contact email stays with RevenueCat until you clear it in Settings or use Delete App & Device Data. Website forms, email, and Zendesk support conversations are kept while the request or early-access relationship is active and then deleted or de-identified when no longer needed, subject to provider backup timing, legal claims, and statutory records. Research sign-ups from people we do not invite are deleted 60 days after sign-up, unless you asked to hear about future research, and the last backup copy is gone by day 90. We keep only anonymous totals, such as country, age band and how you found us. If we talk with you, we keep your answers and our call notes while the research is active and then delete or de-identify them. Use https://flowoapp.com/data-rights/ or privacy@flowoapp.com to request deletion of records we control. The privacy request process explains identity verification and the limits of matching an account-free installation after app data has been removed.
8. International Transfers
BBMM Technologies Inc. is based in Canada. The providers listed above may process data in Canada, the United States, the European Economic Area, or other locations disclosed in their service terms. Photos of paper notes are stored in Canada and read in the United States (section 2). For a restricted transfer, we use an applicable adequacy decision or contractual safeguard, such as the European Commission Standard Contractual Clauses and, where required for the United Kingdom, the UK Addendum or another valid mechanism. You may request information about the safeguard relevant to you at privacy@flowoapp.com. Data sent from the app or website is protected in transit using HTTPS/TLS.
9. Your Privacy Rights
Depending on where you live, you may have rights to access, correct, delete, restrict, or receive a portable copy of personal information we control; object to processing based on legitimate interests; withdraw consent; and complain to a privacy regulator. California and other US state rights apply when their statutory scope and thresholds are met. Use https://flowoapp.com/data-rights/ or send a request to privacy@flowoapp.com. We may need to verify the request without collecting more information than necessary. We will respond within the period required by applicable law. Because planning content is stored locally and is not held in a Flowo task database, the in-app export and erasure controls are usually the direct way to act on that content.
10. Security
Flowo uses encrypted local records, hardware-backed key storage where supported, HTTPS/TLS for network requests, release configuration controls, and consent and policy gates around external services. The Flowo API does not act as a centralized storage database for user tasks. Website submissions and operational systems use access controls appropriate to their purpose. No system can guarantee absolute security. If you believe your information is at risk, contact security@flowoapp.com or privacy@flowoapp.com.
11. Children and Policy Changes
Flowo is not directed to children under 16, and we do not knowingly collect their personal information. If you believe a child has provided information, contact us so we can review and delete it where appropriate. Where a law makes the App Store or Google Play share the age on an account (Texas today, California from January 1, 2027), the app reads that age once during setup and does not continue if the store reports the account as under 16. The app asks for no date of birth and uses the store's answer for nothing else. People aged 16 and 17 may use Flowo. The in-app assistant says that it is an AI. Its answers are written by Anthropic's Claude models through Amazon Bedrock, and we follow Anthropic's Usage Policy and its guidelines for products that minors use, alongside the children's privacy laws that apply to us, including COPPA in the United States and PIPEDA in Canada. We may update this policy when the product, providers, or law changes. We will update the date above and provide additional notice when a material change requires it.
12. Contact
BBMM Technologies Inc. 1800 Argyle St, Unit 801 Halifax, Nova Scotia, B3J 3N8, Canada Privacy Officer: Director, BBMM Technologies Inc. Privacy: privacy@flowoapp.com Security: security@flowoapp.com General support: hello@flowoapp.com Data-rights instructions: https://flowoapp.com/data-rights/ Canadian residents may contact the Office of the Privacy Commissioner of Canada at https://www.priv.gc.ca. Quebec residents may also contact the Commission d'accès à l'information du Québec at https://www.cai.gouv.qc.ca. EEA and UK residents may contact their local supervisory authority.