Privacy Policy

When you use Bluelake (restricted access), we process:

• Your account : email address, used for magic-link authentication. Purpose: to give you access to the service and secure your sign-in. Legal basis: performance of the service.
• Your use of the product : usage events (sign-ins, navigation, filters, searches, questions to Billy) measured via an analytics tool, to understand and improve Bluelake. Legal basis: legitimate interest; you may object at any time by writing to privacy@getbluelake.ai. We minimize this data (searches are measured only by their length, page addresses are recorded without the search terms or filters they contain, and questions to Billy only by their number and the tools they used, never their content) and the tool does not place any tracker on your device (see section 4). The analytics tool also records sessions (pages visited, clicks and scrolling) to understand how the product is used; these recordings mask all text, inputs, labels and tooltips, and are deleted after 30 days.
• Our relationship with your company : we keep the contact details of the people we work with at your company (name, role, company, work email), our exchanges with them, and notes on how your team uses Bluelake (such as the last sign-in and activity) in our customer relationship tool (Attio). Purpose: to support your team, prepare demos and follow up with your company. Legal basis: legitimate interest; you may object at any time by writing to privacy@getbluelake.ai.
• Prospects : if you work at a company we think Bluelake could help, we may contact you about it, in connection with your professional role.

  • What we use: your name, job title, company, the link to your public professional profile, and your work email address. Never a personal email address or a phone number.
  • Where it comes from: professional databases built from publicly available information, and a work-email lookup service. Ask us and we will tell you the exact source.
  • Why, and on what basis: business-to-business prospecting, in our legitimate interest (GDPR, art. 6(1)(f)). We only contact you at your work email address or on LinkedIn, about your role (French Postal and Electronic Communications Code, art. L.34-5).
  • Who sees it: Bluelake, and the services we use to do it: our CRM (Attio), our email (Google Workspace), the email lookup service (FullEnrich, which keeps a lookup history for 3 months), our sending tool (lemlist, run by Lempire SAS in France), and the provider of the AI model that helps us draft our messages and answers your questions in the demo (Anthropic). Our messages are written or approved by a person. lemlist sends our emails and some of our LinkedIn messages, with their follow-ups, on a schedule we set, and stops as soon as you reply; we send the other LinkedIn messages ourselves. Some of these services process data outside the EU, in particular in the United States, under appropriate safeguards (standard contractual clauses or the EU-US Data Privacy Framework; for Attio, run from the United Kingdom, an adequacy decision): see Transfers outside the European Union.
  • How long: 3 years after our last contact with you, then deleted. If you object, we keep only what we need to make sure we never contact you again.
  • The demo of Billy: if you try it from one of our messages, we count the questions asked per company, never per person. We keep the text of the questions for 30 days at most, to improve the demo, without linking it to you.
  • Your rights: you can object at any time, by replying STOP to any of our messages or writing to privacy@getbluelake.ai. You can also ask to access, correct or delete your data.
• Billing : if you subscribe to a paid plan, payment is processed by our payment provider (Stripe); we store your subscription status, your credit balance and what used your credits (for example, each contact search: who asked, for whom and when), but not your card details, which are handled directly by Stripe. Legal basis: performance of the contract and our legal accounting obligations.
• Feedback you send us : when you use Share feedback or Report this problem, we store your message, the type you chose (if any), your account (email, role and company) and plan, the address of the page you were on (without search terms or filters), your browser window size, the app version and, from an error page, the error reference. Purpose: to fix problems and improve Bluelake. Legal basis: legitimate interest. Our team is notified by email; that email contains your email address, the type you chose, the kind of page you were on and your message (with any secret it contained removed), not the page address.
• Your exports : when you export a list, we keep the file so that you can download it again from your Exports page. It holds the data of the people, accounts or projects in the list, such as names, roles, profile links and, when your company holds them, contact details. Purpose: to provide exports. Legal basis: performance of the service.
• Your CRM connection : when your company connects its CRM, a manager enters its API keys, which we store encrypted and never display again. When you add a person or a list to your CRM, Bluelake reads your CRM's contacts and companies to find whether the person is already there, then writes only what you validated (the contact, a company if you chose to create it, a note). To make you the owner of what you create there, Bluelake looks you up among your CRM's users by your email address, and keeps nothing of that lookup. We keep a record of each write, with the value it replaced, to show it in Activity. To check a list, Bluelake reads your CRM's contacts and companies and keeps those that could match a person of the list until the review is ready, then deletes them; the review itself (who matches whom, and what would be written) is kept with the import. Purpose: to provide the CRM connection. Legal basis: performance of the service.
• Your conversations with Billy : when you use Billy, our agent, we store your questions, its answers, the searches it ran (with their filters) and the results it showed you, as they were at that time, so that you can come back to a conversation. To answer, your question and the context it needs (the conversation so far, what you told Billy about your business, your plan, and how your team has set up Bluelake, such as whether its CRM is connected) are sent to our AI provider, Anthropic, which does not use them to train its models and deletes them within 30 days, unless a legal obligation or a breach of its usage policy requires keeping them longer. Purpose: to provide Billy. Legal basis: performance of the service.
• Files you attach to Billy : when you attach a file to a question (a CV or a job description, as a PDF, Word, text or image file), we store the file and the text read from it, so that Billy can read it in that conversation and you can find it later. A scan or an image is transcribed into text by our AI provider, Anthropic, when you attach it. Such a file often holds personal data about someone else, such as a candidate's name, contact details and career: attach only a document you are allowed to share. Its text is sent to Anthropic with your question, on the same terms as your conversations. The administrators who can read your conversations can also open the files attached to them, on the same terms described below. Deleting a conversation deletes its files, and deleting your account deletes all of them with the rest of your account data (see Retention). Purpose: to provide Billy. Legal basis: performance of the service.
• Billy's memory : Billy remembers what you tell it about your work (what you sell, your current strategy, who you target, the roles you sell to, how you like its answers), the accounts you name as clients or ask it to leave out, and up to 50 short notes in your own words about anything else (for example, an account you already work with), so that it doesn't ask again. Each time it remembers or forgets something, it says so under its answer, with a button to undo it, and you can ask it to forget anything. When you refer to an earlier conversation, Billy can also search your past conversations. In My profile you can see, change or delete this memory, and turn it off, which stops both. Purpose: to provide Billy. Legal basis: performance of the service.
• Billy in Slack : when your team adds Billy to its Slack workspace, we store the identifier of that workspace and, for each member who connects their Bluelake account to it (once, from a link Billy sends them privately, confirmed on Bluelake while signed in), their Slack identifier, the Bluelake account it is connected to, the identifier of their direct message with Billy and those of the Slack threads that hold their conversations with it (deleted within two days once you delete the conversation). We do not read the e-mail of Slack profiles. Your messages to Billy in Slack and its answers are a conversation like the others, stored and readable under the same terms, and they also pass through Slack, under Slack's own terms. To answer you from Slack, Bluelake keeps a session token of your account, encrypted, so that Billy reads only what your account can read. You can disconnect Slack at any time from the Integrations page: your connection is deleted, that token is closed, and Billy no longer answers you in Slack. Billy only answers when you write to it: it never writes to you first. When your team has connected its CRM, Billy can read it during a conversation with the keys your team's manager entered: your team's consultants and candidates (profile, skills, availability, daily rates, references), its opportunities, positionings and projects, the notes, calls and meetings your team logged in the CRM, including their text, and its companies and contacts by name. Billy is never given their e-mail, phone or links; when you ask it for drafts to contacts of your CRM, Bluelake itself reads each contact's e-mail in the CRM to fill in the draft's recipient, and the draft's receipt in the conversation shows it. What it reads is used for that answer and archived with it like any other search, under the same terms as the conversation, and Billy never writes to the CRM from a conversation. The people named in your CRM (your consultants, candidates and contacts) are your team's data, processed on its instructions. Purpose: to provide Billy where your team works. Legal basis: performance of the service.
• Your Google mailbox and calendar : when you connect your Google account to Billy (Integrations page), Bluelake stores the address you authorized and a Google token, encrypted, that lets Billy read your Gmail threads and your calendar events when you ask it a question about them, and create, change or delete drafts in your Gmail when you ask. Billy never sends a message, never changes or deletes a message you received or sent, reads only the mailbox you connected, and never uses it in a Slack channel, where other people read its answers. What it reads is used for that answer and archived with it like any other search, until you delete the conversation; nothing from your mailbox is copied elsewhere, and Billy's memory never keeps the content of a mail. When you ask Billy for drafts to the people in your lists, Bluelake fills in each recipient with the work email your company already found for that person, the one your exports contain, and the draft's receipt in the conversation shows it; Billy never starts a search for contact details. You can disconnect at any time from the Integrations page: the token is revoked at Google and deleted. Bluelake's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Purpose: to provide Billy on your own conversations. Legal basis: performance of the service, at your request.
• Reading of conversations with Billy by our team : Bluelake administrators can read your conversations with Billy (questions and the files attached to them, answers, searches run and the results you saw) to understand how the agent is used and improve Bluelake. Every reading is logged. We never use your conversations to prospect your clients or to train AI models, and never show them to another customer. Legal basis: legitimate interest. You can object at any time by turning off Help improve Bluelake in My profile: the team can then no longer open your conversations. When Billy can't do or answer something you ask, it also notes it in one line (a category and a short summary, without names or contact details) so that we can improve Bluelake; turning off Help improve Bluelake stops this too. These lines are kept for 12 months. My profile always shows whether this is on.

Bluelake restitutes a read of accounts through public professional data of Data & AI talent, processed on the basis of our legitimate interest. If you are concerned, our Your professional data page explains precisely what we process and how to exercise your rights, including requesting your removal. See also our approach to data.

When a Bluelake user asks for it, Bluelake also looks for a professional's work email address and mobile number. It sends FullEnrich, a provider specialized in professional contact data, the person's name, public profile link and current employer, and FullEnrich returns what its sources hold. We never ask for a personal email address. The contact details found are shown only to the users of the company that asked for them, and are deleted with that company's account. A user of that company can also have Billy prepare drafts to that professional in their own mailbox: the work email already found fills in the recipient, without a new search. FullEnrich keeps a history of its searches for 3 months. Legal basis: legitimate interest.

Our website, getbluelake.ai, sets no cookie and stores nothing on your device. Our host (Vercel) receives the technical data needed to serve its pages, such as your IP address. The website measures its audience with Vercel Web Analytics, without cookies: for each page viewed, the page address (without anything after "#" and without parameters other than campaign tags), the referring site, the approximate location (country, region, city), the type of device, the browser and operating system, and the time; and each click on "Book a demo", with the page it came from. A visitor is counted through a hash of the request, which Vercel discards after 24 hours, and we only see these figures in aggregate, to know which pages are read and where visitors come from. Legal basis: legitimate interest.

When you request access from it, we keep your work email address, when you asked and how many times, and the status of your request, to open your access and follow up with you. Our team is notified by email, through n8n. Each request is also counted in our usage-measurement tool, under your email address, and if you already have an account, Bluelake sends you a sign-in link. We never use this email for a newsletter or for advertising. Legal basis: legitimate interest, and steps taken at your request before an agreement. How long we keep it: see Retention.

When you book a demo from it, you do so on a Google booking page: the name and email address you give and the time you choose reach our team's calendar (Google Workspace) and our customer relationship tool (Attio), to hold the meeting and follow up with you. Legal basis: steps taken at your request before an agreement. How long we keep them: see Retention.

Bluelake uses strictly necessary cookies for your authentication and the operation of the service, including, for 30 minutes, the page you asked for while you sign in. Our usage-measurement tool (hosted in the European Union) works without placing any cookie or other storage on your device. No advertising cookie or third-party tracker is used. Our website, getbluelake.ai, sets none, including to measure its audience.

Your data is intended for Bluelake. It is processed by our technical providers acting on our behalf: hosting and our website's audience measurement (Vercel), database and authentication (Supabase, EU), database backups (Google Cloud, EU), error monitoring (Sentry, EU hosting), audience measurement (PostHog, EU hosting), payments (Stripe), transactional email (Resend), our team's email (Google Workspace), the notification of access requests (n8n, EU hosting), the AI model behind Billy (Anthropic), customer relationship management (Attio), the search for professional contact details (FullEnrich), the sending of our prospecting emails and LinkedIn messages (lemlist, France) and, when your team has installed Billy there, Slack (Slack Technologies, for the messages exchanged in your workspace), and, when you connect your Google account, Google (Gmail and Google Calendar APIs). We do not sell your data.

When Bluelake processes personal data on behalf of your company, such as the files your users attach to Billy or what Billy reads in the tools your team connects, it acts as your company's processor, under our Data Processing Agreement.

The database (Supabase, EU region), its backups (Google Cloud, Belgium), error monitoring (Sentry), audience measurement (PostHog EU Cloud) and the notification of access requests (n8n, Germany) are hosted in the EU. Payments (Stripe), transactional email (Resend) and the AI model behind Billy (Anthropic) involve processing in the United States, framed by the standard contractual clauses provided for by the GDPR. Our customer relationship tool (Attio) is run by a UK company, a country the European Commission recognises as providing adequate protection; its own providers include companies in the United States, framed by the same standard contractual clauses. Slack, when your team uses Billy there, is run by a US company, framed by the same standard contractual clauses, and so is FullEnrich, which searches professional contact details. Our host, Vercel, is a US company: the application runs in Paris, France, and our website is served from Vercel's worldwide network, framed by the same standard contractual clauses. Our team's email (Google Workspace) is run by Google, which may process it in the United States under the EU-U.S. Data Privacy Framework, to which Google is certified.

Account data is kept for the duration of your access to Bluelake, then deleted. Usage data is kept for a maximum of one year; session recordings are deleted after 30 days. Our website's audience figures identify no one, and we can read them for 12 months. Feedback you send is kept for 12 months after it is sent, then deleted automatically. Contact details, exchanges and notes in our customer relationship tool are kept for 3 years after our last contact. Requests for access are kept for 3 years after our last contact or, if you become a user, until your account is deleted, and n8n keeps the notification of a request for 30 days. Conversations with Billy, and the files attached to them, are kept until you delete them or your account, and Billy's memory until you delete it or your account; the log of team readings is kept for 12 months. The record of what Bluelake wrote to your CRM, list import reviews included, is kept for as long as your account exists. Your exports and their files are kept for as long as your account exists. Billing records are kept for the period required by applicable accounting and tax law.

When you delete your account, access is closed immediately and your account data, including your exports and the files you attached to Billy, is permanently erased within 30 days. During this window you can ask us to restore your account at privacy@getbluelake.ai; after it, deletion is irreversible. Copies in our daily database backups are deleted after 30 days.

You have the right to access, rectify, erase, object to, restrict and port your data. Exercise these rights at privacy@getbluelake.ai. You may also lodge a complaint with the CNIL (the French supervisory authority).