Skip to content

Security and data

Version of

Here is how WYRLO protects the data your company’s assistant sends it. This page describes the service as it works today.

The essentials

  • Your documents stay with you: WYRLO never stores them.
  • Question history is masked (on by default), then kept 30 days by default (90 or 180, your choice).
  • Processed in France and the European Union; database in Paris.
  • No AI is trained on your data.
  • Access restricted to your organisation, with roles per member.
  • Data processing agreement (GDPR) available.
  • Certifications: none yet, and no external audit.

When the assistant opens

The assistant for companies is coming soon. When it opens, it will follow these rules, which will then be written into our legal terms:

  • Your documents stay in your tools: we never copy them. The assistant reads them at question time, then forgets them.
  • Read-only: it can neither change, delete nor share your files.
  • One base per company: your administrators choose the files the assistant reads for everyone, and can remove some or disconnect everything at any time. We keep the list of these files (name, folder, dates), never their content.
  • An employee never sees other people’s questions.
  • Access to your tools is stored encrypted; the short excerpts used to check an answer are kept 30 days, masked.

The details, for your IT and data protection teams

The path of your data

Your assistant

Your documents stay there: WYRLO never stores them.

question, excerpts, answer

WYRLO API

Paris (eu-west-3). A request received in another region is refused without being read.

during processing

Inference server

France (OVHcloud). Masking personal data before storage; no text kept.

Mistral AI

European endpoint: European Union and EFTA, according to Mistral AI. Checks answers in French and English: an excerpt of 600 characters at most, masked beforehand by Presidio.

masking

Masked history

30 days by default, 90 or 180 at your organisation’s choice, then deleted overnight.

Subprocessors

The facts

Hosting
Paris (eu-west-3 region) for the database and functions
Documents
Never stored
Question history
Masked, kept 30 days by default (90 or 180, your choice)
Encryption
In transit (HTTPS) and at rest (AES-256 for the database and its backups, at Supabase)
Access
Restricted to your organisation
Training
None: your traces train no model, neither ours nor a third party’s.
API keys
Stored as a fingerprint, shown only once, revocable at any time.
Tracking
No non-essential cookie or tracking tool, on the website or in the customer workspace.
Certifications
None yet, and no external audit. Supabase and Vercel publish their own reports.
Data processing agreement
Request the data processing agreement

The details

Where your data is

  • Database and WYRLO functions (API, waitlist, improvement loop): Supabase, eu-west-3 region (Paris). The API processes every request in Paris: a request received in another region is refused without being read.
  • API address (api.wyrlo.io): Scaleway relay, fr-par region (Paris). It forwards each call to WYRLO’s functions in Paris, enforces the Paris region, and neither stores nor logs the content of calls. Calls then go through the network of Cloudflare, Supabase’s provider, to the functions in Paris.
  • Inference server (masking personal data before storage): OVHcloud, in France. It does not keep the texts.
  • Checking French and English answers: Mistral AI, a French company, through its European endpoint (inference in the European Union and EFTA countries, according to Mistral AI). Mistral AI only receives texts masked beforehand by the inference server.
  • Web application: Vercel, functions in the cdg1 region (Paris).
  • Other providers and processing locations: see the Subprocessors page.

Your documents are never stored

For each question, WYRLO receives the question, excerpts of the passages retrieved by your RAG, and the answer. Your documents stay with you: we never copy or index them.

Your data trains no model

WYRLO never uses your traces (questions, passage excerpts, answers) or your documents to train or fine-tune AI models, whether ours or a third party’s. They are used only to provide the service to your organisation: answer checking, the improvement loop specific to your organisation, which measures the effect of its settings on your own questions, and the weekly report.

This commitment is set out in the terms of use and in the data processing agreement.

Trace masking, limited retention

If your organisation has enabled masking (enabled by default), traces are masked before storage: email addresses, phone numbers, IBANs, bank card numbers and French social security numbers (NIR) are detected and replaced, with no guarantee of completeness. 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”). Only the 3 best passages keep an excerpt, of 600 characters at most.

They are kept for 30 days by default, then deleted automatically every night. Your organisation can choose 30, 90 or 180 days.

Encryption

Data is encrypted:

  • in transit: HTTPS (TLS) is mandatory between your application, the library, the API, the customer workspace and our hosting providers. An API call is decrypted and re-encrypted by the Scaleway relay (Paris) and by the network of Cloudflare, Supabase’s provider, to be forwarded; neither keeps its content for WYRLO;
  • at rest: AES-256 encryption of the database and its daily backups, kept for 7 days, by our hosting provider Supabase.

Strict isolation between organisations

Each organisation only sees its own data. Isolation is enforced by access rules at database level, not just in the application code: a query can only read rows that belong to the signed-in person’s organisation.

API keys

  • An API key is shown only once, when it is created.
  • Only its hashed fingerprint is stored: the key itself cannot be read back, not even by WYRLO.
  • A key can be revoked at any time in the project’s integration page; create a new one to replace it.

Activity log

Sensitive actions, such as creating an API key or changing a setting, are recorded in an activity log with who did them and when.

The log records the creation, modification and deletion of organisations, members and roles, invitations, projects, API keys, reliability settings and fixes. It can be viewed by the organisation’s owners and admins, and is kept for 1 year, then deleted automatically.

Website and browser

The website uses no non-essential cookies and no tracking tools. It enforces HTTPS, refuses to be displayed inside third-party pages and limits the information passed on to other sites.

Certifications and audits

WYRLO does not have any certification or external security audit yet. Its main hosting providers, Supabase and Vercel, publish their own compliance reports.

Report a vulnerability

Think you have found a security flaw? Write to contact@wyrlo.io with a description of the issue and the steps to reproduce it.

Please do not make the vulnerability public before it is fixed. We acknowledge receipt within 5 working days and keep you informed until it is fixed.

Your RAG deserves a second reading.

Access to the API is opening gradually.

  • Free to get started
  • Database hosted in Paris
  • Your RAG answers even if WYRLO does not