Data collected
JobOS stores account identity, profile data, resumes, jobs, applications, notes, generated documents, billing metadata, support diagnostics, and consent records needed to operate the service. If you allow advertising measurement, JobOS records the consent version and timestamp against a random first-party browser identifier. If you arrive through a campaign link, JobOS may associate the campaign source, medium, campaign name, and optional ad-click identifier with it. No full URL, referrer, IP address, or user-agent is stored in the campaign attribution record.
Campaign URL handling
Campaign parameters arrive in the initial page request and are removed from the visible browser URL as the page initializes. Until you choose, the JobOS app keeps them only in page memory and discards them if you reject. The deployed public Nginx configuration disables access logs for JobOS web, API, and staging hostnames, so their requested URLs are not written to Nginx access logs. JobOS campaign attribution records do not contain the full URL. Campaign data is stored only after you allow advertising.
Purposes and legal bases
Data is processed to provide the job-search workspace, secure accounts, generate requested documents, manage billing, provide support, and meet legal obligations. Campaign attribution is optional and based on your consent; it measures campaign visits, registrations, and paid Premium subscriptions for JobOS. Depending on the workflow, other processing may rely on contract performance, legitimate interests, consent, or legal obligations.
Recipients and processors
Personal data is accessible only to the user, authorized JobOS operators where needed for support or security, and configured processors such as hosting, email, billing, storage, and AI providers. If Google Ads is configured and you allow advertising, Google receives consent signals, ad-click information, and a paid Premium conversion's value and currency. The Stripe Checkout session identifier is used only in first-party browser storage to prevent duplicate events and is not sent to Google. JobOS does not send Google your account email, profile, resume, job-search content, or other account data for advertising, and does not enable enhanced conversions. When OpenRouter is enabled, requested AI prompts and grounding context are sent to OpenRouter and the selected model provider to generate the requested output.
Advertising measurement and consent
Campaign source details and optional Google Ads measurement are used only after you explicitly allow advertising. Campaign attribution uses a random first-party browser identifier to connect a consented campaign visit to a later registration and paid Premium conversion; the identifier is not shared across websites. You can refuse or withdraw consent at any time using Cookie settings on any page. Withdrawal immediately removes campaign attribution from this browser and sends JobOS a request to delete the active record. If the request cannot be delivered, JobOS retries it when the browser is online. Withdrawal prevents future advertising conversion events. A minimal withdrawal record is retained for up to 180 days to prevent a delayed request from restoring withdrawn data; backup copies expire under the configured backup retention period. The consent choice is remembered for up to six months. Analytics storage and advertising personalization are not enabled.
Diagnostics and error reporting
JobOS uses Sentry’s EU instance (the configured DSN uses its EU ingestion endpoint) to diagnose application errors and improve service reliability. Diagnostic events can include an error type and stack trace, app version, environment, and limited runtime or device details. The SDK removes account identity, raw error messages, request data, headers, cookies, URL query parameters, AI inputs and outputs, and replay data before events are sent. Network metadata needed to deliver events may also be processed. Nginx access logs are disabled for JobOS web, API, and staging hostnames. The proxy error-log retention target is no more than 30 days; the host policy is being configured and verified. Docker also caps stored logs at 10 MB per file and three files. Abuse-prevention events retain a hashed network identifier, route, method, and reason for up to 30 days. Sentry retention is controlled in the project settings. For privacy questions or requests, use the contact details in the Legal Notice.
Redaction defaults
Exports, support bundles, observability events, and abuse records redact or hash sensitive content such as email addresses, message bodies, IP addresses, secrets, and raw resume text where possible.
User rights
Users can request access, rectification, erasure, restriction, portability, objection, and consent withdrawal where applicable. Use the legal or privacy contact listed in the Legal Notice.
User controls
Settings include export redaction, notification preferences, data export, and a deletion preview. For each connected email account, choose whether JobOS stores message content on the Integrations page.
Retention
Campaign attribution records are deleted when consent is withdrawn or within 180 days of collection, whichever comes first. Records linked to an account are also removed when that account is deleted. Aggregated campaign counts are derived from these records and are not retained separately. Profile, resume, job, and application data are stored during the account lifetime and removed from active product storage when the account is deleted. Backup copies are retained for the configured period (14 days by default). AI-generated artifacts and grounding reviews are removed after 90 days. Documents separately saved by the user remain in the account until deletion. Support diagnostic bundles are removed after 14 days; abuse records and completed or failed background jobs after 30 days. Minimal billing records may be retained as required for accounting and legal obligations.
International transfers
Provider locations depend on the infrastructure and AI providers enabled by the operator, including OpenRouter and the selected downstream AI model when AI generation is requested. Any production provider outside the EU should be reviewed for appropriate transfer safeguards before activation.