Privacy policy

• We store what is needed to run your account and send your email. Nothing is sold, and nothing is shared for advertising.
• Your contacts are yours. We process them on your instruction and never email them on our own behalf.
• Email tracking records when something was opened or clicked - not from where, on what device, or by what browser.
• Ask us to delete your account and we delete it, including everything stored for your brands.

For your account - your name, email, billing - Flowzio is the controller. We decide what to collect and are answerable for it.

For your contacts, you are the controller and Flowzio is the processor. You decide who is on your list, on what basis they consented, and what you send them. We store and deliver on your instruction. That distinction matters in practice: we cannot lawfully email your contacts on our own behalf, and we never do.

• Account. Name, email address, a hashed password, and the plan you are on. Passwords are hashed - we cannot read yours, which is also why we cannot recover it for you.
• Brand settings. Your sending name, from-address, physical mailing address (required by anti-spam law in most countries) and any logo or images you upload.
• Billing. Handled by Stripe. Flowzio stores a customer reference and your plan; card numbers never reach our servers.
• Activity.What was created, sent, and by which user in your account. This is what makes “who changed this flow” answerable.

Whatever you import or collect: email address, and optionally first and last name, phone, city, region, country, birthday, tags, and notes you add. Plus their consent status and where it came from - a signup form, a CSV import, a connected store.

We also store what was sent to them and what they did with it, because that is what segments and reporting are built on.

We never enrich this. Flowzio does not buy data, append fields from third parties, or infer attributes about your contacts from outside sources. What you put in is what is there.

When tracking is on, a sent email carries an invisible image and its links are rewritten to pass through Flowzio. That is how “opened” and “clicked” get recorded.

What is stored is a timestamp against a delivery - that this email was opened, and when. We do not record the IP address the request came from, the user agent, the device, or a location. Those are the fields most email platforms keep and we do not collect them, so there is nothing to disclose, breach, or hand over.

Open tracking is approximate by nature: a client that blocks images records no open even though the email was read, and some privacy proxies load images automatically and record one that never happened. Treat it as a trend, not a fact about a person.

When you ask Flowzio to write or rewrite something, the prompt and the relevant context - your brand name, tone settings, the copy being edited, product details if the email features products - are sent to OpenAI to generate a response.

Your contact list is not sent. An AI request carries the content being written, not the audience it will be sent to.

OpenAI processes these requests under its API terms, which do not permit using submitted data to train its models.

Flowzio runs on infrastructure and services it does not own. Each one sees only what its job requires:

• Supabase (PostgreSQL) - the database. All of it, at rest.
• Amazon Web Services - the servers the application runs on.
• Resend - email delivery. Recipient addresses and the message being sent.
• Stripe - payments. Your billing details; never your contacts.
• OpenAI - AI generation, as described above.

That is the complete list. Flowzio has no advertising pixels, no analytics trackers, and no data brokers.

• While your account is open - contacts, campaigns and flows stay until you delete them. We do not expire your work.
• Delivery history is kept so reporting and segments stay meaningful, and older records are pruned once they no longer serve either.
• Unsubscribes and suppressions are kept deliberately, even though they are a record of someone who left. Deleting them is how a future import silently re-adds a person who asked not to hear from you.
• When you delete your account, we remove your data. Backups roll off on their own cycle, so a copy may persist briefly in encrypted backups before it ages out.

Depending on where you live, you may have the right to access, correct, export or delete your personal data, and to object to how it is processed. For your own account data, email support@flowzio.ai and we will act on it.

If you are someone's contact rather than a Flowzio customer - you received an email sent through Flowzio and want your data removed - the fastest route is the unsubscribe link in that email, which works immediately and without us. For deletion rather than unsubscribe, contact the business that emailed you: they control the list, and they can delete you from it. Write to us and we will pass it on, but they are the ones who can act.

• Traffic is encrypted in transit; the database is encrypted at rest.
• Passwords are hashed, never stored or logged in a readable form.
• API keys are shown once when created and stored so they cannot be read back - lose one and you rotate it rather than recover it.
• Access to production data is limited to what is needed to operate and support the service.

No system is perfect. If you find a vulnerability, email support@flowzio.ai with enough detail to reproduce it and we will treat it as urgent. We will not pursue anyone who reports a genuine issue in good faith.

If we change how data is handled in a way that affects you, we will update the date at the top and tell account owners by email. We will not quietly broaden what we collect and rely on you re-reading this page.

Questions about any of it: support@flowzio.ai.