← Back to BioFlow

Privacy Policy

Effective October 16, 2026 · BioFlow is a product of Devino Solutions (14930398 Canada Inc.), Ottawa, ON, Canada.

This policy explains what data BioFlow (“we”, “us”) collects from creators and visitors, why we collect it, who we share it with, and how you can exercise your rights. We aim to keep it short and honest. If anything is unclear, email hello@devino.ca.

What we collect

How we use your data

We do not sell your personal data, and we do not use it to train machine-learning models without explicit consent.

Who we share with

We share the minimum data required with the third parties listed below. Each operates under its own privacy policy:

Google Analytics and your choice

BioFlow uses Google Analytics 4 to measure how its marketing site, getbioflow.com, and its app are used. It is off until you choose “Allow analytics” on the bar at the bottom of the page. Until then no Google Analytics script is loaded, no request is sent to Google for it, and no Google Analytics cookie is set. “Decline” keeps it off and is remembered.

This choice covers Google Analytics only. It does not change the analytics described under “Usage analytics” above.

Google user data and Limited Use

BioFlow’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

What we ask for. Connecting Google Calendar requests a single read-only scope, granting permission to read the events on the calendar you choose and nothing else. We never request write access, and BioFlow cannot create, change, or delete anything in your Google account.

What we read. For each of your next 25 upcoming events we read only the title, location, start and end time, cancellation status, and the Google event link. We do not read attendee lists, guest email addresses, event descriptions, organiser details, attachments, conferencing links, or any calendar other than the one you select.

What we do with it. The only purpose is to render the Events block on the BioFlow page you chose to put it on. We do not sell Google user data, do not use it for advertising or ad-personalisation, do not transfer it to data brokers, and do not use it to build profiles or to assess creditworthiness or eligibility for anything. Humans at BioFlow do not read it, except in the narrow cases the Limited Use policy permits: with your explicit consent, where required by law, or where strictly necessary for a security investigation.

Data protection for sensitive data

Connected-account credentials and the data we read on your behalf are treated as sensitive. These are the specific controls in place:

Third-party AI services

BioFlow has one AI feature of its own: an in-app copilot that edits your bio page when you ask it to. It uses a single provider chain, and we use no other AI service ourselves:

When it runs and what it sees. Nothing is sent unless you type a request into the copilot. When you do, we send that request together with the content of the page you are editing, because the copilot cannot edit a page it cannot see. That is your own page copy — the text, links, layout and settings you wrote yourself. Three things travel with it: the names, file types and storage paths of the uploads in your workspace, so the copilot can place one when you name it; any file you attach to that particular message; and, on a turn where you ask about performance, that page’s view, click and unique-visitor totals.

Content synced from a connected account is removed first. Before the page reaches the AI provider we strip out everything a connected account put on your page: your Google Calendar events, and equally your Shopify products, Instagram posts, TikTok videos, YouTube video titles and view counts, RSS headlines and summaries, your mailing-list name and subscriber count, and your booking link. On a block bound to a connected account we blank every field the sync writes — the heading of that block included, not only its list of items — and we put the real values back only after the copilot has answered. What the copilot is left with is the block’s position, its layout settings, which service it is connected to and how many synced items it holds. It can reorder that block, restyle it, and change its layout, but it cannot read a word of what the connected account put there.

What the copilot is never sent. Your OAuth tokens, your Google account credentials, any calendar or event data at all, attendee lists and guest email addresses (which we never receive from Google in the first place), and the contents of other pages in your workspace. The connector itself never calls an AI provider.

Training. We do not use your content to train machine-learning models. Every request we send to our AI gateway carries an instruction forbidding it from routing that request to any provider which collects prompt data for training.

Connecting BioFlow to your own AI app. Separately from our copilot, you can authorise an AI assistant or agent of your own choosing to reach your workspace, by signing in to it through BioFlow and granting it permission. That app is yours, not ours: we do not choose it, run it, or send it anything until you connect it, and what it does with what it reads is governed by its own privacy policy, not this one. It can read only what the permissions you granted allow, and it never receives raw block content. What it can read is: your page titles, slugs, publication status and theme name; the kind of each block with a short label of at most 80 characters, which on a block bound to a connected account can be the synced title; your view, click and unique-visitor totals together with your most-clicked links and referrers; the email addresses and names of contacts your forms captured, and when and from which block; and the names, file types, sizes and storage paths of your uploads. Your calendar’s list of events, their times and their locations are not among them, and no connected-account credential ever is. One consequence is worth naming plainly: a click on any link you publish is recorded with that link’s own text, and on a synced event row that text is the event title you have already published on your public page, so an app you have granted analytics permission can read it there. You can withdraw any app’s access at any time under Settings → Connected AI apps. Revoking removes your consent, so the app’s next request is refused even if the access token it holds has not expired, and its refresh token is revoked, so it cannot obtain a new one.

Where we store data

Application data is stored on infrastructure operated by Devino Solutions in the European Union and the United States. Backups are encrypted at rest. Stripe stores payment data in its own infrastructure under PCI-DSS controls.

How long we keep it

Account data is kept for the lifetime of your account and deleted within 30 days of account deletion. Anonymised analytics is retained for up to 24 months. Payment records are kept for 7 years to comply with tax law.

Your rights

You can request access, correction, export, or deletion of your data, or object to specific processing, at any time. Contact hello@devino.ca and we will respond within 30 days.

Children

BioFlow is not directed at children under 13 (or under 16 in the EU/UK), and we do not knowingly collect personal information from them. If you believe a child has provided personal information, contact us and we will delete it.

Changes

We will update this page when our practices change. Material changes will be announced by email or in-app at least 14 days before they take effect.

Contact

Devino Solutions (14930398 Canada Inc.)
2149 Johnston Rd, Ottawa, ON K1G 5K1, Canada
Email: hello@devino.ca