Private by default while the market is opening.

When you sign in with ChatGPT, the hosting platform provides a stable site-specific user identifier, email address, and sometimes a display name. When you choose Google sign-in, Google provides an account identifier, verified email address, and display name. We do not request Gmail, Drive, or Calendar access. We store the Google identity link and a hash of an expiring OutbidJobs session token; the raw session token stays in a secure, HTTP-only browser cookie. We store your selected persona, profile fields, visibility settings, optional HTTPS booking link and its visibility, role or talent drafts, ranking intent, bounty drafts, account status, checkout amount, mode, and state, Stripe session and payment references, and operational timestamps in the site database. OutbidJobs does not receive or store full payment-card details.

Resume and supported document bytes are stored in private object storage; searchable file metadata, ownership, filename, type, size, and status are stored in the database. Founding-cohort intake separately records name, email, focus, discipline, persona, consent time, and review status. The link-based scheduling integration does not store Google Calendar or Calendly OAuth tokens or event contents.

Direct applications, scout introduction proposals, candidate decisions, response states, notifications, support-ticket messages, and append-only consent receipts are stored with the role, parties, policy version, sharing scope, decision time, and a hash of the consent statement.

For the U.S./Canada launch market, we store the work country on each post and a candidate's yes/no attestation for current legal work authorization and no employer visa sponsorship. We do not ask candidates to submit nationality, birthplace, race, ethnicity, religion, visa type, document number, Form I-9 documents, or SIN through public profiles or listings.

Market-access review stores your selected persona, declared country, state or province, city, and ZIP or postal code. We do not request a street address. We also store a coarse country code supplied by our network provider, the review status, reason code, policy version, and review timestamps. We do not store your raw IP address in the market-access review record.

Account assurance stores an authenticated-email status and domain, verification states and timestamps, a Stripe Identity session reference and result when you choose or are required to complete a step-up check, private risk reason codes, and a versioned audit event. OutbidJobs does not collect a phone number or verification code, and does not store an identity-document image, selfie, government identifier, or Stripe verification report in its database.

The site stores your light/dark preference in local browser storage. Hosting, security, email, and network providers may process IP address, request timing, browser or device information, security signals, and essential anti-abuse cookies to deliver and protect the service.

We do not currently use advertising trackers or sell personal information.

A signed, essential first-party device cookie helps identify unusual multi-account velocity. The database stores a keyed device identifier linked to account IDs and first/last-seen times—not a commercial fingerprint, advertising ID, browser history, or raw IP address. Shared-device signals trigger human review rather than automatic rejection.

A network country signal can be wrong because of VPNs, mobile routing, travel, or provider error. It is used to hold a marketplace action for human review, not to determine nationality, citizenship, or legal work authorization.

• Provide account profiles, private documents, marketplace posts, applications, introductions, notifications, support, ranking intent, and owner moderation.
• Respond to founding-cohort and support requests.
• Operate, secure, debug, and improve the public beta.
• Prevent fraud, spam, abuse, and unauthorized access.
• Meet legal obligations and enforce platform rules.
• Enforce the U.S./Canada work-market scope and match a candidate's selected authorization market to a role.
• Review persona-specific market access, investigate country mismatches, rate-limit high-volume activity, and give users a correction or appeal path.
• Send product communications only where permitted; you may ask us to stop.

We may share information with service providers that host the site, store files, deliver email, secure infrastructure, process sandbox tests or live payments, or help operate the beta, subject to their service terms. Cloudflare may process a Turnstile challenge, and Stripe may receive identity details directly through its hosted Identity flow. Stripe also receives the information needed to operate hosted checkout. OutbidJobs receives only the minimized verification results described above. We may also disclose information when required by law, to protect rights and safety, or in a business transfer.

The read-only public API returns only listings that are both published and public. It excludes email, owner identifiers, resumes, private contacts, storage keys, drafts, payment references, and matched-only or invite-only records. A booking link appears there only when its owner explicitly chooses public booking visibility.

Public results may include the selected work country and a neutral eligibility summary. They do not include nationality, citizenship details, immigration category, visa type, identity documents, or authorization evidence.

Private resume files require the signed-in owner, an authorized owner administrator, or the employer for the exact application or candidate-approved introduction. A scout proposal does not reveal candidate identity, contact information, or documents to the employer until the candidate accepts inside OutbidJobs. Buying visibility never grants private-data access.

We retain member profiles, documents, marketplace records, founding-cohort intake, and support emails only as long as reasonably needed for account service, the pilot, operations, disputes, security, or legal obligations. Reasonable safeguards and server-side ownership checks are used, but no internet system can be guaranteed perfectly secure.

Verification-event records and keyed abuse signals may be kept long enough to investigate account farms, repeated failed challenges, chargebacks, evasion, or appeals. Provider-held identity data follows the selected provider's retention and deletion controls.

The current beta supports direct applications, candidate-gated scout introductions, on-platform notifications, and support threads. Applications are limited to one published public role; introductions are limited to one published public role and one public talent signal. These records are not bulk resume access or an automated hiring decision.

Private verification evidence and payment references must not become public leaderboard or API content. Protected characteristics must not influence search, listing order, or future recommendations.

Work-market and no-sponsorship attestations are used only to enforce the stated launch scope and compatible role matching. They are not a substitute for an employer's legally required employment-eligibility verification.

Signed-in members can download a structured copy of their current profile, posts, document metadata, bounties, rank records, market-access reviews, applications, introductions, notifications, and support threads from Account & Data in the workspace. You may request access, correction, deletion, or additional copies by emailing outbidjobs@gmail.com. We may need to verify your identity before completing a request.

The preview is intended for adults and is not directed to children under 18.