Privacy — Lexora

IN SHORT

It reads. It never writes.

This policy covers the personal data Lexora collects from you and from your Google Account. Lexora checks the Google Sheets you choose and stores the findings. It reads; it writes only fixes you approve and never keeps a copy of it. It cannot see anything in your Google Drive that you did not pick. We do not sell your data and we do not advertise with it.

Your spreadsheet is read for a check and released, never stored.
Only the files you pick — nothing else in your Drive is visible to us.
We do not sell your data, and we do not advertise with it.

SIGNING IN WITH GOOGLE

Four things, one purpose

If you choose “Continue with Google”, Google tells us four things: your email address, your name, your profile picture and a stable identifier for your Google account. We use them for exactly one purpose — to create your account and let you sign back into it.

Beyond sign-in, Lexora asks for two permissions: access to the files you pick in Google’s picker, and the Sheets permission needed to read cell values and, crucially, the formulas behind them. We deliberately do not ask for the broader Drive permissions that would let Lexora scan your whole Drive. Lexora’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: Google data is used only to provide the checks you asked for, is not used for advertising, is not sold, is not used to train models, and is not read by a person except with your permission to resolve a problem you raised.

WRITING TO YOUR SHEET

Only a fix you approve

Every check is read-only. Your spreadsheet is fetched, examined and released. The only writes are fixes you apply yourself.

The Sheets permission we request (spreadsheets rather than spreadsheets.readonly) is what lets a fix you approve be written to the cell. Nothing is written without you pressing apply on that specific fix; each cell is checked against what the audit saw first, and what was there before is kept so the fix can be undone.

No analytics service, advertising network or third-party tracker runs on Lexora. Our own server runs the application and its database.

WHAT WE STORE

When you connect a spreadsheet

Personal data: your email address, name, profile picture and Google account identifier, so you can sign in.
The refresh token Google issues, encrypted (AES-256-GCM), so Lexora can recheck a sheet without you being present. You can revoke it from your Google Account at any time.
For each spreadsheet you connect: its Google file identifier, its title, your watching settings, and any column meaning you corrected by hand.
The findings of each check, with their evidence: severity, title, explanation, the cell addresses involved, the few values and formulas needed to show the finding, and the derivation rows behind a money figure.
The history of what changed between checks, which findings you dismissed, the fixes you applied (each cell before and after, so they can be undone), and usage counts (checks run, rows read) used to apply plan limits.

WHAT WE NEVER STORE

The lines we do not cross

Your spreadsheet. The grid is read for a check and released. It is not saved, cached or copied.
Anything from your Drive other than the files you picked.
Cell contents in our application logs — logs carry identifiers and rule names only. How we protect what we do hold: every connection to Lexora runs over HTTPS with TLS; the Google refresh token is encrypted with AES-256-GCM before it is written to the database, and its key is held outside the database; the database listens on the application server itself and accepts no connection from the network; access to the server is limited to named Lumerexa staff using individual credentials and two-step verification on the accounts that reach it; passwords are stored as salted scrypt hashes and never in readable form; and the findings for a spreadsheet are deleted with it.
Card numbers. Payment is handled by Lemon Squeezy, and card details never reach us.

PROCESSORS

Who else touches your data

Google — signs you in and serves the spreadsheets you picked, with your authorisation. Google user data stays between you, Google and Lexora: we do not share, transfer or disclose it to anyone else, and none of the processors below receives the contents of your spreadsheets.
Our own server — runs the application and the database. It holds the findings and your settings. No spreadsheet content leaves it except back to you. It is operated by Lumerexa alone; no other company is given access to it.
Resend — delivers the emails you opt into (digests, invitations, report links) on our behalf, as our data processor. It receives the recipient address and the message, which names findings and the cells they point at; never the contents of your spreadsheet and never your Google credentials.
Lemon Squeezy — our merchant of record: takes the payment, issues the invoice and collects tax. It receives your email address and what you bought; card details go to it, never to us. It receives no Google user data and no spreadsheet content.

We do not sell your data, and we do not use it to advertise to you or anyone else. We disclose data outside these processors only where the law requires it, such as a valid legal order, and we transfer it if the business itself is ever transferred, in which case this policy follows it.

YOUR CHOICES

Leave whenever you like

You can revoke Lexora’s access from your Google Account at any time; Lexora loses it at once. To remove a spreadsheet, delete your organisation, or receive a copy of what we hold, email us. Deletion removes the organisation, its spreadsheets, findings, history and credentials, and we confirm when it is done.

Questions about this policy or a data request: support@lumerexa.com.

Privacy policy