This document is not available for printing. Read it online: www.wyrlo.io/en/confidentialite
Privacy policy
This policy explains which personal data WYRLO processes, why, for how long, and what your rights are. It covers the public website and the WYRLO service.
Who is responsible
For account and website data, the controller is Mayeul FLORY, sole trader (entrepreneur individuel; trade name: FUSION-IA), publisher of WYRLO, 49 chemin des Verrières, 69260 Charbonnières-les-Bains, France, reachable at contact@wyrlo.io.
For traces sent to the WYRLO API, and for the questions your company’s members ask its assistant, your organisation remains the controller. WYRLO acts as a processor within the meaning of article 28 of the GDPR, under the data processing agreement.
Data protection officer
WYRLO has not appointed a data protection officer. For any question about your personal data, write to contact@wyrlo.io.
Data we process
- Account data: name, work email address, organisation, role in the organisation, role given at sign-up (founder, developer…), sign-in information, email language (French or English, taken from the browser language at sign-up, editable in Account, Emails section).
- Sign-in with Google, if you choose it: Google sends us your name, email address, profile picture address and Google account identifier. This information is used only to create your account, sign you in and show your name to the members of your organisations; it is kept with your account, is never sold or passed on to third parties, and is used neither for advertising nor to train AI models. WYRLO’s use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- Breached password check: at sign-up and when changing a password, your browser sends the Pwned Passwords service of Have I Been Pwned the first 5 characters of the password’s SHA-1 hash, never the password or its full hash (k-anonymity).
- Invitations: email address of the people invited to an organisation. The invitation link is passed on by the person who invites; WYRLO does not send it by email.
- Launch waitlist, if you ask to be told: email address and, if you provide them, organisation and intended use (500 characters at most), page language, date of the request and date of confirmation (click on the link received by email; the link carries a random token of which only a fingerprint is kept); to limit abuse, a fingerprint of your IP address (computed with a secret key; the address itself is not stored) and the time of each request.
- Traces: the question asked, the answer produced, the confidence level and the decision; for each passage retrieved by your RAG, its identifier, its source (name of the original document) and its scores, and for the 3 best passages only, an excerpt of 600 characters at most. If your organisation has enabled masking (enabled by default), the following items are detected and replaced before storage, with no guarantee of completeness: email addresses, phone numbers, IBANs, bank card numbers and French social security numbers (NIR). Names of people and other entities are detected by the inference server (Presidio, open-source software), then the local rules apply on top; each passage’s source is masked by the local rules. No text is stored unless it has been fully masked by the inference server: texts already masked for the check by Mistral AI are reused as they are; otherwise, the trace is masked after the answer and, if that server is saturated, masking is retried for 30 seconds at most; beyond that, the trace is stored without any text (scores, decision and timings only, marked “text not kept”).
- Your company’s assistant, if your organisation uses it: each question asked by a member is recorded as a trace (question, answer, confidence level and decision, names of the documents cited, an excerpt of 600 characters at most from the 3 best passages), with the same masking, in a project reserved for the assistant. A member’s feedback on an answer (helpful or not) is recorded without any text. The documents themselves are never copied: the assistant reads them at the time of the question, then forgets them.
- Company knowledge base (Google Drive), if an owner or administrator of your organisation links it: the address of the linked Google account, the date it was linked, the person who linked it and the long-lived access issued by Google, encrypted before it is recorded (the encryption key is not in the database). This access only covers the files and folders the administrators choose in Google’s window (“drive.file” permission); WYRLO only reads them. WYRLO keeps the list of these items (Google identifier, name, type, parent folder, dates added), never their content: the files are never copied and the search results are not kept. Only the names of the documents cited and short masked excerpts are kept with each question (see “Your company’s assistant”). The address of the linked account and the list of files are only visible to owners and administrators; the other members only see whether the base is linked and how many files it contains. Information received from Google Drive is used neither for advertising nor to train AI models. WYRLO’s use and transfer of information received from Google APIs, including Google Drive, adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- Passage fingerprints: to recognise a passage already analysed without keeping its text, WYRLO keeps a digital fingerprint (SHA-256) of the passage, a numeric representation (vector) computed on its beginning and its security verdict (injection detected or not).
- Improvement loop analyses: failure groups, missing topics and suggested fixes, which include example questions (masked if masking is enabled); weekly reports (topics and figures).
- Weekly report sent by email: the recipient’s email address, the organisation and project names, and aggregated indicators for each project (score, change since the previous week, number of questions analysed, of “I don’t know” answers, of automatic fixes applied, of missing topics and of fixes to make on your side), with a link to the report in the customer workspace. The email contains no excerpt of any question, answer or passage, and no topic name.
- Monthly cap warnings, by email: address of owners and admins, organisation name, number of analysed questions and the month’s cap. No excerpt of any question or answer.
- Activity log: sensitive actions performed in your organisation, with who did them and when.
- Support exchanges: your messages to contact@wyrlo.io (directly or through the “Need help?” button) and our replies; the questions asked to the help assistant and its answers.
- Billing data, if you subscribe to a paid plan: name or company name, billing address, VAT number where applicable, billing email address, plan subscribed, amounts, dates and status of payments, invoices. Payments are processed by Stripe: WYRLO never receives or stores your full card number, only limited information (card type, last four digits, expiry date) so that you can recognise the saved payment method. No paid plan is open yet.
- Technical logs needed to run and secure the service: at our hosting providers, IP address, approximate location derived from that address (country, region, city, network operator), date and time, requested address, response code, browser and a technical fingerprint of the encrypted connection; for the API, the first 10 characters of the API key (never the whole key) and information about each request (organisation, decision, processing time, language), never the content of questions, passages or answers. Calls made through api.wyrlo.io reach Supabase with the relay’s IP address, not yours.
Your documents are never stored: WYRLO only receives the excerpts sent with each question.
Purposes
- Providing the service: checking answers against their sources, computing the confidence level, and deciding whether to answer or say “I don’t know”.
- Answering the questions asked to your company’s assistant: searching the company knowledge base, that is the documents its administrators have chosen in the linked tools (Google Drive), drafting an answer, then checking it against its sources before displaying it.
- Answering the questions asked to WYRLO’s help assistant, from our help centre: the question is masked by our inference server, then an answer is drafted and checked against the help centre’s answers before it is displayed.
- Adjusting your organisation’s settings from its own traces (every night, or every week for the current access), and producing the weekly report.
- Proposing improvements to your company’s assistant, if WYRLO enables them for your organisation: every night, analysing the masked questions and their answers, then proposing settings that the owner, an administrator or a developer approves or dismisses. Nothing is applied without this approval. If your organisation turns off masking, the improvements stop.
- Sending the weekly reliability report by email, on Mondays, when it flags something (a correction applied, a missing topic, a fix to make on your side, a score drop): by default to the organisation’s owner only; each member chooses whether to receive it in Account, Emails section.
- Managing your account, your organisation and, where relevant, your subscription.
- Invoicing paid plans, collecting payments through Stripe, handling failed payments and, where necessary, recovering amounts due.
- Keeping the service secure and preventing abuse: Cloudflare Turnstile anti-bot check on sign-in, sign-up and forgot password; number of requests limited per IP address, in particular on the waitlist.
- Confirming your address and then telling you when WYRLO launches, if you ask: one confirmation email, then a single email at the launch, no marketing. Your address is only added to the list after you click the confirmation link.
- Responding to your requests.
WYRLO does not use traces, nor the documents read by the assistant, for any other purpose, and in particular not to train AI models.
Legal bases
- Performance of the contract: providing the service (including sending the weekly report by email), managing your account, subscribing to, paying for and invoicing paid plans.
- Pre-contractual steps taken at your request: launch waitlist.
- Legitimate interest: security of the service, abuse prevention, activity log, replies to support requests, recovery of amounts due.
- Legal obligation: issuing and keeping invoices and accounting records.
- No processing is based on your consent: the website uses no cookie or tracker that would require it.
- An email address and a password, or signing in with Google, are required to create an account: without them, the account cannot be created. Your name is optional. To be told about the launch, only the email address is required.
Retention periods
- Traces: 30 days by default, then deleted automatically every night. Your organisation can choose 30, 90 or 180 days.
- Questions asked to your company’s assistant: like traces, 30 days by default, or 90 or 180 days as chosen by your organisation, then deleted automatically every night. Members’ feedback on answers (helpful or not, without any text): deleted with the corresponding question; feedback not linked to any question after 2 days is deleted.
- Company knowledge base (Google Drive access and list of files): until an administrator disconnects it, which also revokes the access at Google. A file or folder removed from the base is erased from the list at once. When the person who linked the base leaves, deletes their account, or when the organisation is deleted, the access is revoked at Google within 15 minutes, then erased; if Google does not answer, WYRLO retries and keeps the encrypted access for 7 days at most. Exception: if that person still uses Google Drive with WYRLO in another organisation, the access is only erased, without being revoked at Google. In all these cases, WYRLO also erases everything that came from this Drive: the list of files, the text-free index, the questions whose answer cited these documents and the improvement proposals that relied on them. Backup copies, kept for 7 days, then disappear.
- Passage fingerprints and security verdicts, without the text: same period as traces, counted from the last time the passage was received, then deleted automatically every night.
- Example questions included in the improvement loop’s analyses: removed at the same time as the corresponding traces. Analyses (failure groups, missing topics, fixes) and weekly reports, which keep only the titles of topics and fixes: for as long as the service is used, then deleted with the organisation; a topic or group that has no example left and does not come back for 180 days is deleted automatically.
- Inference server access logs: 14 days. The texts processed by this server (questions, passages, answers) are not kept.
- Accounts and organisations: for as long as the service is used. Anyone can delete their account at any time in Account, “Delete my account” section: it is then erased immediately, with its profile and memberships; if the person had linked a company knowledge base, that base is disconnected and everything that came from it is erased (see “Company knowledge base” above). An organisation’s owner can delete it at any time in Organisation, Data section: its data is then erased immediately. An account closure requested at contact@wyrlo.io is carried out within 30 days. Backups, kept for 7 days, then disappear.
- Sign-ins: sign-in sessions are deleted after 90 days without use (you then sign in again); confirmation, sign-in and password reset links: 7 days; unfinished sign-in requests: 1 day; then deleted automatically.
- Invitations: the invited person’s email address is kept until 30 days after the invitation ends (accepted, cancelled or expired), then deleted automatically; it remains in the activity log until 1 year after the invitation was sent. The invitation link expires after 7 days.
- Activity log: 1 year, then deleted automatically.
- Launch waitlist: unconfirmed request, 7 days after the request; confirmed request, until the launch of the assistant for companies (the day we write to you), then three months after the launch if you have not created an account, or 30 days after your access opens if you have one, and in any case at most 12 months after the request, then automatic deletion. You can ask to be removed at any time by writing to contact@wyrlo.io. IP address fingerprints of requests: 24 hours.
- Invoices: 10 years, under French accounting obligations (article L. 123-22 of the French Commercial Code). No invoice is issued until a paid plan is subscribed.
- Billing data other than invoices: for the duration of the subscription, then 5 years after it ends, the limitation period for claims between businesses (article L. 110-4 of the French Commercial Code).
- Support exchanges: 3 years after the last contact.
- Questions asked to the help assistant: the masked question, the answer and the verification decision, 30 days, then deleted automatically every night; the date of the question, 24 hours (limit of 5 questions a day).
- Database backups: daily, encrypted and kept for 7 days by our hosting provider Supabase. Deleted data disappears from them within 7 days at most.
- Emails sent and sending logs, at our email provider (Brevo): 30 days (period set in our Brevo account), then deleted.
- Technical logs at our hosting providers: 7 days at Supabase (API gateway, authentication, functions and database) and 1 hour for function logs at Vercel. Supabase keeps its logs on its logging infrastructure, hosted by Google, whose storage location is not guaranteed to be in the European Union; any transfers are covered by standard contractual clauses (see the Subprocessors page).
Recipients and subprocessors
Data is only accessible to authorised people at WYRLO and in your organisation, and to the technical subprocessors that help us provide the service. The list of subprocessors, their role, the data concerned and where it is processed is on a dedicated page.
Within your organisation, the questions asked to the assistant are read by no one in the application, neither by the other members nor by the administrators. Exception, if WYRLO enables assistant improvements for your organisation: the owner, administrators, developers and viewers see, in each proposed improvement, at most 5 example questions, automatically masked (names, email addresses, numbers…) and without their author’s name, as well as the titles of the topics and corrections drawn from them; members do not see them. The examples are deleted with the questions (30 days by default). Each person’s access to Google Drive is visible only to them. The Developers area only shows the questions received through the API.
Some of these providers are established outside the European Union or may process data there, in particular Vercel and Cloudflare (United States), Brevo for its delivery network and a group company, as well as Supabase for its technical logs, kept at Google with no guaranteed location in the European Union. These transfers are covered by the European Commission’s standard contractual clauses and, for certified US companies, by the EU–US Data Privacy Framework, according to these providers’ contracts. You can obtain a copy of these safeguards by writing to contact@wyrlo.io.
For paid plans, Stripe processes payments on behalf of WYRLO. For its own purposes, in particular fraud prevention and compliance with its legal and regulatory obligations, Stripe acts as an independent controller, under its privacy policy. Each provider’s privacy policy is linked from the Subprocessors page.
Your rights
The GDPR gives you the following rights over your data:
- access;
- rectification;
- erasure;
- restriction of processing;
- objection;
- portability;
- instructions on what happens to your data after your death.
Without writing to us, you can download a copy of your account data and delete your account from the Account page. To exercise your other rights, write to contact@wyrlo.io. We reply within one month.
For data contained in traces, contact the organisation that uses WYRLO first: it is the controller, and we help it respond to you.
WYRLO makes no decision that produces legal effects concerning you, or similarly significantly affects you, based solely on automated processing (Article 22 GDPR). The “answer” or “I don’t know” decisions concern the answers of a customer organisation’s RAG, which remains responsible for them.
If you believe your rights are not being respected, you can lodge a complaint with the French data protection authority, the Commission nationale de l’informatique et des libertés (CNIL), 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, or online at cnil.fr, or with the data protection authority of your country of residence in the European Union.
Security
The technical and organisational measures that protect your data are described on the Security page.
Changes
This policy may change. The date of the current version is shown at the top of the page. In case of a significant change, we notify account holders by email before it takes effect.