Trust
Who is the controller here?
For the employment data of your team, you are the controller and we process it on your instructions. For the accounts your administrators use, we are the controller. Confusing the two changes who has to answer a data subject request.
Your configuration is the instruction
The roles you define, the permissions you set, the retention you choose and the integrations you authorise are the documented instructions we process under.
Not used to train outside your account
Your people data and your documents are not used to train models made available to anyone else. That is a contractual commitment rather than a preference.
Subprocessors, with notice
The categories are published and the named list comes with the agreement. New ones get notice before they are added, not a changelog entry afterwards.
Trust Centre
The rest of this area.
Security, employee privacy, AI permissions, audit and availability — stated plainly.
Security
Encryption, tenant isolation, production access and credential handling.
Employee privacy
What the people in the system can see, and what is kept from whom.
AI permissions
The assistant inherits your permissions exactly — no more, no less.
Audit trail
Who changed what, who approved it, and who looked at the sensitive things.
Availability & continuity
Backups, recovery and what happens on a bad day.
Run your team with clarity.
From the moment someone joins to the day their responsibilities are handed over, Orglume keeps your people, their work and your organization connected.
Set up from a spreadsheet · Nothing about the AI is metered · [email protected]