Privacy Policy
Last updated: May 21, 2026
Who we are
HIRED-OS is an AI-assisted job-search workspace operated by an individual at hired-os.com. This policy describes what data we collect, how we use it, and what choices you have.
Data we collect
- Account information — email and authentication identifiers provided through our auth provider (Clerk).
- Content you upload — resumes, job descriptions, career stories, and any other text you submit to use the AI features.
- Generated artifacts — tailored resumes, cover letters, outreach drafts, interview prep packets, and mock interview transcripts produced by the service.
- LinkedIn data export (optional) — if you choose to upload the ZIP from LinkedIn’s “Get a copy of your data” export, we parse
messages.csv(outbound only — to build your voice profile) andConnections.csv(to populate your address book for warm-intro suggestions). The original ZIP is not retained; only the parsed message bodies + connection rows are stored. You can revoke this by deleting your account. - Run metadata — cost, status, latency, and timestamps for each AI run, used for observability and to show you your usage.
- Google OAuth tokens — if you connect Google, we store the OAuth refresh token needed to use the Google features you opted into. We request only four scopes:
auth/documents— create and update Google Docs containing the resume content you choose to export.auth/drive.file— file-scoped Drive access limited to documents HIRED-OS itself creates or that you explicitly open through HIRED-OS. We never read the rest of your Drive.auth/calendar.events.readonly— read-only access to upcoming calendar events, used to surface interview slots in the Prep tab so we can pre-generate prep packets for them. We never create, modify, or delete calendar events.auth/gmail.readonly— read-only access to your Gmail used only to (a) identify recruitment-related threads (recruiter outreach, application updates, interview scheduling, offers and rejections) so we can surface them in the drafts queue, and (b) read those threads to draft a candidate response in your voice. We never send, delete, modify, or label any email. HIRED-OS does not requestgmail.send,gmail.compose, orgmail.modify; drafted responses are shown to you for copy-paste into Gmail manually.
How we use your data
We use your data solely to operate the service: authenticate you, run the AI features you request, store your work between sessions, and show you cost + usage information. We do not sell your data, share it with advertisers, or use it to train third-party AI models.
Who we share data with
- Anthropic — content you submit is sent to Anthropic's Claude API to produce AI outputs. Anthropic does not train on API inputs per their commercial terms.
- Voyage AI — text snippets are sent to Voyage for embedding generation used in retrieval/search features.
- Clerk — handles authentication on our behalf.
- Google — if you connect Google, we call the Google Docs, Drive, Calendar, and Gmail APIs to (a) create and update the resume documents you choose to export (Docs + Drive,
drive.file-scoped), (b) read upcoming events so we can pre-generate interview-prep packets (Calendar,calendar.events.readonly), and (c) read recruitment-related email threads so we can draft replies in your voice (Gmail,gmail.readonly). We use only the scopes listed above; we never read non-recruitment files in your Drive, modify your Calendar, or send, modify, or delete email.
We do not share data with any other third parties.
Google API Services User Data Policy — Limited Use
HIRED-OS’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, data obtained from Google APIs — Docs / Drive content for files you create or open through HIRED-OS, upcoming calendar event titles and times via calendar.events.readonly, and the contents of recruitment-related email threads via gmail.readonly — is:
- Used only to provide the user-facing features you explicitly invoke — resume export and document update (Docs / Drive), interview prep packet generation from upcoming calendar events (Calendar), and recruitment-thread classification + reply drafting (Gmail). Email content fetched from Gmail is used to identify recruiter / hiring-manager threads and to generate a candidate reply in your voice; drafts are shown to you for copy-paste into Gmail and are never sent automatically;
- Not transferred to others except as necessary to provide those user-facing features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to users;
- Not used to serve advertising;
- Not read by humans, except (a) with your explicit consent for specific documents, (b) for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) where the data has been aggregated and anonymised for internal operations;
- Not used to train, fine-tune, or otherwise improve generalised or third-party AI / ML models. AI calls made on your behalf (Anthropic, Voyage) operate on the content you submit to HIRED-OS or on the specific recruitment thread you ask HIRED-OS to draft a reply for; Gmail content is never used as training data.
Data retention
Your data is retained while your account is active. You can delete individual items (jobs, stories, resumes) from inside the app at any time. To delete your account and all associated data, contact us at privacy@hired-os.com and we will permanently delete it within 30 days.
Security
All traffic is encrypted in transit via TLS. Authentication is handled by Clerk using industry-standard JWTs. Data is account-isolated at the database layer; users cannot see other users' data.
Your choices
- Disconnect any third-party integration (e.g., Google) from your profile at any time.
- Export or delete your stories, resumes, jobs, and runs from inside the app.
- Request a full account deletion via the contact below.
Contact
Questions or requests: privacy@hired-os.com.
Changes
We may update this policy as the service evolves. Material changes will be announced in the app and reflected in the “Last updated” date above.