Privacy
What we do with personal information, in plain words.
Two kinds of reader
If you are reading this site, FastFlowUp decides what happens to the little we hold about you, so we are the controller.
If your employer uses FLO, your employer decides what is stored and what happens to it. They are the controller and we are the processor acting on their instructions. Ask them first about anything in your mailbox; we help them answer, then we say below what we do on our own account.
If you visit this site
This site has no forms, no analytics, no advertising trackers, no cookies. Nothing follows you between pages or between sites.
Our hosting keeps ordinary request records for a short time, which include the address your connection came from, so that an attack can be recognised and a fault can be traced. If you write to us, we keep that conversation so we can reply and follow it up.
What the product holds
| Category | Examples |
|---|---|
| Who you are at work | Name, work address, org unit, role, plus the mobile number used for sign in codes |
| What you write and keep | Mail and attachments, files, calendar events, contacts, meeting recordings, transcripts, booking answers |
| How you sign in | Passkeys, the devices holding them, one time codes, security answers, recovery attempts |
| What the product did | Sign ins, administrator actions, scan verdicts, link clicks where your company turns that on, delivery records per message |
| Paying for it | The administrator who buys, their contact and invoice details |
We do not sell personal information, we do not use it for advertising, we do not train any model on it. Nobody at FastFlowUp reads a customer's content except through the staff surface, with a recorded reason and inside a window an administrator can see.
The phone app
The FLO app for iPhone and Android is another way into the same account, not a separate service. What it shows is what the product holds, as listed above. It stays where this page says. This part covers what the app adds: what it keeps on the phone, what it asks the phone for and what it sends that a browser would not.
Nobody creates an account in the app. Your company's administrator adds you, then the app signs you in through the same sign in page as the browser, opened in the phone's own browser.
| What | How it is kept |
|---|---|
| Mail, calendar events, chat messages and the address book you have synced | Inside the app's private storage on the phone, which other apps cannot open, so you can read them without a connection |
| Messages waiting to send and uploads in progress | In the same storage, until they reach the server |
| Cloud files you choose to keep offline | Encrypted again under a key made for that phone alone, held in the phone's secure key storage |
| What keeps you signed in | A sign in token in the phone's secure key storage, never copied to another device. The short lived access token is held in memory only |
| Meeting reminders | Scheduled on the phone from your calendar and shown by the phone itself |
Signing out of the app removes all of it from that phone, even without a connection: the mail, calendar and chat stores with anything still waiting to send, the Cloud copies with the key that sealed them, the reminders, the sign in token and your notification settings. Clearing what is kept offline from the app's settings frees space on the phone and never deletes anything from your account. On Android the app is left out of the phone's backups, so none of this travels to another phone that way.
| What it asks for | When it is used |
|---|---|
| Notifications | To tell you about new mail, chat messages and meetings about to start. The phone asks you first; you can turn them off at any time |
| Microphone | Only while you are in a meeting in Live with your microphone on |
| Camera | Only while you are in a meeting in Live with your camera on |
| Photos | Only the photos and videos you pick to upload to Cloud. The app does not see the rest of your library |
| Running in the background | To keep a meeting going with the screen locked, with an ongoing notice on Android. To fetch new mail when a notice arrives. On Android, also to check for new mail about every half hour while the phone is connected |
A meeting in Live is not added to the phone's call history. Captions in a meeting arrive from the meeting as it happens and are not kept by the app afterwards. Whether a meeting is recorded is shown before you join, exactly as it is in the browser.
Notices. A notice says who a message is from and where it arrived, such as the mailbox or the chat channel, with what the app needs to open it. It never carries the subject or the body. To deliver it we register an address for this phone with a notice delivery service, which hands iPhone notices on to the phone maker's own service. We keep that address with the kind of phone, which of Inbox and Chat it is for and the phone's language setting. It is removed when you sign out, or when the delivery service tells us the phone no longer uses it.
Crash reports. Builds from the app stores send a report when the app fails: where in the code it failed, the phone model, the system version and the app version. We do not attach your name, your address or your account to a report. Test builds send none.
Version checks. When it opens, the app asks our release service whether its version is still supported and whether any feature is paused, sending only the kind of phone, the app version and its build number. It may also download a fix to the app's own code, which comes from an update service that sees the app version and the connection's address.
The app has no analytics, no advertising identifiers and no trackers. It does not read your phone's contacts, your location or any file you have not picked.
Why we may hold it
Where European or United Kingdom law applies, our grounds are these. Where Australian law applies, the same purposes are the ones we collect for.
| Purpose | Ground |
|---|---|
| Running the service for your employer | The contract with them, plus our legitimate interest in providing it |
| Signing you in and keeping the account safe | Legitimate interest in security, plus legal obligations where they apply |
| Checking mail and files for phishing and malicious content | Legitimate interest in protecting the company and its people |
| Keeping an audit trail | Legitimate interest, plus the obligations your employer is meeting |
| Billing and tax records | The contract, plus the law that requires records to be kept |
The FLO IQ features are off unless your company turns them on. A company can allow the summarising of its content without allowing anything to leave for an external model.
Where it goes
The database and the object storage run in Singapore. That is where your mail, files and calendars live. The mail server keeps nothing of its own: it runs on the edge and stores every message there.
Two things leave that region, which we say plainly rather than bury. Sending mail passes through our sending service in the United States, so a message you send is processed there on its way out. Meeting media in Live is carried by the media service node nearest the people in the meeting, which may be anywhere. Text messages carrying sign in codes are sent from Singapore.
Where a company turns on the escalated part of FLO IQ, the text of that one request goes to a model provider in the United States with names and addresses replaced by tokens first, under retention switched off on their side.
The phone app adds two small things to that list. A notice to a phone passes through the notice delivery service, which runs worldwide, carrying who a message is from and where it arrived but never what it says. A crash report from the app goes to the crash reporting service in the United States, carrying no name or account.
A company may also opt into a cache node inside a local internet exchange, such as Dhaka. Those nodes hold encrypted bytes only and the keys never leave the company's chosen region, so a seized node yields nothing readable.
How long we keep it
| What | How long |
|---|---|
| Mail, files, events and contacts | As long as your company keeps them, under the retention setting it chooses |
| Backups | Thirty five days, under a lock that prevents early deletion |
| Audit records | Seven years, because that is what a company being audited needs |
| Link clicks | The period your company sets, only where it turns the feature on |
| What the app keeps on a phone | Until you sign out on that phone. Removing the app removes it too. Deleting the app and installing it again starts signed out |
| A phone's notice address | Until you sign out on that phone, or until the delivery service says the phone no longer uses it |
| App crash reports | Ninety days |
| After a person or a company is deleted | The key is destroyed when the retention window ends, thirty days by default |
Destroying the key is what makes deletion true. Everything sealed under it, including every backup already written, becomes unreadable rather than merely hidden.
Your rights
You can ask to see what is held about you, to correct it, to have it deleted, to limit what we do with it, to object to it, or to receive it in a portable form.
If your employer uses FLO, ask them first: the mailbox is theirs to answer for, so their administrator can do most of this from Console immediately. Where a request needs us, we assist them within ten working days.
Deleting your account. Your account was made by your company's administrator, not in the app, so it is removed the same way: ask your administrator, who can remove you from Console. Once you are removed, everything held for you follows the retention your company chose, then the key is destroyed as described above. If you cannot reach your administrator, write to support@fastflowup.com and we will pass your request to your company and help them complete it. Signing out of the app or removing it clears the phone, not the account.
For information we hold on our own account, such as a message you sent us, write to legal@fastflowup.com. We answer within thirty days. There is no charge. We will ask enough to be sure it is really you, no more.
How it is protected
Sign in is by passkey, which cannot be phished. Everything is encrypted in transit and at rest under a key held for your company alone, with the option for a company to hold that key itself. A company's rows are separated in the database by a rule that fails closed. Every message and file is checked before it is delivered. Backups are locked; restores are rehearsed.
Our security page says more, including what encryption at rest does not promise. If you think you have found a weakness, write to security@fastflowup.com; we will not pursue anybody who reports one in good faith.
Children
FLO is sold to companies for their staff. It is not meant for children. We do not knowingly collect information about anybody under sixteen. If you believe we hold some, write to us and we will remove it.
Changes
When this notice changes in a way that matters, we tell the administrators of every company using FLO at least thirty days beforehand, with the date at the top of this page changing. Minor corrections are made without notice.
Contact and complaints
Privacy questions go to legal@fastflowup.com.
If we have not put something right, you may complain to the Office of the Australian Information Commissioner. In the European Union or the United Kingdom you may complain to your own supervisory authority instead.