Legal
Privacy policy
Last updated 7 September 2026
reflex is a Notion automation tool built by workFlowers. This page explains what we collect, why we hold it and how to get rid of it. Plain English, no lawyer voice.
Who we are
reflex is operated by Company Flow Pte. Ltd. (UEN 202442050M), trading as workFlowers, a company incorporated in Singapore and registered at 160 Robinson Road, #14-04, SBF Center, Singapore 068914. For any privacy question, or to ask for a copy or deletion of your data, email dennis@work.flowers. We are the data controller for your account details and a data processor for the Notion content your flows touch.
What we collect
- Account details. Your name, email address and sign-in identifier from Google or your magic-link email.
- Notion connection. An encrypted key identifying the authorised connection to the Notion workspace you connect, plus the workspace name and id. We never see or store your Notion password, and the OAuth grant itself is held by our connector gateway rather than by us.
- Flow definitions. The triggers, steps, conditions and text you build, including the ids and titles of the Notion databases and pages your flows watch, and a cached copy of those objects’ property schemas so the editor can show them.
- Run records. For each run we store what triggered it, each step’s inputs and outputs, and any error. These are what you see on the Runs page.
- Notion content in transit. To run a flow we read the pages and properties it needs and write the changes you asked for. Snapshots of that content appear in the run record so you can debug a run.
- Technical logs. Request timestamps, error traces and basic usage counters.
What we don’t do
- We don’t sell your data or share it with advertisers.
- We don’t use your Notion content to train machine-learning models.
- We don’t read your workspace beyond the databases and pages you explicitly connect to a flow.
Why we hold it
To run the service you signed up for: authenticating you, executing your flows against Notion, showing you run history and enforcing plan limits. We also use aggregate usage numbers to work out what to build next.
Who else processes it
- Notion — the workspace your flows read and write.
- Lovable — the application platform we build and host on, including the connector gateway that holds your Notion authorisation and brokers our calls to Notion.
- Supabase — database and authentication.
- Cloudflare — hosting, content delivery and server-side execution.
- Google — optional sign-in.
Each of these processes data only to deliver reflex. If we add a processor we will update the sub-processors page, which lists what each one handles and where.
How long we keep it
Run records, their content snapshots, flow definitions and account details are kept while your account is open. Automatic deletion of run records after 90 days is planned but not yet running, so until it is, ask us and we will clear your run history for you. Disconnecting Notion deletes the stored connection key immediately. Delete your account and we remove everything within 30 days, apart from records we must keep for accounting.
Security
Connection keys are encrypted at rest. Every table is protected by row-level rules so one account can never read another’s data. Traffic is encrypted in transit. Incoming Notion webhooks are signature-verified before we act on them. The security page has the detail.
Cookies
We set only the cookies needed to keep you signed in. No advertising or cross-site tracking cookies.
Your rights
You can ask for a copy of your data, correct it, or have it deleted — email us and we will respond within 30 days. You can export your flows yourself at any time from the app.
Changes
If we change this policy in a way that matters we will email account holders before it takes effect.
See also our terms of service, security and sub-processors pages.