Bluelake
Privacy Policy
Last updated November 21, 2026
Bluelake is a product operated by Bluelake (a French simplified joint-stock company, 60 rue François 1er, 75008 Paris, SIREN 101 883 510, R.C.S. Paris), acting as data controller (see our legal notice). For any question: privacy@getbluelake.ai. This policy covers three types of data: that of Bluelake users, that of the professionals whose profile is restituted in Bluelake, and that of the visitors of our website, getbluelake.ai, including when they request access.
1. Data of Bluelake users
When you use Bluelake (restricted access), we process:
- Your account : email address, used for magic-link authentication, and the first name, last name and company you give when you sign up. Purpose: to give you access to the service and secure your sign-in. Legal basis: performance of the service. We also send you a few e-mails to help you get started, based on what is already set up in your account, greeting you by your first name when we have it; a link in each one stops them. While you have no alert of your own, we also send you, on Mondays, an e-mail with a few of the week's new job posts and moves at the accounts we follow, which may say what the paid plan adds; it stops at your first alert, or from the link it carries. We keep that it was sent (the week, your plan and the number of lines) for 30 days, and your request to stop it for as long as your account exists. We also send each account Bluelake's product news, what is new in Bluelake; you are subscribed by default, and a link in each issue unsubscribes you. We keep that an issue was sent to you for 30 days, and your request to unsubscribe for as long as your account exists. Legal basis for these e-mails: our legitimate interest in helping you use Bluelake and telling you what is new in it.
- 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. 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, our email, the email lookup service (which keeps a lookup history for 3 months), our sending tool (run by a company in France, which also uses AI to sort the replies to our messages, for example to spot an out-of-office reply or the tone of an answer), the provider of the AI model that helps us draft our messages and answers your questions in the demo, and LinkedIn, for our ads (see Advertising on LinkedIn). Our messages are written or approved by a person. Our sending tool 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 our CRM, 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 Billy from one of our messages, the link is yours: we send one link to each person we write to, and our sending tool and our customer relationship tool know which link went to whom. We count the questions you ask, to enforce the link's quota, and your clicks on the page's buttons, including the actions shown under each answer, to know whether the demo is useful to you; we never count when a link is opened. Your question, with the earlier questions and answers of the same conversation, is sent to our AI provider, on the same terms as conversations with Billy. We keep your conversation with your link (your questions, Billy's answers and the results shown under them), so that you find it when you come back, to check the answers and improve the demo, and so that our team can read it before following up with you. Your counts, and what we note about your conversation, go into our customer relationship tool and are kept like our other notes. Do not put anyone else's personal data in a question. Our host receives your IP address to serve the page and to protect it from abuse, and keeps it only in its usual technical logs. The page sets one strictly necessary cookie, which carries your link (see Cookies), and it loads no analytics tool; errors, and a sample of page loads and requests, reach our error-monitoring tool without the link or your question. Billy is an AI agent: its answers are generated by AI and may contain errors. Links expire on a fixed date, at most two months after they are sent, and your conversation, with what the demo keeps about your link, is deleted 30 days after the link expires or is revoked, with up to 38 more days in our backups. You can ask us at any time for your conversation or for its deletion. Legal basis: our legitimate interest in showing Bluelake and following up with you.
- Advertising on LinkedIn: we may show Bluelake ads on LinkedIn to people who work at the companies we prospect. To do so, we give LinkedIn lists of company names and, for the people we write to, their work email address, which is hashed before it reaches LinkedIn. LinkedIn uses these addresses only to find the matching members, deletes the list within 30 days, and never tells us who was matched: we only see aggregated figures. In Europe, LinkedIn only matches members who have allowed it in their LinkedIn settings, and it shows its ads under its own privacy policy. Legal basis: our legitimate interest in business-to-business prospecting. If you object, we stop giving your address to LinkedIn and remove it from the lists we gave it; on LinkedIn, you can also hide an ad and manage your ad preferences. If you answer one of our ads with LinkedIn's form, we receive the details you give in it: your name, work email address, company and job title, which LinkedIn fills in from your profile and you can change, and the size of your sales team. We use them to get back to you about the demo you asked for; they go into our customer relationship tool and are kept like our other exchanges with you, and LinkedIn keeps them in our advertising account for 90 days. Legal basis: steps taken at your request before an agreement.
- Your rights: you can object at any time, including to our ads on LinkedIn, 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; 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 our payment provider. It issues the invoices, and they are kept in our accounting software. 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. To sort it with the other requests we receive, our AI provider writes a one-line summary of your message, written and checked to leave out names and contact details. That summary, the type you chose, the kind of page, the month and your company's name are added to our product backlog, with a link to your message that only our team can open; your message itself stays in Bluelake. Our backlog keeps the request itself, which includes neither your name nor your message, even after your account is deleted. Nothing is added when Help improve Bluelake is off.
- 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 data export : in My profile, "Download my data" prepares one ZIP file with what you did in Bluelake: your conversations with Billy and the files you attached, Billy's memory, your e-mail signature and your booking link, your lists, alerts and exports, what Bluelake wrote to your CRM for you, the profiles and projects you unlocked, the contact details found for you and your credits. It never contains the keys of your connections, our notes on our relationship with you or our internal measurements. When it is ready, we send you an e-mail that points to My profile, never to the file, which you download there while signed in. We keep the file for 30 days, then delete it, and keep a record of each export (when it was prepared and downloaded, and its size). Purpose: to let you take your data with you. Legal basis: performance of our contract with you, and our obligation to let you exercise your right to data portability.
- Your team's export : your team's manager can download, from My profile ("Download the team's data"), one ZIP file with your team's whole workspace. For each member, it holds what they did in Bluelake: their conversations with Billy and the files they attached, Billy's memory, their lists, alerts and exports, what Bluelake wrote to the CRM for them, the profiles and projects they unlocked, the contact details found for them and their credits. It never holds a member's mailbox or calendar: a conversation in which Billy read their e-mails, drafts or calendar events is left out whole, with its title, its files and what Billy remembered from it, and stays only in their own data export. It also holds the team's own records, such as its CRM settings without their keys and its company page. Members are not notified of each export. Once downloaded, this copy is your company's: your company decides how it uses it and informs its users. We keep the file for 30 days, then delete it, and keep a record of each export. Legal basis: performance of our contract with your company.
- 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 e-mail signature and booking link, your plan, and how your team has set up Bluelake, such as whether its CRM is connected) are sent to our AI provider, 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. Billy helps find and present profiles; it makes no decision about anyone. 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, a job description, or a spreadsheet such as a list of accounts or contacts, as a PDF, Word, Excel, CSV, text or image file), in Bluelake or in a message to Billy in Slack (Bluelake then downloads it from Slack, with the access your team gave Billy there), 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 when you attach it; a spreadsheet is read as it is, without AI. Such a file often holds personal data about someone else, such as a candidate's or a contact's name, contact details and career: attach only a document you are allowed to share. Its text is sent to our AI provider 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.
- Your company page : when your team's manager fills in the "My company" page (your company's positioning, offers, references and what it does, such as the sectors of its clients, its types of engagement, technologies and roles), we store it for your team, with the source and date of each field and the version before the last change, so that Billy and your agents use it for every member, along with which manager changed it last. It must hold no one's name: no consultant, contact or candidate; e-mail addresses, phone numbers and links are refused. Every member of the team can read it; only a manager changes it. It is sent to our AI provider with each question, on the same terms as your conversations. To propose its fields, a manager can ask Bluelake to read your company's public website, which our AI provider reads on that site only, or a brochure, whose text is sent to it; neither the pages read nor the brochure are kept, only what the manager saves. A manager can also ask Billy to fill in its lists (client sectors, engagement types, technologies, roles, use cases) from your CRM: Billy reads it as for any question, and only the lists the manager confirms are saved, without anyone's name. Purpose: to provide Billy and the agents. Legal basis: performance of the service.
- Your e-mail signature : when you save a signature in My profile, or give it to Billy in a conversation, we store its text, as you wrote it (usually your name, your role, your company and your phone number), so that Bluelake adds it at the end of the Gmail drafts Billy prepares for you, and Billy ends the e-mails it writes in its answers with it. Billy saves only a signature you wrote in your own message, never one found in a mail or a document, and it is not used in a Slack channel, where other people read its answers. When your Gmail has a signature, Billy uses that one instead (see below). You can see, change or delete yours at any time in My profile. Purpose: to provide Billy. Legal basis: performance of the service, at your request.
- Your booking link : when you save a booking link in My profile (the page where people book a meeting with you, such as a Calendly page), or give it to Billy in a conversation, we store that address so that Billy can add it to the e-mails it writes for you. Billy saves only a link you wrote in your own message, never one found in a mail or a document, and only an https address. You can see, change or delete it at any time in My profile. Purpose: to provide Billy. Legal basis: performance of the service, at your request.
- 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. Purpose: to provide Billy where your team works. Legal basis: performance of the service.
- Billy and your team's CRM : when your team has connected its CRM, Billy can use it in your conversations, with the keys your team's manager entered. It reads what it needs to answer you among what your team keeps there: its consultants, candidates, contacts and companies, its opportunities and projects with their commercial and financial details (such as rates, costs, margins and invoicing), and the activity your team logged (notes, calls, meetings, e-mails). From a candidate's administrative file, it uses only what you ask for, such as the daily rate they expect, and keeps nothing else. Billy is never given a person's e-mail, phone or links: when it prepares drafts, Bluelake fills in the recipients itself. What Billy reads is used for that answer and archived with it, under the same terms as the conversation. Billy writes to the CRM only when you say yes in the conversation, for example to log there a mail you sent, with its text; while the CRM is in test mode, nothing is written. When you ask, Billy can also prepare files from the CRM, such as Excel files, which Bluelake builds when you download them and does not keep; Billy sees only their description and how many rows they have. The people named in your CRM are your team's data, processed on its instructions. Purpose: to provide Billy where your team works. Legal basis: performance of the service.
- Your mailbox and calendar (Google or Microsoft 365) : when you connect your Google account or your Microsoft 365 mailbox to Billy (Integrations page), Bluelake stores the address you authorized and a token from Google or Microsoft, encrypted, that lets Billy read your mails and calendar events when what you ask needs them, and create, change or delete drafts in your mailbox when you ask. Billy also uses the signature set in your Gmail to sign those drafts and the e-mails it writes in its answers. 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, until you delete the conversation. Nothing from your mailbox is copied elsewhere, except what you ask Billy to log in your CRM, such as a mail you sent or a notice that a mail could not be delivered, and Billy's memory never keeps the content of a mail. When Billy prepares drafts to people in your lists, Bluelake fills in each recipient with the work email your company already found for them; Billy never starts a search for contact details. You can disconnect at any time from the Integrations page: the token is deleted (and revoked at Google for a Google account). 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.
- Your agents : when you turn on an agent, Bluelake runs it at the time you set, or on the new signals of the alerts it follows, under your own account. It reads only the sources you chose for it (the market map, your team's CRM, your mailbox or calendar), at the time of the run, prepares the result in a conversation with Billy and, if you chose so, tells you by e-mail or in Slack. An agent never sends a message and never writes to your CRM; it may save drafts in your mailbox when you set it to. So that it can run while you are not signed in, Bluelake keeps a session token for your account, encrypted, only while one of your agents is on, and deletes it when your last agent stops. The log of each run (when, how many items, what it cost, which conversation) and of the drafts it saved is kept for as long as your account exists, and deleted with it. Your team manager sees your agents' settings, state and log, never what an agent prepared for you alone. Purpose: to run the agents you turned on. 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, and adds that line to our product backlog with its month and your company's name. Turning off Help improve Bluelake stops this too. These lines are kept for 12 months; our backlog keeps the requests themselves, which include neither your name nor your message, even after your account is deleted. My profile always shows whether this is on.
2. Data of the professionals restituted in Bluelake
Bluelake restitutes a read of accounts through public professional data of Data & AI talent and of the IT leaders and buyers of the accounts we follow (CIOs, CTOs, IT and data directors, buyers of IT and professional services, vendor management), processed on the basis of our legitimate interest. Our clients use it to read their accounts, including to identify professionals for their own recruitment or staffing needs. A client who contacts a professional about a job or an engagement does so as a separate controller: they inform the person at the latest in their first message, keep their data only as long as their recruitment process needs, and the decision about them remains theirs. 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. The demo of Billy, which we open to the people we write to (see Prospects), shows the same reading without any name: the professionals of an account by role, with their headline, technologies, certifications, projects and city or area, and a team's moves by role, with the previous or next company and the month.
When a Bluelake user asks for it, Bluelake also looks for a professional's work email address and mobile number. It sends a provider specialized in professional contact data what identifies the person at work, such as their name, current employer, public profile link or the domain of their work email, and that provider 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. That provider keeps a history of its searches for 3 months. Legal basis: legitimate interest.
3. Our website and requests for access
Our website, getbluelake.ai, keeps your choice about cookies in a cookie (bluelake_consent, for 6 months), and sets LinkedIn's advertising cookies and those of our detailed audience measurement only if you accept them (see below); otherwise, it stores nothing else on your device, except a marker (bluelake-visite-interne) that our team sets on its own browsers, through a dedicated link, so that our own visits are not counted. Our host receives the technical data needed to serve its pages, such as your IP address. The website measures its audience with our host's analytics service, 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 "Request a guided trial", with the page it came from; and, in the demo on the home page, each step reached, with the language of the page. A visitor is counted through a hash of the request, which our host 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.
The website also tells Bluelake where each visit comes from, without identifying anyone. When a visit arrives from outside the website, and when someone clicks on "Request a guided trial", it sends our application the campaign tags of the address, the domain of the referring site (for example linkedin.com, never the full address) and the first page viewed, plus, for "Request a guided trial", the page of the click. With the same three items, it also counts a few steps of each visit, for every visitor: a click towards sign-up and the page it came from, the start and the sending of the sign-up form, how far the home page is scrolled (by quarters), each question opened in a FAQ, each step reached in the demo on the home page, with the language of the page, and the choice made in the cookie banner (accepted, refused, or accepted for one purpose only). Our application records these signals in our usage-measurement tool without any identifier, without your IP address and without location, and nothing links one signal to another; we read them as totals, per source and per week, to know which of our messages and channels bring visitors. "Request a guided trial" therefore goes through a page of our website, which counts the click and then opens the booking page. The links from our website to Bluelake ("Sign in", "Request access") carry the same three items in their address, never your email address, so that a request for access says where it came from. The footer of each page also asks our application for the current status of the service, to show it live; this request carries no cookie and no identifier, and the answer is the same for everyone. The home page asks our application, in the same way, for recent public signals at large companies (projects, appointments and job openings, with the company's logo, served by our application) to display them. Apart from checking our team's marker (see above), nothing is read from or stored on your device. Legal basis: legitimate interest.
If you accept them, from the banner of our website or later from "Cookie settings" at the bottom of each page, getbluelake.ai loads LinkedIn's tag (Insight Tag). It sends LinkedIn the page you view (its address without anything after "#" and without parameters other than campaign tags and LinkedIn's click identifier), the referring site, your device and your IP address, and two actions: a request for access, and a click on "Request a guided trial". LinkedIn uses them to measure the results of our ads and to show our ads to visitors of our website who are LinkedIn members: it matches these visits with its members, removes direct identifiers within seven days and deletes the data after 180 days, and we only see aggregated reports, never who you are. LinkedIn's cookies are li_fat_id (30 days), li_giant (7 days) and ar_debug (for the session) on our domain, and, on linkedin.com, bcookie (1 year), li_gc (6 months), li_sugr (90 days), UserMatchHistory and AnalyticsSyncHistory (30 days) and lidc (24 hours). If you reject them, or until you choose, the tag is not loaded and nothing reaches LinkedIn. You can withdraw your consent at any time from "Cookie settings", as easily as you gave it: we then delete LinkedIn's cookies on our domain, and those on linkedin.com expire there. For collecting and transmitting this data, Bluelake and LinkedIn Ireland Unlimited Company are joint controllers; LinkedIn alone decides what it does with it afterwards, under its own privacy policy. Legal basis: your consent.
Our detailed audience measurement is a separate choice: "OK" in the banner accepts it together with LinkedIn's tag, "Continue without consent" refuses both, and the banner's details and "Cookie settings" let you accept or refuse each of them on its own. If you accept it, getbluelake.ai loads our usage-measurement tool (hosted in the European Union, acting as our processor), which records the pages you view, your clicks, how far you scroll, the type of device and browser, and a recording of your visit (the pages as displayed, your mouse movements, scrolls and clicks), with everything you type in a form field masked, so that we can improve the website. Page and link addresses are sent without anything after "?" or "#", with the origin of your visit described above, and without location. To recognise your browser from one visit to the next, it keeps a random identifier in a cookie on getbluelake.ai (ph_ followed by our project key and _posthog, for 6 months after your last visit) and in the storage of your browser. If you then open a Bluelake account from the website, this identifier is sent with your request and linked to your account, so that your earlier visits are counted with it. If you reject it, or until you choose, the tool is not loaded and nothing is recorded, apart from the signals without any identifier described above. You can withdraw your consent at any time from "Cookie settings": the measurement stops at once, and its cookie and storage are deleted from your browser. Recordings of visits are deleted after 30 days. Legal basis: your consent.
When you request access from it, we keep the first name, last name, company and work email address you give, when you asked and how many times, the status of your request and the origin of your visit (the campaign tags of the address you arrived on, the domain of the referring site and the first page you viewed), to open your access, follow up with you and know which of our messages brought you. Our team is notified by email, through an automation service hosted in the EU. Each request is also counted in our usage-measurement tool, under your email address, with this origin, and if you already have an account, Bluelake sends you a sign-in link. When sign-up is open and you do not have an account yet, Bluelake opens your Free account from this request and emails you the link to activate it; our team receives an email for each sign-up. Beyond your access and the e-mails described under Your account, including our product news, we never use this email for advertising. Legal basis: legitimate interest, and steps taken at your request before an agreement. How long we keep it: see Retention.
When your access is opened, this origin is kept with your account as its first source, with the date of your first request (or the fact that you were invited directly), recorded once on your profile in our usage-measurement tool, and noted in our customer relationship tool, so that we can see which sources lead to using Bluelake. Your request for access and your account are then counted as the same person in our usage-measurement tool, and so are your earlier visits to the website if you accepted our detailed audience measurement (see above). The first source is deleted with your account, and removed from our usage-measurement tool within 30 days as well (see Retention); in our customer relationship tool, it is kept like the rest of our exchanges with you. Legal basis: legitimate interest.
When a sign-in to Bluelake fails, our team receives an email with the email address that was typed (when Bluelake knows it: not for a sign-in link that was refused), the kind of failure, the time, and the IP address with its approximate location (city, region and country, as given by our host), so that we can help someone who cannot sign in and spot misuse of the sign-in page. This address is not recorded in our usage-measurement tool. Legal basis: legitimate interest. How long we keep it: see Retention.
When a request for access is refused (an email address that is not valid, a personal email address, an address with a "+", or a missing or invalid first name, last name or company), Bluelake does not record it in its database. Our team receives an email with what was typed in the form (the email address, and the first name, last name and company if they were given), the reason for the refusal, the origin of the visit (campaign tags, referring site and first page viewed), the time and the approximate location of the request (city and country, as given by our host; never the IP address itself), so that we can help someone whose request did not go through. The refusal is also counted in our usage-measurement tool, under the email address that was typed, with the reason and the same origin. Legal basis: legitimate interest. How long we keep it: see Retention.
When you request a guided trial from it, you book a time on our calendar provider's booking page: the name and email address you give and the time you choose reach our team's calendar and our customer relationship tool, 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.
4. Cookies
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. The demo of Billy sets one more: it carries your link, is sent only to the demo's pages, and expires with the link. In Bluelake, our usage-measurement tool (hosted in the European Union) works without placing any cookie or other storage on your device. Our website, getbluelake.ai, measures its audience without cookies unless you accept them. It keeps your choice about cookies in a cookie (bluelake_consent, 6 months), and LinkedIn's advertising cookies, and the cookie and browser storage of our detailed audience measurement (ph_ followed by our project key and _posthog, 6 months after your last visit), are each set only if you accept them (see section 3); you can change your choice at any time from "Cookie settings", at the bottom of each page. On our team's own browsers, it also keeps a marker (bluelake-visite-interne) so that our own visits are not counted.
5. Recipients and processors
Your data is intended for Bluelake. It is processed by our technical providers acting on our behalf: hosting and our website's audience measurement, database and authentication (EU), backups of the database and files (EU), error monitoring (EU hosting), audience measurement (EU hosting), payments, our accounting (France), transactional email, our team's email, the notification of access requests (EU hosting), the AI model behind Billy, customer relationship management, our product backlog, the search for professional contact details, the sending of our prospecting emails and LinkedIn messages (France) and, when your team has installed Billy there, Slack (Slack Technologies, for the messages and files exchanged in your workspace), and, when you connect your Google account, Google (Gmail and Google Calendar APIs) or, when you connect Microsoft 365, Microsoft (Microsoft Graph API). For our ads on LinkedIn, LinkedIn Ireland Unlimited Company receives the lists described in Prospects and, if you accept its cookies, the visits described in section 3, and uses them under its own terms. The up-to-date list of our providers is available on request at privacy@getbluelake.ai. 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.
6. Transfers outside the European Union
The database and files, their backups, error monitoring, audience measurement and the notification of access requests are hosted in the EU. Payments, transactional email and the AI model behind Billy involve processing in the United States, framed by the standard contractual clauses provided for by the GDPR. Our customer relationship tool 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 our provider of professional contact details. Our host is a US company: the application runs in Paris, France, and our website is served from its worldwide network, framed by the same standard contractual clauses. Our team's email is run by a provider that may process it in the United States under the EU-U.S. Data Privacy Framework, to which it is certified. Our product backlog is hosted by a US company, under the EU-U.S. Data Privacy Framework or standard contractual clauses; the requests it holds include neither names nor messages. LinkedIn, run in the EU by LinkedIn Ireland, may process the lists we give it and the visits its tag records in the United States, under the EU-U.S. Data Privacy Framework, to which LinkedIn Corporation is certified, and standard contractual clauses.
7. Retention
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. When your account is deleted, your profile in our usage-measurement tool, with your email address and the first source of your account, is deleted within 30 days; other usage events are kept for a maximum of one year. Our website's audience figures identify no one, and we can read them for 12 months; with your consent, the recordings of your visits to it are deleted after 30 days, and the other events of its detailed audience measurement are kept for a maximum of one year, like usage data. 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, and their count in our usage-measurement tool, are kept for 3 years after our last contact or, if you become a user, until your account is deleted, and the automation service that notifies us keeps the notification of a request for 30 days. The emails about a failed sign-in or a refused request for access are kept in our team's mailbox for 30 days, then deleted; the count of a refused request in our usage-measurement tool is kept like that of a request for access. Conversations with Billy, and the files attached to them, are kept until you delete them or your account, and Billy's memory, your e-mail signature and your booking link until you delete them 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, and so is the log of your agents' runs. For your prospecting campaigns, Bluelake keeps one record per prospect (the step, the dates, the status, and the identifiers of the CRM record and of the e-mail thread, never an e-mail address, a phone number or the text of a reply), with its tasks and its log, for as long as your account exists. Your team's company page is kept for as long as your team's workspace exists. Your exports and their files are kept for as long as your account exists. Your data exports, and your team's, are deleted after 30 days, or with the account that prepared them if it goes first; the record of each export is kept for as long as that account exists. In the demo of Billy, each link, with its conversation and its counts, is kept until 30 days after it expires or is revoked, with up to 38 more days in our backups. 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 backups of the database and files are deleted after 30 days, and erased for good within 8 more days.
When your team's manager deletes the team's workspace ("Delete the team's workspace"), access closes at once for every member, and each member receives an e-mail. The connections to Google and Slack are removed at once. The accounts and all the team's data, including the contact details found, the unlocks and the CRM settings and keys, are permanently erased within 30 days; during these 30 days, the team can be restored by writing to privacy@getbluelake.ai, and its connections must then be made again. When the last member of a company closes their account, the company's data is erased with it, within the same 30 days.
8. Your rights
You have the right to access, rectify, erase, object to, restrict and port your data. You can download your data yourself at any time from My profile ("Download my data"). Exercise these rights at privacy@getbluelake.ai. You may also lodge a complaint with the CNIL (the French supervisory authority). Your conversation in the demo of Billy is kept with your link: you can ask us for a copy of it or for its deletion.