Flowo is operated by Hopson & Cie Srl, a company incorporated under Belgian law:
Hopson & Cie Srl
149 avenue du Domaine, 1190 Bruxelles, Belgium
VAT: BE 0450.443.155
Email: privacy@getflowo.com
Website: https://getflowo.com
Hopson & Cie Srl acts as the data controller within the meaning of the EU General Data Protection Regulation (GDPR — Regulation 2016/679) for personal data processed through Flowo, unless stated otherwise for Team workspaces (see Section 5d).
This Privacy Policy applies to all Flowo products and channels that share the same account and backend, including:
Unless a feature is platform-specific (for example push notification tokens), the same account data model applies across devices.
Payments are processed by Stripe. We do not store card numbers. We store:
If you publish a Flowo booking page, guests may provide name, email, and booking notes. We process that data to create the appointment, sync to your connected calendar when enabled, and send confirmation / reminder emails.
| Category | Examples | Stored in | Retention |
|---|---|---|---|
| Account | Email, username, password hash, OAuth IDs | Cloudflare D1 | Until account deletion |
| Subscription | Plan, status, Stripe IDs, credits | Cloudflare D1 | See Section 7 |
| Content | Tasks, notes, events, projects | Cloudflare D1 | Until deletion / account deletion |
| Calendar tokens | Google / Microsoft OAuth tokens | Cloudflare D1 (encrypted) | Until disconnect / account deletion |
| Push tokens | Web Push / Expo tokens | Cloudflare D1 | Until disable / account deletion |
| Local prefs | Language, UI state, cookie consent | Browser / app local storage | Until cleared |
| Processing activity | Legal basis |
|---|---|
| Account, core product features, billing | Contract (Art. 6.1.b) |
| Calendar OAuth (Google / Microsoft) | Consent (Art. 6.1.a) |
| Push notifications | Consent / contract (depending on channel and settings) |
| Booking guest data (host-initiated) | Contract with host; host’s instructions (Art. 6.1.b) — see §5c |
| Security, fraud prevention | Legitimate interest (Art. 6.1.f) |
| Optional marketing measurement cookies | Consent (Art. 6.1.a) |
| Tax / accounting records | Legal obligation (Art. 6.1.c) |
Flowo uses Google APIs for (a) Sign-In and/or (b) Google Calendar (and optionally Meet-related configuration). We comply with the Google API Services User Data Policy, including Limited Use.
Identity (Sign-In): openid, email, profile — Google account ID, email, name, picture URL.
Calendar (when you connect Calendar or when calendar access is part of the Google authorization you grant):
https://www.googleapis.com/auth/calendarhttps://www.googleapis.com/auth/calendar.eventsGoogle Meet space configuration (https://www.googleapis.com/auth/meetings.space.created) is requested only when enabled in our production configuration after Google OAuth verification of that sensitive scope. Until then, Meet links for bookings may still be created via Calendar conference data without that extra scope.
Calendar fields we may sync: titles, start/end, descriptions, locations, attendees, Meet links, recurrence, status, reminders metadata.
Tokens and synced events are stored in Cloudflare D1, encrypted at rest, isolated per user, transmitted over TLS. Tokens are never exposed to the browser. You can disconnect Calendar in Settings, revoke access at Google Account permissions, or delete your Flowo account. Deletion of Google tokens/events happens on disconnect; full account erasure within 30 days of account deletion.
If you sign in with Microsoft and/or connect Outlook, we may request scopes such as openid, email, profile, offline_access, User.Read, Calendars.ReadWrite, and OnlineMeetings.ReadWrite as needed for the features you enable. We store OAuth tokens encrypted and sync calendar events similarly to Google. We do not use Microsoft data for advertising or model training. Disconnect in Settings or revoke in your Microsoft account. Privacy: privacy.microsoft.com.
When a Flowo user (“Host”) shares a booking link, guests submit booking details to Flowo so we can create the appointment for the Host. For that guest data, the Host is typically the party who decides why the booking exists; Flowo processes the data to provide the booking feature. Hosts should only collect what they need and inform guests as required by law.
We may email guests confirmations, updates, or reminders related to the booking, and may write the event to the Host’s connected Google or Microsoft calendar when the Host enabled that sync.
On a Team plan, organization admins invite members by email. Within a Team workspace, members may see shared projects, assigned tasks, and related collaboration data according to roles/permissions. AI credits may be pooled at organization level. Admins are responsible for lawful use of the workspace and for informing their members. If you leave a Team, organization-owned shared content may remain with the Team; your personal account data remains subject to this Policy.
| Sub-processor | Purpose | Location |
|---|---|---|
| Cloudflare, Inc. | Hosting, CDN, Workers, D1, security | USA / global (SCCs) |
| OpenAI, LLC | AI features | USA (SCCs) |
| Stripe | Payments & subscriptions | USA (SCCs) |
| Resend, Inc. | Transactional email | USA (SCCs) |
| Google LLC | OAuth / Calendar (if connected) | USA (SCCs) |
| Microsoft Corporation | OAuth / Outlook (if connected) | USA / global |
SCCs = EU Standard Contractual Clauses (Decision 2021/914).
You may exercise access, rectification, erasure, restriction, portability, objection, and withdrawal of consent (where processing is consent-based). Email privacy@getflowo.com — we respond within 30 days. You may lodge a complaint with the Belgian APD (dataprotectionauthority.be) or your local EU authority.
Personal data breaches likely to risk your rights will be notified to authorities within 72 hours (GDPR Art. 33) and to individuals when required (Art. 34).
Flowo does not use advertising cookies inside the authenticated app by default. We use:
| Name / type | Purpose | Duration |
|---|---|---|
sa_session (HttpOnly cookie) | Web session authentication | Session / JWT lifetime |
OAuth state cookies (g_state, gcal_state, Microsoft equivalents) | CSRF protection during OAuth | ~10 minutes |
localStorage prefs (sa_lang, UI state, etc.) | Remember settings | Until cleared |
flowo_cookie_consent | Remember marketing cookie choice | Until cleared |
Cloudflare __cf_bm | Bot / security | Short-lived |
On marketing pages, Google Tag Manager and Google Ads (gtag) load only after opt-in. Rejecting optional tags prevents loading them. Clear site data to reset the banner.
Flowo is not directed at children under 16. We do not knowingly collect personal data from under-16s. Contact privacy@getflowo.com for deletion requests. Separately, our Terms require users to have legal capacity to contract (generally 18+) to create a paid account.
Primary sub-processors listed in Section 6 may process data in the United States or other countries. Transfers rely on Standard Contractual Clauses and provider DPAs where applicable. Cloudflare may process traffic globally for performance and security.
We may update this Policy. For material changes we will update the “Last updated” date, email registered users at least 14 days in advance where practicable, and/or show an in-app notice. Continued use after the effective date constitutes acceptance where permitted by law.
Data Controller — Privacy Contact
Hopson & Cie Srl — 149 avenue du Domaine, 1190 Bruxelles, Belgium
Email: privacy@getflowo.com
VAT: BE 0450.443.155
Belgian Data Protection Authority (APD/GBA): Rue de la Presse 35, 1000 Bruxelles — dataprotectionauthority.be — contact@apd-gba.be
EU ODR: ec.europa.eu/consumers/odr