Who owns your professional data?

In practice, usually not you. Your employment record sits with employers, your professional profile sits with a platform that sets the terms, and your work history is spread across services you do not control. You can normally export a copy under data-protection law, but a copy is not ownership: the working version — the one other people read and act on — still lives somewhere else.

What does ownership mean here?

Four things, and all four have to hold. You decide what the record contains. You decide who can read it. It goes with you when you leave a job, a platform or a country. And no one can change the terms under which it exists.

A profile fails the last two. An export satisfies the first and, briefly, the third — the file is yours, but nothing reads from it, so it is an archive rather than an identity.

Does GDPR not already solve this?

It solves access, not authority. The EU and UK GDPR give you the right to see your data, correct it, take a portable copy and have it deleted, which matters and is worth using. What they do not give you is a record that other systems read from as the source. That is a design problem, not a legal one.

What does getlandy do differently?

The record is the person’s. getlandy builds and maintains it, but what it holds, where it goes and who sees it are the individual’s decisions — and the whole thing is portable by design, because an identity that cannot leave is a profile with better wording.

The privacy policy sets out how the data is processed, which processors are involved and how to exercise your rights.