AI annotator privacy digest: audit what your work tools can see

For AI annotators, privacy checks are practical risk management. A browser extension may need access to a work site to perform its stated job, but that does not by itself explain what it records, where the record goes, or whether the client permits it.

The information available for this edition does not establish a confirmed platform-wide release, privacy-policy shift or subscription-price change. That makes this a useful month to review the basics rather than mistake product chatter for a policy update. The key questions remain concrete: what can a tool access, what does it retain, and does using it fit the rules for the project?

Permission is not the same as collection

When evaluating a browser extension, read its permission request alongside its data description. Site access tells you where an extension may operate; it does not, by itself, tell you whether it captures page contents, keyboard input, images or only limited activity signals. Look for a plain account of what is recorded and what is explicitly excluded.

Keep scope narrow. Use a work tool only on websites you have deliberately approved, and check whether the project’s terms allow it there. A client rule against third-party extensions takes precedence over a personal preference for better records. Do not install a tracker to get around monitoring requirements or other controls.

Our earlier guide to separating permitted platform sessions by browser profile covers one useful boundary: keeping work contexts distinct does not require collecting the contents of the work itself.

Monitoring and personal records serve different jobs

Contractors often have to distinguish a client’s monitoring system from their own administrative log. A platform may require a specific timer or monitoring tool. A personal record can help a contractor track time, tasks and estimated earnings across separate work sources, but it is not a substitute for the required system and does not prove that a client’s records are wrong.

For risk-averse workers, “no screenshots” is worth checking, but it is not a complete privacy review. Ask whether keystrokes, recordings, task text, page addresses or credentials are collected. Check how the tool handles account data and how you can remove records. If an NDA or project rule is unclear about external tools, ask the client before connecting one. A tool’s privacy design cannot settle a contract question.

What RaterSidekick says it records

RaterSidekick is a Chrome extension for tracking work sessions, tasks and estimated earnings across AI contractor platforms. The company says it does not capture screenshots, keystrokes, screen recordings or task content. It detects task completion through a keyboard shortcut selected by the user and runs only on websites the user designates.

That description gives a contractor specific points to verify against a project’s rules: the extension is active only on chosen sites, and the completion signal is a selected shortcut. RaterSidekick says it records work timing and task counts rather than the content of prompts, answers, ratings or comments. No personal tracker should be treated as automatically approved for every client environment.

Its Pay Checker compares a user’s records with platform reports. Users can also import history from spreadsheets, Clockify or platform exports. Imported history is a different source from sessions tracked by the extension, so keep the origin of each record clear when reviewing totals. For a step-by-step approach to investigating discrepancies, see our guide to comparing a work log with platform pay reports.

Pricing and a useful monthly check

RaterSidekick offers monthly and annual subscription options and a seven-day free trial with no credit card required. Its Pro plan includes unlimited project profiles, work history, Pay Checker and Evidence Packs. No subscription price or pricing change is established in the information available for this digest, so workers should check the current plan terms before deciding whether the tool fits their budget.

A short monthly review can catch avoidable problems: confirm that each extension remains allowed for the projects where it runs; revisit site permissions; keep personal records separate from client-required logs; and compare recorded totals with platform reports before a dispute deadline. Save only what you need to support your own administration. Privacy-minded work tracking is not about collecting everything. It is about knowing what is collected, why it is needed and whether you are permitted to collect it at all.