Contributor Privacy Notice

This is for you if you contribute, review or provide expertise through Largwit, whoever engaged you and whether you came through a talent platform, an agency or directly.

Two organizations hold data about you and it is worth knowing which is which.

The organization you work for decides that the work happens, sets the standard it is held to, and decides who is on a project. For most of what follows they are the controller: they answer for it, and they are your first point of contact.

Largwit provides the platform that work runs on. For most of your data we are a processor acting on that organization’s instructions. For a small amount (your login and the security records attached to it) we are the controller, because we decide what is needed to keep an account safe.

We do not sell your data. We do not use it to train models. We do not advertise to you.

Who you are. Your name, the email address you signed up with, the organizations you belong to and the role you hold in each.

Access and security. A hashed password, never the password itself. Whether you have multi-factor authentication on, your active sessions, and a record of sign-in attempts including failures. Failed attempts are kept because refusing an address after repeated failures is how an account survives somebody guessing at it.

Your work. The items you claimed, what you submitted, when you started and finished, whether work was approved or sent back, and the reason given when it was sent back.

Quality and standing. The outcome of reviews of your work, whether you meet a project’s qualification bar, and your standing in an organization: active, paused pending a review, or withdrawn, with the reason recorded.

Availability. Your timezone and the hours you have said you work, if you have set them. You set these, and you can change them.

Technical records. Ordinary server logs, including IP address and device type, kept to operate the service securely.

We do not use webcam monitoring, keystroke logging or screen recording. We do not track you across other websites.

• To give you work you are eligible for. Matching what a project needs against the roles and qualifications you hold.
• To pay and account for work. A record of what was done, by whom, and when.
• To run quality. Review outcomes are how a customer knows the output is sound, and how you find out something needs fixing.
• To keep your account and the data safe. Authentication, session control and the audit trail.
• To meet legal obligations where they apply.

Where GDPR or UK GDPR applies, the legal basis is performance of a contract for the work records, our or the organization’s legitimate interests for security and quality, and legal obligation where one exists. Where we rely on legitimate interests you can object; see section 7.

The organization you work for. Its project managers and administrators can see your work, your review outcomes and your standing, within that organization only.

Reviewers on your projects. They see the work, and who submitted it.

Other organizations you belong to: no. If you work for two organizations through Largwit, neither can see your work or standing in the other. Your hours in one are not carried into the other. They are separate engagements and the platform keeps them that way.

The end client. Clients are shown progress, quality and delivery status. Internal workforce records, including who is paused and why, are not part of what a client sees.

Largwit staff. Only where needed to resolve a fault or a security incident, and it is logged.

Sub-processors. The short list at largwit.com/subprocessors.

Work records and their review history are kept for as long as the organization needs them for the engagement, and then on their retention schedule, which they set, because it is their record.

Sign-in attempt records are short-lived; they exist to slow down an attack in progress, not to build a history.

If you leave an organization, your membership is marked as ended rather than erased, because the work you did still has to add up for the customer and for anyone auditing it later. Your account itself is yours and outlives any one engagement.

Automated checks run over submitted work and can flag it for a person to look at. A flag is not a decision.

Decisions that affect your standing (work sent back, a qualification withdrawn, a membership paused) are made by people in the organization you work for, and the reason is recorded. If you think one is wrong, ask them, and the record is there to be checked.

Depending on where you live, you may have the right to ask for a copy of your data, to correct it, to delete it, to restrict or object to how it is used, and to get it in a portable form. You can also complain to your data protection regulator.

Ask the organization you work for first. For your work records and your standing they hold the decision, and going to them is the faster route.

If they do not respond, or your question is about your login rather than your work, write to hello@largwit.com. If you contact us about something an organization controls, we pass it to them without undue delay and tell you we have.

Some of this you can do yourself in the product: change your details and availability, sign out other sessions, turn on multi-factor authentication, and turn off notification email.

The platform runs in the region named in the sub-processor list. Where data moves out of the EEA, the UK or Switzerland, standard contractual clauses cover the transfer.

If this notice changes in a way that matters to you, we will say so rather than quietly changing the date. Questions: hello@largwit.com.