Most platforms collect your data and ask you to trust them with it. SafeQloud asks something different. It asks you to stay in control of it — and gives organisations the infrastructure to work that way without building it themselves.
The problem
Every platform you sign up to takes a piece of your identity. Most store it indefinitely. Few tell you what they do with it. None make it easy to take back.
Your name, address, payment details, employment history — spread across services you used once, twice, or have forgotten entirely. No single view. No single control.
You clicked agree. You had no real choice. It was not specific, not revocable, and not visible afterwards. That is not consent.
You have the right to be deleted. In practice that means finding a privacy address, writing, waiting, and hoping. It should be a button.
What we believe
Platforms need your identity in order to serve you. They do not own it.
SafeQloud keeps identity with its source — the person — and lets platforms request access rather than assume it.
A consent that cannot be withdrawn is not consent. It is a transaction you did not negotiate.
Every agreement made through SafeQloud is logged, visible to both sides, and cancellable at any point by either of them.
SafeQloud is not built on top of a data business. The product exists to return control to individuals, not to accumulate data as an asset.
That is a structural choice, not a policy statement. Organisations pay for what we do for them. Individuals never do, and there is nothing for us to sell if they did not.
Good data practice is expensive to build and hard to prove. Most organisations that get it wrong were not careless — there was simply no way to do it properly.
SafeQloud is that way, bought rather than built.
Who we are
SafeQloud is not a product people choose between. It sits underneath other companies and does one thing for all of them: it establishes that a person is who they say they are, and carries the record of what they agreed to.
Independent companies with their own pricing, their own regulators and their own customers. Payments, check-in, HR, finance, hotels, car rental, healthcare. None of them is SafeQloud.
Independent companies, separately held, sharing a founder. Each operates a group of those brands in its own market, on one shared identity.
Four identity types issued against a verified person, six APIs, and the consent record that both sides read and neither can alter. Everything above asks it for something. It asks nothing of them except that they state what they want before the person answers.
How it is operated
Everything above is structural. Each boundary exists because collapsing it would make the layer underneath harder to trust.
Verification against issuing authorities, the four identity types, and the consent record. It never holds the documents on a brand's behalf, and it is paid by organisations rather than by what it knows about anyone.
One shared institutional operator across SafeQloud, Club TXP and the independent brands. Every support channel, response workflow and formal correspondence runs through it, so there is one record of what was asked and what was answered.
A payments brand carries payment regulation. A healthcare brand carries its own. Folding them inward would pull every obligation onto the identity layer, and an identity layer that is also a payments business is harder for a bank to accept.
Individuals do not pay, at any tier, ever. It is not a promotion. If the person were the revenue, every other principle on this page would eventually be negotiable.
Where we are
A page of principles is easy to write. Here is the part that is harder, and the reason you can believe the rest.
If that is you, the personal account is free and always will be. If you run an organisation, the first ten people cost nothing.