Your data on Sillage

In short

• Your activities are shown to the members of your groups, in their feed: their summary and their map, without the start or end of the track; never your heart rate, your power or your weight. You can stop showing them. Your efforts on a group's segments are shared with its members.
• Nothing is public, except a race you share yourself with a link.
• No advertising, no audience tracking, no data sold or lent.
• Sillage only receives the files you export, the activities from Garmin Connect, Polar Flow or intervals.icu if you link them, and, in the app, the sessions you allow it to read in Health or in Health Connect. It does not connect to Strava.
• No artificial intelligence processes your data, and it trains no model.
• You delete an activity, or your whole account, in one step, on the website.

Who is responsible

The company that publishes Sillage, named in the legal notice. For any question about your data, write to support@sillage.team.

What Sillage keeps, and why

What it takes to run the service you use, nothing more:

• Your account: your email address, your password (in a form that cannot be read back), and the name and colour others see you under. If you sign in with Google, the identifier Google gives you, nothing else: no photo, no access token.
• Your account photo, if you upload one: it personalises your profile and Account menu, and the members of your groups see it instead of your initials, in leaderboards, the feed and member lists. Nobody else: it is only served to you and to them. You can replace or remove it from your profile.
• Your activities: what your files say about each ride (the GPS track, times, elevation, distance, the device and its model, the calories it counted) and what your sensors measured (heart rate, power, cadence). The file itself is not kept: only what is drawn from it. On a bike, when the file does not count calories, Sillage estimates them from power, never from your weight.
• What Sillage calculates from them: your efforts on segments, your records, your badges, your dashboard and your training plan.
• Your smart trainer sessions: their measurements, the devices used (their name, the protocol that controlled them, connection drops) and, if you answer, what you say about your equipment. The mass a session declares is used to redo its calculation, then forgotten.
• Your weight and your bike's, only if you save them on your profile.
• Your goals, one per sport: the race or distance you aim for, its elevation gain, the time, the date and, if you import one, its course (a lighter version of the track and its elevation; the file is not kept). Only you can see them, and they disappear when you remove them.
• intervals.icu, if you link it: its access key, encrypted, and what became of each activity that came from it.
• Garmin Connect, if you link it: the identifier Garmin gives you, the access tokens it hands to Sillage, encrypted, what you chose to share, and what became of each activity that came from it (see below).
• Polar Flow, if you link it: the identifier Polar gives you, the access token it hands to Sillage, encrypted, and what became of each session that came from it (see below).
• What you create: your segments, groups, invitations, share links, the duels you start and your answers to those you receive, the “Yay!”s you leave, the cheers you give on a shared race (to which rider, and at which point of the road), and the suggested segments you dismissed.
• Riding together live: your positions during a meetup (time, distance, speed, power, cadence; in a game, the lane; in Tug of War, your pull, that is your power as a share of your threshold, instead of distance, speed and power).
• A meet-up: who was there, and who brought their segments.
• Your sign-ins: for each day you use Sillage, what you came with (the website or the app, a computer, a phone or a tablet, the system, the browser, the app version), the number of sessions opened, and the times of your first and last visits. No IP address, no device identifier.

Sillage does this to provide the service you ask for when you create your account (performance of the contract). For your health data, it is your consent (below). Server logs, the list of your sign-ins and limits on attempts serve its security and tell us which devices it has to work on (legitimate interest).

Your health data

Heart rate and weight are health data. You choose to provide them: heart rate comes with the files you import, those Garmin Connect and Polar Flow send, and the sessions the app reads in Health or in Health Connect; weight only if you enter it.

• Your heart rate goes with your efforts to the members of your groups, and in the races you share. It is never sent during a live meetup.
• Your weight never leaves your account: it is only used to calculate your smart trainer sessions and the time a cycling goal predicts, which only you can see.
• The calories burned during an activity are only shown on its page, to you alone: not in the feed, not to the members of your groups, not in a share.
• To withdraw this consent: empty the weight fields on your profile, delete the activities whose measurements you no longer want, import files without heart rate, unlink Garmin Connect and Polar Flow, or withdraw Sillage's access to Health or to Health Connect.

Data from Garmin

If you link Garmin Connect from the Integrations page of your account, Garmin asks you, on its own page, what you agree to share with Sillage. Then, each time your device syncs, Garmin announces your new activities, and Sillage downloads their file.

• What Sillage receives: the file of each activity (the track, times, elevation, what your sensors measured, heart rate included, the device that recorded it and the calories it counted), the name you gave it in Garmin Connect, and the identifier Garmin gives you. Sillage keeps only what is said above about activities, not the file. It asks Garmin for nothing else: not your sleep, your steps or your daily health data. Activities entered by hand in Garmin Connect are left aside.
• What it does with it: exactly what it does with a file you import yourself. The activity is shown to the members of your groups in their feed, unless you do not want it to be, and its efforts on your groups' segments to their members, as “Who sees what” says. Nothing else leaves your account.
• What it does not do: it does not sell or rent this data, does not hand it to any third party, and uses it neither for advertising nor to train an artificial intelligence model.
• For how long: the address of the file Garmin announces, encrypted, for as long as it takes to download it, two days at most. The identifier and tokens, as long as the link lasts. Imported activities, like the others: until you delete them, or your account.
• Ending it: unlink Garmin Connect from your integrations, or remove Sillage from the connected apps in Garmin Connect. Sillage deletes the identifier and tokens, and asks Garmin to send it nothing more; deleting your account does the same. Activities already imported stay, for you to delete if you wish.

Data from Polar

If you link Polar Flow from the Integrations page of your account, Polar asks you, on its own page, to allow Sillage to read your data. Then, every quarter of an hour, Sillage asks Polar for the list of your synced sessions, and downloads the file of those it does not have yet.

• What Sillage receives: the list of your sessions from the last thirty days (their time, their sport, whether they have a GPS track), the file of each one (the track, times, elevation, what your sensors measured, heart rate included, the device that recorded it and the calories it counted), and the identifier Polar gives you. Sillage keeps only what is said above about activities, not the file. It asks Polar for nothing else: not your sleep, your daily activity or your daily health data.
• What it does with it: exactly what it does with a file you import yourself, as with Garmin. Nothing else leaves your account.
• What it does not do with it: it does not sell it, rent it out or hand it to any third party, and uses it neither for advertising nor to train an artificial intelligence model.
• For how long: the identifier and the token, as long as the link lasts. Imported activities, like the others: until you delete them, or your account.
• Ending it: unlink Polar Flow from your integrations, or withdraw Sillage's access from your Polar account. Sillage deletes the identifier and the token, and removes its registration at Polar; deleting your account does the same. Activities already imported stay, for you to delete if you wish.

Sessions from Health and Health Connect

In the Sillage app, the Integrations page of your account can read the sessions your watch has left on the phone: in Health on an iPhone (the Apple Watch), in Health Connect on Android (Wear OS, Samsung and Fitbit watches, and those whose app shares them there). The phone first asks you, on its own screen, what you allow Sillage to read.

• What the app reads there: your sessions (their sport, their time, their name), their GPS track, and what your sensors measured during them: heart rate, power, cadence. Nothing else: not your steps, your sleep, your weight or any other health data. It writes nothing to Health or to Health Connect.
• What goes to Sillage: only the sessions that have a GPS track, when you start the import or, if you ticked it, when the app opens. Each one arrives like a file you would import yourself, and Sillage does exactly the same with it: the activity is shown to the members of your groups in their feed, unless you do not want it to be, and its efforts on your groups' segments to their members, as “Who sees what” says.
• What it does not do with them: it does not sell them, rent them out or hand them to any third party, and uses them neither for advertising nor to train an artificial intelligence model. Its use of data from Health Connect complies with the Health Connect Permissions policy, including its Limited Use requirements.
• How long: the imported sessions, like other activities, until you delete them, or your account. For Sillage, the phone only keeps the date of the last import and the marker that tells Health or Health Connect where it is up to.
• Ending it: untick the automatic import, or withdraw Sillage's access in Health (Sharing, then Apps) or in the Health Connect settings. The activities already imported remain; it is up to you to delete them if you wish.

Artificial intelligence

Sillage has none of your data processed by an artificial intelligence, its own or anyone else's, and uses it to train no model. Its calculations (efforts, the speed of a session, potential, the training plan) are formulas written by hand, the same for everyone. This applies in particular to data from Garmin, Polar, Health and Health Connect. Should this change, this page would say so first.

Who sees what

• Only you: your activities and their tracks, your dashboard, your weights, your sessions, your settings.
• The members of your groups: your name and colour; your efforts on the group's segments (the time, the date, and what your sensors measured during the effort); the group rides Sillage deduces from them; the badges earned in the group. And, in their activity feed, your activities: their name, date, sport, distance, duration, elevation gain and map, without the first 100 or the last 100 metres of the track, where one sets off and comes home; the name of the personal segments those activities rode and your time on them, without those segments or their leaderboards opening, once the site has told you so; with the “Yay!”s they leave there. Not if you stop showing your activities, from your profile, nor the ones you hold back, one by one. Never your heart rate, your power or your weight in the feed. A group sees nothing of another.
• During a live meetup, those riding or watching it, all members of the group: your position, speed, power and cadence, and in a game your lane. In a live game of The Chase, the meetup page tells the group's members who caught the fugitive, at what distance, and by how much the others missed. In a live Tug of War, your power is not sent: only your pull, which gives away neither your watts nor your threshold, and the meetup page gives both teams' score, round by round.
• A wanted notice (The Chase, a game), which you post in one of your groups: its members receive your ride on the game circuit (the time you passed every five metres), to replay it, and see your name; never your power or your weight. Your threshold, estimated from your activities, is only used to work out each hunter's handicap; those who hunt you see their result, and you see theirs.
• A game of The Broom Wagon played to the end: the members of your groups see, in today's ranking, your name, the time you held on and the distance; never your power, your weight or your threshold, which the broom wagon rides at.
• In a company group, members only see each other through the weekly challenge: from Monday at 8:00, your name, your photo and your best time of the week on the challenge segment, and, if you are among the best eight, the race where they are replayed, with times only: no day, no time of day and none of your measurements. Nothing else: not the feed, not your other efforts, no group outings, badges, duels, games or meetups. The group's admin places the company's office there, around which the challenges are picked. A group of friends can also keep its challenge ranking closed until Monday at 8:00: until then, everyone only sees their own time.
• A duel, on a segment of one of your groups: the person you challenge sees your challenge, and you see their answer. Once the challenge is accepted, the members of the group see who is up against whom, and each rider's best time during the duel, which the segment's page already shows them. A challenge that is waiting, declined or withdrawn concerns only the two of you.
• A cheer, given during the replay of a shared race, on a segment of one of your groups of friends: the members of that group who open the link see your name, the rider you cheer on and the point of the road. That rider is told at the top of their pages, and by a notification if they receive them. Nobody else: whoever opens the link without being in the group, with or without an account, sees none of it. No written message, nothing in a company group, and you remove it below the race.
• A meet-up shows your name to those who have your code, and the list of those present to those who joined it. Your phone broadcasts nothing but this code.
• Everyone, only through a share link you create: the names of the race's riders and their split times, without the time of day. Your sensor measurements, and not those of riders from another account. The link works until you close it. A member of your groups can likewise share a race your effort is part of: your name and times appear in it, without your measurements. The group's cheers do not appear in it.
• Sillage's administration: accounts (email address, name, groups), their sign-ins and the devices used, counters, dates and states. Never a track, a map, a sensor measurement or an activity's name.

The services involved

• Amazon Web Services (Amazon Web Services EMEA SARL): the server that runs Sillage, in Paris.
• Scaleway (Scaleway SAS): the database and account photos, in the European Union. Photos are stored in a private bucket in Paris.
• The email service, when Sillage sends emails: your address and the message (the link to choose a new password).
• Google, if you sign in with it: it then knows you use Sillage. And when Sillage offers its base maps, your browser requests the images from it: it sees your IP address and the area shown.
• OpenStreetMap (OpenStreetMap Foundation): your browser requests the base map images from it, with your IP address and the area shown.
• The terrain of the perspective views comes from Amazon's open data (AWS Open Data): your browser requests it in the same way.
• Overpass, OpenStreetMap's public servers: Sillage's server, and only it, requests the scenery around a segment there. It sends only the segment's bounding box, nothing from your account.
• intervals.icu, if you link it: Sillage reads your activities and planned workouts there, and sends your smart trainer sessions there if you ticked the box.
• Garmin, if you link Garmin Connect: Garmin announces your activities to Sillage, which downloads their files. Sillage sends it nothing from your account, only what the link requires (renewing it, removing it).
• Polar, if you link Polar Flow: Sillage asks it for your sessions and downloads their files. It sends it nothing from your account, only what the link requires (registering you, removing the registration).
• Notification services, if you receive notifications on a device: your browser's (Google, Apple, Mozilla or Microsoft) or Firebase (Google) for the Android app receives the device's address and the text of each notification (a name, a segment, an activity), nothing else.

Google and Amazon are American companies that have joined the EU–US Data Privacy Framework. The OpenStreetMap Foundation is in the United Kingdom, which the European Union recognises as protecting data adequately.

Cookies and browser storage

Sillage only sets what the site itself needs:

• the session, which keeps you signed in during your visit, and “stay signed in”, for two weeks, if you ticked it;
• the appearance and language you choose on this device, and the filters you leave on your activities list and the segments list.

No audience-tracking or advertising cookies: that is why no banner asks for your consent. The browser also remembers your display settings, the Bluetooth devices you connected, and a session not yet saved. This stays on your device, except the session, which goes to the server when it is saved.

For how long

• Your account and activities: as long as you keep your account. Deleting an activity deletes its efforts. Deleting your account deletes everything in it, except the segments you created in a group: their route stays there, handed to another member, without your efforts.
• The positions of a live meetup, and a meet-up: one day. Of a meet-up, all that remains on your side is its time, counted for a badge.
• A wanted notice: it can be hunted for a week, then stays attached to the activity of your escape, with the results of those who hunted it; it is deleted with that activity, or when you leave the group.
• A game of The Broom Wagon: its place in the ranking of the day stays attached to its activity, and is deleted with it.
• A duel: as long as you are both in the group and its segment stays there; it is deleted with your account, or when either of you leaves the group.
• A cheer: as long as the share link stays open and you are both in the group. It is deleted when you remove it, with your account or the rider's activity, when either of you leaves the group, when the segment changes group or route, and when the group becomes a company or is dissolved.
• An invitation: fourteen days; a group link and your upload link, thirty days.
• Your sign-ins: ninety days.
• Server logs (IP address, page requested, time): as long as the security and diagnosis of the service require, then they are deleted.
• Database backups: deleted data may remain in them until the end of their cycle, a few days, then disappears.

Your rights

You can access your data, correct it, delete it, ask for a copy, object to or restrict its processing, and withdraw your consent. Most of this is done on the website, without asking anyone:

• your name, colour and weights, on your profile;
• an activity, from its page;
• your whole account, from “Account”, which first tells you, with numbers, what will go;
• Google, intervals.icu, Garmin Connect and Polar Flow, which you unlink from your account and its integrations;
• Health and Health Connect, whose access you withdraw on the phone;
• what you share with Sillage at Garmin, which you can also change or withdraw in Garmin Connect.

For the rest, a copy of your data for example, write to support@sillage.team: you will get an answer within a month. You can also lodge a complaint with the CNIL, the French data protection authority (cnil.fr).

Security

The site only uses encrypted connections (HTTPS). Passwords are only kept in a form that cannot be read back, the intervals.icu key and the Garmin Connect and Polar Flow tokens are encrypted, and sign-in attempts are limited. The code lets nobody but you access your activities, administration included.

If this page changes

Its update date changes with it. A change that would show more of your data to others would be announced on the website before it applies.