Privacy
Last updated 8 August 2026
In short
Flula runs on your organisation's own server. Your formulations, INCI lists and screening history stay there. They are never sold, never shared with ingredient suppliers, and never used to train any model — by us or anyone else.
1.What this document covers
Flula is deployed on infrastructure your organisation controls. That shapes everything below: for most of what you do, there is no third party involved to have a policy about.
Where this document says we, it means the operator of your deployment — usually your own IT or R&D function. Where it says you, it means the person using the application.
2.What the application stores
Only what it needs to do the job:
- Account — name, email address, a hashed password, role, and team.
- Your work — projects, formulations, briefs, saved screenings and supplier sample requests.
- Administrative activity — sign-ins and administrative actions, with the address and browser they came from, so an account holder can see who changed what.
- Preferences — time zone, and which notices you have dismissed.
Passwords are stored as one-way hashes and cannot be read back, including by an administrator. If you enable two-factor authentication, the shared secret is stored so codes can be verified, and recovery codes are shown once at the moment they are generated.
3.What it does not do
These are the commitments the architecture allows us to make plainly:
- Your formulations do not train any model. Not ours, and not a third party's. The formulation engine is deterministic — it composes from rules and a local ingredient database, and learns nothing from what you enter.
- Your data is not sold, and not shared with ingredient suppliers. Supplier details in the catalog flow one way, to you. Nothing about your formulations, searches or interests is passed back to them.
- There is no advertising or analytics code in the application — no trackers, no third-party pixels, no session recording.
- No profile is built about you beyond the account record and the activity log described above.
4.Where your data goes
Your work stays in databases on your own server. The application makes outbound requests in only these circumstances, none of which carry your formulations:
- Regulatory and product sources — the EU CosIng inventory, the US FDA openFDA drug label API and Open Beauty Facts, queried to build and refresh the ingredient and product catalogs. These requests contain ingredient or product names being looked up, not your formulas.
- An optional local language model, if your operator has enabled it, running on hardware inside your own network. It is used to summarise or widen a search; it is not required, and the core screening and formulation work without it.
If your deployment is configured to send email or process payments, those services are named in the system settings your administrator controls, and only the data needed for those purposes reaches them.
5.How long it is kept
Your work is kept until you delete it or your administrator removes the account. There is no silent expiry.
- Projects and formulations — until deleted by you or by a member of your team.
- Sessions — eight hours, then re-authentication is required.
- Activity log — retained so administrative history stays reviewable; the panel filters to the last year by default.
- Backups — nightly snapshots on a grandfather-father-son rotation, keeping roughly the last week daily, four weeks weekly and six months monthly. Deleted work persists in older snapshots until those age out.
Deactivating an account keeps the record so the activity log still shows who did what, and immediately ends that person's sessions. Deleting an account removes it and its credentials outright.
6.Who can see your work
Work belongs to your team. Members of your team can see and edit your team's projects and screenings; accounts outside it cannot, and this is enforced by the database query rather than by hiding things in the interface.
Within a team, an owner or administrator can set each person's role and adjust individual capabilities — for example allowing someone to manage suppliers without allowing them to delete projects. The operator of the deployment additionally has access to the underlying databases, as anyone administering a server necessarily does.
7.Your rights
You can, at any time:
- See and correct your account details from Settings.
- Export your formulations and screenings to PDF or CSV, in a form that is useful outside this application.
- Delete your projects, individually or entirely.
- Ask your administrator to deactivate or delete your account and its data.
If you are in the EEA or the UK, the GDPR rights of access, rectification, erasure, restriction, portability and objection apply. If you are in California, the CCPA rights of access, deletion and correction apply. There is no right to opt out of sale to exercise, because nothing is sold.
8.Security
Sessions are httpOnly and SameSite-protected. Sign-in attempts are rate limited, and repeated failures from one address block it. Two-factor authentication is available and can be required. Administrative endpoints require an administrator role, not merely a valid session, and can be restricted to specific networks.
Backups are verified rather than assumed: every snapshot is reopened and integrity-checked before it is kept, and one that fails is discarded rather than left to be discovered during a restore.
No system is perfectly secure. If a breach affects your data, your operator is responsible for telling you what happened and what to do about it, within the timescales the law requires.
9.Children
Flula is a professional tool and is not intended for anyone under 18. Accounts are created by administrators or by approved sign-up, not by the public at large.
10.Changes
If this document changes in a way that affects what happens to your data, the change will be announced in the application rather than quietly published. The date at the top always reflects the current version.
Questions about this document?