Legal
Privacy
Last reviewed 20 September 2026
Legal
Everything described below is behaviour this platform implements today, and each statement is checkable against the system that performs it. What is still with legal counsel is the formal instrument itself, the name of the operating legal entity, and the statutory periods for which records must be kept. Those three are marked where they appear rather than invented.
1.In short
Almost everything we hold about you is something you typed, uploaded or did on this platform. There is no quiet collection behind that.
- We do not sell personal data, and we share none of it for anyone else's marketing.
- There is no advertising network, no third-party tracker and no profiling of you for ads anywhere on this site.
- Our own usage measurement is de-identified. Your address and browser string are used to derive an anonymous daily hash and are then discarded; neither is written down, and no page view is ever linked to your account.
- We honour Do Not Track and Global Privacy Control. If your browser sends either signal, nothing is measured at all.
- Documents you upload are private by default and reachable only by the people a project or a review makes responsible for them.
- We do not watch how you work. There are no screenshots, no keystroke or mouse capture, and no time-monitoring software.
- Deleting your account anonymises you. A small set of shared records survives because they are also the other party's record — “What deleting your account actually does” lists exactly which, and why.
2.Who and what this covers
This notice covers the WorkExp platform: the website and every feature reached through it, for Candidates, for Organizations, and for visitors who never create an account.
It covers the decisions we make about your information. It does not cover what another user does with information you chose to show them — an Organization that reads your profile is responsible for what it then does with what it read.
The legal entity that operates WorkExp, its registered address and its named data protection contact are being settled before public launch, and will appear in this section. Until then every request described under “Your rights” reaches us through Support, and we answer it.
3.What we collect
Grouped by where it comes from, because that is what determines how much choice you have over it.
Given by you
- Your account
- An email address, a password stored only as a one-way hash — the password itself is never held — the role you chose, and your language.
- Signing in with Google or LinkedIn
- If you use a provider, it tells us your email address, your name, and — when it sends one — a link to your profile picture, which we keep on your account. That is the whole of what we receive. Your password for that account never reaches us, and we tell the provider nothing about what you do here.
- A Candidate profile
- Full name and form of address, headline, biography, country and city, languages, professional titles and skills, education you list, and the work samples you publish with their links. There is no second email address to give: your account address is the one we use. A phone number is optional, and both it and your email stay private unless you change that yourself, each one separately.
- An Organization profile
- The organization's name, type, field, stage and size, description, website and social link, country and city, a contact name, email and phone, and a commercial registration number if you choose to give one. The contact email and phone are private unless you change that.
- Photographs and logos
- Your profile photo and an organization's logo are stored re-encoded from decoded pixels, which removes the metadata an image carries — including GPS coordinates people upload without knowing — and for those two the file you selected is never stored. Other images you upload, such as a work sample or a file sent in a project conversation, are kept as you sent them, because they are your work and re-encoding would damage it.
- Credential documents
- What you submit for verification: a certificate, a transcript, a letter. Stored privately, never made public, and readable only by you and by the administrators who review credentials.
- A CV, if you use one to fill in your profile
- Read in memory to produce the fields you are then shown for review, and discarded. The file is never written to storage and no copy is kept. Only what you accept becomes part of your profile.
- Project content
- Project descriptions and applications, messages and their attachments, deliverables and work samples, expense requests — what is needed, how many, what one costs — and the quotations, invoices or receipts attached to them.
- Support requests
- What you write to us, and anything you attach to it.
Created by using the platform
- Records another party relies on
- Applications, the project agreement and each side's acceptance of it, scope-change requests, expense decisions, reviews and issued certificates. These are shared records, not only yours, which is why deleting an account treats them differently from your profile.
- Administrative decisions
- Every decision an administrator takes about an account, a credential, an organization or a project is written to an audit record with who took it and when.
- Sign-in protection
- Failed sign-in attempts are counted so an account cannot be attacked by guessing. What is stored is a one-way hash of the identifier and a counter — never your address or your email address in readable form.
- Notifications
- The notifications we generated for you, and whether you have opened them.
- How often your profile was seen
- A count, per day, of how many times your profile was opened and how many times it came back in someone's search. This half is a count only — it records whose profile was seen, never who looked. The totals are shown to you alone, on your own profile, and only while you hold a Gold subscription. Opening your own profile is not counted.
- Who viewed your profile
- When you open someone's profile, a record of that visit is written for them. What it contains is decided by your own setting, which you change on your profile page under “How you appear when you view someone”. If you chose to be named — the setting a new account starts on — it stores your account so they can be shown your name and headline. If you chose your field only, it stores a short description of what you do, copied at that moment, and no link to your account. If you chose to be hidden, it stores a timestamp and nothing else: there is no identity in that record to disclose later, to anyone, including us. The record also keeps how visible YOU were at that same moment, and a name is shown only where both sides were open when the visit happened — so nobody can browse privately and then reveal names afterwards by changing a setting, and paying for Gold does not change that either. Opening your own profile is not recorded, and neither is a visit by someone who is not signed in.
Measured, in de-identified form, and only if you agree
- What a page view records
- The route you were on with the language prefix removed and the query string dropped, which of the two site languages you were reading, a coarse device, browser and operating-system class, the host name of an external site that referred you, the time, a session identifier that lapses after thirty minutes without a page view, and a visitor hash that changes daily. If you complete one of a short list of milestones — registering, publishing a project, sending an application, finishing a CV import — the name of that milestone is recorded too.
- What it never records
- Your address and your browser string are used to derive the daily hash and are then discarded; neither is written down. No page view carries an account, a name, or anything you typed into a form. Record identifiers in the address are replaced with a placeholder, though a readable code that is part of an address — a certificate number, for instance — is kept as part of the route. Administrator pages are excluded entirely, as are bots and browser prefetches.
- How to change your mind
- Analytics preferences in the site footer reopens the choice at any time, and declining stops collection immediately. If your browser sends Do Not Track or Global Privacy Control we do not ask and do not collect.
What we deliberately do not collect
- Payment card details
- We never see them. No payment processor is connected to this platform today, and no card number ever reaches us.
- Identity documents and biometrics
- No photograph of an identity card, no selfie, no liveness check, and no face or fingerprint data.
- Precise location
- We never ask your device where it is, and we do not work it out from your connection. Your country is always chosen from a list. Your city is chosen from a list where we have data for your country, and typed by you where we do not — a city you type is stored and shown exactly as you wrote it.
- How you work
- No screenshots, no keystroke or mouse capture, no time tracking, and no activity monitoring of any kind. Work is judged by what is delivered, not by watching the person doing it.
- Your contacts and your calendar
- We never read them, and never ask for access to them.
- Training data for AI models
- Your content, your messages and your files are never used to train a model. Reading an uploaded CV is done by deterministic rules on our own server. An optional assist that would send the text of a CV to an external model exists in the system and is switched off; if it is ever turned on, this notice will say so first and it will be your choice.
4.Why we hold it, and on what basis
Every purpose below is one of the reasons anything is collected at all. There is no further use behind them.
- To give you the account and the features you asked for
- Necessary to provide the service you signed up for.
- To show your profile to Organizations looking for someone
- Why the platform exists, and the reason your profile is visible once you register. Your own choice governs it: you can hide the profile at any time, and the contact details on it are private unless you decide otherwise.
- To let a project's two parties work together
- Necessary for the agreement both sides accepted before the work began.
- To review credentials and classify organizations
- Your submission, plus our interest in a platform where a claim of experience means something.
- To keep the platform safe
- Malware scanning, sign-in rate limits, moderation of published projects, and the audit record. Our legitimate interest in protecting users, and in places a legal obligation.
- To answer you
- Support requests, and the service messages an account cannot operate without — security alerts, verification, and notices about your own account. These are not marketing and cannot be turned off.
- To measure usage in de-identified form
- Your consent, given in the banner and withdrawable from the footer at any time.
- To meet legal obligations
- Where a law that applies to us requires a record to be kept or produced.
5.Who can see what
Visibility on this platform is decided by role and by relationship, server-side, on every request — never by hiding a control in the interface.
- You always see everything of your own.
- Your profile is visible from the moment you register, so an Organization can find you — there is no separate publishing step. You can hide it at any time from your profile page, which removes it from talent search and makes the page unreachable immediately. Search engines are a separate switch and are off unless you turn them on. Your contact email address and your phone number are controlled separately again, and each stays private unless you change it.
- A project's two parties see that project's content, messages and files, and so does a Supervisor either of them invites. Nobody else does, except that an administrator handling a report or a dispute can read what it concerns — and that is written to the audit record.
- A Supervisor invited to a project follows progress and decisions, and can open the files shared in the project conversation. They never open a delivered work file, the evidence attached to an expense request, or a credential document, and they can never write anything to the project.
- Reviewers and administrators see what the decision in front of them requires, and every decision they take is written to the audit record with their identity.
- A certificate can be checked by anyone holding its number, without signing in. It shows whether it is still valid, your name and the organization's as they stood on the day it was issued, the project's title and dates, and the skills recorded then. Your name links to your profile, which opens only if your profile is visible.
- Your profile is offered to search engines only if you turned that on. It is off unless you chose it, and hiding your profile removes it from them either way.
- A private work sample is unreachable by anyone else — not the page, not the cover image, not the files behind it.
- When you open someone's profile, they may be shown that you did. Your own setting decides whether that appears as your name, as your field alone, or as an unattributed count — and the same setting, as it stood at that moment, decides how much you are shown about the people who open yours.
When you publish something, you are publishing it. Other people can read, copy and keep what you made public, and we cannot undo that for you. Publish accordingly.
7.Where it is processed
The server that runs WorkExp and the storage that holds uploaded files are both in Frankfurt, Germany. The managed database and the email service run on their own providers' infrastructure.
This means personal data is processed outside the Kingdom of Saudi Arabia. We state that plainly rather than leaving it to be inferred: if that matters to you, it should matter before you upload, not afterwards.
Everything in transit is encrypted. The site is served over HTTPS and instructs browsers to refuse any downgrade for a year; the database connection requires TLS with channel binding; file links are signed and short-lived, and authorisation is re-checked each time one is used.
8.How long we keep it
While your account exists we keep your account, your profile and your project history, because that is the service.
- De-identified usage measurement
- 400 days by default, then deleted. This is a technical bound on telemetry rather than a legal period, and it is stated on the page where the figures are read.
- Sign-in protection counters
- A counter holds a one-way hash of the identifier and stops counting once its window has passed. The rows are removed by a sweep that runs opportunistically rather than on a timer, so a spent counter can sit for a while before it is cleared. Nothing about a successful sign-in is kept for this purpose.
- Uploaded files that fail scanning
- A file the scanner condemns while it is being uploaded is refused before it reaches storage, so nothing is kept. A file already stored that a later rescan condemns stops being downloadable immediately and is never served again, though its bytes are retained rather than erased.
- Who viewed your profile
- 90 days, then deleted. Deliberately shorter than anything else here: knowing who looked at you recently is useful, and a permanent record of who read whom is not something this platform should hold. Deletion is by date and runs from the platform itself, not on request — the rows for your profile are cleared whenever this panel is opened, and a sweep removes the rest.
Statutory retention periods for the historical records listed below — how long an audit entry, an agreement acceptance or a billing record must be kept — are part of the legal review that is not finished. Nothing is purged on a timer today, which is the safer default. We will not print a plausible-sounding number here. When real periods are set, they will appear in this section.
9.What deleting your account actually does
You can delete your account yourself, from the account page. Deletion here means anonymisation: the account stops authenticating, disappears from everywhere it could be found, and loses the information that identifies you.
- Your email address is replaced with an unusable placeholder, your name and picture are removed from the account, your profile name becomes “Deleted Candidate” or “Deleted Organization”, and the stored image file itself is deleted.
- Your password is removed, so signing in stops working at once. Any session already open ends on its next request rather than surviving until it expires.
- Profile fields are cleared: headline, biography, the separate parts of your name, country and city, phone number, and for an Organization its description, website, contact details and commercial registration number. Your profile is then taken out of public view, out of talent search and out of search engines.
- The credential documents you uploaded are deleted from storage.
What survives is the part that is also somebody else's record, or that someone else is entitled to rely on:
- Project history, the agreement and each side's acceptance of it — a completed project does not stop having happened because one participant later left.
- Issued certificates, in full, showing the names as they stood on the day of issue. A certificate that changed after issue would be worthless to the person holding it.
- The audit record, including the entry recording your own deletion, so that the deletion itself can be verified later.
- Billing history for any subscription, and the fact that a credential was reviewed and by whom — without the document itself.
Projects an anonymised Organization had already published stay in public discovery under the anonymised name, as project history. Its profile page becomes unreachable.
10.Your rights, and how to use them
Under the Saudi Personal Data Protection Law, and under comparable laws elsewhere, you have the right to be told what is collected and why, to see it, to receive a copy in a readable form, to have it corrected or completed, and to ask for it to be destroyed when it is no longer needed for what it was collected for.
- See and correct
- Your profile and account pages show what we hold and let you change it directly. Nothing about you is edited by us behind your back.
- Receive a copy
- Ask Support and we will give you a copy of your personal data in a readable format. There is no self-service export button yet; the request is answered by a person until there is.
- Ask for destruction
- The account page deletes your account, with the effects set out under “What deleting your account actually does”. Where a record is retained because another party relies on it, we say so rather than quietly keeping it.
- Withdraw consent
- Analytics preferences in the footer withdraws analytics consent. Unpublishing your profile withdraws it from public view. “How you appear when you view someone”, on your profile page, stops future visits of yours being attributed to you; it does not change visits already recorded, and it does not need to, because a visit recorded while you were hidden never held your identity in the first place.
- Object, or complain
- Write to us through Support and tell us what is wrong. If our answer does not satisfy you, you may complain to the competent supervisory authority where you are.
We answer requests without charge. We may need to confirm that a request really comes from you before acting on it, and we will ask for no more than that confirmation needs.
11.How it is protected
What is actually in place, rather than a claim of general diligence:
- Passwords are stored only as one-way hashes; we could not tell you your own password if you asked.
- Every request re-checks the account's live status, so a suspended or deleted account loses its session immediately rather than at expiry.
- Every upload is checked for what it really is, size-limited, and scanned for malware before it is stored. A file that fails, or that the scanner could not judge, is never downloadable.
- Images are re-encoded, which removes embedded metadata and neutralises anything hidden in the original file.
- Storage keys are random, so files cannot be found by guessing. Download links are signed, short-lived, and re-check your authorisation every time they are used.
- Authorisation is re-derived on the server for every action. Hiding a button is never how access is restricted.
- The administrative interface writes every decision to an audit record that cannot be edited afterwards.
No system is perfectly secure, and we will not claim this one is. If a breach affects your personal data we will notify the competent authority and the people affected without undue delay, and we will tell you what actually happened rather than the least alarming version of it.
13.Children
WorkExp is for adults: holding an account requires being 18 or older, which the terms of use state. We do not ask for a date of birth and do not verify age, which means we cannot identify a child's account on our own.
If you believe a child's personal data is on this platform, tell Support and we will remove it and close the account.
14.Changes to this notice
When what we do changes, this notice changes with it — before the change takes effect where that is possible, and the review date at the top moves. If a change materially affects your information we will tell you rather than rely on you noticing.
Questions about any of this can go to our support team. Contact