Privacy when embedding: what the player does on your website

If you embed the player or the story row on your own website, you need to classify it in your cookie banner. This article says what the player stores, where data goes and how to describe it in your consent tool.

Short version for your consent tool

• The player sets no third-party cookies and does no tracking across websites. There are no advertising IDs and no personalised advertising.
• Everything it stores serves a function: a random session cookie so that reactions, votes and comment limits work, and a few values in local storage (sound on or off, recently used reactions).
• Audience measurement is anonymous and only for you as the publisher. It knows neither name nor email address, links nothing across websites and shares nothing with third parties. Viewers can switch it off for their device in every story under «Legal» → «Measurement».
• When a video plays, the browser fetches it directly from our video service Mux (USA); Mux sees the IP address, as with any video request.

This lets you classify the player as functional (strictly necessary) in most consent tools. If you want to be extra careful, load the player only after consent to «statistics»; the measurement then starts after consent anyway.

What the player stores

| Name | Type | Purpose | Duration | | --- | --- | --- | --- | | sc_session | cookie | random session identifier: one vote per poll, comment limits, ad frequency | 6 months | | sc_name | cookie | last chosen display name for comments | 12 months, only after a comment with a name | | sc_access_… | cookie | unlocking a password-protected story | 12 hours | | sc_cookie_ok | local storage | cookie notice seen in the story | until cleared | | sc_sound | session storage | sound on or off | until the tab is closed | | sc_react_recent, sc_react_order | local storage | recently used reactions, order of the quick reactions | until cleared | | sc_row_seen | local storage | stories already opened in a story row (the «new» ring) | until cleared | | sc_notify_mail, sc_notify_off | local storage | voluntary address for replies, or «no thanks» | until cleared | | sc_measure_off | local storage | measurement switched off for this device | until cleared |

All values are set on the player's domain (your subdomain at SwypeCast), not on your website.

Where data goes

• SwypeCast (servers in Frankfurt and London): usage events such as «clip watched», «swiped», «shared», with device type, operating system, country and the domain of your website, without IP address. Reactions, comments and votes with the session identifier.
• Mux (USA): the video itself, fetched by the browser. No cookies.
• Apple (USA): only for clips with an iTunes song, the browser streams preview and cover directly from Apple.
• Fonts, music from the music library and stickers are delivered by SwypeCast from its own servers; the browser does not connect to Google or other third parties for them.

What you need to do yourself

1. Provide legal texts: under Settings → Legal, enter your imprint and privacy information. They appear in every story under «Legal», together with the switch for the measurement. Once texts exist, the player shows a short notice with a link there on the first visit.
2. Extend your privacy policy: name SwypeCast (my105 GmbH, Zurich) as processor for player, comments and statistics, and Mux as video service. You find wording in our privacy policy under sections 2 and 7.
3. Set up your consent tool: classify the player as functional, or load the embed script only after consent. Both work; the player needs no release from outside.