Privacy policy

Last updated: [YYYY-MM-DD]

Template: This page contains placeholders in square brackets. Whoever runs this instance describes here which data it processes – this is not legal advice.

1. Controller

[Name or company, address, email]

2. Hosting

[Where this instance runs and who receives data there (data center, mail delivery, online storage).]

3. Account and sign-in

[Which sign-in service is used, which data the account stores (email address, settings) and for how long.]

4. Music and analyses

[What happens to uploaded or connected audio files: analysis, deletion of the copy after measuring, stored measurements.]

5. Cookies and browser storage

What the Timbre software sets by itself (check it for your instance, add the legal basis and any services you embed):

• Cookies: the session cookie “timbre” (only once sign-in starts, at most 14 days, cleared on sign-out), “timbre_sprache” (only the language code, 12 months, only when a language is actively picked) and after sign-in “timbre_geraet” (random value and checksum, 400 days, for the security email on a new device). [Cookies of your sign-in service.]
• in the browser's persistent storage (localStorage), not sent to the server: timbre.erscheinungsbild, timbre.player.sparsam, timbre.player.laut, timbre.player.gain, timbre.player.pegelart, timbre.player.gainoffen, timbre.genres.schwelle;
• in the browser's session storage (sessionStorage): timbre.player, timbre.status, timbre.stuetz, timbre.genres.neu.

Live demo (only if set up): the live demo sets no cookies and creates no session; the Tag List stays in the browser (localStorage, timbre.demo.taglisten). [Abuse counters, legal basis.]

6. Logs

[Which server logs exist and when they're deleted.]

7. Your rights

[Access, rectification, erasure, restriction, data portability, objection, complaint to a supervisory authority.]