Privacy Policy
Non-binding courtesy translation. This English text is provided for your convenience only. The legally binding version is the German one: Datenschutzerklärung. In the event of any discrepancy, the German wording prevails. See also the terms and conditions in English.
1. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) is:
Timothy Schulz
Düsseldorfer Straße 131
51063 Cologne
Germany
Email: support@squaresmile.de
2. Overview
Protecting your data matters to me. This website (squaresmile.de) is deliberately built to collect as little as possible: the public pages load no content from third-party servers. Fonts, icons, images and all program libraries are served directly from my own server (first-party). No tracking cookies and no third-party analytics scripts are embedded. For that reason, no cookie consent banner is required on the marketing pages.
Some features do call third-party services — but only if you actively use them (e.g. weather, notifications, embedded Spotify content) or for order processing when you make a purchase. Below I explain which data is processed in which case.
3. Hosting
This website is hosted by an external service provider (the host):
ALL-INKL.COM – Neue Medien Münnich
Owner: René Münnich
Hauptstraße 68, 02742 Friedersdorf, Germany
The host processes, on my behalf, the data generated when you visit the website (in particular server log files, see below). The servers are located in Germany. The legal basis is my legitimate interest in providing the website securely and reliably (Art. 6(1)(f) GDPR). A data processing agreement pursuant to Art. 28 GDPR has been concluded with the host.
4. Server log files
When the website is accessed, the server automatically collects information transmitted by your browser and stores it in what are known as server log files. These are:
- the address (URL) requested and the date/time of access
- the volume of data transferred and confirmation of successful retrieval
- browser type and version, operating system used
- referrer URL (the page visited previously)
- the IP address in truncated or anonymized form
This data is not merged with other data sources. Processing is based on Art. 6(1)(f) GDPR for the technical provision, security and stability of the website. Log files are stored for a limited period and then deleted.
4a. Tool usage counters (aggregated, anonymous)
In order to understand which tools are used and how often, the platform collects purely aggregated usage counters: for each tool, a daily count is kept of how often it was opened and which actions were performed in it (e.g. “opened”, “exported”). These counters deliberately use the same technique as the click counters already used for support links (see the section on server log files / internal statistics) and are subject to the same data-minimization requirement.
In the same way, the dashboard counts how often a recommendation (“Picked for you”) is shown and clicked, how often “Unlock” is clicked, and how often tools are pinned or reordered — again only as a daily total per tool.
Likewise, we count how often the full-version notice on the free plan is shown and its buy link clicked, and how often the pointer to a matching Squaresmile product below a free tool comes into view and is clicked — again only as a daily total per tool, with no link to your account.
No personal data is stored in the process — in particular no IP address, no user identifier, no cookie and no timestamp more precise than the calendar day. The counters are pure daily totals per tool and allow no conclusions about individual persons. They are not linked with other data sources. The legal basis is my legitimate interest in the basic statistical improvement of the service (Art. 6(1)(f) GDPR); consent is not required because no personal reference exists.
5. Contact by email
If you write to me by email (e.g. to support@squaresmile.de), I process the details you provide (email address, content of the message) in order to deal with your inquiry. The legal basis is Art. 6(1)(b) GDPR (for contract-related inquiries) or Art. 6(1)(f) GDPR (for other inquiries, legitimate interest in responding). The data is deleted as soon as it is no longer required and no statutory retention obligations conflict with deletion.
6. Registration and user account
You can create a user account to use the platform. On registration I process:
- Name (a display name of your choosing, used among other things for the salutation in emails)
- Email address
- Password (stored exclusively in encrypted/“hashed” form)
I process this data in order to provide you with the account and its associated features. The legal basis is Art. 6(1)(b) GDPR (establishment and performance of the user relationship).
In addition, I store the time at which you accepted the terms and conditions and the privacy policy and — if you ticked the optional box — the time of your newsletter consent (see section 14). These timestamps serve as proof of the consent given and of the conclusion of the contract (Art. 7(1) GDPR, accountability under Art. 5(2) GDPR).
The account gives you limited storage (up to 50 MB) with which you can link content from the apps (e.g. saved projects) to your profile and back it up server-side. This content is stored on the host’s server (see section 3) in Germany, is assigned to your account and is removed when the account is deleted. For details, see section 13.
Your account also stores the license keys of the premium products you have purchased, so that the corresponding features remain unlocked. The validity of these license keys is checked with Gumroad (see section 8). The legal basis for storage is Art. 6(1)(b) GDPR (performance of a contract).
From the times at which content is saved to an account, share links are created and licenses are added, I compile aggregated per-tool figures for my own use as operator only (e.g. how many accounts use the free plan and how many of them later buy a license). No per-person analysis and no new data are created. The legal basis is my legitimate interest in improving the service (Art. 6(1)(f) GDPR).
The data is stored for as long as your account exists. You can delete your account at any time or request deletion by email to support@squaresmile.de; the associated data is then deleted, unless statutory retention obligations conflict with deletion.
A technically necessary session cookie is used for signing in and maintaining your session. It is strictly necessary for login and requires no consent (Section 25(2) no. 2 of the German Digital Services Data Protection Act, TDDG).
Your display settings — the language you chose and the color theme (dark, light or high contrast) — are stored in your user account so that they apply on all your devices. Your browser also remembers this choice in two technically necessary cookies ("pf_locale" and "pf_theme", stored for one year) and the color theme in your browser's local storage as well — even without signing in. They contain only the chosen value, no identifier, and are not evaluated for any other purpose (Section 25(2) no. 2 TDDG; Art. 6(1)(b) GDPR).
6a. Signing in with Google or Apple
Instead of an email address and password, you can sign in with your Google account or your Apple ID. This is optional; registering with an email address and password remains possible at any time.
Before you click, nothing is sent to Google or Apple: the "Continue with Google" and "Continue with Apple" buttons are part of my website; no scripts, fonts or images are loaded from Google or Apple.
After you click, you are sent to Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) or Apple (Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland) and sign in there. The provider then sends me:
- your email address and the confirmation that it belongs to your account,
- a pseudonymous identifier of your Google or Apple account,
- your name (with Apple only at the first sign-in, and only if you share it).
I do not store anything else the provider sends along (with Google, for example, the address of your profile picture). With Apple you can choose a relay address instead of your real one ("Hide My Email"); Apple forwards my emails to that address to you.
I store the email address, name and identifier in your user account to recognize you at later sign-ins; no confirmation email is then needed. If you already have an account with the same email address, I link the identifier to that account. If you don't, I first ask you to accept the terms and this privacy policy; if you cancel there, I create no account and the information received is deleted when your session ends. I receive no password, store no access tokens and have no access to any other data in your Google or Apple account.
For signing in with Apple I also set a technically necessary cookie ("pf_oauth", stored for 10 minutes). It holds a random number I use to check that Apple's answer belongs to your browser (Section 25(2) no. 2 TDDG).
Google and Apple process the sign-in under their own responsibility and learn that, and when, you sign in to Squaresmile Tools. Their privacy policies apply: policies.google.com/privacy and apple.com/legal/privacy. Data may be transferred to the USA in the process. Google bases this on the EU-US Data Privacy Framework (Art. 45 GDPR); Apple, by its own account, on the EU Standard Contractual Clauses (Art. 46 GDPR).
The legal basis is Art. 6(1)(b) GDPR (setting up and running the user relationship at your request). The stored identifier is deleted with your account. You can also remove the link at any time in your Google account ("Third-party apps & services") or your Apple Account ("Sign in with Apple"); your account with me stays, and you can set a password with "Forgot password".
7. Sending transactional emails
Functional emails (e.g. confirmations, system-related notifications) are sent via the SMTP server of my host ALL-INKL.COM – Neue Medien Münnich (address see section 3). The recipient’s email address and the content of the message are processed in doing so. Processing takes place in Germany; no transfer to a third country occurs. The legal basis is Art. 6(1)(b) GDPR (performance of a contract) or Art. 6(1)(f) GDPR (legitimate interest in reliable delivery). Sending is covered by the existing data processing agreement with the host pursuant to Art. 28 GDPR.
8. Sale of tools and plugins via Gumroad
The sale of the paid tools and plugins (e.g. SoundSense, SetlistForge, SubPress) is handled via the platform Gumroad:
Gumroad, Inc., 548 Market St, San Francisco, CA 94104, USA
Gumroad acts as seller/reseller (merchant of record) and independently handles ordering, payment and invoicing. When you buy something, you enter your payment and billing details directly with Gumroad; from Gumroad I receive only the information necessary for order processing (e.g. email address and the product purchased).
In addition, the validity of license keys is verified server-side with Gumroad (“license validation”). The license key you enter is transmitted to Gumroad and the result (valid/invalid) is returned. Purchase links also point to the product pages on Gumroad.
Processing takes place for the performance of a contract (Art. 6(1)(b) GDPR). As Gumroad is based in the USA, data may be transferred to the USA. Such transfers are based on the EU standard contractual clauses or — where applicable — on the EU-US Data Privacy Framework. Details: gumroad.com/privacy
After a purchase, Gumroad sends me the purchase data (email address, product, order number and license key). I then check the license key again directly with Gumroad. If a user account with the same confirmed email address exists, I unlock the license there automatically. Otherwise I keep the email address, product, order number and the encrypted license key for at most 90 days, so the license can be assigned to the account you create and confirm with that email address; after that I delete them. If Gumroad cannot be reached when the purchase comes in, I keep the purchase data encrypted for at most 24 hours to check it again. If a purchase is refunded or charged back, I remove the license and this data. The legal basis is Art. 6(1)(b) GDPR.
If a bundle is refunded or charged back, I keep the refund's order number and time encrypted for at most 24 hours while I check which licenses came from it.
8a. Donations via PayPal
If you would like to support Squaresmile with a donation, the “Donate” button takes you to PayPal:
PayPal (Europe) S.à r.l. et Cie, S.C.A., 22–24 Boulevard Royal, L-2449 Luxembourg
The donation is handled entirely by PayPal; you enter your payment details there. PayPal provides me with the information needed to process it, e.g. your name, your email address, the amount and, if you leave one, your message. I use this information only for the donation itself (e.g. bookkeeping) and keep it for as long as the statutory tax and commercial retention periods require.
After the donation, or if you cancel it, PayPal sends you back to a page on this website (/donate/thanks or /donate/cancelled). PayPal may append details of the transaction to that address. They are not analyzed or stored but removed from the address straight away; like any address you call up, they can only be recorded in the server log files (section 4).
The legal basis is Art. 6(1)(b) GDPR (processing of the donation). PayPal also processes your data under its own responsibility and may transfer it to third countries such as the USA. Details: paypal.com/uk/legalhub/privacy-full
9. Show Clock – weather data via Open-Meteo
The Show Clock feature can display weather data. This data is retrieved only once you have set a location for the weather display; after that Show Clock refreshes it about every 15 minutes while it is open in the foreground. To do so, your browser sends a request to the weather service Open-Meteo (open-meteo.com); your IP address and the coordinates of the location are transmitted to Open-Meteo in order to return the matching weather data. The coordinates are also synchronized with your account (see section 13a); share links do not contain them.
The legal basis is my legitimate interest, respectively your active use of the feature (Art. 6(1)(f) GDPR). Further information: open-meteo.com/en/terms
10. Show Clock – notifications (web push)
The Show Clock can send you notifications (web push) if you enable them. This feature is opt-in: it only becomes active once you expressly allow it and confirm your browser’s notification request.
If you enable push notifications, your browser registers a push subscription with the push service of the respective browser/device manufacturer (e.g. Google for Chrome, Mozilla for Firefox, Apple for Safari). A technical subscription address (endpoint) is generated and stored, through which notifications are delivered. This is not intended to identify you personally.
The legal basis is your consent (Art. 6(1)(a) GDPR). You can disable notifications again at any time in your browser settings. Delivery runs via the infrastructure of the respective browser/device manufacturer; their privacy policy applies in addition.
11. Embedded Spotify content (click to load)
In individual places, content from Spotify may be referenced. It is not loaded automatically. Instead, you initially see only a button (“Play on Spotify” with the note “Loads content from open.spotify.com”). Only when you actively click that button is a connection to Spotify established and the player loaded. No data is transmitted to Spotify before that.
By clicking, you consent to the content being loaded (Art. 6(1)(a) GDPR). From that moment, Spotify’s privacy policy applies: spotify.com/de/legal/privacy-policy. The provider is Spotify AB, Regeringsgatan 19, 111 53 Stockholm, Sweden.
12. Google Search Console
I use Google Search Console to monitor how the website can be found in Google Search. Search Console evaluates aggregated, anonymized data on how the website appears in search results (e.g. search terms, click and impression figures). No analytics script is embedded in the website and no cookies are set on your device; the data comes from Google Search itself. It does not enable me to identify individual visitors. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
12a. Update check in the KlarFunk desktop application
Our KlarFunk desktop application can check, if you want it to, whether a newer version of the program is available.
This function is disabled by default. It only becomes active once you switch on the “Automatically check for updates” option in the application’s settings or press the “Check for updates” button. Without one of these actions the application establishes no connection to any server.
If the automatic check is enabled, the application retrieves a file containing the current version number at most once every 24 hours; if you press the button manually, the file is retrieved once, at the moment of your input. That file is not provided by us but via GitHub Pages, a service of GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA (a subsidiary of Microsoft Corporation):
https://square-smile.github.io/klarfunk-updates/latest.json
This is a plain request that transmits no content: no parameters, no identifiers, no device information and no details of the program version installed on your machine are transmitted. The version numbers are compared exclusively locally on your device.
No data reaches us through this function. For technical reasons, however, GitHub as the operator of the service processes the data that arises whenever a web address is retrieved, in particular:
- your IP address
- the date and time of the request
- the file requested
- the identifier of the browser engine used (user agent)
As GitHub is based in the USA, this data is transferred to a third country. Details of GitHub’s data processing and of the safeguards that apply to it can be found at: docs.github.com/site-policy/privacy-policies/github-general-privacy-statement
The legal basis is your consent under Art. 6(1)(a) GDPR, which you give by enabling the function. You can withdraw this consent at any time with effect for the future by switching the option in the application’s settings off again.
Beyond that, the application stores exclusively on your own device whether the function is enabled, when it last checked, and which version notice you have already dismissed. This information does not leave your device.
12b. Downloading the KlarFunk desktop application
The installer files for KlarFunk are not provided by me but via GitHub Releases, a service of GitHub, Inc. (for the address, see section 12a). The download is available without a user account or license. When you click one of the download buttons, my server redirects you to the file hosted there. In doing so GitHub processes the data that arises with every request (IP address, date and time, the file requested, user agent), and the data is transferred to the USA. The legal basis is Art. 6(1)(b) GDPR (provision of the software you requested, including the free 14-day trial). To protect against abusive request volumes, your IP address is processed in hashed form on my server for at most one minute to count requests (Art. 6(1)(f) GDPR).
12c. SelektorCue – song wishes from guests
SelektorCue (song wishes from guests for DJs) has its own privacy notice, which guests and DJs accept before using it: squaresmile.de/selektorcue/privacy.
12d. Lighting Watchdog – download and desktop application
Lighting Watchdog is a free desktop application (beta). The download requires a free user account (section 6); the legal basis is Art. 6(1)(b) GDPR. The installer files are provided via GitHub Releases (GitHub, Inc., address see section 12a): when you click a download button you are redirected there via my server; GitHub processes your IP address, date and time, the requested file and the user agent, and the data is transferred to the USA. To protect against abusive numbers of requests, your IP address is processed in hashed form for at most one minute to count requests (Art. 6(1)(f) GDPR).
The application itself runs entirely on your computer: captures, reports and settings are stored only there, and no usage or diagnostic data is sent to me. Features that send data are off by default and only switched on by you; the data then goes directly from your computer to the destination you choose, not via my server: phone alerts to the service you choose (ntfy, Pushover, Telegram or a webhook address – content: universe, source, time and likely cause of a dropout), switch queries via SNMP and the comparison with a second watchdog only within your local network. Processing by an alert service you choose is governed by its privacy policy.
12e. KlarVox – activation, trial and license check
KlarVox is an audio plugin (VST3/AU) and desktop application. Its license and its free trial belong to your user account (section 6) and require a confirmed email address. To activate, KlarVox shows a code that you approve at squaresmile.de/activate after signing in. During activation and every later license renewal, KlarVox sends my server: a device identifier (an irreversible SHA-256 hash of your operating system's device ID – the ID itself never leaves your computer), the computer's name, the operating system version, the KlarVox version and the most recent license token. Stored with these are your account, the time of activation, the last contact and, where applicable, when and how the computer was removed. The license token contains your email address and the device identifier and is stored on your computer.
The purpose is to perform the license agreement: unlocking KlarVox, the limit of three computers and the trial (Art. 6(1)(b) GDPR). KlarVox transmits no audio, no settings and no usage or diagnostic data; processing runs entirely on your computer. Recordings made with the "Capture" button are stored locally only.
Retention: the computers of your license are deleted with your account. So that the free trial cannot be repeated with a new account, the device identifier and the start and end of a trial are kept until three years after the trial ended, even if you delete your account earlier; in that case the computer's name is removed within one day (legitimate interest in preventing abuse, Art. 6(1)(f) GDPR). Activation codes are deleted one day after they expire. To protect against abusive numbers of requests, your IP address is processed in hashed form for at most one minute for counting (Art. 6(1)(f) GDPR); otherwise section 4 (server log files) applies. The data is processed on my server in Germany (section 3) and not passed on to third parties. Your computers and trials are included in the data export on your account page.
Launch list. Before the release you can join the launch list on the KlarVox page. This needs a user account with a confirmed email address; only your account, the product and the time are stored. At the release you get one email with the promised discount code, nothing else. The legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time on your account page ("Launch lists" → "Leave") or by email to support@squaresmile.de. The entry is deleted with your account, at the latest 90 days after the release email was sent. It is sent as in section 14 via my mail server, without an external newsletter service and without tracking.
13. Local storage in the tools (browser storage)
Many of the tools on squaresmile.de run entirely in your browser. Input and settings are first stored locally in your browser (e.g. via localStorage). Tools that are not named in the following list do not transmit them to my server. You can delete this local data yourself at any time by clearing your browser’s storage for this website. Local storage serves solely the function of the respective tool (Section 25(2) no. 2 TDDG, as it is strictly necessary for the service you have expressly requested).
The dashboard also remembers in your browser which tools you opened last, to show them under “Jump back in”; this list is not sent to my server.
Automatic synchronization: as soon as you are signed in, the following tools reconcile their data with your account without a separate save step, so that every device you use shows the same state:
- Show Clock – timetables, notes, settings, share links and rider files (details in section 13a). If you link a timetable to one of your venues (see below), Show Clock keeps the venue’s identifier with the timetable and shows its name; the identifier is not part of a share link. Show Clock writes nothing into your venues except the name of a venue you start in Show Clock; your location for sunset and weather stays with Show Clock
- Stage Plot Generator – your stage plots and your “Your equipment” items (name, look and the picture you upload, stored as a small icon of at most 160 pixels) and your saved venues (stage size, room size, desks, PA and stage power). If you link a saved venue or a plot to one of your venues (see below), Stage Plot keeps that venue’s identifier with it and writes the stage (width, depth, height, load-in side) into the venue; the room size and the stage power (as a note) only where the venue holds nothing yet. Desks and PA stay in Stage Plot only. If the venue’s room has a plan (RoomSense, “Stage & audience”), Stage Plot copies where the stage stands in the room, the FOH position and the audience areas into the plot and shows them there; the copy belongs to the plot, so it is saved, synced and shared with it. “Save position to venue” writes where the stage stands (where its center is and how it is turned) into the venue’s plan; the FOH position and the audience areas stay as they are. Existing saved venues are taken over only when you confirm each line; first a backup file is downloaded and a backup copy is kept in your browser. A venue you newly save also becomes one of your venues – linked to the one of the same name if there is one
- SetlistForge – automatically, unless you choose “Keep my library on this device only” in SetlistForge’s backup settings (the cloud button) – this switches synchronization off for your account and deletes the copy stored in it: song library (including the names of composers, lyricists, arrangers and publishers, and ISWC codes), setlists with show details and the details for royalty reports, settings and the “reported” mark. The details for royalty reports can include other people’s data that you enter for them (e.g. the organizer’s name and address, venue or organizer phone numbers, the person responsible for the program, the musicians), as well as your member numbers and money figures (ticket prices, revenue, costs, fees). Logos and audio files stay in your browser. If you create a read-only link to a setlist, anyone who knows the link can read that setlist (details in section 13c). If you pick one of your venues for a setlist’s show (see below), SetlistForge copies its name into the show details and keeps the venue’s identifier with the setlist; it is part of neither a read-only link nor a royalty report. SetlistForge writes nothing into your venues except the name of a venue you start in SetlistForge; the details for royalty reports never go into a venue
- SoundSense – training progress, best scores and settings, and the listening devices you name (for example "studio headphones") with your results per device; the hearing profile stays in your browser (see below)
- PatchSmith – your patches (band, venue, date, channel list and notes), routing presets, named versions and your color scheme (the default channel color per instrument group). If you pick one of your venues for a patch (see below), PatchSmith copies its name into the patch and keeps the venue’s identifier in the patch. PatchSmith writes nothing into your venues except the name of a venue you start in PatchSmith
- RiderSmith – your riders (band and contact details: contact person, phone, email, website; venue, town and show date; the tables and texts of every section, e.g. crew tables and hospitality notes; the rider language and any further document languages, your own translations of clauses, versions with their date and the list of changes), your own text blocks and the images you attach (logo, band photo, stage plots and other pictures – each stored as its own entry in your account; images are re-drawn as JPEG, so location data in the original file is not kept; deleting a rider deletes its images too). A rider often contains data about other people that you enter, e.g. names, phone numbers and email addresses of band or crew members, photos in which people can be recognized, or catering notes. Such notes can be health data (allergies, intolerances) or reveal a religious belief; do not enter health data, religion, passport numbers or dates of birth – “on request” is enough – and enter other people’s data only with their consent and only as far as the venue needs it. If you create a venue link, anyone who knows the link can read that rider (details in section 13d). RiderSmith reads your own data from your other Squaresmile tools (Stage Plot Generator, SetlistForge, FreqSense, PowerSense) only when you start an import, and takes it over only after you confirm the preview. With the setting “Use details from my other tools” you can switch this off for all your riders; PowerSense then no longer reads your riders either. If you pick one of your venues for a rider (see below), RiderSmith copies its name and town into the rider, keeps the venue’s identifier in the rider and shows you the venue’s stage, room, house power, rigging points and notes for your advance (also where the stage stands in the room and the FOH position), independently of that setting; these details are not copied into the rider, not printed and not shared through a venue link. RiderSmith writes nothing into your venues except the name and town of a venue you start in RiderSmith; contact details from a rider never go into a venue.
- PowerSense – your power distribution plan. If you link a list to one of your venues (see below), PowerSense keeps the venue’s identifier with the list, and the outlet you took the list’s feed from, and shows the venue’s house power (outlets with label, connector, current, phases and place, and the date they were last checked); what you enter there is written into the venue when you save it. Your distros (your own equipment) never go into a venue
- RiggingSense – your rigging plan. On the Saved tab, RiggingSense shows the rigging points a venue states for one of your venues (label, safe working load, height, place and the date the venue gives); for this it reads them, and the venue’s name and room height, from your account in your browser, writes nothing into your venues and does not calculate with these points. Which venue the list shows is remembered by your browser only
- FreqSense – your frequency plans and display settings
- RoomSense – venue profiles: for each venue its rooms with their room and system input and the last five saved versions of each room, and the visits you log (date, room, air temperature and humidity, correction values K1/K2 with their measuring places, the delays used, measured reverberation times and levels, your free-text notes and – if you link any – the identifier and label of level protocols, i.e. date, venue and event); language and display setting. Notes are stored as you type them – please don’t put other people’s personal data into them. These stay on your device and are not transferred: the level monitor’s calibration value, the running level log, the protocol form fields and saved level protocols. Protocols you saved to your account earlier stay there until you remove them. For “Fill from Show Clock”, RoomSense reads your Show Clock timetables from your account in your browser; only what you put into the protocol form is kept (on your device). The venue profile also holds the input of the Surfaces and materials (with your own materials), Delay plan, Sub array and Crew dose cards (per role: its label, hours and hearing protection). To pick a measurement mic, RoomSense reads your SpectraSense mic library from your account in your browser and does not change it. If you create a link to a venue sheet, anyone who knows the link can read that sheet (details in section 13e). When a venue profile is linked to one of your venues (see below), RoomSense keeps that venue's identifier in the profile and, when you save, writes the name, rooms, dimensions, the acoustics summary and the level limit into that venue; visits, notes, correction values, measuring places and protocols stay in the venue profile only. Existing venue profiles are brought over only when you confirm each line; before that, a backup file is downloaded and a backup copy is kept in your browser. When you add a venue sheet to your venues, it is also saved as a venue, with what the sheet shows (stage, house power and rigging points included). A room's input can also hold a calibration from a measurement you apply: the measured reverberation times per band, the day, how they were taken (a bang or clap, an imported file or typed in), the number of measuring positions, the air temperature and humidity, whether the room was empty or how many people were in it (standing or seated, as a number only), and the absorption RoomSense works out from them. A visit's measured reverberation times also keep how full the room was and how they were taken. This syncs with the venue profile like the rest of the room's input; in the acoustics summary of a linked venue and on a venue sheet RoomSense notes that the estimate is calibrated from a measurement and on which day. When you measure the reverberation at several spots, a visit also keeps the names you give the spots (e.g. “FOH” or “Balcony”), how many there were and, per frequency band, the smallest and the largest value, the standard deviation and the number of measurements; a calibration keeps the values per spot and the number of spots and sources, not their names. Recordings and impulse responses are neither stored nor transferred. Please don’t use people’s names for spots. A room’s input also holds the plan of the “Stage & audience” card: the stage’s width, depth and height, where it stands in the room and how it is turned, the FOH position and up to eight audience areas (standing or seated, size and position, for a balcony the height of its floor, and a label if you give one). It syncs with the venue profile like the rest of the room’s input. When the profile is linked to a venue, RoomSense also writes the stage (width, depth, height) and this plan into the venue when you save – only what the plan holds; an empty plan deletes nothing there. Where you place the measuring spots on the plan stays on your device only and is kept neither in a visit nor in a venue. A link to a venue sheet also shows the stage and the plan (section 13e). A room’s input can also hold the room’s shape: the floor plan (rectangle, L-shape, fan, hexagon, octagon, round or oval) with its measurements, or a floor plan you draw (its corner points), the ceiling (flat, sloped, pitched or vaulted, with its heights), up to three balconies (depth and heights) and a stage house (width, depth and height). It syncs with the venue profile like the rest of the room’s input. It is not written into a linked venue: the venue keeps the room’s outer dimensions and the volume RoomSense works out from the shape.
- LoudSense – your own loudness targets (name, value, tolerance, ceiling). The audio files you check are decoded and measured in your browser and are not uploaded. A history of the files you checked (file name, measured values and date, no audio) stays in your browser and is not synced. If you share an audio file to the installed LoudSense app on Android, the browser’s service worker hands the file to the page inside your device, and it stays in your browser’s storage until LoudSense has read it. If the service worker is not active at that moment (e.g. right after an update or after you cleared the site data), your browser sends the file to our server instead; the server does not store or evaluate it, discards it at the end of the request and only redirects you to LoudSense
- BPM Forge – setlists and settings, including the tuner’s
- ClickSmith – click settings, projects and sets (only values such as tempo, time signature and cues; the audio files never leave your device)
- DMX Dip – the name, DMX address and switch 10 position of each saved fixture.
- PitchSense – A4 reference, waveform and note-name style; the playback volume stays on each device
- SpectraSense – display and detection settings; the snapshot library (stored spectra and transfer curves with the names, notes and show or venue names you type, and the microphone’s name) and the microphone library (name, type, maker and model, optionally the serial number, calibration curves and sensitivity of each microphone). The audio input and channel, which microphone is on which input, this browser’s calibration, level logs, protocols and the list of rings it found stay on your device (see section 13b)
- Venues (venues shared by several tools) – for each venue its name, town, country, the address if you enter one, and the kind of venue; for each room its name, type, dimensions, stage, an acoustics summary (reverberation time, predicted or measured, with its date), house power (outlets with label and place), rigging points (label, safe working load, height and place), level limit and your notes, each with the time it was last changed and – if you give it – the date it was last checked; and from which venue profile of a tool the venue was taken. Contact details are not part of it; please do not enter names, phone numbers or email addresses in notes, labels or places. A tool in which you pick a venue reads this from your account in your browser and writes only its own parts. A deleted venue is kept for up to 180 days as a deletion note (its identifier and the time), so that your other devices remove it too. Which parts a tool writes and reads is listed with that tool (RoomSense, Stage Plot Generator, RiderSmith, PowerSense, RiggingSense, PatchSmith, SetlistForge, Show Clock). On the account page, in the “Venues” section, you can edit a venue’s name, town and address and, for each room, its notes and rigging points (label, safe working load, height, place and the date the venue gives), and also the stage (width, depth, height, load-in side), where it stands in the room (where its center is and how it is turned) and the FOH position, each as numbers. House power, acoustics and the audience areas are only shown there. There you can also download your venues as a JSON file and delete them one by one or all at once; a deleted venue is kept as a deletion note as described above. A tool that was linked to a deleted venue drops the link, keeps its own data and remembers only the deleted venue’s identifier, so that it does not create the venue again by itself. A room can also hold, if you draw them in RoomSense, where the stage stands in the room (where its center is and how it is turned), the FOH position and up to eight audience areas (standing or seated, size and position, for a balcony the height of its floor, and a label if you give one), with the time they were last changed. These describe the building, not people; please don’t use people’s names for areas. On the account page you can edit where the stage stands and the FOH position as numbers; the audience areas are only shown there
All other tools (e.g. TempoSense and MicSense) store data only in your browser.
Shared computers: browser storage belongs to the device, not to a person, and it survives signing out. So that one person’s data on a shared computer (e.g. at front of house) does not end up in someone else’s account, Show Clock, Stage Plot Generator, SetlistForge, SoundSense, PatchSmith, RiderSmith, PowerSense, RiggingSense, FreqSense, RoomSense, LoudSense, BPM Forge, ClickSmith, PitchSense, SpectraSense, MicSense, and the venues, remember which account the data in this browser belongs to. If someone else signs in here, these tools neither show the previous account’s data nor transfer it to the new account; it is set aside or removed from this browser. Whatever had already been synchronized with the account of the person who created it stays there. On someone else’s computer it is still best to work in a private window.
When you are signed in to your user account, you can additionally save content server-side to your profile (limited storage of up to 50 MB, see section 6). This content is stored with the host (section 3) in Germany, is assigned to your account and serves to keep your work available and usable across devices. The legal basis is Art. 6(1)(b) GDPR (performance of the user relationship). When your account is deleted, this content is deleted as well.
Note on confidentiality: Content saved server-side is stored unencrypted in the database; there is no end-to-end encryption. It is therefore visible to me as the operator and technically to the host (see section 3). Access only takes place where it is necessary for operating the service — for example to investigate a fault at your request, to restore data after an incident, or to comply with legal obligations. The administration interface does not display the contents of your tool data. Content that stays exclusively in your browser (see above) is not affected. Please do not save information server-side that you consider particularly confidential.
Certain particularly sensitive data is deliberately refused by the server: the hearing profile (audiogram) from SoundSense constitutes health data within the meaning of Art. 9 GDPR and is rejected server-side — it remains exclusively local to your browser.
13a. Show Clock – share links, rider files and synchronization
Show Clock is made for sharing: you pass your timetable on to crew, bands and technicians. This section explains which data sits on my server when you do, who can see it and when it is deleted. Timetables, notes and riders often contain information about third parties (names, phone numbers, and in riders sometimes allergies or intolerances, i.e. health data). Please put into a share link only what its recipients really need.
Share links (live view)
When you share a timetable, the server stores a copy of it under a random identifier that is
part of the link (/show-clock/view?s=…). Stored are: the show title and timetable
name, the slots (label, type, times, duration, day), the start date, a running-late offset,
the current cue, the color theme and – if set – your logo. Notes and
riders are included only if the link expressly grants them; without that
grant the copy does not contain them, not even hidden.
Who can see the content? Anyone who has the link – no account is needed. The
identifier cannot be guessed, but whoever forwards the link also forwards the content. The view
is closed to search engines (noindex). Open views ask the server for changes every
few seconds; this produces the usual server log files (section 4).
For how long? A link exists until you withdraw it. You can delete any link at any time in your account under Share links; it stops opening immediately. Links you have not updated for 90 days are deleted automatically by the server – but not until 30 days after the last day of the show, if the timetable carries a date. Deleting your account deletes all your links.
Snapshot links (?c=… or ?show=…) work differently:
the whole timetable is contained in the link itself. The server keeps no copy; when the link is
opened, the address is merely recorded in the server log files like any other (section 4). A
snapshot link therefore cannot be withdrawn – only the rider files it refers
to stop opening once no live link grants them any more (see below).
Rider files
Files you attach to a slot (PDF, PNG, JPEG, WebP or GIF, up to 10 MB each) are at first stored only in your browser. While you are signed in, Show Clock uploads them to your account automatically so that you can open them on your other devices too; for a link with riders access they are uploaded as well. The files are stored non-publicly on the host’s server in Germany (section 3) and can only be retrieved through an address that cannot be guessed.
You can always open your own files on your devices. Other people can reach a file only while a live link of yours contains it with riders access. If you withdraw riders access, remove the file from the slot or delete the link, the file can no longer be retrieved by link holders from that moment on (I cannot, of course, recall copies that were already downloaded). Files are deleted when you remove them from the slot, when the link they were uploaded for is deleted, and when your account is deleted; a daily clean-up run removes orphaned files.
Please upload only files you are entitled to pass on (e.g. the rider the band sent you for this show). Reports of illegal content in hosted files or share links can be sent to me by email at support@squaresmile.de (subject “Content report”, with the link and a short reason). I review every report, block access where a report is substantiated, and inform the person who shared the content.
Push notifications for a link
If someone enables notifications in the shared view (section 10), the server stores the push subscription (endpoint and keys, and the chosen slot if any) together with the link. The content of the notifications is transmitted to the browser in encrypted form. The subscription is deleted when the person unsubscribes or when the link is deleted.
Automatic synchronization
Like the other tools listed in section 13, Show Clock synchronizes its data with your account automatically as soon as you are signed in – without a separate save step. This covers your timetables including slots and notes, the list of your timetables, settings (e.g. color theme, 12/24-hour display, warning time, title), the access keys of your share links, the current cue and running-late offset and – if you set a location for the weather display – the coordinates of that location. This way every device you are signed in on shows the same state. Section 13 applies to this data (stored with the host in Germany, unencrypted, deleted with the account). The legal basis is Art. 6(1)(b) GDPR (performance of the user relationship); the same applies to share links and rider files.
13b. Microphone access in the tools
Some tools analyze the sound that your device’s microphone or audio interface delivers:
- PitchSense – live tuner: detects frequency and note
- BPM Forge – tuner (the “Tuner” tab) and the freely accessible tuner demo at squaresmile.de/online-tuner: detects the pitch
- TempoSense – detects tempo and the beat; also the freely accessible demo at squaresmile.de/temposense
- SpectraSense – shows the frequency spectrum and finds feedback frequencies; it also measures sound levels (level meter and level protocol) and a system’s transfer function
- RoomSense – the “LUFS” tab (live loudness meter) and the “Level” tab (level monitor, calibration and level protocol) and “Measure the reverb” (Venue tab: the reverberation time from a bang, a clap or a sine sweep – a test signal that RoomSense, when you click, plays through your device’s audio output into your sound system and records with the microphone at the same time) and “Measure the delay at the spot” (System tab: the time of flight from a loudspeaker to the listening spot)
How the access works
- Only when you ask for it: a tool only accesses the microphone when you press the tool’s start button, and your browser asks for your permission first. While a tool is listening, your browser or operating system shows this (e.g. with a microphone or recording icon).
- Only on your device: the sound is analyzed exclusively in your browser on your device. It is not recorded, not uploaded and not stored – neither on my server nor with any third party.
- End of access: access ends when you stop the measurement or close the page. PitchSense, BPM Forge’s tuner, the tuner demo and SpectraSense also release the microphone as soon as you switch tabs; so does TempoSense, unless you have switched on a MIDI output. Exception: on a computer, a SpectraSense level log or transfer measurement that is running – or a level log waiting for a start time you set – keeps listening in the background, so it has no gaps and the scheduled log can start; on a phone or tablet the microphone is released then too. The measurements in RoomSense deliberately keep running in the background (e.g. for a level measurement across a whole evening). The sweep measurement in RoomSense, however, ends at once when you switch tabs or the page goes to the background; the test signal stops with it.
- SpectraSense – two inputs at once: to calibrate a device’s built-in microphone against a measurement microphone, SpectraSense can open two inputs at the same time when you click (e.g. a USB measurement microphone and the built-in microphone). The sound is still analyzed only on your device; only the resulting curve is stored, if you add it to your microphone library.
- SpectraSense – UMIK-1 by serial number (optional): if you fetch a miniDSP UMIK-1’s calibration file by its serial number, the serial number you type is sent to my server, which uses it to request the file from miniDSP’s website and passes it back to your browser. My server neither stores nor logs the serial number; miniDSP sees a request from my server, not from you. You can upload the file yourself instead. If you save the microphone, its serial number is kept in your microphone library like any other (see below).
- So a tool can tell you which other tab is using the microphone, open tool pages tell each other inside your browser whether they are listening and the tool's name; this never leaves your device and is not stored.
What is stored
Sound recordings are never stored – only settings and, where the function needs them, individual measured values from which the sound cannot be reconstructed:
- PitchSense: the A4 reference, waveform and note-name system (synced with your account); the volume, the engineer's view settings and the note history stay on your device.
- BPM Forge: the tuner settings (e.g. instrument, tuning, A4 reference). The tuner demo stores nothing.
- SpectraSense: its settings (display, detection and the A4 reference), synced with your account. The audio input you chose last – the identifier your browser assigns to it for this website, and the input’s name – stays on your device and is not synced. The list of rings it found (time, frequency and note of each, the suggested cut and the labels you type) is kept only in your browser on this device and is never uploaded. When you are signed in, two libraries are also synced with your account: the snapshot library – stored spectra (a frequency spectrum averaged over a few seconds, not a sound recording) and transfer curves, each with its time, the names and notes you type, the name of the show or venue you file it under and the name of the microphone it was measured with – and the microphone library: for each microphone its name, type, maker and model, optionally its serial number, its calibration curves and its sensitivity. A calibration file you loaded earlier is copied into the microphone library once (with its file name and serial number). The measurement functions store the following only in your browser on this device; none of it is synchronized with your account or uploaded: the chosen input channel; which microphone is on which input; this browser’s calibration (the content of a microphone calibration file you load, including its file name and serial number – a copy of it is in the microphone library, as described – and the SPL calibration values with their date); the level log (per second one A-, one C- and one unweighted (Z) value, the peaks and the highest Fast and Slow values); the meters you set up and the protocol plan (row interval, values, start and stop time); and saved level protocols including the details you type in (e.g. organizer, author, event, venue, sound engineer) – the snapshot library only lists them. A log is saved as a protocol when it stops. You can export all of it as a file yourself, and a protocol also as a CSV or PDF file. If you tap Yes or No under a ring in the Found list (“Was it feedback?”), SpectraSense stores your answer together with the numbers its detector calculated for that ring (for example how far the peak stood above its surroundings, how quickly it rose, how steady its pitch was, the Sensitivity setting). No sound, no recording, no spectrum, no time of day and no location are stored. The answers are kept only in your browser’s local storage on that device (at most 2,000 entries); they are not synced to your account and are not sent to me. You can export them as a JSON file (Settings → Your answers → Export labels) to share them voluntarily, and delete them at any time (Delete labels, or by clearing the site’s data in your browser). No legal basis is needed for processing that never leaves your device; if you send me an export, I use it to improve the detector on the basis of your consent (Art. 6(1)(a) GDPR).
- TempoSense: the settings including the chosen audio input and, if you record the set log, the measured tempo per section. Both stay in your browser; the set log only leaves your device if you export it as a CSV file.
- RoomSense: the level monitor keeps a log of the measured levels (one A- and one C-weighted value per second) in your browser. The calibration value, this level log and saved level protocols stay on your device; a protocol leaves it only as a file you export yourself. Values you carry over from a measurement into an input field are stored in the venue profile like the rest of your input. The level log also holds the C-weighted peak level of each second; from it, the crew dose works out the exposure per role on your device. For the reverb measurement and the delay finder, the sound is held only in your browser’s memory while it is analyzed and is not stored; only the results you take over are stored (the reverberation times into a visit, the measured time of flight into the delay plan). The same applies to the recording of a sine sweep and the impulse response worked out from it: they are analyzed only on your device (partly in a background process of your browser), not stored and not uploaded; until you close it, the page keeps only the resulting decay curves and reverberation times. An impulse response you load as a WAV file is likewise read only in your browser and not uploaded. If you pick a measurement mic from your mic library, RoomSense applies its calibration curve in your browser; which mic this device uses stays on the device with a copy of the curve.
Which of these data are synchronized with your account is set out in section 13.
Withdrawing permission
You can withdraw the permission at any time in your browser’s site settings (usually via the icon to the left of the address) or in your operating system’s privacy settings. The functions that need the microphone are then unavailable; every other part of the tools keeps working.
Legal basis
Access to your device’s microphone is strictly necessary for the service you have expressly requested – the measurement you start yourself (Section 25(2) no. 2 TDDDG). Where personal data is processed in the process (for example when voices in the room are audible), this happens exclusively on your device and in order to provide the function you are using (Art. 6(1)(b) GDPR) or on the basis of my legitimate interest in offering you the analysis you requested (Art. 6(1)(f) GDPR).
13c. SetlistForge – read-only set link
If you create a read-only link to a setlist in SetlistForge (“Share read-only link”), the server
stores a copy (a snapshot) of that setlist under a random identifier that cannot be guessed and is
part of the link (/setlist/view/…).
What the link shows: the show’s title, date, venue and artist, the setlist’s name, and for each song its title, duration, key and BPM (for medleys, the titles of the parts), plus the set breaks with their label and planned length. Your stage notes on the songs are included only if you tick “Include stage notes”, and your lighting cues only if “Include lighting cues” is ticked (it is ticked by default; you can untick it). While the page is open it asks the server every 30 seconds whether you have updated the link; that request carries no personal data beyond what every page request does. Never included are composers, lyricists, arrangers, publishers, ISWC codes and any detail for royalty reports (e.g. organizer and addresses, phone numbers, member numbers, ticket prices, revenue, costs, fees); the server does not store these fields even if they are sent to it.
Who can see it? Anyone who has the link – no account is needed. Whoever forwards
the link also passes on its content. The page is closed to search engines (noindex)
and does not pass its address on when a visitor follows a link from it. The server counts how often
the page was opened, without any details about the people; each visit produces the usual server
log files (section 4).
For how long? The link shows the state of your last click on “Create link” or “Update link”. It works until 90 days after the last update – if the show carries a later date, until 30 days after the show, but never longer than one year. After that it says “Link expired”, and a daily clean-up deletes the copy. “Stop sharing” in SetlistForge, or deleting it under Share links in your account, removes the link at once; deleting your account deletes all your links. An account can have at most 50 set links active at a time.
Show details and notes can contain other people’s data (e.g. names). Please share only what the band really needs. The legal basis is Art. 6(1)(b) GDPR (performance of the user relationship).
13d. RiderSmith – read-only venue link
If you create a read-only link to a rider in RiderSmith (“Venue link”), the server stores a copy (a
snapshot) of that rider under a random identifier that cannot be guessed and is part of the link
(/rider/view/…).
What the link shows: the band, the venue, town and date of the show, the version number with its date and the list of changes since the previous version, the logo and band photo, and every section you switched on in the rider (heading, tables such as the input list, standard texts, your own texts and the attached image). Of the contact block only the contact person and the web address are included; phone numbers and email addresses only if you tick “Include contact details”. Never included are your account’s email address, your other riders and anything outside the rider; the server does not store such fields even if they are sent to it.
Who can see it? Anyone who has the link – no account is needed. Whoever forwards
the link also passes on its content. The page is closed to search engines (noindex)
and does not pass its address on when a visitor follows a link from it. The server counts how often
the page was opened, without any details about the people; each visit produces the usual server
log files (section 4).
For how long? The link shows the state of your last click on “Create link” or “Update link”. It works until 90 days after the last update – if the rider carries a later show date, until 30 days after the show, but never longer than one year. After that it says “Link expired”, and a daily clean-up deletes the copy. “Stop sharing” in RiderSmith, or deleting it under Share links in your account, removes the link at once; deleting your account deletes all your links. An account can have at most 50 venue links active at a time.
A rider often carries other people’s data (e.g. crew names). Do not enter health data (such as allergies or intolerances), religion, passport numbers or dates of birth – “on request” is enough; tell the promoter such things directly. Please share only what the venue really needs. The legal basis is Art. 6(1)(b) GDPR (performance of the user relationship).
Responses to a RiderSmith link. If you answer a rider through a RiderSmith link as a venue, promoter or venue technician, I process your name, your role, your email address, your answer (“Accepted” or “Accepted with changes”), the rows and clauses you struck through, your notes on them, and the date and time. You do not need an account; the form uses a strictly necessary session cookie. Only the person who sent you the link sees these details; the link page itself shows your name, role, date and marks, not your email address – anyone with the link can read that page. To limit abuse I count answers per IP address for at most one hour; the IP address is not stored with the answer. The answer records which version of the rider you agreed to (Art. 6(1)(b) GDPR where you are a party to the contract, otherwise Art. 6(1)(f) GDPR: both sides’ legitimate interest in showing which version was accepted); it is not an electronic signature. The answer is deleted with the version it belongs to: when the rider or the sender’s account is deleted, and at the latest 12 months after the show date (without a show date: 12 months after it was sent). A submitted answer cannot be changed.
Stage Plot Generator – link to a venue. If you send a stage plot through a read-only link, the server stores every version you send unchanged (plot, input list, outputs, monitor mixes, backline, personnel and an image of the drawing) under a random identifier in the link. The server removes contact details (phone, email, promoter line) and your notes from earlier responses. Anyone with the link can read that version; the link is valid for 360 days after the last send. If someone answers through this link, the paragraph “Responses to a RiderSmith link” applies accordingly – instead of rows and clauses, these are the rows of the input list, outputs, monitor mixes, backline and personnel, and notes on sections and on the drawing. I delete versions and responses when the stage plot or your account is deleted, and at the latest 12 months after the date of the show (without a show date: 12 months after it was sent).
Email notice. When a venue or promoter answers a contract link, I send you, as the sender, an email notice with the responder's name, role and answer and the number of struck lines and notes; it is sent through the platform's mail server, with the responder's email address set as the Reply-To address. You can switch this notice off in your account or with the link in each of these emails.
13e. RoomSense – read-only venue sheet (link and QR code)
If you create a read-only link to a saved venue in RoomSense (“Share link”), the server stores a copy
(a snapshot) of that venue profile under a random identifier that cannot be guessed and is part of
the link and the QR code (/venue/…). Only accounts with a confirmed email address can
create links.
What the link shows: the venue’s name, town, country and kind, and for each room (at most 20) its name, room type, dimensions, audience size (seated or standing), surfaces, air temperature and humidity, the acoustics summary (the estimate calibrated from a measurement when the room has one, otherwise the reverberation time last measured in a visit, otherwise the predicted one, with its date), the verdict on level, speech and music, the delay settings of the latest visit, the audience level rule, stage, power connections and rigging points – with the labels and locations you type in for them. If a room has a plan (RoomSense, “Stage & audience”), the link also shows where the stage stands in the room, the FOH position and the audience areas with their kind, size, a balcony’s floor height and the labels you type in for them. The street address and your notes for crews are included only if you tick “Include the street address” or “Include notes for crews”. Never included are contact details, the list of your visits and their notes, earlier versions, correction values, level logs and level protocols, your name and your account’s email address; the server does not store such fields even if they are sent to it.
Who can see it? Anyone who has the link or scans the QR code – no account is
needed. Whoever forwards the link also passes on its content. The page is closed to search engines
(noindex) and does not pass its address on when a visitor follows a link from it. The
server counts how often the page was opened, without any details about the people; each visit
produces the usual server log files (section 4). Someone who opened the page once can keep reading
it offline in their browser – even after you stop sharing. With “Add to my venues”, a person with a
Squaresmile account can take the sheet into RoomSense as their own copy; that copy is then theirs
and stays when you stop sharing.
For how long? The link shows the state of your last click on “Create link” or “Update link”. It works until 365 days after the last update or – if you choose so – until 30 days after it. After that it says “Link expired”, and a daily clean-up deletes the copy. “Stop sharing” in RoomSense, or deleting it under Share links in your account, removes the link at once; deleting your account deletes all your links. An account can have at most 50 venue links active at a time (one per venue).
Notes and labels can contain other people’s data. Do not put names, phone numbers or email addresses into them, and share only what the crew really needs. The legal basis is Art. 6(1)(b) GDPR (performance of the user relationship).
14. Newsletter and product updates
During registration you can voluntarily tick the box “Send me occasional updates about new tools by email”. The box is not pre-selected, and consent is not a condition of registering or of using the platform. You can also give or withdraw it at any time later in your account under email preferences.
Data processed: your email address and the time of your consent; the name stored in your account may be used for the salutation. No separate mailing list is kept — the recipients follow from the consent timestamp on your user account. The legal basis is your consent under Art. 6(1)(a) GDPR.
Sending: Emails are sent from my own platform via the mail server of my host ALL-INKL.COM in Germany (see sections 3 and 7). I use no external newsletter service (e.g. Mailchimp, Brevo, CleverReach); your address is therefore not passed on to any further recipient for this purpose. The emails contain no tracking pixels and no open or click tracking.
Confirming your address: Consent is given inside your password-protected user account, and your email address is verified via a confirmation link during registration anyway (see section 7). I therefore do not send an additional confirmation email for the newsletter alone (a separate double opt-in).
Withdrawal: You can withdraw your consent at any time with effect for the future — using the checkbox in your account’s email preferences, using the “manage your email preferences” link at the end of every such email, or informally by email to support@squaresmile.de. On withdrawal, the stored consent timestamp is deleted and you receive no further updates. The lawfulness of processing carried out up to the withdrawal remains unaffected.
Transactional emails (e.g. email address confirmation, password resets, license and account information) are independent of the newsletter. They are necessary for the performance of the user relationship and are sent regardless of this consent (see section 7).
15. Recipients of the data / processors
Your data is passed on only to the extent necessary for the performance of the contract, for the functioning of the features you use, or for the operation of the website, to the following recipients:
- ALL-INKL.COM – Neue Medien Münnich (hosting and the sending of transactional and newsletter emails, Germany)
- Gumroad, Inc. (order processing and license validation for the paid products, USA)
- PayPal (Europe) S.à r.l. et Cie, S.C.A. (processing of voluntary donations, Luxembourg)
- Open-Meteo (weather data in the Show Clock, only when used)
- The push service of the respective browser/device manufacturer (web push notifications, only if opted in)
- GitHub, Inc. (provision of the installer files and the version file for the KlarFunk and Lighting Watchdog desktop applications, USA — see sections 12a, 12b and 12d)
- Apple Distribution International Ltd. / Apple Inc. (song search, cover images and previews for SelektorCue – queried by our server, without guests' data; Ireland/USA – see section 12c)
- GetSongBPM, ReccoBeats, MetaBrainz Foundation (MusicBrainz) (song data in SelektorCue – information about the title only, no personal data; see section 12c)
- Google Ireland Limited / Google LLC and Apple Distribution International Ltd. / Apple Inc. (signing in with Google or Apple, only if you choose it; Ireland/USA – see section 6a)
16. Your rights
Under the GDPR you have the following rights regarding your personal data:
- Access (Art. 15 GDPR)
- Rectification (Art. 16 GDPR)
- Erasure (Art. 17 GDPR)
- Restriction of processing (Art. 18 GDPR)
- Data portability (Art. 20 GDPR)
- Objection to processing based on Art. 6(1)(f) GDPR (Art. 21 GDPR)
- Withdrawal of consent given, with effect for the future (Art. 7(3) GDPR)
An informal email to support@squaresmile.de is enough to exercise them.
17. Right to lodge a complaint with a supervisory authority
You have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for me is:
Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW)
Kavalleriestraße 2–4, 40213 Düsseldorf, Germany
www.ldi.nrw.de
18. Currency of this policy
This privacy policy is adapted whenever something changes in the data processing (e.g. when new services or new features are integrated).
Last updated: November 2026 — non-binding translation of the German Datenschutzerklärung.