Security

Last updated 8 September 2026

This page says how the work is actually done. It names no certification, because we would rather tell you what happens than hand you a badge to take on trust.

Where the work runs

Each job runs on a machine created for that job, on infrastructure we operate. The machine is destroyed after the job finishes and a short follow-up window elapses. It is not your laptop, and it is not a copy of your whole office environment.

Your deliverables are kept on our servers so you can download them and follow up on the same files. They are yours. We do not use them to train public models.

When a machine is created

A machine is created after we know who you are - an email code on the web, or the number you texted from. We do not spin up compute for a stranger who typed in the box and walked away.

Who can see a job

You, and the people operating Demandwork in order to do the work. Access is scoped to the job in front of us. A job's page opens only for the person who asked for it, signed in; a screenshot link in an email opens that one file and nothing else. Vendors we use to run the service (sign-in, compute, email, SMS) see only what they need to provide that piece.

What we never ask for

We do not ask for a password or a card number through this channel. If a site needs you signed in, you type it yourself in a handoff, not into a chat with the agent.

Telling us about a weakness

If you find a weakness in something we built for you, write to work@demand.work and say so plainly. You will get a person, and you will get an answer that says what we found and what we did about it.

Contact

Real Time Skills Technologies Inc. (doing business as Demandwork)
95 3rd St, 2nd Floor, San Francisco, CA 94103
work@demand.work
(888) 364-8275

← Demandwork · Privacy · Terms