Platform · Security & compliance
Who may read an answer is part of the answer.
An assistant cannot keep a secret it was never told. The moment an answer is handled by a machine, every permission in your organization has to travel with it. Polly keeps ownership, access and history on the record itself, in an environment that never leaves the region you chose.
Settlement threshold for fast-track claims
Claims below €1,000 are settled without a second assessor.
The assistant in the customer portal asked this question today. It did not get this answer, because the record says it may not.
Hosting
Four environments. Your knowledge sits in one of them.
Polly runs fully isolated environments, each independently hosted and managed. Data residency and sovereignty are not a setting you switch on afterwards, they are which environment you are in.
EU
Europe
The default for organizations that answer to a European regulator.
DE
Germany
A separate environment for German public bodies and enterprises that require it.
UK
United Kingdom
A separate environment from the EU one, for organizations that keep their data in the United Kingdom.
US
United States
For organizations whose data may not leave the United States.
Isolated means isolated. The environments do not share a database, a search index or a cache. An answer written in the German environment is not reachable from the other three, and no administrator on our side can move it between them.
Standards we work to
The list your security review starts with.
A knowledge platform sits on top of everything your organization knows. That is why this list is short and specific, and why every line on it is one you can hold us to.
ISO/IEC 27001:2022
Our platform and operations follow the 2022 revision of the international information security standard.
GDPR
Data privacy rights, transparency about processing, and deletion on request.
NIS2
Built for organizations that fall under the directive, and for the suppliers they are now accountable for.
EU AI Act
An assistant answering from a validated source is a different risk profile than one answering from a document store.
WCAG 2.2
Accessible knowledge is part of the same promise. If an answer cannot be read, it was not delivered.
Your identity provider
SSO and RBAC through the directory you already run. Revoke there and access is gone here, in the same minute.
None of this is worth anything if the answer underneath is wrong. That is the other half of the argument, and it lives on governed & validated.
The same answer, from the inside.
Access and history on one record, not in a separate tool.
Who may open this SSO and RBAC
Roles come from your identity provider. Revoke there and it is gone here, in the same minute.
What happened to it v14
Every version is kept. You can show a regulator what the answer was on any given day.
Louwman · one of the organizations running on Polly
Who this is actually for
Somebody is on the phone right now.
She has ninety seconds. The customer wants to know whether the repair covers a replacement device. She finds three answers: one from the intranet, one a colleague pasted into the team chat last spring, and one the assistant just produced with complete confidence. Two of the three are wrong, and nothing on her screen says which two.
So she picks the one that sounds most official, and hopes. Everything on this page exists for that ninety seconds. Not for the audit, not for the dashboard. For her, on that call, with the customer waiting.
Somebody is in the field right now.
He is standing at a street cabinet with a procedure to follow and a work instruction that changed in June. He opens it on his phone, in the app he already uses for the job, and it comes from the same source the people on the phone work from. Same question, same validated answer, whichever end of the organization it is asked from.
Built by people who did that job.
Polly did not start in a category playbook. It started in contact-center projects across Europe in 2015, where the same thing kept happening: good people giving confident answers nobody had checked. We built the fix we kept wishing existed.
Meet the team
