It touchesbank data. So it'sbuilt like it.
Read-only by design, encrypted in transit, kept separate per company, and traceable to the record. Restraint isn't a feature here - it's the design.
It has no way to touch your systems.
Every connection is granted read-only access at the provider, so there is nothing for Fluxion to write with. Concretely, it cannot:
It can only read
Every connection is granted read-only access at the provider. Fluxion has no way to move money, change a CRM record or send from your mailbox - not by policy, but because it was never given the permission.
Encrypted, and kept apart
The keys to your tools are stored encrypted, and everything travels over an encrypted connection. Each company's data is separate: one workspace can never read another's, even under the same sign-in.
Every figure, traced
Nothing is a black box. Every number Fluxion reports opens onto the records behind it, and every change in your workspace - who did it and when - is written to an audit log you can read.
You decide who sees what
Roles decide which screens each person on your team can open, enforced by the server. Disconnect a tool and Fluxion's access ends at once. What we keep, and for how long, is set out plainly in the Privacy Policy.
What we keep, said plainly.
Leaving ends Fluxion's access to your tools. It does not erase what was already read: we keep it, and use it to improve Fluxion and the models behind it. We never sell it, and no other customer ever sees it.
Read the Privacy Policy →You disconnect a tool
Fluxion's access ends at once and it stops syncing.
What was already read stays in your reports.
You delete a workspace
You have 7 days to change your mind. Then it is closed and nobody can open it.
Fluxion retains the data it holds.
You delete your account
You have 7 days to change your mind. Then your sign-in, sessions and personal connections are removed.
Data in workspaces is retained.
Your plan ends
The workspace stays, and its screens wait until a plan is chosen.
Nothing is removed.