Last updated: 06.11.2026

Privacy Policy

eterlab is a Mac app for DJs who stream their sets: it recognises the tracks being played, shows them on the stream and collects comments from live chats. This policy explains what data we process, why, for how long and what your rights are. Like the app, it is in beta.

1. Data controller

HEXO GROUP Sp. z o.o., ul. Gerberowa 4AA, 52-221 Wrocław, Polska, NIP 8943162915. Privacy contact: privacy@eterlab.app. General contact: hello@eterlab.app.

2. Scope

• The eterlab.app website – beta information, beta sign-up and app download with an invitation code.
• The eterlab app for macOS (closed, invite-only beta), the eterlab.app server it connects to, and the third-party services the app uses.

3. Website

• Ads and measurement (Meta, TikTok) – only with your consent. We run advertising campaigns on Meta (Facebook, Instagram) and TikTok. On your first visit a banner asks for your consent. Without it we load no scripts from these companies and set no cookies; the choice itself is remembered in this browser’s storage (localStorage). After you consent, these load: Meta Pixel (Meta Platforms Ireland Ltd, Dublin) and TikTok Pixel (TikTok Technology Ltd, Dublin). They may set cookies (e.g. _fbp, _fbc, _ttp) and pass to these companies your IP address, browser data, the pages of eterlab.app you visited and the fact of a confirmed beta application – to measure and optimise our ads (these companies may also use the events to build audiences). You can withdraw consent at any time with the “Privacy settings” button in the footer (we then also delete the pixel cookies). These companies process the data under their own terms (Meta, TikTok) and may transfer it outside the European Economic Area.
• We do not use Google Analytics or any analytics tools other than the advertising pixels described above.
• Which events we measure after consent. Visiting the site, clicking the beta sign-up button, submitting the form, confirming the application and downloading the app. So that an application can be attributed to a campaign even if you come back after a few days, after consent we keep the campaign parameters from the ad link in your browser’s storage (localStorage) for 30 days; withdrawing consent removes them.
• Instant forms in ads. If you leave your details in a form inside an ad on Facebook, Instagram or TikTok, the form data (first name, last name, email, answers) is processed first by that platform under its own terms and then reaches us only to select beta testers; you give your consent in the form’s text and can withdraw it by writing to privacy@eterlab.app. We label such applications “lead-form”.
• Events sent from the server (the same consent as in the banner). If you choose “Accept” in the banner (or turn on “Ads and measurement” in the settings), once your application is confirmed our server sends a “Lead” event to Meta and/or TikTok: a hashed (SHA-256) email address, the IP address and browser details at the time of confirmation, and the ad click identifier (fbclid / ttclid). Click identifiers are stored with your application only in that case. Campaign parameters and click identifiers are deleted together with the application. Without this consent nothing is sent and your application works the same.
• Download with a code. We check the invitation code and count downloads. To prevent code guessing we store a keyed, irreversible hash of your IP address (not the address itself) for up to 24 hours.
• Beta sign-up (eterlab.app/beta-testing): first name, last name, email, a link to your channel or stream, the platforms you stream on and – if you enter it – your console. We use them only to select testers and to contact you about the beta. We send an email with a confirmation link to the address you enter (from our beta@eterlab.app mailbox at dhosting.pl; at most 3 emails per address per day) – we only consider the application once you open the link and confirm it with the button, and unconfirmed applications are deleted after 7 days. Against bots: a hidden field, a minimum time to fill in the form and a limit on applications, for which we store a keyed, irreversible hash of your IP address (not the address itself) for 24 hours. If we pick you as a tester, your first and last name become the name of your invitation code, and your email, link, platforms and console go into its note; the application itself is deleted. You can withdraw your application at eterlab.app/unsubscribe (after email confirmation we delete it immediately; if you already have a tester code, we handle the request to delete it within 30 days).
• Launch and news notifications – only if you tick a separate, optional consent box in the form (the application works without it). Once you confirm your address, we store your email, first name, language and the date of consent so we can let you know when the app is available to everyone and about important news. This also applies to people picked as testers. You can unsubscribe with the link in the confirmation email or in any message (and the “Unsubscribe me” button), at eterlab.app/unsubscribe, or by emailing privacy@eterlab.app. We will send messages to the list through MailerLite (UAB “MailerLite”, Vilnius, Lithuania), which will then receive only this data, as a processor under a data processing agreement; until then the list is kept only on the eterlab server.
• Where your application came from. When you arrive from one of our ads or from a link tagged with campaign parameters, the address carries them (utm_source, utm_medium, utm_campaign, utm_content, utm_term). We pass them on in the site’s links and store them with your beta application so we know which campaign works. No cookies or browser storage are used for this. We also count visits from such links anonymously (how many times a day a source and campaign is visited) – without IP addresses, browser data or any identifiers.
• Hosting logs. Our hosting provider (dhosting.pl) keeps standard server logs (IP address, time, request URL, browser) for security purposes, for the period set by its own rules. From version 0.73 the app sends the licence and computer identifiers in request headers, so they do not appear in these logs; older versions put them in the URL of update requests.

4. The app – what is sent to the eterlab server

While a code is active, the app contacts eterlab.app (every few seconds while streaming, every few minutes otherwise) for the beta licence, updates and technical support. It sends:

• Activation: the invitation code, a computer identifier (a hash derived from the Mac’s hardware identifier), the Mac model (e.g. “MacBook Pro”) and the app version. We do not store the computer name (which often includes a first name) – names stored earlier were replaced with the model on 27 Sep 2026.
• Technical information: app version, Mac model and chip, macOS version and language, CPU and memory load, free disk space, battery state, network type, the audio input name (may include a name, e.g. “AirPods – Jane”), OBS status (scene, streaming service, bitrate), the app’s self-check results (e.g. whether audio is coming in, whether the console and chat work), for a DJ console on the local network: detected devices (model and local IP address), network adapters with their local IP address and the state of the console ports with the name of the program using them (e.g. rekordbox), and up to 10 recent error messages – without keys, your macOS account name or tunnel addresses.
• Set timeline: recognised tracks (artist, title, label, cover URL), recognition source and timing, audio level (numbers only, no recordings).
• Chat and viewers – numbers only: how many comments came from each platform, how many viewers there are, for how many commenters a profile picture could be loaded and whether chat connections work. Chat messages and viewer names are not sent – except as described under diagnostics below and for Kick chat.
• Kick (when you connect your Kick account): your Kick channel name and channel ID – linked to your code so that chat can be connected only to your own channel (we do not store the account name; the link is removed when you disconnect the channel or the code is disabled or deleted). The eterlab server then subscribes with Kick to that channel’s events and passes to the app the chat messages (viewer nickname, ID and avatar, colour, badges, text, emotes), stream status changes and viewer bans, plus the viewer count read from the Kick API. Details in section 8.
• Twitch (a channel link without a connected account – from versions before 0.73 or left after signing out): the Twitch channel name – the server reads its stream status and viewer count from Twitch (section 8).
• YouTube (a channel or broadcast link without a connected account – from versions before 0.73 or left after signing out): the YouTube channel or broadcast name or ID – the server reads its stream status and viewer count from YouTube (section 8).
• Facebook and Instagram (when you connect your Facebook account): the eterlab server mediates the sign-in – it exchanges the one-time code from Facebook for a token (this requires the eterlab app secret), reads your Facebook name and ID, the list of Pages you manage with their linked Instagram accounts and their tokens, passes them to the app and deletes them right after they are collected (at the latest after 10 minutes). Details in section 8.
• Diagnostic report: when you send it in the app (“Send diagnostics”, with your “What’s not working?” message) or when an eterlab support person requests it and you agree (“Send report” – you can decline, and then nothing is sent). It contains self-check results, settings without keys or passwords, the last 60 lines of the app log (without keys, your macOS account name or tunnel addresses; from version 0.73 without viewer nicknames or comment text), the Mac’s network interfaces and addresses, and devices found on your local network (e.g. Pioneer players). Reports are read by an eterlab support person, who uses an AI assistant (Claude by Anthropic) for analysis and passes the report to it with email addresses, nicknames and comment text masked. App versions older than 0.73 (which do not ask for consent) are not sent report requests.
• On our side: when we create a code we give it a name and a note (e.g. your first name and how we know you) so we know who it was given to. The code history records activations, versions, downloads and service connections – without IP addresses or platform account names.
• Remote help (only when you turn it on): one-time links with an access key to view the app and the comments panel; control only works after you allow it (“Allow”) and lasts until you end it or turn off remote help. While remote help is on, its indicator is always visible at the top of the app. Through it, a support person cannot send a diagnostic report or change the addresses your keys are sent to.

API keys, passwords and platform tokens are not sent to the eterlab server, and the server rejects fields that look like secrets.

5. Purposes and legal bases

• Licence, downloads and updates – performance of a contract (Art. 6(1)(b) GDPR).
• Fixing bugs, stability, technical support, security and abuse prevention – our legitimate interest (Art. 6(1)(f) GDPR).
• Remote help, remote control of the app and diagnostic reports requested by eterlab – your consent (Art. 6(1)(a) GDPR), which you can withdraw in the app at any time.
• Beta sign-up – your consent given in the form (Art. 6(1)(a) GDPR), which you can withdraw at any time at eterlab.app/unsubscribe or by emailing privacy@eterlab.app.
• Launch and news notifications – your separate consent (Art. 6(1)(a) GDPR), which is also your consent to receive commercial information from us by email (Polish Electronic Communications Law); you can withdraw it at any time with the “unsubscribe” link or by emailing privacy@eterlab.app. We keep the date of consent so we can show that you gave it (Art. 7(1) GDPR).
• Passing Kick chat to the app – performance of a contract with you (Art. 6(1)(b) GDPR); viewers’ chat data – our legitimate interest in providing the chat feature you request (Art. 6(1)(f) GDPR).
• Where an application came from (campaign parameters) – our legitimate interest in assessing how campaigns perform (Art. 6(1)(f) GDPR).
• Advertising pixels in the browser and events sent from the server – your consent (Art. 6(1)(a) GDPR and the ePrivacy rules on storing and reading information on your device), which you can withdraw at any time; withdrawal does not affect the lawfulness of earlier processing.

We do not sell data and we do not build profiles ourselves; Meta and TikTok process pixel data under their own terms. App data is not used for advertising. To measure our own ads we use only the tools described in section 3, and only with your consent.

6. Retention on the server

7. What stays on your Mac

Most data is kept locally, in the app folder (usually ~/Documents/eterlab) – we have no access to it:

• Settings – e.g. gig schedule, social media profiles, My list of tracks, chat links, Twitch login, audio input name, and keys and tokens for services (ACRCloud, AudD, Social Stream Ninja, Euler Stream, Twitch, Google/YouTube, Facebook, Cloudflare tunnel). They are stored in the settings file in the app folder; the folder and the settings, key and log files are readable only by your macOS account. You can delete a saved key with the bin icon next to its field.
• My list from a folder – the app reads only the tags of music files (artist, title, label, cover art) on the DJ’s computer; the files themselves are never uploaded. When the tags lack a label or cover, only the artist and title are sent to Deezer and Apple (as for recognised tracks). Covers from files and custom covers are saved locally in the app data.
• Profile (Settings › Account, from version 0.75) – nickname, first and last name, email, photo and consent to news. They stay on your Mac – the app does not send them to the eterlab server. The nickname and the number of the current live are also visible to anyone you give the comments panel link to (e.g. a moderator); they do not see your name, email or photo.
• Set history and tracklists – kept with no time limit until you delete them.
• App log – contains e.g. recognised tracks and the platform of a comment selected for the screen (from version 0.73 without nicknames, comment text or the computer name). Above 2 MB a single older copy is kept.
• Chat comments – in memory only (last 200), gone when the app closes.
• Audio sample for recognition – deleted right after recognition (at the latest after 25 seconds).

8. Third-party services used by the app

The app connects to these services directly from your Mac; the data does not pass through our server (the exceptions are Kick, the Twitch and YouTube viewer counts from a link and the Facebook sign-in – described below). Each of these companies sees your Mac’s IP address and applies its own privacy policy.

• Apple ShazamKit (on by default) – Apple receives only an audio fingerprint (a digital signature) computed on your Mac from the last several seconds; the recording itself never leaves the computer.
• ACRCloud and AudD (off by default, with your own keys) – when enabled, they receive a short audio sample (4–12 seconds) from your audio input, usually only when Shazam does not recognise the track.
• Deezer and Apple iTunes Search – cover art, label and track details (looked up by ISRC, Apple Music track ID, or artist and title). Cover images load directly from Deezer and Apple servers.
• YouTube – the app uses YouTube API Services. After Google sign-in (“Connect YouTube”) it requests read-only access only (youtube.readonly): it finds your ongoing broadcast and reads its chat and viewer count directly from YouTube on your Mac, without the eterlab server. The token is stored on your Mac; “Disconnect” next to your YouTube account (Settings › Chat) asks Google to revoke it (if Google cannot be reached, e.g. without a network, the app says so and you can revoke access in your Google account settings). The app never publishes or changes anything on your channel. Once your account is connected you can also add a link to another broadcast – the app reads its chat and viewer count directly from YouTube with your token. Without a connected account (links from versions before 0.73 or left after signing out) chat is not read, and the eterlab server uses YouTube API Services (the eterlab project key, with no access to your account) to read only the stream status and viewer count. (Up to version 0.72 you could also enter your own YouTube API key – it was stored only on your Mac; from version 0.73 this option is gone and the app deletes a saved key.) By using these features you agree to the YouTube Terms of Service; the Google Privacy Policy applies. You can also revoke the app’s access to your Google account at security.google.com/settings/security/permissions. eterlab’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. With whom we share this data and how we protect it: Google user data.
• Twitch (when you connect your account) – the app requests only permission to read chat (user:read:chat); the token is stored on your Mac, and the app then reads chat, the viewer count and the profile pictures of people chatting (public Twitch account data) directly from Twitch, without the eterlab server. Disconnecting in the app deletes the token from your Mac and asks Twitch to revoke it (if Twitch does not confirm it, e.g. without a network, the app says so); you can also do it in your Twitch connections settings. Once your account is connected you can also add another channel – the app reads its chat and viewer count directly from Twitch with your token, without the eterlab server. For channel links without a connected account (from versions before 0.73 or left after signing out) the eterlab server uses the official Twitch API (the eterlab app registered with Twitch, with no access to your account) to read only that channel’s stream status and viewer count – chat is available only after signing in. The Twitch privacy notice applies.
• Kick (when you connect your Kick account) – “Connect Kick” opens the Kick sign-in; eterlab asks only to read your account and channel name (user:read, channel:read) to establish which channel is yours. The sign-in is handled by the eterlab server (it needs the app secret): it reads the account and channel name, revokes the token with Kick right away and stores only the link between your channel and your code – no token is kept. Kick does not offer chat to desktop apps, so your channel’s chat is received by the eterlab server through the official Kick API (the eterlab app registered with Kick, scope events:subscribe). The server verifies Kick’s signature, passes the messages to the app and deletes them right after they are collected, at the latest after 24 hours; it keeps no chat history. The Kick privacy policy applies.
• Facebook and Instagram (when you connect your Facebook account) – Facebook sign-in (the eterlab app registered with Meta) with read-only permissions: the list of your Pages (pages_show_list), live videos and their stats (pages_read_engagement), comments on the Page (pages_read_user_content), the Instagram account linked to the Page (instagram_basic), its comments (instagram_manage_comments) and the public profiles of business and creator accounts (instagram_manage_insights – the Business Discovery feature). The app never publishes, replies or reads private messages. After sign-in the app reads your Page’s live videos, viewer count and comments (name and text) and comments on your Instagram live broadcasts (username and text) directly from Meta on your Mac; Instagram does not provide a viewer count. Commenter profile pictures: from Facebook – from the comment data; from Instagram – only when the commenter has a business or creator account, the app asks Meta for that public profile by username (Business Discovery). The app downloads Facebook and Instagram pictures itself to your Mac (once per person) and keeps them in memory only – they are gone when the app closes or Facebook is disconnected, and are not saved to disk or to the browser or OBS cache; neither the pictures nor their addresses reach the eterlab server. Private accounts and people without a picture get a letter instead. Tokens are stored on your Mac; “Disconnect” in the app deletes them from your Mac and asks Meta to revoke access (if Meta does not confirm it, e.g. without a network, the app says so), and you can also do it in your Facebook business integrations settings. The Meta Privacy Policy applies.
• TikTok (unofficial mode, off by default, only with your consent) – the app reads the public chat and viewer count of a live stream by account name. On each connection the Euler Stream service receives the live stream number (which identifies the account) and your Mac’s IP address.
• Social Stream Ninja – if you provide your session ID, the app receives chat comments and viewer counts through this service. Viewer pictures from Social Stream Ninja: when SSN sends them inside the message they stay in the app’s memory only; when it sends a link, they load directly from that platform’s server.
• Cloudflare – a secure tunnel, only when you turn on “Comments over the internet” or remote help; the comments panel (with your nickname and live number) and the app view go through it, available only with a key in the URL.
• GitHub and PyPI – one-time download of required programs (e.g. the tunnel tool) on first launch.
• Platform servers – viewer avatars and emotes load directly from YouTube, Twitch, Kick, TikTok and other platform servers; Facebook and Instagram pictures are downloaded by the app itself (see “Facebook and Instagram”).

The app uses no analytics, advertising or crash-reporting tools. Support for further platforms will be described here before it ships in the app.

Google user data (YouTube)

“Google user data” means everything the app receives through Google APIs after you sign in (“Connect YouTube”): the access and refresh tokens, your channel name and ID, information about your ongoing broadcast, the viewer count and chat messages (a viewer’s name, profile picture and message text).

Which YouTube API data we use

Deleting YouTube data. “Disconnect” (Settings › Chat) immediately deletes the token, the channel name and ID and the channel link added by the app from your Mac, and then asks Google to revoke access (if Google cannot be reached, e.g. without a network, the app says so and you can revoke access in your Google account settings). The app does the same when Google revokes access – e.g. when you revoke it in your Google account settings. You remove links you pasted yourself. From version 0.74 the app no longer writes the channel name or ID to its log, and on start-up it deletes such entries left by older versions. YouTube data stored on the eterlab server will be deleted at your request (privacy@eterlab.app, instructions: eterlab.app/delete-data) within 7 days at the latest – most of it is deleted after 24 hours anyway.

With whom we share, transfer or disclose Google user data

• We do not sell, share or transfer Google user data to anyone – not to advertisers, data brokers or any other company or person. We do not use it for advertising, profiling or to train artificial intelligence models.
• Tokens, chat messages, and viewer names and pictures stay on your Mac – the app reads them directly from Google and does not send them to the eterlab server.
• Only numbers reach the eterlab server: the YouTube viewer count, the number of chat messages and the connection status – to help you with technical problems and keep the app stable. Per-platform viewer counts are deleted from the server after 24 hours (section 6).
• A diagnostic report – sent only when you send it yourself or agree to it (section 4) – from version 0.74 does not contain your YouTube channel name or ID (the app masks them); reports from earlier versions may contain the name of your connected channel (one line of the app log) and are kept for 30 days. It never contains your token, chat messages or viewer names. The report is read by an eterlab support person; the channel name is removed from the report before any AI tool is used to help analyse it.
• The eterlab server is hosted by dhosting.pl (Poland), which stores the data above on our behalf as a processor and may not use it for its own purposes.
• We may disclose data only when required by law (e.g. a court order or a request from a competent authority).

How we protect Google user data

• Minimum necessary access: the app requests read-only access only (youtube.readonly) and never publishes or changes anything on your channel.
• Secure sign-in: you sign in on Google’s own page in your browser – the app never sees your password. The code exchange uses PKCE and a one-time state parameter, and Google sends the response only to a local address on your Mac (127.0.0.1).
• Encryption in transit: connections to Google and to the eterlab server use HTTPS (TLS) only.
• Token storage: only on your Mac, in the app’s settings file readable only by your macOS user account. Tokens are never written to the log, diagnostic reports or the eterlab server.
• Chat messages are kept in the app’s memory only – they are not written to disk and disappear when the app closes.
• Disconnecting: “Disconnect” (Settings › Chat) deletes the token, the channel name and ID and the channel link added by the app from your Mac and asks Google to revoke access (if Google cannot be reached, e.g. without a network, the app says so); you can also revoke access at security.google.com/settings/security/permissions.
• The eterlab server: only eterlab can access the admin panel – at a non-public address, after signing in with a password, with login rate limits and automatic sign-out; database files have no web address.

9. Data of your stream viewers

The app processes chat comments (nickname, text, avatar, platform, support) on your Mac to show them to you and – when you choose – on the stream. It does not store them in set history or in the log and does not send them to the eterlab server (in versions older than 0.73 the nickname and beginning of a comment selected for the screen could appear in the log and thus in a diagnostic report – section 4). Kick chat passes through the eterlab server on its way to the app and is deleted there right after it is collected (section 8). A comment selected for the screen becomes part of the public stream image. As the streamer, you are responsible for what you show on your stream.

10. Your rights

You have the right to access, rectify and erase your data, to restrict processing, to data portability and to object to processing based on our legitimate interest. You can withdraw consent at any time. Write to privacy@eterlab.app – we reply within 30 days. You may also lodge a complaint with the Polish supervisory authority, the President of the Personal Data Protection Office (uodo.gov.pl).

How to delete your data, step by step: eterlab.app/delete-data.

11. Changes

If we change these rules we will update this page and the date at the top. We will announce significant changes in the app.