PRIVACY & RIGHTS

How privacy is
enforced — at the cell.

PII is tagged at the cell, controlled per role, and never crosses the residency boundary. Compliance is not a policy document — it is how the spreadsheet runs.

Data minimisation — built into the workbook

Tag PII once. Enforce it everywhere.

Mark customer.bsn or customer.iban as PII. Exports redact. Logs scrub. API responses gate on consent.

WHAT CHANGES

✓ No more PII in CSV exports
✓ No more PII in shared workbooks
✓ No more PII in support tickets

Residency — you decide where it lives

HOSTED

Where you want it.

EU-hosted by default. Other regions on request. No surprises in the sub-processor chain.

ON-PREM

Or inside your own walls.

Run Excelerant inside your environment. Your servers, your keys, your auditors. The data never leaves.

The point isn't the topology — it's that you retain control of your data. Always.

Sharing without spilling

THE PROBLEM YOU ACTUALLY HAVE

Someone needs "just the numbers" — so they download the workbook, send it on email, and the customer's BSN is now in three inboxes.

INSIDE

Customer name, BSN, IBAN. PII tagged at the cell.

→

DOWNLOADED

PII cells redacted automatically — based on who's downloading.

Share the workbook through the platform and the file that leaves matches the recipient's role. The original stays intact. No more accidental email leaks. No more spreadsheets going feral with personal data attached. AVG compliance is no longer a posture — it's a property of how the spreadsheet runs.