Legal draft

Privacy Policy

Replace placeholders with real operator details and have the final text reviewed before launch.

Controller

Controller: [Legal operator name], [address], [privacy contact email].

Data we process

Account data such as name, email address, password hash, locale, timezone, and login metadata.
Candidate profile data such as application email, phone number, address, work authorization, language skills, salary expectations, and reusable application answers.
Job-site account data such as provider, username, site URL, status, and encrypted credential reference. Plaintext passwords are not returned to the browser.
Application data such as jobs, campaign rules, submitted documents, answers used, status, blockers, and audit events.
Billing data received from Stripe, including customer ID, subscription status, plan, and billing period metadata.
Privacy-aware analytics events such as page/event name, path, browser language, referrer origin, and limited allowlisted metadata.

Why we process data

To create and operate the user's account and application workspace.
To search for jobs, prepare applications, submit applications where authorized, and track results.
To notify the user when an application needs an email code, SMS code, captcha, manual review, or other intervention.
To process payments, subscriptions, invoices, cancellations, and tax-relevant billing events through Stripe.
To keep the service secure, prevent abuse, debug reliability issues, and improve product funnels with minimal analytics.

Processors and recipients

Current planned processors include hosting infrastructure, PostgreSQL database hosting through the operator's server, Stripe for billing, Resend for transactional email, Telegram for bot notifications if connected, and AI API providers when guarded fallback automation is used. Add exact provider names, regions, and data processing agreements before launch.

AI and automation safeguards

Job pages, employer forms, uploaded files, and user-provided answers are treated as untrusted data. AI usage is budgeted by plan and should receive only the minimum required context. Passwords, email codes, Stripe secrets, webhook secrets, and API keys must not be sent to AI providers.

Retention

Account, profile, application, audit, and billing records are retained while the account is active and then deleted or anonymized according to the final retention schedule. Define exact retention periods before launch.

User rights

Users may request access, correction, deletion, restriction, portability, or objection where applicable. Users may also lodge a complaint with the competent data protection authority. Add the final contact workflow before launch.