Security

This page describes what actually protects your account and your money here, including the parts we have not built yet. A security page that only lists strengths is a marketing page.

Your account

There are no passwords in this system. Not hashed, not encrypted — none exist. Sign-in is Google only, so there is no credential here to steal, guess, reuse from another leak, or reset by social engineering. We never see your Google password.

From Google we receive your name, email address and profile picture. Nothing else, and we cannot read your Gmail, contacts or files.

Your session is a random token stored in our database, not a token you carry. Signing out deletes it, so it stops working immediately — everywhere.

Your money

Balances are not stored as a number. Your balance is the sum of every entry in your wallet history, so the figure on screen and the history behind it cannot disagree. If a payout is ever disputed, it can be reconstructed line by line.

Amounts are held as whole units of the smallest denomination, never as decimals, so no amount drifts by fractions over time.

When a buyer posts a job, the full cost leaves their balance immediately and is held in escrow. It can only move to a worker on approval, or back to the buyer on cancellation. A buyer cannot spend money that is already promised to workers.

Deposits are only credited when the payment provider confirms them to our server directly. Returning to a success page proves nothing — anyone can open a page — so we ask the provider what happened rather than believing the browser.

Fraud and multiple accounts

One Google account is one account here. Each job can be done once per worker, ever, enforced by the database itself and not only by a check that could be raced.

Time on a task is measured from our own record of when you started, never from anything your browser reports. Work submitted implausibly fast, or with proof text already used on another task, is flagged for the buyer with the reason attached.

We record the internet address of each sign-in. If several accounts appear on one connection, everyone on it is told — not blocked. Shared wifi, families, offices and mobile networks all produce this honestly, so it is treated as one signal for a person to weigh, never as proof on its own.

The site itself

• Served only over HTTPS.
• Session cookies are HttpOnly and same-site, so page scripts cannot read them and another site cannot send them.
• Every form that changes anything carries a token tied to your session, so a form on someone else's site cannot act as you.
• Proof screenshots are visible only to the worker, the buyer for that task, and an administrator. They are not public and are not guessable by URL.
• Every administrator action — a suspension, a balance change, a decision on a report — is written to an audit log with who did it and when.

What we have not built

Stated plainly, because you deserve to know what you are relying on.

• No two-factor authentication of our own. Your account is exactly as protected as your Google account, so put two-factor authentication on that.
• No email notifications. Nothing is sent to you; you find out about an approval or a decision by opening the site.
• Payouts are processed by a person. Withdrawals are reviewed and paid by hand, so they are not instant.
• We are not a bank. Money held here is not insured or guaranteed by anyone. Withdraw earnings you are not about to use.

Telling us about a problem

If you find a security problem, please report it through support before telling anyone else, and give us a reasonable chance to fix it. We will not take action against anyone who reports a genuine issue in good faith and does not access other people's data while proving it.

Last updated September 2026.