Privacy Policy

Last updated 22 October 2026

Who is responsible

Data controller: Flow 64.
NIP: PL5542722040.
Contact: support@flowerrecruit.com.

Data we process

  • Account and access data, including email address, the account identifier from the sign-in provider you use (Google or LinkedIn), name and avatar supplied through that provider, account and access status, and security/session data.
  • Career content you provide, including CVs, job descriptions, process records, company and role details, application dates, recruiter details, notes, salary and location fields, event timelines, outcomes, and uploaded files.
  • If you use the optional Chrome extension, pairing sends the one-time code, a random browser identifier and a generic Chrome device label to FLOWer, then stores that identifier and an import-only credential locally in Chrome. The credential is valid for at most 30 days; both local values are removed when you choose Forget this browser or when the extension next checks the pairing after expiry. Opening the popup locally reads the current public tab to show a DOM-only preview; the page URL and content are not sent to FLOWer at that point. The preview card shows detected role, company and source metadata, not the full job text. Clicking Import sends the job page URL and job-posting content selected during that preview — including selected page text and embedded schema.org/JobPosting data — plus any declared company or role title to your paired FLOWer account. The import keyboard shortcut reads and sends in one step. If an HTTPS page removed structured JobPosting data while rendering, the shortcut may request the same URL once without cookies or session credentials to recover it; popup preview remains DOM-only and HTTP pages remain DOM-only. The extension stores only the latest import outcome code in session storage, without the page URL or content. FLOWer receives ordinary request metadata such as an IP address for security and rate limiting and records the pairing's last-use time for device management. The extension does not continuously monitor browsing, access the Chrome history API or read LinkedIn messages, activity or other members’ profiles.
  • With extension version 0.3.4 or later, choosing Import profile on your own main LinkedIn profile checks owner edit controls and reads the visible career sections. It does not request LinkedIn APIs, read cookies or collect hidden profile data. A one-time handoff delivers the profile text and section data to your authenticated FLOWer account, where they are saved as your LinkedIn career record and used as reference by CV Architect. Hidden or collapsed entries may be missing. Re-sync replaces the previous snapshot; it does not create a Base CV or consume a CV Library slot.
  • Inputs and outputs of FLOWer's AI assistants, including chat messages, prompts assembled from relevant CV, job-description and process context, generated analysis, recommendations, drafts, and AI usage metadata.
  • Service and beta-credit records needed to operate access controls, prevent abuse, troubleshoot failures, and account for funded AI usage. The credit ledger stores accounting and token metadata, not prompt or response content.
  • If you add your own OpenAI API key, the key is encrypted at rest. It is decrypted only on the server when needed to make the AI request.

Why we use it and legal bases

  • To authenticate users and provide requested product functions, relying on performance of the service agreement or steps requested before entering it.
  • To secure, monitor and improve the beta, enforce access limits, diagnose faults and protect the service, relying on legitimate interests where those interests are not overridden by your rights.
  • To meet legal obligations and establish, exercise or defend legal claims where applicable.
  • Where consent is required for a specific optional activity, we will ask for it and you may withdraw it for the future.

Optional usage statistics

If you allow it, FLOWer sends a small number of product events (for example: app opened, offer added, AI result received, mailbox connected) to PostHog Inc., hosted in the EU (eu.posthog.com), to understand which steps help and where people get stuck. Events are linked to your account ID only; we do not send your email address, CV, offer or mail content, we do not record sessions, and IP addresses are discarded. The legal basis is your consent; it is off until you allow it, and you can withdraw it at any time in Settings → Account → Preferences, which stops further events. Ask us to delete collected events at support@flowerrecruit.com.

Chrome Web Store Limited Use

The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. FLOWer Recruit uses this information only to provide and secure the disclosed job-description import feature. It does not sell the information, use it for advertising, use it to determine creditworthiness or for lending, or permit human access except with the user's affirmative consent for support, when required for security or legal compliance, or after aggregation and anonymisation for internal operations.

Infrastructure and recipients

The current repository identifies these providers used to deliver the service:

  • Vercel hosts the frontend.
  • Railway hosts the backend service.
  • Neon provides the PostgreSQL database.
  • Google and LinkedIn provide OAuth sign-in.
  • OpenAI is the active AI provider for FLOWer's AI assistants. Relevant user-requested context may be sent to OpenAI to generate the requested response. If you use BYOK, the request uses your configured OpenAI key.
  • PostHog (EU Cloud) receives optional usage statistics only if you allow them, as described above.
  • jsDelivr delivers the application's bundled font files and may receive ordinary web-request metadata such as IP address and user agent.

These providers may process data outside your country. Where a transfer of personal data outside the European Economic Area requires a safeguard, the controller relies on an applicable mechanism such as an adequacy decision or standard contractual clauses. Contact us for information about safeguards relevant to your data.

AI and employment decisions

FLOWer's AI assistants are advisory AI systems for the user managing their own job search and may be wrong. They do not apply for jobs, contact employers, rank candidates for an employer, or make employment decisions. Health and Analytics are deterministic product calculations, not AI, and do not make automated employment decisions. You remain responsible for decisions and for checking important output.

Retention and deletion

We apply the following general retention schedule. A shorter period or earlier deletion applies where the data is no longer needed, you make a valid deletion request, or the law requires it. A longer period applies only where needed for a legal obligation or to establish, exercise or defend legal claims.

  • Account and access data: while the account is active and for up to 30 days after a verified account-deletion request.
  • CVs, job descriptions, application-process records, uploaded files and related personal data: for up to 24 months after the relevant recruitment process ends.
  • Chrome extension transfers: an unclaimed import handoff becomes unavailable after two minutes. Its payload is erased when claimed, and expired handoff rows are removed by the scheduled daily retention sweep. The import-only browser pairing expires after 30 days or earlier when you revoke it. Its local credential and random browser identifier are removed when you choose Forget this browser or when the extension next checks an expired pairing. Content you then choose to save in a process follows the job-description retention period above.
  • Security and system logs, AI usage records and request metadata: for up to 12 months.
  • Stored AI prompts and responses without personal data: for up to 90 days. Content containing personal data follows the period for the related source data, up to 24 months.
  • Accounting and tax records, if generated: for the period required by law, generally five years from the end of the calendar year in which the tax-payment deadline passed; this may be extended where the limitation period is suspended or interrupted.
  • Records needed for claims or disputes: for the applicable limitation period, generally up to six years, although a shorter or longer statutory period may apply.

Expiry is enforced through technical expiry where the feature provides it and through periodic operator review for other records. At the end of the applicable period, data is deleted or irreversibly anonymised unless continued storage is legally required. To request account or data deletion, email support@flowerrecruit.com. We may need to verify your identity. Deletion may be limited where data must be kept for security, legal obligations or legal claims.

You can also delete your account yourself in Settings → Account → Your data. This deletes the account and the data it holds immediately; AI usage records are kept only in anonymised form. Database backups and the logs of our hosting and AI providers are not edited record by record; they expire on their regular rotation.

Your rights

Depending on applicable law, you may have rights to access, correct, erase, restrict or object to processing, receive portable data, withdraw consent, and complain to a data-protection authority. You can download your data as a ZIP file and delete your account yourself in Settings → Account → Your data. For any other right, use the configured contact channel. We may need to verify your identity before acting.