What FL holds, what it never receives, and how each figure stays under your control. This page describes how the product works today.
We never receive your files or your figuresFL runs where your data is: in your Databricks workspace. Our account service holds your company name, the administrator's email, your plan, the payment status and the text of support tickets. Never files, never figures, unless you attach them to a support ticket.
Your identity, your permissionsOn Databricks, FL reads Unity Catalog with the identity of the person signed in. Unity Catalog decides what each person can see; FL adds no access of its own.
The saved analysis is encryptedWhat FL keeps of an analysis is encrypted, with a different key for each analysis. The files FL writes can be read only by their owner.
The AI that reads your files sees labels, never amountsThe AI that reads your files sees the labels of rows and columns with the numbers masked. It never certifies a figure: the engine calculates every one, and the chat only writes the words around figures the engine has already calculated.
It refuses before it guessesA sentence whose figure differs from the engine's is not shown. If a figure cannot be proven with your files, you get no figure: FL says why and asks you.
Sessions and accessEvery request needs a signed-in session. Session cookies are HttpOnly and SameSite Strict; sign-in codes are single-use and expire after ten minutes. Keys and tokens are never printed or written to logs.
What we hold
Two lists, nothing in between.
What our account service holdsCompany name Administrator's email Plan and payment status The text of support tickets
What it never receivesYour files and spreadsheets Your figures and results Your Unity Catalog tables Your Alteryx One datasets
Questions about security?
Open a ticket from inside the app. The details of how we handle personal data are in the privacy policy.