ProfOS is designed around candidate ownership, controlled visibility, and review-first workflows. The platform should help people organize professional information without exposing more than they chose to share.
What ProfOS stores
ProfOS stores account details, profile information, privacy settings, evidence records, credentials, opportunity CRM entries, packets, and other workspace data you choose to create. Candidate records are private by default until you change visibility.
What ApplyPilot stores
ApplyPilot is local-first. Its profile data, saved answers, settings, and learned corrections stay in the browser's local extension storage unless you export or import them yourself. Core ApplyPilot use does not require cloud sync.
Connected Evidence
When you connect outside sources such as GitHub, ORCID, RSS, arXiv, Crossref, Zenodo, or manual URLs, imported items go into a private review inbox first. They are not published automatically.
Visibility and sharing
You control whether profile sections, contact details, goals, references, credentials, timeline items, and capability assessments are private, public, employer-visible, or limited to a secret packet link.
Payments and employer accounts
Employer and recruiter plans use Stripe for billing workflows. ProfOS should receive only the billing metadata needed to manage subscriptions, plan limits, and support; card handling stays with Stripe.
Support and account requests
For support, privacy questions, or account deletion issues, contact sreid1118@gmail.com. Account deletion removes platform-stored workspace data associated with that account, subject to any necessary audit or billing retention.
This page describes the current product behavior in the live platform. It is not legal advice, and it should still receive formal legal review before a larger commercial rollout.