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 all personal data processed through the Flowo platform.
When you create an account, we collect:
Payments are processed exclusively by Polar.sh (our payment processor). We do not store your credit card number or bank details. We receive and store:
To provide the service, we store:
If you choose to connect Google Calendar:
| Category | Examples | Stored in | Retention |
|---|---|---|---|
| Account | Email, username, password hash | Cloudflare D1 (SQLite) | Until account deletion |
| Subscription | Plan, status, dates | Cloudflare D1 | Until account deletion |
| Tasks & Events | Titles, dates, notes | Cloudflare D1 | Until account deletion |
| GCal Tokens | Access + refresh token | Cloudflare D1 (encrypted) | Until disconnection |
| Local preferences | Language, sidebar state | Browser localStorage | Until browser clear |
| Processing activity | Legal basis |
|---|---|
| Creating and managing your account | Contract performance (Art. 6.1.b) |
| Processing subscription payments | Contract performance (Art. 6.1.b) |
| Sending transactional emails | Contract performance (Art. 6.1.b) |
| Google Calendar integration | Consent (Art. 6.1.a) — you explicitly authorise via OAuth |
| AI task suggestions | Legitimate interest (Art. 6.1.f) — core product feature |
| Security monitoring & fraud prevention | Legitimate interest (Art. 6.1.f) |
| Legal obligations (tax records) | Legal obligation (Art. 6.1.c) |
Flowo interacts with Google services in two distinct ways: (a) Google Sign-In for authentication, and (b) Google Calendar integration for calendar synchronisation. This section fully discloses how Flowo accesses, uses, stores, shares, retains, and allows deletion of Google user data, in compliance with the Google API Services User Data Policy, including the Limited Use requirements.
A. Google Sign-In (authentication)
When you sign in with Google, Flowo requests the following OAuth scopes:
openid — to verify your identityemail — to obtain your email address for account creation and loginprofile — to obtain your display name and profile picture URLSpecifically, we access the following data from the googleapis.com/oauth2/v3/userinfo endpoint:
| Data field | What it is | Why we access it |
|---|---|---|
| sub (Google ID) | Your unique Google account identifier | To link your Google identity to your Flowo account (stored as oauth_id) |
| Your Google email address | Used as your account email for login, transactional emails, and account recovery | |
| name | Your Google display name | Used as your default username in the Flowo interface |
| picture | Your Google profile photo URL | Displayed as your avatar in the Flowo sidebar and settings |
B. Google Calendar Integration (optional, user-initiated)
If you choose to connect Google Calendar (a separate action from signing in), Flowo requests these additional OAuth scopes:
https://www.googleapis.com/auth/calendar — read and write calendar datahttps://www.googleapis.com/auth/calendar.events — read, create, and modify calendar eventsSpecifically, we access the following calendar data via the Google Calendar API v3:
| Data field | What it is | Why we access it |
|---|---|---|
| Event titles | Names of your calendar events | Displayed in the Flowo calendar view so you can plan tasks around meetings |
| Event dates/times | Start and end timestamps | Used by the AI scheduler to avoid double-booking and find free time slots |
| Event descriptions | Notes and details of events | Displayed in the event detail view within Flowo |
| Event locations | Physical or virtual meeting locations | Displayed in the event detail view |
| Attendees | Email addresses of event participants | Displayed in event details; used when creating new events to send invitations via Google |
| Google Meet links | Video conference URLs | Displayed as clickable links in event details for easy access |
| Recurrence rules | Repeating event patterns | Used to correctly display recurring events in the Flowo calendar |
| Event status | Confirmed, tentative, or cancelled | Used to filter which events appear in your Flowo schedule |
| Reminders | Event reminder settings | Stored for reference; Flowo does not send its own reminders for Google events |
Flowo uses Google user data exclusively for the following purposes:
| Purpose | Data used | Details |
|---|---|---|
| Account authentication | Google ID, email, name | To create and authenticate your Flowo account when you sign in with Google. Your email is used as your account identifier. |
| Profile display | Name, profile picture URL | To show your name and avatar in the Flowo interface (sidebar, settings). The picture URL is stored as a link — we do not download or re-host the image. |
| Calendar display | All calendar event fields listed above | To display your Google Calendar events alongside your Flowo tasks, enabling you to plan your work schedule without context-switching between apps. |
| AI-powered scheduling | Event dates/times only | The AI scheduler uses event time ranges (not titles or descriptions) to find available time slots when automatically scheduling your tasks. |
| Event creation | Calendar write access | When you create an event in Flowo and choose to sync it to Google Calendar, we use the Calendar API to create the event on your behalf, including optional Google Meet links and attendee invitations. |
| Event modification | Calendar write access | When you edit or delete an event in Flowo that originated from Google Calendar, we propagate the change back to Google Calendar. |
| Real-time sync | OAuth refresh token | We use the stored refresh token to periodically sync new, updated, or deleted events from Google Calendar to Flowo, keeping your calendar view up to date. |
Google user data obtained through Google API Services is shared only with the following categories of third parties, and only for the purposes described:
| Recipient | Data shared | Purpose | Legal basis |
|---|---|---|---|
| Cloudflare, Inc. | All stored Google data (encrypted in D1 database) | Infrastructure provider — hosts the database where Google Calendar tokens and synced events are stored | Contract performance; SCCs for international transfer |
| Google LLC | OAuth tokens (to authenticate API requests) | Required for Calendar API calls to read/write events on your Google Calendar | Consent (you authorise the connection) |
Important: Google user data is never shared with OpenAI, Polar, Resend, or any other sub-processor. Specifically:
Google user data is stored and protected using the following measures:
| Data type | Storage location | Protection measures |
|---|---|---|
| Google OAuth tokens (access token, refresh token) | Cloudflare D1 database (google_calendar_tokens table) |
|
| Synced calendar events | Cloudflare D1 database (calendar_events table) |
|
| Google profile data (email, name, avatar URL) | Cloudflare D1 database (users table) |
Same protections as all account data — encrypted at rest, per-user isolation, TLS in transit |
Additional security measures applicable to all Google user data:
We retain Google user data only for as long as necessary to provide the service:
| Data type | Retained until | Deletion method |
|---|---|---|
| Google OAuth tokens | Until you disconnect Google Calendar or delete your Flowo account | Tokens are permanently deleted from the database. We also attempt to revoke the token with Google's API so your authorization is fully removed. |
| Synced calendar events | Until you disconnect Google Calendar or delete your Flowo account | All synced events with source='google' are permanently deleted from the database upon disconnection. |
| Google profile data (email, name, avatar) | Until you delete your Flowo account | All account data is permanently deleted within 30 days of an account deletion request. |
How to delete your Google user data:
If you connect Microsoft Outlook or sign in with a Microsoft account where offered, Microsoft processes authentication and calendar data according to their terms. We use Microsoft identity and calendar APIs only to provide the features you enable (display sync, creating or updating events when you ask us to). We do not use Microsoft data for advertising or to train unrelated models. For how we store tokens and calendar events, the same security measures as for other calendar integrations apply (encrypted storage, per-user isolation, TLS). Microsoft's privacy statement: privacy.microsoft.com/privacystatement.
We share personal data only with the following categories of recipients:
| Sub-processor | Purpose | Location |
|---|---|---|
| Cloudflare, Inc. | CDN, edge hosting, D1 database, DDoS protection | USA (SCCs) |
| OpenAI, LLC | AI task suggestions (task content only, no account data) | USA (SCCs) |
| Polar.sh | Payment processing and subscription management | USA (SCCs) |
| Resend, Inc. | Transactional email delivery | USA (SCCs) |
| Google LLC | OAuth authentication, Calendar API (only if you connect) | USA (SCCs) |
| Microsoft Corporation | OAuth / Microsoft identity and Outlook calendar (only if you connect) | USA / global (Microsoft DPA & SCCs where applicable) |
SCCs = Standard Contractual Clauses (EU Commission Decision 2021/914) for GDPR-compliant international transfers.
We do not share data with advertisers, data brokers, analytics companies, or any other parties beyond the above.
As a data subject under the GDPR, you have the following rights:
We implement appropriate technical and organisational measures to protect your personal data:
In the event of a personal data breach that is likely to result in a risk to your rights and freedoms, we will notify the relevant supervisory authority within 72 hours as required by GDPR Art. 33, and affected individuals without undue delay as required by Art. 34.
Flowo uses no third-party tracking cookies and no advertising cookies. We use only:
| Name | Type | Purpose | Duration |
|---|---|---|---|
flowo_session / sa_user_* | localStorage | Keeping you logged in between visits | Until logout or browser clear |
sa_lang | localStorage | Remembering your language preference | Persistent until changed |
sa_sidebar_* | localStorage | Sidebar width and mini/expanded state | Persistent until changed |
g_state | HTTP Cookie (HttpOnly) | CSRF protection during Google OAuth flow | 10 minutes (auto-expires) |
gcal_state | HTTP Cookie (HttpOnly) | CSRF protection during Google Calendar OAuth | 10 minutes (auto-expires) |
flowo_cookie_consent). We do not use the Facebook Pixel or Hotjar. Cross-site profiling is not part of our product model.
Cloudflare may set a cookie (__cf_bm) for bot detection and security purposes. This is a strictly necessary cookie. See Cloudflare's privacy policy.
On marketing pages (e.g. homepage, guide, legal pages), we store your cookie choices in localStorage under the key flowo_cookie_consent (JSON with your analytics preference). This record is not used to track you across other companies' sites; it only remembers whether you accepted or rejected optional measurement tags on getflowo.com.
If you accept analytics & marketing measurement, we load Google Tag Manager (which may include Google Analytics 4 or other tags as configured) and the Google Ads gtag library. These tools are not injected before consent. If you reject optional tags, they are not loaded.
You can change your mind by clearing site data for getflowo.com in your browser or by deleting the flowo_cookie_consent entry; the banner will appear again on your next visit.
Flowo is not directed at children under the age of 16. We do not knowingly collect personal data from individuals under 16. If you are a parent or guardian and believe your child has provided us with personal data without your consent, please contact us at privacy@getflowo.com and we will delete the data promptly.
Our primary sub-processors (Cloudflare, OpenAI, Polar, Resend) are based in the United States. These transfers are governed by Standard Contractual Clauses (SCCs) approved by the European Commission under Decision 2021/914, providing adequate safeguards for your personal data as required by GDPR Chapter V.
Data processed by Cloudflare is subject to their Data Processing Addendum and their binding corporate rules. Cloudflare Workers and D1 can be configured to process data exclusively within the EU — we are actively evaluating this option for future compliance improvements.
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements. When we make material changes, we will:
Continued use of Flowo after the effective date of changes constitutes acceptance of the updated policy.
Previous versions of this Privacy Policy are available upon request at privacy@getflowo.com.
For any questions, requests, or complaints regarding this Privacy Policy or the processing of your personal data:
Data Controller & Privacy Contact
Hopson & Cie Srl
149 avenue du Domaine, 1190 Bruxelles, Belgium
Email: privacy@getflowo.com
VAT: BE 0450.443.155
If you are not satisfied with our response, you have the right to lodge a complaint with the Belgian Data Protection Authority (APD/GBA):
Autorité de protection des données (APD)
Rue de la Presse 35, 1000 Bruxelles
Website: www.dataprotectionauthority.be
Email: contact@apd-gba.be
Phone: +32 2 274 48 00
For cross-border disputes, you may also use the EU Online Dispute Resolution platform: ec.europa.eu/consumers/odr