Skip to content

Sillage

Privacy policy

Last updated: 11/13/2026

1. Data controller

The data controller is Breakloop Studio, publisher of the Sillage app, reachable at contact@breakloop.fr. Full contact details are available in the legal notice.

2. Data we collect

2.1 Account creation

When you create an account (optional), we collect your email address. The app does not handle any password: you sign in with a single-use code sent to that address, or with Google.

If you use Google sign-in, we receive the name, email address and profile photo associated with your Google account.

2.2 Use of the app

As part of using the features, we store:
• Your favorite perfumes (hearts)
• Your perfumery (statuses, verdicts, personal notes, shelves, possessions)
• Your scent of the day (SOTD)
• Your scan history
• Your preferences (notifications, price alerts)
• Your tastes, if you declare them: the scent families you like, the accords you prefer to avoid and the perfumes you set aside (“Not for me”)
• The perfumes you prefer in the “this or that” duels, if you answer them
• Your gender and age range, if you provide them

2.3 Bottle scanning

When you scan a bottle, the photo goes to our server, then to OpenAI to identify the perfume. It is sent in full: avoid including a person or a document in it. Sillage first removes its metadata (location, date, device model) and does not send OpenAI your name, email address or account identifier. Our servers do not retain this photo. OpenAI may retain it for up to 30 days, under the conditions described in 4.2.

2.4 Push notifications

If you enable notifications, a notification token (Expo Push Notifications) is stored to send you price alerts and, if you enable them, weather-related suggestions. You can turn off these notifications at any time in the settings.

2.5 Local data

Certain preferences (theme, display density, views) and your recent searches are stored locally on your device via AsyncStorage. No sensitive data (password, contents of your perfumery) is stored locally: this is hosted on our servers.

Your declared tastes (liked families, accords to avoid) and the list of perfumes you set aside are also stored on your device. As soon as an account exists (guest accounts included), a copy is saved on our servers so you get the same suggestions on your other devices. Signing out erases the copy on the device; the copy in your account stays until the account is deleted. Your answers to the “this or that” duels follow the same path: only the identifiers of the perfumes you preferred are copied to our servers.

2.6 Location (weather)

If you enable weather suggestions, your approximate location (rounded to ~1 km) is used to show the local weather and adapt perfume suggestions. It is requested only after your explicit consent, never collected without your knowledge, and can be erased at any time (Settings → Privacy & data). The weather service is provided by MET Norway (api.met.no), Norway.

2.7 Device identifier

The analysis features (scan, voice dictation, concierge, look of the day) query an artificial intelligence model and have a cost. To prevent several accounts from being created on the same device in order to multiply the free quotas, we read a device identifier provided by the operating system (Android: the identifier specific to our signed application on that device; iOS: the identifier for vendor) and convert it, as soon as our servers receive it, into a non-reversible fingerprint by salted hashing. Only that fingerprint is recorded, together with the number of analyses of the day, and it is automatically deleted after 7 days. The raw identifier is neither stored, nor displayed, nor passed to any third party; it does not identify you by name and is used neither for advertising nor for tracking across applications. Legal basis: our legitimate interest in preventing abusive use of a service that has a cost. This identifier stays within the hosting infrastructure described in section 4.1, so no new recipient appears. It changes after a factory reset of the device.

2.8 Public profile

Every account gets a username, picked at random from a list of words: the service needs one to work. You can change it at most once every 30 days; your previous username then stays reserved for you for 30 days, so that no one else can take it. You can also add a photo and a one-line bio.

Your profile is private by default. If you make it public, other members see your username, photo, bio, reviews, the notes you love, the houses you follow, your followers and the people you follow. Your collection only appears if you also turn on “Show my collection”. You can make your profile private again at any time.

Your name and email address are never shown on your profile. A member can report a public profile: its username and bio are then checked again (4.2).

3. Legal bases for processing

Processing is based on the following legal grounds:
• Consent: account creation, Google sign-in, camera scanning, push notifications, weather suggestions (approximate location), public profile (2.8)
• Consent (microphone): voice dictation (4.6)
• Performance of a contract: saving your favorites and your perfumery, your account’s username (2.8)
• Legitimate interest: theme preference (local storage only), reserving your previous username and profile reports (2.8)
• Consent (optional): declared tastes and perfumes you set aside, gender and age range

4. Data recipients

4.1 Hosting and authentication (Supabase)

Authentication, the database, image storage and server functions ("Edge Functions") are provided by Supabase (PostgreSQL database). Your account data, favorites and perfumery are hosted in Supabase's Europe region.

Push notifications are delivered via the Expo Push Notifications service (Expo / 650 Industries, United States).

Supabase and Expo apply the European Commission's Standard Contractual Clauses (SCCs) for data transfers outside the European Union.

4.2 OpenAI

OpenAI analyzes, on behalf of Sillage, bottle photos (scan), the outfit photo (look of the day), concierge text, dictation audio when the system's own dictation returned nothing (4.6), the profile photo before it is published, the profile bio each time it changes, and review text when it is published. When something is reported, it also analyzes the reported review, or the username and bio of the reported profile. This content leaves from our server: OpenAI does not receive your name, email address or account identifier. A photo, a voice or a text can still identify you on its own.

According to OpenAI's documentation, this content is not used to train its models. It may remain for up to 30 days in its abuse monitoring logs and is then deleted, unless the law requires keeping it longer or this is reasonably necessary to protect its services or third parties. During that time, authorized OpenAI employees and specialized contractors bound by confidentiality may access it, in particular to review abuse. Dictation audio does not enter these logs.

The OpenAI API key is stored exclusively on the server side (Supabase Edge Functions) and is never exposed to the client.

4.3 Perfume catalog

Perfume data (brand, name, olfactory notes, price) is hosted in our PostgreSQL database (Supabase). Searches are performed within our catalog of more than 100,000 perfumes, hosted on our servers; no personal data is sent to any third-party service for these searches. This guarantee applies to searches typed on the keyboard: a dictated search involves the recipients described in section 4.6.

4.4 Google Sign-In

If you choose Google sign-in, a standard OAuth authentication token is exchanged with Google's servers.

4.5 MET Norway (api.met.no)

MET Norway (api.met.no, Norway) provides the weather data and for that purpose receives your coordinates rounded to ~1 km along with your IP address, with no account identifier or other data. Norway is part of the European Economic Area: the GDPR applies there directly, without an adequacy decision.

4.6 Voice dictation

Your voice is processed by your system’s speech recognition service — Apple on iOS, Google on Android. Sillage does not enforce device-only processing: depending on the language and the device, your voice may transit through their servers. The transcribed text is sent to our server and then to OpenAI to interpret the atmosphere you describe; if system dictation returned nothing, the audio itself may also be sent to OpenAI. The audio is deleted from your device at the end of the dictation, and our servers do not retain the transcription. The text sent to OpenAI follows the rules in section 4.2; according to its documentation, OpenAI does not keep transcription audio in its logs. Apple and Google are US companies: these transfers are covered by the European Commission’s standard contractual clauses and, for Google, by the Data Privacy Framework.

4.7 Sending emails (Brevo) and the contact mailbox (OVH)

The authentication emails (the six-digit sign-in code, the sign-in link) and the code sent by the account deletion web page are routed through an SMTP relay operated by Brevo SAS (Paris, France — European Union). Brevo receives the recipient address, the content of the message (including the language it is rendered in) and the sending domain; no other data about your account is passed on.

This relay inserts an open-tracking pixel in every email and wraps links in order to measure opens and clicks: Brevo can therefore tell that a message was opened, when, and which link was followed. This tracking concerns the email itself, which carries no commercial content. None of this data comes back into the application: Sillage imports no statistics from Brevo and associates no open with your account.

The domain mailbox (contact@breakloop.fr, as well as the report address sillage@breakloop.fr) is hosted by OVHcloud (France — European Union) and then forwarded to the editor's work mailbox at Google (United States — a transfer covered by the Data Privacy Framework, see section 5). A message sent through "Report a problem" never passes through a Sillage server: the draft is built on your device and sent from your own email app.

5. Transfers outside the European Union

Supabase, Expo, OpenAI and Google (Google sign-in) are US companies. However, the core data is hosted in Supabase's Europe region, and these transfers are governed by:
• The Data Privacy Framework (DPF) for Google
• The European Commission's Standard Contractual Clauses (SCCs)
• Storage of core data in Supabase's Europe region

6. Retention period

• Account data: until the account is deleted
• Favorites and perfumery: until manually deleted or the account is deleted
• Scan history: until manually deleted or the account is deleted
• Content sent to OpenAI: up to 30 days at OpenAI, with the exceptions described in 4.2; scan and look photos and concierge text are not retained on our servers
• Voice dictation: audio deleted from your device at the end of the dictation, transcription not retained on our servers (4.6)
• Notification token (Expo Push): until notifications are disabled or the account is deleted
• Local preferences: stored locally until the app is uninstalled

7. Your rights (GDPR)

In accordance with the General Data Protection Regulation (GDPR), you have the following rights:
• Right of access: obtain a copy of your data
• Right to rectification: correct inaccurate data
• Right to erasure: request the deletion of your data
• Right to portability: receive your data in a structured format
• Right to object: object to certain processing
• Right to restriction: temporarily restrict processing
• Right to withdraw consent: at any time, without justification

To exercise these rights, you can use the features built into the app:
• Settings → Privacy & data → Export my data
• Settings → Privacy & data → Delete my account

You can also contact us at contact@breakloop.fr.

You also have the right to lodge a complaint with the CNIL (cnil.fr).

8. Security

We implement the following technical measures:
• Secure authentication via Supabase Auth
• PostgreSQL database security rules (Row Level Security) restricting access to each user's data
• Encrypted transmission (HTTPS) for all communications
• Third-party API keys stored exclusively on the server side (Supabase Edge Functions)

9. Cookies, local storage and partner links

The Sillage mobile app does not use cookies. Local storage on the device (via AsyncStorage) is limited to your preferences (theme, display density, views), your recent searches, your declared tastes and the perfumes you set aside; a copy of those tastes is saved on our servers as soon as an account exists (see 2.5). Your answers to the “this or that” duels are also stored on the device.

The "View offer" buttons and the "Compare merchants" section may contain affiliate links: if you buy from a partner merchant through one of these links, Sillage may receive a commission, at no extra cost to you. These links do not add any tracking cookies in the app and do not influence the prices shown or the ranking of offers.

To find out whether the taste quiz and the “this or that” duels are useful, the app counts, without any identifier or precise timestamp, how many times each of their steps is used.

10. Minors

The app is not intended for anyone under 15. If you are a parent and believe your child has provided us with personal data, contact us to have it deleted.

11. Changes

This policy may be updated to reflect legal or functional changes. In the event of a material change, users will be informed the next time they use the app.

Exercising your rights from this page

You can delete your account and all of your data without the app and without giving a reason, from the account deletion page (verification by a code sent to your address). For any other right — access, rectification, objection, restriction, portability — write to contact@breakloop.fr: we answer within thirty days.

Back to top

contact@breakloop.fr