Privacy policy

Your verified email identifies your WorkerSignal account. It is encrypted and linked to an internal identifier; it is not duplicated in analytics events. Keys, OAuth tokens, OTPs, and sessions are stored as irreversible verifiers or encrypted credentials according to their purpose, never inside prompts or URLs.

IP and device data are reduced to pseudonymous fingerprints for security, rate limiting, and abuse prevention. We do not use IP as identity proof or to create a commercial profile.

When an action reaches WorkerSignal, we may record the function, date, verified channel, status, technical identifiers, request and result hashes, credit charged, and balance. This lets us execute credits idempotently, prevent fraud, support users, and demonstrate what our system returned.

This history does not contain the complete search, profile, vacancy, prompt, or result. We may derive only allowed professional categories, such as role family, skill tags, broad region, document kind, or result count, after redaction and bounding.

WorkerSignal can observe actions performed in its browser interface and calls received by its own MCP or API. Clicking “Use in Codex” records only an intent to open it. An OAuth call is recorded as authenticated MCP activity; a dynamically registered client's declared name does not cryptographically prove that it is Codex.

We cannot see and do not collect chats, files, repositories, commands, or actions inside Codex, Claude, or another tool unless they are expressly submitted to a WorkerSignal function.

Recommendation personalization is off by default and requires separate consent. Recommendation or offer emails have another independent control that is also off by default. Accepting the terms, spending credits, or connecting Codex does not enable either permission.

You may withdraw either permission at any time. Withdrawal stops new derivation or communication and removes active commercial interests, without affecting prior lawful processing or the minimum records needed for security, credits, or disputes.

We use Google Analytics 4 to measure public routes, aggregated navigation, and openings to Codex or Claude. We do not send emails, OTPs, keys, prompts, searches, or form content, and query parameters are removed from the measured location.

Analytics and advertising storage remain denied by default through Consent Mode. Advertising signals and ad personalization are disabled; Search Console is used to diagnose crawling, indexing, and organic search performance.

Credit events and completed or replayed functions are retained for up to 180 days. Failures and Codex-open intent are retained for up to 30 days. Derived commercial interests are retained for up to 90 days from the latest observation and are deleted when permission is withdrawn or erased.

Technical worker runs are retained for up to 30 days. An active preference remains while active; proof of activation or withdrawal is retained for up to 24 months. Other data, including encrypted receipts, documents, OTPs, and sessions, follows the specific periods stated in the terms.

Activity, preference, and interest tables are not directly accessible from the browser, MCP, Codex, or a personal key. Workers use bounded functions and cannot alter keys, credits, Hiring, Missions, or source data.

You may request access, correction, export, objection, withdrawal, or deletion through the legal channel. We retain only what law requires or what is needed for fraud, security, accounting, or an active dispute, and will explain the applicable limit.

Email legal@workersignal-ai.com to exercise a right or ask about privacy. Do not include your key, OTP, complete tax documents, or unnecessary third-party information.