Privacy Policy
This Privacy Policy explains how flor.rgb LLC ("we," "us") handles information in connection with the flor application for computers and its iPhone companion (together, the "App") and the flor.cam website (the "Site").
The short version
flor is local-first. Your business records and credentials are stored on your own devices, in an encrypted vault. We never receive your password, and there is no account to look after. Signing in with your email finds your purchase or starts your free trial. After that the App checks your license on your device and works with the wifi off. The App contains no telemetry or analytics. Seven features pass through servers we run: email sign-in, which sends your address once to find your purchase; web search, which forwards the words being searched; the TikTok, Twitch, Kick, Vimeo and Patreon sign-ins, which swap the platform's code for your token and keep nothing; and sync anywhere, the sealed copy, client pages and the Team relay, which carry only sealed data we cannot read. Every other connection goes from your device to the provider you choose, and only when you turn it on or ask for it. Each one is described below.
1. Data stored by the App (on your devices)
The App stores your records and credentials locally in an encrypted vault, protected with AES-256-GCM and a password that only you hold. This includes clients, prospects, jobs, bookings and calendar entries, invoices, payments, expenses, hours, gear and rentals, crew and what you paid them, footage shoots and drives (including a small still frame from a shoot's footage), miles and tax payments, channel readings, media file metadata, drafts and settings. Encrypted rotating vault backups, a local device identity, optional OS-protected "remember me" material and downloaded on-device model files also live in the App's local data folder.
Some files are kept outside the vault, as plain files on your device: photos you file through Snap; the fingerprint file (flor-checksums.sha1, a list of file hashes and file names) the App writes beside your footage on each drive it copies to; and anything you export or save, such as a PDF, a spreadsheet or the tax pack folder. Your media stays in your own folders. We have no access to any of these files and cannot recover your vault if you lose both your password and your spare key.
2. AI processing
Many everyday requests to the assistant are worked out in the App's own code, on your device, with no model at all. By default, anything else runs on a local model entirely on your device. On the iPhone, the App can use Apple's on-device model. If you optionally sign in with your ChatGPT plan or add a third-party AI provider key (for example OpenAI or Anthropic), then, only when you use that brain, the App sends the prompt and the context needed to answer it to that provider on your behalf, subject to that provider's privacy policy. This is your choice and is off by default.
3. Connections that pass through our servers
Web search. When you ask the App to research something, read a link, check your own site or read trends, and you have not set up your own search key, the search goes through a relay we run. The relay receives the words being searched and an anonymous entitlement id derived on your device from your license (the relay never sees your license key; if it does not know your license yet, the App sends the key once to flor.cam, which checks that we issued it and registers its anonymous id with the relay), and forwards only the search words to our search provider (currently Serper). The search words may be ones you typed, or ones the App or the assistant wrote for the task you asked for, such as your field when reading trends. The relay does not store your search words or the results. It keeps usage counters per entitlement id and daily totals without any id; for a trial it keeps the trial's public key and a salted hash of the address it registered from. Web search is on by default and only runs when you ask; you can switch it off, or use your own search key or a SearXNG instance instead.
Email sign-in. When you sign in with your email, the App sends that address to flor.cam. We email you a six-digit code and keep only a scrambled copy of it and a count of tries, for ten minutes, and the times codes went to your address, in the same scrambled form, so nobody can flood your inbox. When you type the code, flor.cam looks up your purchase at our store and sends your license back to the App, which checks it before it goes in. If you haven't bought flor, signing in starts your free trial, and we keep the day it started so it can't start over. Nothing else is kept. The App never signs in again by itself.
TikTok sign-in. If you sign in with TikTok to read your own numbers, TikTok requires its app secret when you sign in and each time the sign-in is renewed, and only a server can hold that secret. So those two steps pass through flor.cam: your device sends TikTok's one-time code (for a renewal, your refresh token), flor.cam adds the secret, asks TikTok for your token and hands it straight back. It stores nothing and logs no code or token. The token is kept in your vault, and every read goes straight from your device to TikTok. A renewal happens about once a day, when the App reads your numbers.
Twitch, Kick, Vimeo and Patreon sign-in. These four work the same way. Each requires its app secret when you sign in (Twitch, Kick and Patreon also when the sign-in is renewed), so those steps pass through flor.cam: the platform sends your browser to flor.cam, which sends it straight on to your own device; your device then sends the one-time code (for a renewal, your refresh token), flor.cam adds the secret, asks the platform for your token and hands it straight back. It stores nothing and logs no code or token. The token is kept in your vault, and every read goes straight from your device to the platform.
Sync anywhere. With a paid plan, signing in with your email keeps your computers in step over the internet. It is on from sign-in, and you can switch it off on any computer in Settings → Devices & sync. Your records are sealed on your device before they leave it, with a sync key that only your flor password opens. We never receive your password or your records. If you connected a mailbox, its login travels inside the same sealed bundle, so your other computers read your inbox without asking for it again. When a computer joins, it sends flor.cam your license key and the computer's public key, and flor.cam answers with a pass that lasts fifteen minutes. The relay then asks the computer to prove your password without sending it (a method called SRP). For each person the relay keeps the latest sealed bundle from each computer, each computer's public key, the size and time of each bundle, a check value made from your password that can confirm a proof but cannot be turned back into the password, and your sync key sealed under your password. Your box is named by a keyed hash of your email, so the relay never sees the address. To confirm the plan is paid, the relay checks an anonymous id derived from your license and does not keep it. After a wrong password it keeps the time and a scrambled form of the address it came from for one day, to stop guessing. Switching sync anywhere off on a computer deletes that computer's bundle. When the last computer leaves, everything in the box is deleted, and a box no computer has sent to for 400 days is emptied the same way.
Sealed copy. With a paid plan you can switch on a sealed copy of your vault in Settings, so a lost computer does not lose your records. The copy is sealed on your device with a key worked out from your spare key, which we never receive, and goes up a few minutes after you make changes. The relay keeps the newest copy of each of the last seven days with its size and time, and the box's public key. The box is named by a number worked out from your spare key, which says nothing about you. To confirm the plan is paid, the relay checks an anonymous id derived from your license and does not keep it. Receipt photos and footage stay on your device. Switching it off deletes every copy; a box with no new copy for 400 days is emptied the same way. It is off until you switch it on.
Client pages. With a paid plan you can send a client one link for a job: the quote, the invoices with your own pay links, the cuts to watch and the files. The page is sealed on your device with a key that lives only in the link, after the # sign, so it never reaches our servers. A relay we run keeps the sealed page, the page's own public key, the day it closes and when it was made, changed and answered. It cannot read the page. What your client sends back, such as a yes or notes on a cut, is sealed in their browser to your computer, waits on the relay until your computer takes it, and is then deleted. To confirm the plan is paid, the relay checks an anonymous id derived from your license and does not keep it. Pay opens your own payment page, so your client's card never reaches us. Your client's browser loads the page from flor.cam and the sealed parts from the relay, so both see their network address, as any website does. Each visit, flor.cam serves the code that opens the page, and that code is what keeps it sealed, so the page is only as private as the code flor.cam serves. A page closes 180 days after it last changed, and the relay deletes all of it 30 days later. Turn off on the job deletes it at once. A page is made only when you press Client page.
Team relay. If you own a Studio license and switch on syncing over the internet in Settings → Team, the work your team shares (such as clients, jobs, bookings and deliverables; never money, mail or journals) is sealed on your device with your team's key before it is sent. The relay stores the latest sealed bundle from each device, sealed key boxes, device public keys and timestamps, and cannot read the contents. Switching it off deletes the bundles and key boxes; a team idle for 180 days is emptied the same way. It is off by default.
4. Connections between your own devices
Pairing your own computers and your iPhone on the same network happens directly between them, encrypted, after you pair them with a six-digit code. There is no server in the middle. Sync anywhere, described in section 3, goes through our relay, sealed. While the pairing window is open, a Mac announces its device name on your local network so your phone can find it; the phone looks for it only while its sync screen is open.
5. Connections to providers you choose
If you connect a work inbox, the App reads messages directly from your mail provider to your device, read-only, using credentials you store in your vault. If you configure outgoing SMTP and press Send on a draft, that message is sent directly through the mail provider you configured. A connected Stripe or PayPal account is queried with your own read-only credentials, only to check payment status. Slack, Telegram or Discord receive the text of an event you switched on, posted to your own channel. If you add your own YouTube key, the App reads public channel numbers and the trending chart from YouTube; reading trends also fetches public Reddit feeds. If you add a Bluesky handle, the App reads that handle's public follower and post counts from Bluesky once a day, with no sign-in. Model files download when you ask for them: flor’s AI from our release page on GitHub, the voice pack and older assistants from Hugging Face. Once flor’s AI is on your computer, the App fetches its newer versions from the same page by itself. None of these credentials or contents are sent to us; each provider processes the request you ask the App to make. On the iPhone, the calendar on your phone is read only if you switch it on, and its events are never stored, synced or sent anywhere.
Your own YouTube, TikTok, Twitch, Kick, Vimeo and Patreon numbers. If you sign in with Google for YouTube, or with TikTok, Twitch, Kick, Vimeo or Patreon, the App reads your own account's numbers, read-only: subscribers, followers or members, views or plays, likes and videos (on TikTok, each video's views and likes), and up to 90 days of YouTube history. It asks for no permission to post. To start a sign-in, the App asks flor.cam which app to introduce itself as; that request carries nothing about you. YouTube's sign-in and every YouTube read go straight between your device and Google (the TikTok, Twitch, Kick, Vimeo and Patreon sign-ins are described in section 3). Once you are signed in, the App reads these accounts once a day when you open it; you can switch that off in Numbers. Disconnecting deletes the token and the numbers read through it.
6. Update check
When you open it, every six hours while it stays open, and whenever you press "check for updates", the App on your computer makes a single request to flor.cam to read the newest version number. The request carries no data about you or your vault — it is the same as visiting a tiny public web page — and you can switch the check off in Settings. Standard hosting logs (see below) are the only trace it leaves.
Renew by itself (monthly plans only). A monthly plan comes with a new key each month, and the App fetches it for you: in your plan's last week it sends your license key, once, to flor.cam, which checks with our reseller that the month was paid and sends back the new key. The key holds the name and email you bought with, which we already have from the sale. Nothing from your vault is sent. Switch it off in Settings → Your plan & updates and you sign in again after each renewal instead. Founding and annual keys never make this request.
7. Information handled when you buy or download
Buying a license and downloading the App do involve limited information, handled by our providers rather than by the App:
- Purchases are processed by Link (Sold through Link, LLC), the merchant of record service run by Stripe, for every order. When you buy, Link collects and processes your payment and contact details (such as your email, country and billing information) to complete the sale and handle the tax. Their handling of that information is governed by Link’s Privacy Policy. We receive order information (such as your email and purchase record) so you can sign in with that email to get your plan, and so we can provide support. The checkout is Stripe’s own page: our buy page (flor.cam/buy) only links to it and loads nothing from anyone else. Purchases made earlier through Gumroad were handled the same way under Gumroad's Privacy Policy.
- The Site may keep minimal hosting logs (such as your browser's IP address and request data) for security and to keep the Site running. The Site sets no tracking cookies and uses no third-party advertising or analytics. If we ever add privacy-respecting analytics, we'll update this policy first.
- Support: if you email us, we receive the information you choose to send.
- Briefs and held names (flor.cam/hire). A brief you send from flor.cam/hire reaches us by email, through our email provider, with what you typed and your email address, so a person can answer it. We use it only to answer you, and we delete it if you ask. The Site itself keeps no brief: only a count of briefs each month, and for one day a scrambled form of where the request came from and of the address you gave, to stop floods. If you hold a name, we email you a code as sign-in does, check that the address has flor (a purchase or a free trial), and keep the name, the day you held it, and the same scrambled form of your address that sign-in uses. Nothing is published. To let a name go, write to us.
8. How we use the limited information we receive
We use order and support information only to deliver your license, provide support, prevent abuse, and meet legal and accounting obligations. We do not sell your personal information, and we do not use your data for advertising.
9. Sharing
We share information only with service providers that make the sale possible or run the services described above (such as Stripe and Link, our email and hosting providers, Cloudflare, which runs our relays, and our search provider, which receives search words only), and where required by law. We never share your on-device App data, because we never have it.
10. Retention
We keep order records for as long as needed for support, warranty, tax, and legal purposes. Your App data is retained by you, on your device, for as long as you keep it. Sealed data on our relays is kept and deleted as described in section 3.
11. Your rights
Depending on where you live (for example under the GDPR or CCPA), you may have rights to access, correct, delete, or port the personal information we hold about you, and to object to certain processing. Because your App data lives only on your device, you already control it directly and can export or delete it at any time. To exercise rights over order/support information, contact us at flor.support@proton.me.
12. Children
The App and Site are not directed to children under 13, and we do not knowingly collect their personal information.
13. Changes
We may update this policy; we'll change the "last updated" date and, for material changes, provide reasonable notice.
14. Contact
flor.rgb LLC — flor.support@proton.me.