Privacy policy

This English translation is provided for convenience. The French version is the legally binding text: Politique de confidentialité (French).

This policy describes how Salesia processes personal data through its salesia.fr website and its platform, in accordance with Regulation (EU) 2016/679 (the GDPR, RGPD in French) and the French Data Protection Act (loi « Informatique et Libertés »).

Data controller

The data controller is Salesia (see the Legal notice). For any question about your data or about exercising your rights: hello@salesia.fr.

The data we collect

1. Demonstration request / prospect

When you request a demonstration or leave your details on the landing page, we collect:

• your work email address and your telephone number (both required);
• the name and website URL of your brand, where they are provided;
• the record of your consent, together with technical data (IP address, browser type) for security and evidential purposes.

Purpose: to get back to you, arrange a demonstration and present the service. Legal basis: your consent (and Salesia's legitimate interest in developing its B2B business).

2. User account (customers)

When an account is created, we process your email address, your identity and your sign-in data (including through Google if you choose that option). Purpose: to provide and secure access to the service. Legal basis: performance of the contract.

3. Business data processed on your behalf

As part of the use of the platform (CRM, orders, catalogue, pharmacies, agents), Salesia processes data on behalf of the client brand. For that data, the brand is the data controller and Salesia acts as a processor, under the conditions set out in the contract (article 28 of the GDPR).

4. Personalised demonstration

When you enter the URL of a website to personalise the demonstration, Salesia retrieves publicly accessible information from that site (name, logo, images and product prices) to populate the demo. Those elements are stored locally in your browser and do not create an account; you can erase them at any time with the “Réinitialiser” (reset) button or by clearing local storage.

Connected Google services (Gmail and Google Calendar)

From the Calendar page of the platform, a user may choose to connect their Google account to Salesia. This connection is optional, separate from signing in to the service, and relies on two distinct permissions that the user grants or declines independently of each other.

• Google Calendar (“calendar.events” permission): Salesia creates, updates and deletes, in the user's calendar, the events that match the visits and calls planned in Salesia, and reads the state of those events back to keep them up to date. When the user runs the import of their calendar themselves (the “Import from Google Calendar” button), Salesia reads the events of their primary calendar over the past twelve months and the next twelve (title, description, location, times, organizer and attendees with their names and email addresses) to suggest the ones that match an appointment with a client. The email addresses, phone numbers and postal addresses found in the event are compared with the client records and contacts of their company in Salesia. In the same way, when the user displays their own calendar in Salesia, the Google events of the period displayed are read and shown to them alone, next to their Salesia appointments; they are never shown to any other user. Nothing from that read is kept, except for the events the user chooses to attach to a client: Salesia then stores the date, duration, title and Google identifier of the event, and never modifies the original event. An event the user chooses to ignore receives, on their copy of the calendar, a private marker so it is not suggested again. Salesia does not access contacts or calendar settings.
• Gmail (“gmail.send” permission): Salesia sends, from the user's own mailbox, the emails the user composes and submits in Salesia (visit report, performance report), so that the recipient receives a message from their usual contact and can reply to it. Salesia never reads, lists, searches or modifies the content of the mailbox, and does not access contacts.

Data obtained and retention. Salesia keeps only the access token issued by Google and the identifiers of the calendar events it created, on its servers in the European Union, for as long as the connection lasts. An event the user chooses to attach to a client becomes a visit recorded in Salesia: its date, duration, title and Google identifier are kept like any other visit, including after Google is disconnected, until the user deletes the visit. That data is used solely to provide the two features above. It is never sold, never passed on to third parties, never used for advertising, and never used to train artificial intelligence models. No member of the Salesia team accesses users' Gmail mailboxes or Google calendars.

Revocation. The user can withdraw each permission at any time, from the Calendar page in Salesia (“Déconnecter” button) or from the permissions page of their Google account (myaccount.google.com/permissions). Salesia then immediately stops using the access concerned.

Artificial intelligence. Salesia uses a single third-party AI service, ElevenLabs, to transcribe the voice notes a sales rep dictates from their own device. No data received from Google APIs — raw, aggregated, anonymised or derived — is passed to it, nor to any other artificial intelligence or machine learning service, and none is used to create, train or improve a model, generalised or specialised. The “gmail.send” permission grants no read access to the mailbox in any case, and Salesia only reads back the calendar events it wrote there itself.

Salesia'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.

The mobile app and offline data

The mobile app for field sales reps is built to work without a network. It therefore keeps a copy of the rep's portfolio data on the device (points of sale, orders, appointments), together with the queue of actions entered offline and waiting to be sent, and the photos and voice notes taken during a visit for as long as they have not been uploaded. Those files live in the app's private area, which the operating system isolates from other apps; the session token is kept separately, in the phone's secure store (Keychain on iOS, Keystore on Android).

This local copy is erased in full when the rep signs out themselves, and when the app is uninstalled. When the session is invalidated remotely, the actions entered but not yet sent are deliberately kept on the device, so that work only the rep holds is not destroyed; they go at the next sign-out. It is for the brand, as data controller, to require device locking on the phones it issues.

The app asks for three phone permissions, each when it is first needed and each optional:

• Location, to sort points of sale by distance and centre the map. It is read once at a time, only while the app is in use, stays on the device and is sent neither to Salesia nor to the brand.
• The microphone, for three distinct uses. Dictating a report or a field: the audio is sent to our transcription processor and then erased; only the text is kept. Searching for a customer by voice: this uses the phone's own speech recognition service (Apple or Google), under that service's terms, and nothing is sent to Salesia. Recording a visit: before starting, the rep confirms that the person they are meeting has agreed to the recording; the audio is kept in a private area for as long as it takes to transcribe it, telling the speakers apart, and to turn it into a draft report with a language model; the recording is then deleted, whether or not the drafting succeeded, and only the draft, which the rep reads and corrects, is kept. The brand, as data controller, is responsible for informing the people recorded.
• The camera and photo library, to attach photos (shelf, window display, point-of-sale material) to a visit report and the documents (bank details, company registration) of a new customer. These files are stored with the brand's other documents.

Declining a permission only disables that one feature.

Recipients and processors

Your data is never sold. It is accessible to the authorised Salesia team and to our technical processors, strictly for the purposes above:

• Neon — database (hosted in the EU, Frankfurt);
• Render — hosting of the website and the API;
• Cloudflare R2 — storage of files and images, in EU-jurisdiction buckets;
• Resend — transactional email delivery;
• Mapbox — map display;
• ElevenLabs — transcription of the voice notes dictated and the visits recorded in the mobile app;
• Anthropic — drafting of visit reports from the visit transcripts, and the platform's analysis assistant; used through its API under a commercial agreement, with no reuse of the data to train its models;
• Yousign — electronic signature of documents;
• Sentry and New Relic — technical monitoring (error reports and performance measurements, which may contain technical identifiers);
• PostHog (hosted in the EU, Frankfurt) — usage measurement of the platform, described below.

Authentication is handled by our own servers and by the database above. No third-party identity provider is involved, apart from signing in with Google when you choose that option.

Recipients chosen by the client brand. When a brand connects one of its own tools to Salesia (Sellsy, HubSpot, Pennylane, Shopify, Aircall, e-Logik, Alloga), it does so with its own credentials, and data flows to that tool on its instruction. Those services are the brand's providers, not ours; their use of the data is governed by their own privacy policies.

Transfers outside the European Union

The main database is hosted in the European Union. Some processors are established in the United States; any transfers are framed by the European Commission's standard contractual clauses and/or by certification under the Data Privacy Framework, which guarantee an adequate level of protection.

Usage measurement of the platform

To improve the product, Salesia measures how the platform is used, with PostHog, hosted in the European Union. Two levels:

• Actions accomplished, counted by our servers: an order entered, a visit report submitted, a call logged, a question asked of the analysis, an import finished. Each event carries only a technical user and brand identifier, the category of the action and a few counts. No name, no email address, no client, pharmacy or product name, no amount and no free text ever leaves our servers. Legal basis: Salesia's legitimate interest in understanding and improving its product.
• Screens viewed and a session recording, only if you accept it in the app: a card in a corner of the screen offers it, with "Accept" and "No thanks" equally easy, and you can change your mind at any time in the app's Settings. The recording masks every text and every input: only the layout of the screens, the navigation and the clicks remain visible. Page addresses are reduced to their generic form before being sent. Nothing is loaded or measured until you have accepted. Legal basis: your consent.

This data serves Salesia's product decisions. It is never shown in the platform, never passed on to the brand that employs or mandates you, and never used to assess a person. Your choice is kept on your device, in the browser's local storage.

Retention periods

• Prospects: 3 years from the last contact (recommendation of the CNIL, the French data protection authority, for B2B prospecting).
• Accounts and business data: for the term of the contractual relationship, then archived in line with the applicable legal obligations.
• Sign-in data / logs: 12 months maximum.
• Usage measurement: session recordings 30 days; usage events 25 months maximum.

Your rights

You have the rights of access, rectification, erasure, restriction of processing, objection and portability, as well as the right to withdraw your consent at any time and to set instructions on what happens to your data after your death.

To exercise them, write to hello@salesia.fr or by post to Salesia, 16 rue de Picardie, 75003 Paris. You may also lodge a complaint with the CNIL (cnil.fr).

Cookies and trackers

The website uses only cookies and local storage that are strictly necessary for it to work: authentication (session) and remembering how the demonstration was personalised. No advertising cookie and no third-party tracker for targeting purposes is set. In the platform, the usage measurement described above sets no cookie and is only switched on after your consent, collected in the app.

Security

Salesia implements appropriate technical and organisational measures: encryption of data in transit (TLS), hosting of the database in the European Union, strict separation of the data of each brand and access restricted to authorised people.