BiFlow

Privacy Policy

Effective date: August 16, 2026 · Last reviewed: August 16, 2026
This is a first draft written from a direct review of BiFlow's actual code, so the descriptions of what data goes where are accurate to how the app works today. It is not a substitute for review by a lawyer, especially once BiFlow has paying customers outside Lebanon — please have it checked before you rely on it for Google's verification review or for real customer contracts.

Who this policy covers

BiFlow ("we," "us") is a clinic/business management app. This policy explains what happens to data when you or your clients use BiFlow, across every version of the app (including any demo, trial, or client-specific deployment).

The short version

BiFlow is built to keep your business data on your own device, under your own control. There is no BiFlow server sitting in the middle collecting your clients' information. The only times data leaves your device are things you explicitly choose to do: backing up to your own Google Drive, or using the optional AI Assistant add-on (which talks directly to Anthropic using an API key you provide). Both are detailed below.

What data BiFlow stores, and where

Everything you enter into BiFlow — clients, appointments, packages, invoices, payments, expenses, notes, and settings — is stored locally in your device's browser storage (localStorage), tied to the specific BiFlow site you're using. It is not transmitted to us or to any server we operate; we have no access to it unless you choose to share it with us directly (for example, sending a screenshot for support).

Photos and documents you attach to a client record (prescriptions, reports, etc.) are stored separately, in your browser's IndexedDB storage, and stay on that device only — they are not included in any backup, local or cloud.

DataWhere it livesLeaves your device?
Clients, appointments, packages, invoices, payments, expenses, notesBrowser localStorage on your deviceOnly if you back up (below)
Client documents / photosBrowser IndexedDB on your deviceNo — device-only, excluded from all backups
Your activation/license codeBrowser localStorage on your deviceNo — checked entirely on-device using cryptographic verification

Backups

Manual backup: you can export a full backup of your BiFlow data as a file to your own device at any time. This file goes wherever you choose to save it — we never see it.

Google Drive Auto-Backup (optional): if you choose to connect Google Drive, BiFlow asks Google for permission to create and manage a folder called "BiFlow Backups" in your own Google Drive account. It uses Google's drive.file permission scope, which means BiFlow can only see and manage the files it creates itself — it cannot browse, read, or touch anything else in your Drive. Backups go directly from your browser to your Drive; they never pass through any server we run. Only your five most recent backups are kept. You can disconnect this at any time from within the app, which stops future backups but does not delete ones already saved to your Drive.

AI Assistant (optional paid add-on)

BiFlow offers an optional AI Assistant that understands typed or spoken commands ("book Sara for Tuesday at 10"). This feature is off by default and requires you to enter your own Anthropic API key, which you obtain and control yourself.

When you use this feature, BiFlow sends the following directly from your browser to Anthropic's API (api.anthropic.com), using your own API key — this data does not pass through any server we operate:

This means using the AI Assistant shares a working snapshot of your client and business data with Anthropic in order to process each command. Anthropic's handling of that data is governed by Anthropic's own privacy policy, not this one — we encourage you to review it, and to only use this feature if you're comfortable with that. If you never enter an API key or never use voice/text commands, none of this data is ever sent anywhere.

Messaging clients via WhatsApp

BiFlow's "message client" buttons open WhatsApp on your own device with a pre-filled message — the same as if you typed it yourself. BiFlow does not send messages on your behalf, does not integrate with the WhatsApp Business API, and does not see or store the content of your WhatsApp conversations.

What we don't do

Licensing and device activation

Activating BiFlow uses a device fingerprint and a signed activation code, verified entirely on your own device using public-key cryptography. This check does not contact any server — we cannot see when or whether your device checks its license.

Third-party code libraries

BiFlow loads a small number of standard, publicly available JavaScript libraries from established content delivery networks (jsDelivr and cdnjs) to generate Excel exports, PDFs, and charts, and to build zip downloads. Loading these causes your browser to make a request to those CDNs in the same way loading any website does; they do not receive your BiFlow data.

Data retention and deletion

Because your data lives in your own browser, you are always in control of it. Clearing your browser's site data, uninstalling the app (if installed as a home-screen app), or switching devices without restoring a backup will remove it. If you've connected Google Drive Auto-Backup, backup files remain in your Drive until you delete them yourself — we have no ability to delete them for you.

Children's privacy

BiFlow is a business tool intended for use by adult business owners and staff, not by children, and is not directed at or knowingly used to collect data from children.

Changes to this policy

If this policy changes in a meaningful way, we'll update the "last reviewed" date above. Continued use of BiFlow after a change means you accept the updated policy.

Contact us

Questions about this policy or your data:
biflow961@gmail.com