Make any field secure.
For bank accounts, card numbers and national identifiers: switch a field to secure, and its values are encrypted with a key of their own, apart from everything that searches or computes. Cells show a mask or dots, and a value in full takes a reveal — recorded, every time.
Coming soon. Talk to us to hear when it opens for your workspace — or to tell us how you would use it.Talk to us
Sensitive values, encrypted and masked
- 1
Switch a field to secure
One switch on a text, number or date field: every value is encrypted where it is stored, and the copies the app kept of them — undo history, source highlights — are cleared.
- 2
Choose what cells show
The value, a mask that keeps a few characters — never more than half — or only dots. The mask can follow the field's input mask: 756.••••.••••.97.
- 3
Reveal on purpose, on record
Choose who may reveal a value: everyone who sees the row, those who can edit the table, or owners and admins only. Each reveal writes a line to the audit log; support staff working in your workspace never see one.
Encrypted means unreadable — to filters too.
Nothing in the app can read a secure value, so whatever works by reading values stops on that field. Keep it for the identifiers you look up by equality — not for the amounts you add up.
Still works
- Shown in the grid, row details, forms and boards — as the value, a mask or dots
- Typed, pasted, imported and filled by the AI — encrypted as it is written
- Filters asking whether it is empty and, on a text field, whether it equals a value
- Matching on the exact value: the IBAN on an invoice still finds its supplier
- Lookups from linked rows, undo and redo, duplicated and merged rows
Stops working
- Search — in the table and across the workspace
- Sorting and grouping by the field
- Every other filter: contains, starts with, ranges, comparisons with another field
- Totals other than the row count, rollups, formulas and if-then-else values
- Folders and file names built from the field
What you get
Encrypt a field's values with a key of their own: cells show a mask, a full value takes a recorded reveal, and search and most filters stop. Coming soon.
Unreadable in the database
The field's values are stored encrypted, apart from the tables that search and compute: a database dump or a later backup shows ciphertext where the numbers were.
Masks that keep their shape
Separators and fixed characters stay where they are, so a masked value still reads as what it is: CHE-•••.•••.789, •••• •••• •••• 1234.
Still filled by the AI
Extraction fills a secure field like any other: the value is encrypted as it is written, and no source highlight or stored model answer keeps it.
Document text too
A table can keep the text read from its documents encrypted as well. Its files are then found by name and by their fields, no longer by the words inside.
Platform features work around the whole cycle: they secure, explain and set up every stage, from the moment a document arrives to the action it calls for.
Used in
Frequently asked questions
Why can't I filter or sort on a secure field?
Because the database can't compare what it can't read. A filter can still ask whether a cell is empty and, on a text field, whether it equals a value you type — compared by a keyed fingerprint, never in clear. Search, sorts, ranges and totals other than the count stop.
Is the document a value came from encrypted too?
Your original files are already encrypted before they are stored. The text read from them stays readable in your workspace so it can be searched — unless the table keeps its document text encrypted too. A secure field protects the value in its table, not the page it was read from.
Who can see a secure value?
Everyone who sees the field sees what its cells show: the value, the mask or dots. Only the people you allow can reveal one in full, and each reveal is recorded in the audit log.
