Privacy Policy.

Workbloom S.r.l., Innovative Startup, Via Sardegna 32, 20146 Milan, Italy. Tax Code and VAT registration number 13981770962. For privacy and data inquiries: privacy@workbloom.io or info@workbloom.io.

This document covers the current Workbloom web application and backend infrastructure. The definitive notice must be formally verified under the European General Data Protection Regulation (GDPR - Regulation EU 2016/679) and applicable privacy laws. Statements, registrations, brokers, or retention metrics from older legacy systems are not imported into this platform.

Company accounts use verified work email addresses; Bloomers may use their own verified email. Company profiles contain business and representative details, with optional invoicing information visible only to the company Owner. Needs contain business problems, objectives and constraints. Private professional applications contain contact details, expertise and specializations, experience and project summaries, working preferences, and optional portfolio or professional-registration information.

Technical connection data may appear in system logs. Such logs are not described as fully anonymous or aggregated without specific technical auditing. Do not enter third-party personal data or proprietary secrets into briefs unless authorized to share them.

Conversations and confirmed requirements are restricted to authorized members of the corresponding company workspace. Imported Bloomer records are private and there is no open specialist directory. Following essential follow-ups and verification of a complete company account, automatic anonymous matching displays only anonymous, limited candidate information until an authorized identity unlock succeeds.

Names and contact details are disclosed only within the authorized company after the required verified payment and token debit. Test payments cannot reveal real identities. Approval alone never publishes a profile.

A Bloomer can read and edit their own profile after verified-email ownership checks. Pending and rejected applications are excluded from matching. All approved profiles participate in matching using their available professional evidence, regardless of completeness, specialization depth, availability status, or confirmation date, while profile completeness and accuracy confirmations serve to improve matching quality rather than exclude candidates.

Unsent chat drafts stay in the tab’s sessionStorage. Sent visitor messages and draft needs are stored privately in Supabase. Each visitor conversation remains accessible for 24 hours after the visitor’s latest message; sending another message renews that period, while starting a new chat does not delete earlier conversations. Expired visitor records are removed by a scheduled cleanup every 15 minutes. Essential HttpOnly cookies identify the visitor’s chats and prevent other visitors from reading them. After verified signup or login, the visitor can save the reviewed conversation into their company account; that copied account history is not deleted by visitor-session expiry. Authenticated messages, confirmed need versions and in-app professional communications remain private under the account retention policy, whose final wording requires approval. Avoid shared workstations. Use Log out to end an authenticated session; closing a tab does not necessarily terminate it.

Approved Bloomer professional evidence is indexed privately in Supabase using multilingual embeddings generated on the application server, rather than an external embedding API. The search source selects professional fields, not identity or fiscal fields. Missing specializations or other incomplete details do not remove an approved profile from matching; the results disclose evidence gaps. Withdrawal of approval removes the profile’s search documents and vectors, while its private administrative record remains available to authorized staff.

The public contact form opens your local email client and does not submit its draft to our servers. In-app messages are stored by the platform. BlooMIA sends relevant conversation context, confirmed requirements and retrieved anonymous professional evidence to OpenAI (United States) and, only if OpenAI is unavailable, to OpenRouter and its selected free-model provider. Matching/assessment context excludes candidate names, contacts, employers, raw roles and biographies. OpenAI requests ask OpenAI not to store the completion; OpenRouter requests deny providers marked as collecting user data. Neither is a contractual zero-retention or EU-residency guarantee. Do not share unauthorized confidential or personal information. Stripe hosts payment checkout; Workbloom does not store card details or record calls. Final processor disclosures, lawful bases and retention require qualified privacy approval before public launch.

CV-assisted onboarding is optional. After your explicit permission, a PDF or UTF-8 text document is parsed in memory and its extracted text is sent to OpenAI (United States) or, only if OpenAI is unavailable, to OpenRouter and the selected free-model provider. Unlike anonymous matching, this text can include your name and any other personal information you leave in the document: remove unnecessary or sensitive details first. Workbloom does not persist the original file or extracted text. Suggested professional fields appear for your review and are saved only when you save or submit your profile. Enter everything manually instead if you do not want this AI processing. Provider retention and international-transfer terms still require final privacy review.

Current technical purposes include guest chat and abuse prevention, account access, private conversation and business-need storage, internal candidate review, and system security. The data controller must formalize legal bases, data provenance, and notifications with its privacy counsel.

No automatic marketing subscriptions, promotional campaigns, or bulk invites are sent to candidates purely by virtue of record importation. Inclusion in the candidate archive does not constitute consent for public web display.

Database storage and authentication run on Supabase, hosted within the European Union (Ireland region). Identity and authentication providers, subprocessors, and international transfer safeguards will be formally itemized in the approved notice, without inferring contractual guarantees solely from database geography.

Workbloom uses only technical cookies/storage and preferences you request, so no consent banner is shown. First-party language and theme cookies last 365 days, guest-chat cookies 24 hours, and the password-setup journey cookie one hour. Supabase authentication cookies and temporary authentication-helper cookies have a configured browser maximum of 400 days; this is not the server session's authorization period, and helpers are removed during authentication cleanup. Tab sessionStorage holds unsent chat drafts. No advertising/profiling cookies, external analytics or translator widgets are deployed. Fonts are served locally; blog images may be served through Supabase Storage. The Cookie policy at /cookie-policy (also linked in the footer) lists names, purposes, durations, deletion instructions and the separate Stripe-hosted checkout.

Data retention is limited to specified service purposes and applicable legal requirements. The definitive retention schedule and operational disposal procedures require privacy approval; neither arbitrary fixed deadlines nor indefinite storage are promised.

A self-service data export or deletion portal is not active in this pre-launch version. For data subject inquiries, contact the controller, who will verify requests in accordance with statutory rights and compliance duties.

The database enforces Row Level Security and role-based access separation. Operations on specialist records strictly require an internal staff role verified server-side; client company credentials or client-declared roles cannot grant staff privileges.

Communications with the Supabase backend use HTTPS encryption. Local developer evaluation on loopback (HTTP) does not represent a protected public deployment. Organizational safeguards and hosting hardening will be reviewed prior to public launch.

To exercise rights of access, rectification, erasure, restriction of processing, portability, or objection under the GDPR, write to privacy@workbloom.io. The controller will verify requester identity and respond in accordance with statutory requirements without compromising third-party data.

You retain the right to lodge a complaint with your competent supervisory authority. In Italy: Garante per la protezione dei dati personali (www.garanteprivacy.it).