Privacy, in plain language.
Last updated 10 November 2026.
Founding purchases
The site creates an anonymous purchase reference before sending you to checkout. Dodo Payments collects your email and payment details as our merchant of record. After a signed payment notification, we store the customer email and operational references needed to fulfill founding hosted access and resolve payment disputes. We never receive or store your full card details.
Agent usage analytics
Structured usage analytics are enabled by default so we can learn which job sources, ATS flows, and workflow steps work. Analytics events do not include your name, email, phone, résumé content, prompts, answers, browser data, or IP addresses. Error events include only a short sanitized error message, with file paths, your home folder, OS username, and contact details redacted. The analytics retention policy is 24 months; automatic raw-event expiry still requires configuration with PostHog. Run telemetry disable to stop all analytics. Previously collected events are not deleted by opting out.
Private contact store
Separately from analytics events, the agent may store the name and email you explicitly saved in your candidate profile in a private maintainer database tied to your anonymous install ID. We use this only to support you and send product updates, including when you never contact support yourself. This contact record is not written into PostHog event payloads (since version 3.7.3; the relay also strips name and email fields sent by older versions) and is not exposed on public community or job endpoints. Run telemetry contact disable to stop future contact sharing, or telemetry disable to stop both analytics and contact sharing. Opting out does not automatically delete a contact already stored; for deletion requests, open a private contact request through the project's GitHub profile until a dedicated support address is published.
Community statistics
Public community totals contain only aggregate usage counts. They contain no names, profiles, résumés, emails, or raw installation identifiers. Small segments are grouped to reduce re-identification risk.
Job search alerts
If you save a search on the job board, we store only the email address you enter, the filter query (the same filters as the board URL), whether you chose daily or weekly, a confirmation token hash, an unsubscribe token (a random secret that only deletes that saved search), and timestamps for when you subscribed, when you confirmed, when we last sent an alert, and a watermark of the newest role already considered. We send a confirmation email first and send no alerts until you confirm. Each email has a one-click unsubscribe link. Unsubscribing deletes that saved search. Unconfirmed searches are deleted after 7 days. Confirmed searches are kept until you unsubscribe. We do not store your name, résumé, or IP address on the saved search, and the emails we send have no tracking pixels.
Why we store it
To fulfill founding hosted access, support payment disputes, support product users, send product updates, email new roles that match a search you saved, and prevent automated abuse. Rate limiting stores only a pseudonymous identifier derived from a visitor's network address; the application database does not retain the raw address. We do not sell this information.
Your choices
You can unsubscribe from any email. Each saved-search email has an unsubscribe link that deletes that saved search. Use telemetry contact disable or telemetry disable in the CLI for agent contact/analytics controls. For access or deletion requests, open a private contact request through the project's GitHub profile until a dedicated support address is published.
Cloud access
The cloud agent will have separate, explicit controls for candidate profiles and application data before it accepts either.
About the open-source agent: About the project · See how it compares