EXA29
— Send data to a third party —
Email Attachment Sealing
A common data leak isn't a hacker — it's that email you sent yesterday with the customer spreadsheet attached.
The problem to solve
A common accidental leak: a spreadsheet of customers, a PDF report, a CSV export — emailed to '[email protected]' or accidentally cc'd to the wrong distribution list. Once sent, you have minimal recall, no field-level control, and limited visibility on what they did with it.
The solution it enables
An email-client extension built on Polymonial would intercept the attachment, derive a schema from the file (CSV columns, spreadsheet headers, PDF form fields) and seal it. The recipient gets a sealed file + their schema-derived viewer reveals only the fields they're authorised for. A recipient without a key for the file sees nothing in it. Field-level access is enforced by keys, not by trust in the recipient's data hygiene.
What it looks like
A regional sales director emails the quarterly customer revenue spreadsheet to the marketing team for a campaign — and accidentally cc's the partner-distribution list, exposing 8,000 customer revenue lines to 47 partners overnight. After Polymonial: the same email goes out, but the spreadsheet is sealed. Marketing's schema-bound viewer unseals revenue + segment. The accidentally-cc'd partner-distribution list holds no key to unseal it — they get an empty viewer with a 'no access' message. The leak that would have been a press incident becomes a non-event.
“A common data leak isn't a hacker. It's that email you sent yesterday.”
Who’s this for you?
We have this problem.
Your organisation needs this for its own data, product or programme of work.
We deliver this for clients.
A consultancy, integrator, service provider, industry programme or technology vendor.