Two barriers, and neither depends on the other
The server filters every request by company. And the database itself, separately, rejects whatever doesn't belong to whoever is asking.
AI security for small business usually arrives as one reassuring sentence and not much else. Here it comes as three lists: what we've verified, what's half done and what doesn't exist today. And a few things up front, so you don't find them at the end: Flipa has no SOC 2 report, no HIPAA agreement, no security certifications and no two-factor sign-in. Our terms of use and our privacy policy are still drafts.
The two companies in the example, Larkspur Coffee Roasters and Tamarack Charter, are invented. The app's interface is in Spanish today; English isn't available yet.
When someone asks “is AI safe for business?”, this is usually the first worry, and it comes from whoever has to sign off. This is what's been verified, with the test figures.
The server filters every request by company. And the database itself, separately, rejects whatever doesn't belong to whoever is asking.
One company tries to read, change and delete every kind of thing that belongs to another. It has to fail at all of it, and it does.
Documents, corrections, agents and skills don't cross from one company to another. What it learns with you doesn't come out in anyone else's answers.
Anyone who hasn't signed in with their email and password has permission over nothing. And no customer can touch the balance, the usage figures or the activity log, not even their own admin.
Larkspur Coffee Roasters and Tamarack Charter share a server, the way companies using Flipa do. You're Tamarack. It's a drawing of what our tests do, not a real attack.
Put yourself in Tamarack’s shoes and try to get into Larkspur’s space.
3 of 3 attempts rejected
Every attempt hits the server first. If the server failed, the database is behind it, and it doesn’t depend on the server.
In the full test, 82 of 82 (November 12, 2026): one company tries to read, change and delete every kind of thing that belongs to another, and fails at all of it.
Row by row. If a cell is empty, it's because there's nothing to put in it.
| Verified | Half done | Doesn't exist today | |
|---|---|---|---|
| Separation between companies | Two independent barriers. 82 of 82 attempts rejected. | It hasn't been tested with many companies and people at the same time. | — |
| Keys for connected tools | Stored encrypted, tied to their company. They can't be read from any session. | — | — |
| Connected tools | They come in view-only: actions that change things stay switched off. | What counts as viewing and what counts as a change is declared by each tool. If the account admin turns changes on, the risk we explain further down comes back. | An approval step before each change. |
| Backups | One backup every night, which leaves the server. They're kept 7 days on it and 14 days off it. | We've never rehearsed a restore. Between one backup and the next, up to a day can be lost. | — |
| Export and deletion | A company's data can be exported in full and deleted completely. | Our team does it by hand. After an account is closed, the data is kept for 30 days. | A button to do it yourself. |
| Passwords | Minimum of 10 characters. Five sign-in attempts per minute. The recovery link is good for one hour and one use. | Changing the password doesn't close sessions that were already open. | A second step at sign-in (two-factor). |
| Security review | We do it ourselves, in-house. | — | An outside audit and third-party security seals. No SOC 2 report. |
| Legal texts | — | Terms of use and privacy policy: a draft with no legal review. | A data processing agreement. A HIPAA business associate agreement. |
Status as of November 12, 2026. When a row changes, it gets changed here.
In a database, on a server managed by the team that makes Flipa. That server and the sign-in system, the one with the email and password, are shared today with other services run by the same team. Flipa's data is kept in its own separate area.
We're not going to state the data center's country on this page, because we don't have it documented well enough to put it in writing. If you need it to decide, ask us and we'll answer with what there is.
Flipa works with an AI from another provider. To write each answer, the text that's needed is sent to the AI provider, which is Anthropic, with Claude. We don't have documentation on which region it processes that text in, or under what safeguards, so we don't state those here either.
It's the same worry behind a search like “does AI train on my data”: where does what you type go? Here the answer has two parts. Between companies, it doesn't cross. Toward the AI provider, what's needed to answer does travel.
Besides the person asking and the account admin, there's a third role: the team that operates Flipa. It sets each account's seats and top-ups and has screens for costs and usage. The screen it uses to manage accounts shows counts, not the content of conversations.
That same team is the one that exports and deletes a company's data by hand when the company asks.
Every night the whole database is backed up, and the backup leaves the server for external storage. Backups are kept 7 days on the server and 14 days off it. There's an automatic alert if the service goes down.
What's missing: we've never done a test restore. And between one backup and the next, up to a day of work can be lost.
A company's data can be exported in full and deleted completely. After an account is closed, the data is kept for 30 days. There's no button: you ask us and we do it by hand.
If your work comes with a duty of confidentiality, as at a law firm, read this page slowly before you upload a client file. The same goes for health records: there's no HIPAA agreement. The texts that will govern all of this are the privacy policy and the terms of use, which are provisional today.
The separation between companies is on us. Inside yours, the account admin holds the keys.
No. Uploading and deleting documents, connecting tools and inviting people is the admin's job. The rest of the team asks, hands over jobs and sees their own conversations.
Can the intern delete the price sheet?
Every change is recorded with who made it and when, in one plain sentence (in Spanish, like the rest of the interface). It doesn't store passwords, keys, or the content of documents or conversations. It can't be edited or deleted.
Who connected this, and when?
Removing a person cuts off their access right away. Their conversations and what they created are kept, and they can be added back.
Dana's last day at the roastery is Friday
Passwords under 10 characters, common ones and ones that contain the email address aren't accepted. To change it you have to type the current one, and the recovery link only travels by email.
Is “roast123” OK?
These are the two most common slips. For the first there's a fixed rule. For the second, an instruction and, above all, a switch.
Don't paste it: I don't accept keys or passwords in the chat. The account admin types it into the protected field under Connections, and it's stored encrypted there.
No. Each company has its own space, separated by two independent barriers: the server filters by company and the database rejects whatever doesn't belong to whoever is asking. In the test that checks it, one company tries to read, change and delete every kind of thing that belongs to another and fails all 82 times (November 12, 2026).
The text needed for each answer. If a tool is connected, also what Flipa looks up in it. The provider is Anthropic. We don't have documentation on which region it processes that text in, or under what safeguards.
In a database on a server managed by the team that makes Flipa, shared today with other services run by the same team; Flipa's data is kept in its own separate area. We don't state the data center's country on this page. If you need it, write to us.
Yes. A company's data can be exported in full and deleted completely. Our team does it by hand, because there's no button yet, and after the account is closed the data is kept for 30 days.
No, none of them. There's no SOC 2 report, no HIPAA agreement, no third-party security seals and no outside audit: the review is in-house. And the second step at sign-in doesn't exist yet; you sign in with email and password.
Each person sees their own conversations. The account admin sees those of the whole account, and everyone's usage too. Documents are a different matter: the whole team draws on the same knowledge, and today you can't reserve a document for just a few people.
Write to us before you upload anything. If this is enough for you, start free.
Start free