Issue a role against an identity someone else already verified. It opens what the role needs, and closes the day the role ends.
Free for the first ten people. No card, and no call unless you want one.
Businesses, communities, landlords and public bodies. One account type.
In production across Club TXP, Servicea, Fluxa, SeeYo Soon and Qlavia — and the brands inside each.
Who this is for
You run something with people attached to it.
They need to get into buildings, systems and records. They need to prove who they are before you let them. And when they leave, all of it has to stop. Today that means you keep a copy of their passport and hope somebody remembers to close the door.
Every person you ever onboarded left a passport scan behind. Employees, contractors, tenants, volunteers. Some left years ago. Nobody has looked at the folder since.
It is worth nothing to you and everything to whoever breaches it. And you checked each one by hand, for a document another organisation had already verified that week.
Someone leaves on a Friday. IT disables what it knows about. The door badge, the supplier portal, the folder nobody documented — those stay open until somebody remembers.
A role that ends when the employment ends does not need remembering. It closes because the fact underneath it closed.
Every day an old account stays open is a day you cannot account for. Ten people costs nothing and takes an afternoon.
Open an accountOne account. Two directions.
The same mechanic points two ways. Inward, it gives your team a verified identity tied to a role. Outward, it lets people arrive at your product already verified, without a form.
Before you ask
Four answers a technical buyer needs before the second meeting.
We would rather answer these now than have you find out in month three.
One of the answers is noThen keep it. Entra, Okta and Google Workspace authenticate people you have already hired and already verified. They are good at that.
They cannot verify a stranger. They have no concept of a passport issued by a country. And they have no place for the people who are not on your payroll — contractors, tenants, students, members, visiting trades. SafeQloud does the verifying. Your provider keeps signing people in.
A REST API with a sandbox, and SDKs for Node, Python, PHP and Ruby. Verification is one
call: POST /v1/identity/verify returns whether the person is verified and
what they approved you to see.
Nothing has to be replaced. Most organisations start by adding it to one flow — onboarding, or a door — and leave the rest alone.
In the EU. Identity documents are verified against the issuing authority and the result is held against the person’s own identity, not against your organisation.
You receive answers, never files. There is nothing of theirs on your systems to locate, secure or delete.
A data processing agreement. SafeQloud is a processor under GDPR. The agreement names our sub-processors and the breach notification window. It says what happens to the record if you leave.
Ask and we will send it before you open an account, not after.
Where we are
You are being asked to trust us with identity. The least we can do is say plainly where we have got to.
If none of the noes are blockers for you, the first ten people cost nothing. Send this page to whoever signs it off
Open an accountNot sure which applies to you
Most organisations start on one side and add the other later. One account covers both — you do not choose at sign-up.
Setup
Two minutes, no card. It gives you the dashboard and the API, whichever side you start on.
Inward: issue Work IDs and place codes at the doors and documents that need them. Outward: connect the API — the docs cover every endpoint.
Your people scan. Your customers arrive verified. Everything is logged, governed and revocable from the dashboard.
What it costs
The identity belongs to the person and always will. What is priced is what we do for you — verifying, issuing, carrying consent, and keeping the record.
Work IDs, QR deployment, consent management, dashboard and full API with sandbox. No card required.
Everything above, plus advanced audit logs and role-based access. Scales with people and API volume.
SQ Pay, SQ Check-In and the rest are independent companies built on SafeQloud. Activate from your account; they bill you directly.
What it will never do
You receive a verified answer, not a passport scan. There is no folder to secure, no retention policy to write, and nothing to lose in a breach.
A request states its scope before the person answers it. Their other documents, their other roles and their other relationships are not visible to you.
Consent runs from their side as well as yours. That is not a weakness in your access — it is what makes their data lawful for you to hold at all.
Not your people, not your customers, not your volumes. SafeQloud is paid by the organisations that use it and by nothing else.
Organisation account
Free for the first ten. Two minutes to open. No document you have to keep.
Free for the first ten people. No card, and no call unless you want one.