Privacy

Waitlist information

When you join the early-access waitlist, Jobby stores your email address and, if you provide them, your name and target role. The signup record also includes the time it was created.

How it is used

This information is used to manage early-access interest, understand which job seekers are interested, and send updates about Jobby. It is not used to make automated employment decisions.

Storage and access

Waitlist records are stored in the Jobby application database. Access should be limited to operating and maintaining the early-access program. No payment information is collected by this site.

Retention and choices

Waitlist information is kept while the early-access program is active or as needed to communicate about Jobby. You may ask to have your waitlist record corrected or removed using the contact method included in Jobby communications.

Cofounder applications and optional research

The AI Engineer / Technical Cofounder opportunity accepts agent-assisted applications and separate, optional research submissions. cofounder_interest=true permits Anmol Desai to review a genuine applicant's materials for the opportunity and contact them using the details supplied. Omitted or false cofounder interest does not permit recruitment review or contact. research_consent=true permits research analysis; false excludes the submission from research analysis and reporting. Declining research does not affect cofounder eligibility. These are agent-supplied declarations of purpose and authorization, not independently verified consent or identity.

Synthetic or consented human material is accepted under the published protocol. Cofounder applications require the current protocol, candidate_type=consented_human, and resume_owner_consent=true, declaring the resume owner's consent to the selected purposes. Synthetic and legacy-protocol submissions are research-only. A consented resume may contain the owner's name, contact details, and other resume information. Minimize unnecessary sensitive data, omit unrelated people's private information, and never submit government IDs, passwords, API keys, access tokens, private keys, medical data, or financial data. Automated checks are best-effort and are not claimed to detect every issue.

Validated submission fields, a bounded HTTP user agent, timestamps, deterministic fingerprints, hashes of the client-generated submission key and withdrawal token, and a deletion deadline may be stored in the isolated study store. IP addresses are processed transiently for abuse prevention and may appear in infrastructure or security logs, but are not stored in the research application database. Uploaded files are not accepted or stored.

Full submission text for either purpose is scheduled for deletion 90 days after receipt. Periodic cleanup runs hourly, at service startup, and before study operations, so physical deletion may complete shortly after the deadline. Raw submissions, applicant names, contact details, resumes, and other private applicant information are never published. Only aggregate, non-identifying findings from research-consented submissions may be retained or reported.

The client must retain its withdrawal token. An accepted response returns a submission ID and deletion deadline but never returns or repeats the token. Send that ID and the original token to the withdrawal endpoint to remove the record for either purpose during the retention window.

Changes

This notice may change as the product and its data practices develop. The effective date above will be updated when material changes are published.