How we handle your personal data – collect little, sell nothing, track nothing. Last updated: 14 November 2026.
1. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) is:
Lukas Wójcik
Tuwima 61 m. 10
90-025 Łódź
Poland
Email: contact@luky.music
No data protection officer has been appointed, as the legal requirements for doing so are not met. Please send all data protection enquiries to the email address above.
2. Our principles at a glance
- No external analytics service, no advertising tracking, no social media plugins, no profiling.
- Fonts, scripts, images and audio are loaded from our own server – no data is transferred to third parties while you browse normally. The only exception is the script of the formconfirmed form protection on pages with forms, a service of the controller itself (section 8a).
- Only strictly necessary cookies are set, which is why there is no cookie banner.
- Third parties receive data only where this is necessary for a service you have requested: payment (Stripe), spam protection when certain forms are submitted (Google reCAPTCHA), and sending emails.
- We do not sell data and do not share it for advertising purposes.
3. Hosting and server logs
This website runs on a server operated by the controller in Łódź (Poland); no external hosting provider is involved. Each time the site is accessed, the web server automatically records: IP address, date and time, requested address, HTTP status code, amount of data transferred, referring page (referrer) and browser and operating system (user agent). These web server logs are rotated daily and deleted after 14 days.
In addition, the website records every page view in its own access log: IP address, the country derived from it, the page requested, the referring page, browser, operating system, device type, language and – if you are signed in – your account. From this, the operator compiles page-view statistics (page views, countries, devices) without any third-party service.
Purpose: delivering the website, ensuring security and stability, preventing and investigating attacks and abuse, analysing errors, and the page-view statistics. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure and functioning operation and in knowing how our own offering is used). Retention period: the website’s access log is deleted after 60 days and error logs after 90 days, unless a specific security incident requires individual entries to be kept longer as evidence.
Security-relevant events (e.g. sign-in, password change, account deletion, administrative actions) are recorded in a security log with the time, account and IP address and are deleted after 365 days (Art. 6(1)(f) GDPR).
4. Cookies and local storage
We use only cookies and local storage entries in your browser that are strictly necessary to provide the service you have expressly requested (Art. 399(3) of the Polish Electronic Communications Law of 12 July 2024 (Prawo komunikacji elektronicznej), Art. 5(3) of Directive 2002/58/EC; for users in Germany: § 25(2) no. 2 TDDDG). No consent is required for this.
| Name | Type | Purpose | Duration |
|---|---|---|---|
| bpid | Cookie | Session: sign-in, security token for forms, session language | until you close your browser |
| bp_remember | Cookie | only if you select “stay signed in” when signing in | 30 days |
| Preview cookie | Cookie | only for invited test listeners before the site is launched | 7 days |
| bp_theme | Local storage | your choice between light and dark theme | until you delete it |
| lm_player | Local storage | player state (queue, position, volume) | until you delete it |
| lm_saved_tracks_v1 | Local storage | tracks you save on this website | until you delete it |
| lm_sidebar, lm_sidebar_tab | Session storage | whether the player sidebar is open and which tab is selected | until you close the tab |
None of these entries is used to recognise you across other websites or for advertising purposes. You can delete or block cookies and local storage in your browser at any time; signing in and purchasing may then not work. For entries that Google reCAPTCHA may set when protected forms are submitted, see section 8. Our own form protection (section 8a) sets no cookies and stores nothing in your browser. Entries that YouTube may set only after your consent are described in section 16b.
5. Cookie-free listening statistics
So that the artist can see which tracks are being played, the website reports playback events (start, 30 seconds played, played to the end, skipped), opening of the player sidebar, clicks on buy buttons and the start of a purchase – including when a player is embedded on another website (section 15). We store the event, the track, release or product, the time, the country, the domain name of the referring website (without path) and a visitor hash. The hash is generated from the IP address, the browser signature and a secret random value that changes daily; it cannot be reversed and does not allow you to be recognised from one day to the next. The country is derived on our server from a local geolocation database; no request leaves the server for this. The IP address itself is not stored for this purpose.
Raw events are deleted after 90 days; after that, only anonymous daily totals remain. Clicks on smart links (/go/…) to streaming services are counted only as an anonymous daily number per service. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in privacy-friendly audience measurement of our own offering). You can object to this at any time (section 20).
6. Contact form and email enquiries
If you write to us using the contact form or by email, we process your name, email address, type of enquiry, message and – if provided – budget, timeframe and links, the page from which you are writing, your language and, if you are signed in, your account, and, to protect against abuse, your IP address, country and browser signature. You will receive an acknowledgement of receipt by email. The operator is informed of new messages by a notification that contains no personal data.
Purpose: handling and answering your enquiry and, where applicable, preparing a collaboration (remix, production, booking, licence, press). Legal basis: Art. 6(1)(b) GDPR where the enquiry relates to a contract, otherwise Art. 6(1)(f) GDPR. Retention period: until the enquiry has been fully dealt with; the data is then deleted unless there is a statutory retention obligation or it is needed to establish or defend legal claims. We review the stored data regularly, at least once a year.
Please do not send us any special categories of personal data (e.g. health data) or any payment details via the contact form.
Withdrawal function: If you declare withdrawal via “Withdraw from contract here”, we process your name, email address, order, the items concerned, your message, the time of receipt, IP address, country and browser signature in order to process the withdrawal and confirm receipt to you (Art. 6(1)(b) and (c) GDPR). We keep the declaration as evidence until the limitation periods have expired (Art. 6(1)(c) and (f) GDPR).
7. Protection of sign-in and forms
Sign-in attempts are stored with the IP address, the email address entered, the result and the time, and are deleted after 7 days; after too many failed attempts from one IP address, sign-in is temporarily blocked. We likewise limit the number of orders, free downloads and form submissions per visitor and time period. These counters automatically become meaningless once the relevant blocking period has expired and are deleted regularly. Legal basis: Art. 6(1)(f) GDPR (protecting accounts, the shop and the server against attacks).
8. Google reCAPTCHA
Sign-in, registration, password reset, the “Lost link” form, the contact form, newsletter sign-up and the lyrics tool are protected by Google reCAPTCHA v3, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (“Google”). The Google script is loaded only when you submit one of these forms, not while you are simply browsing. When it is loaded, your browser transmits to Google in particular your IP address, information about your browser, device and language settings, the page you are on and data about your interaction with the page. Google returns an assessment of whether the submission is likely to be automated. Google may set or read cookies or browser storage entries for this purpose.
Purpose: protecting accounts, downloads, the newsletter and the contact form against spam, bots and automated abuse. Legal basis: Art. 6(1)(f) GDPR; access to your device is strictly necessary to protect the service you have expressly requested. Data may be transferred to Google LLC, USA; Google LLC is certified under the EU-US Data Privacy Framework (European Commission adequacy decision of 10 July 2023), and standard contractual clauses also apply. More information: policies.google.com/privacy and policies.google.com/terms.
If you do not want your data to be transmitted to Google, you can instead email us directly at contact@luky.music; you do not need to register an account to make a purchase as a guest.
8a. Our own form protection (formconfirmed)
Signing in, registration, “forgot password” and setting a new password, the “lost link” form, the contact form, the newsletter sign-up, ordering as a guest, the support window and the withdrawal notice are also checked by formconfirmed, a service of the controller that runs on the controller's own servers in Poland; no third parties are involved. Its script comes from formconfirmed.com and is loaded when you open a page with one of these forms. It fetches a signed task, which your browser solves in the background as soon as you use the form (a proof of work), and passes the result to this website with the form as a single-use token. In the process, your browser sends formconfirmed.com the address of the page and your IP address; the token contains the result of the calculation, the points in time and the time taken to fill in the form, and whether a field invisible to humans was filled in, whether the browser is flagged as automated (webdriver) and some counts of how the form was used (how many keys were pressed and how evenly, whether text was pasted, movements of the mouse or finger and signs of an automated browser – never which keys were pressed or what was entered). When the task is fetched, formconfirmed also assesses whether it was fetched by a browser or by a program (based on the browser identifier and the usual request headers). This website submits the token to formconfirmed for checking together with your IP address, the content of the invisible field and, for “forgot password”, the contact form and the support window, the email address you entered; for the contact form and the support window, it also submits the message text (at most 2,000 characters) and, for the contact form, your name, so that spam can be detected. Where Google reCAPTCHA also checks the form (section 8), its score is included so that we can compare the two methods. formconfirmed checks these details automatically with fixed rules. If the content check is switched on, a language model also assesses the message text of the contact form and the support window for advertising, link lists or phishing; the language model runs on the controller's own server in Poland, no external AI provider is involved, and the text is processed for this in memory only, neither stored nor used for training. If it detects spam, the result is “suspicious” or “block”, depending on the settings (the consequences are set out below). What is stored and for how long is set out in the following paragraph. No other content of the form is transmitted.
For its assessment, formconfirmed compares the IP address with known data-centre networks, checks whether the submission comes from the same network as the one from which the task was fetched, and takes into account how requests from the same address range have behaved across all websites protected by formconfirmed (reputation). For this purpose, formconfirmed forms a hash from the truncated IP address (IPv4 without the last byte, IPv6 only the first 48 bits) with a key that changes daily (pseudonymous); it is kept with the check result for at most one hour, with the used token for about eleven minutes and in the counter of fetched tasks for about one hour. Check results (action, score, reasons, domain and, where applicable, the reCAPTCHA score) are kept for 30 days without this hash, together with our feedback on whether it was spam: we report “not spam” when you confirm your account or we reply to your message, and “spam” when we delete a message as spam. For this purpose, this website keeps the random identifier of the check with your new account or your request for at most 30 days and deletes it after the feedback. Of the email address, formconfirmed checks only the domain (for example whether it can receive emails or is known as a disposable provider); the result for each domain remains in a cache for at most seven days, and the address itself is never stored. Name and message text are checked in memory only. As with every request, the web server log of formconfirmed.com records the full IP address and the browser identifier for 14 days. The form protection sets no cookies, stores nothing in your browser and creates no fingerprint of your device.
Campaign detection: In addition, formconfirmed creates fingerprints that cannot be turned back into the original from the message text, the email address and the domains of links in the message, insofar as they are sent along as described in the first paragraph: keyed hashes of the normalised message, of a sample of its word pairs, of the email address and of the link domains (messages with fewer than 40 characters or six words receive no fingerprint of the text). They are compared for 30 days across all websites that use formconfirmed in order to recognise the same spam message, sender address or link target when it is sent to many websites; reports from operators that something was spam are also taken into account. The text, the address and the IP address themselves are not part of this comparison, and other operators learn nothing about your details. A match makes the result “suspicious” or “block”. Responsible for this comparison is formexposed, the controller's service that operates formconfirmed. The legal basis is Art. 6(1)(f) GDPR; the legitimate interest is the joint defence against spam waves across many websites. You can object to this at any time at contact@luky.music (Art. 21 GDPR).
If the result is “block”, the submission is rejected; you can send it again or write to us at contact@luky.music. If formconfirmed cannot be reached, the submission is handled as with a suspicious result; only the newsletter sign-up, the “lost link” form and ordering as a guest are then rejected, and you can send them again later. If the result is “suspicious” (for example for an address from a data centre, automated browser control or a disposable email address), Google reCAPTCHA (section 8) is applied more strictly for signing in, registration and the password forms; without a clear result you can confirm in the form with one click that you are a person (your browser then solves a somewhat larger task) and send it again – it is accepted only if the new check is not suspicious, otherwise it is rejected; a contact or support message is delivered but marked as suspicious for handling. A withdrawal notice is never rejected because of the result. Purpose: the same protection as in section 8. Legal basis: Art. 6(1)(f) GDPR. In the browser, the form protection processes only what is strictly necessary to send the form being used (Art. 399(3) of the Polish Electronic Communications Law – Prawo komunikacji elektronicznej, Section 25(2) no. 2 TDDDG, Art. 5(3) of Directive 2002/58/EC); no consent is required for this. No data are transferred to a third country.
9. Customer account
For a customer account, we process your email address, first name, optionally your surname, your password (only as a cryptographic hash, never in plain text), your settings (language, theme, currency), the times of registration and last sign-in, the IP address last used and the purchases and free downloads linked to the account. For each sign-in we store a session (IP address, browser, operating system, device type, start and last activity) so that sessions can be recognised and ended. When you register, we record as evidence which version of the Terms of Use and of this Privacy Policy you agreed to (version, time, IP address, browser signature).
Purpose: providing the account, permanent access to your purchases under “My Orders”, evidence of contract conclusion. Legal basis: Art. 6(1)(b) GDPR (contract for use of the account); for the evidence of consent, Art. 6(1)(c) and (f) GDPR. Retention period: until the account is deleted. You can delete your account in the settings at any time. Order and invoice data and the evidence of consent are then kept for as long as statutory retention obligations apply or until the limitation periods for any claims have expired; they are then no longer linked to an account. We delete evidence of consent for deleted accounts and for guest orders after four years.
10. Orders and payment
When you place an order, we process: order number, items purchased, price, currency, language, your email address, country (from your IP address or from the payment service provider), the time of your acceptance of the Terms of Sale and of your express request for immediate supply, together with the version of the texts, your IP address and browser signature at the time of acceptance, a visitor hash to prevent abuse, and technical payment identifiers (no card details).
Payment processing: Payment is made via Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland (“Stripe”), on a Stripe payment page. Stripe collects the data required for payment there (e.g. name, email address, card or account details, billing address, device data) and processes it as an independent controller, among other things to prevent fraud and to meet legal obligations (e.g. anti-money laundering). Stripe may decline payments on the basis of automated risk assessment; if this happens, please contact us. Depending on the payment method, other providers are involved (e.g. card schemes, BLIK, Przelewy24, Apple Pay, Google Pay). Data may be transferred to Stripe, Inc. in the USA; Stripe is certified under the EU-US Data Privacy Framework and also uses standard contractual clauses. Stripe's privacy notice: stripe.com/privacy.
Legal bases: Art. 6(1)(b) GDPR (performance of contract), Art. 6(1)(c) GDPR (tax and commercial retention obligations), Art. 6(1)(f) GDPR (preventing abuse, evidence of consent, legal defence). Retention period: We keep accounting-relevant data for the statutory period (in Poland, five years from the end of the calendar year in which the tax liability arose), and the evidence of consent until the limitation periods have expired. If Stripe issues an invoice on our behalf, it will be sent to you by email and also retained.
11. Downloads
Download links are personal and tied to your order or your account. Each download is logged with the time, file, amount of data transferred, country and the same daily visitor hash as in section 5. This allows us to enforce download limits, let you resume interrupted downloads, examine complaints and detect the sharing of links. Legal basis: Art. 6(1)(b) and (f) GDPR. If you request lost links again, we send them only to the email address used for the order – so nobody can find out whether an address is known to us.
12. Free downloads
As a guest you can download free items directly, without signing in and without giving an email address (to prevent abuse, at most 20 downloads per hour), or obtain them with your account (permanently under “My Orders”). We process the same data as for a download (section 11). Some free downloads are only available with a confirmed newsletter subscription (section 13); we point this out clearly before the download. You can unsubscribe at any time afterwards without losing the download. Legal basis: Art. 6(1)(b) GDPR; for the newsletter, Art. 6(1)(a) GDPR.
13. Newsletter
For the newsletter, we store your email address, language, the time and IP address of your sign-up and confirmation, the version of the consent text and where you signed up (e.g. with a free download). The newsletter is sent only after you have clicked the link in the confirmation email (double opt-in). Signed-in customers with a confirmed account email address are added without a second confirmation. Content: new releases, samples and plugins, offers, free downloads and news from the artist.
Legal basis: your consent (Art. 6(1)(a) GDPR, Art. 398 of the Polish Electronic Communications Law (Prawo komunikacji elektronicznej); for recipients in Germany: § 7(2) UWG). You can withdraw your consent at any time with effect for the future – via the unsubscribe link in every newsletter, via your email program's one-click unsubscribe function or by email to contact@luky.music. This does not affect the lawfulness of mailings sent before withdrawal. We do not track whether newsletters are opened or links are clicked.
Retention period: Unconfirmed sign-ups are deleted after 30 days. After you unsubscribe, we keep the evidence of your consent and its withdrawal for three years (Art. 6(1)(f) GDPR, accountability under Art. 7(1) GDPR) and block your address from further mailings.
14. Sending emails
Confirmations, download links, account notifications, newsletters and replies are sent from our server via an email server (SMTP). Each outgoing message is kept in an outbox for 30 days so that it can be resent if there are delivery problems and so that delivery can be proven. If we use an external email service provider for delivery, it processes the data solely on our behalf under a contract pursuant to Art. 28 GDPR; we will tell you its name and registered office on request. Legal basis: Art. 6(1)(b) and (f) GDPR.
15. Embedded player on other websites
Our tracks and releases can be embedded on other websites using an official embed player (/embed/…). If you visit such a page, your browser connects to our server; this generates server logs (section 3) and, when you play a track, listening statistics (section 5). The embedded player sets only the strictly necessary session cookie (bpid, see section 4), which expires when you close your browser; many browsers block it in embedded content anyway. It is used neither for recognition nor for advertising. The operator of the embedding website is solely responsible for any other data processing on that website.
16. Links to streaming services and social networks
Links to Spotify, Apple Music, YouTube, SoundCloud, Bandcamp, Beatport, Instagram and other services are simple links. You leave our website only when you click a link; from then on, the privacy policy of the respective provider applies. We do not embed content from these services, with one exception: YouTube videos on track pages, which load only after your consent (section 16b).
16a. “MP3 to lyrics table” tool
At /tools/lyrics you can upload an MP3 file; the tool turns it into a table of the sung lines with their start and end times. To do this we process the uploaded audio file, your IP address and the size and time of the upload. We do not keep the file name. The file is analysed on a server of the controller in Poland that sits in the same local network as this website; no third party receives the file. Processing is automatic: a source-separation model separates the vocals from the music and a speech-recognition model (Whisper) transcribes them. No person listens to the file, no language model reads the recognised text, and neither the file nor the text is used to train AI models.
Retention: The audio file is deleted immediately after processing, even if processing fails, and in any case after six hours at the latest. On the processing server it exists only during processing, in an isolated, temporary working area. You can retrieve the result (the table) for 24 hours via the random link you receive after the upload; only someone who knows this link can see it. So that the same file does not have to be processed again, we also keep the result for 30 days in a cache – without any link to you, without your IP address and without the file itself. The only key is a fingerprint of the file (SHA-256), the selected language and the tool version. If someone uploads exactly the same file, they receive this result immediately; this reveals that the file has been processed before. With “Clear cache” next to the result you delete the entry for your file; when uploading you can also ask for a fresh calculation. To limit use to three files per IP address and 24 hours and to detect abuse, we store for each accepted upload only the name of the tool, your IP address, the file size and the time, for seven days. The server logs under section 3 also apply. When you submit, Google reCAPTCHA checks the request (section 8).
Purpose: providing the tool you requested, avoiding duplicate calculations and protecting it against overload and abuse. Legal basis: Art. 6(1)(b) GDPR for processing the file, Art. 6(1)(f) GDPR for the cache, the limit and abuse protection (our legitimate interest in an economical, stable service). Please only upload files you are entitled to use and no recordings of other people without their consent. The examples on the tool page come from our own catalogue.
16b. YouTube videos
On track pages we may show an official video and a lyrics video from YouTube, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (“Google”). Nothing is loaded from YouTube when you open the page; in place of the video we only show the cover from our own server. Only when you click “Allow YouTube and play”, or have allowed YouTube in the privacy settings and start the video, does your browser load the player in privacy-enhanced mode from youtube-nocookie.com. In the process, your browser sends Google in particular your IP address, information about your browser, device and language settings, the referring page and data on your use of the player. YouTube may set or read cookies or browser entries, according to Google's own information also for security and advertising purposes (for example YSC and VISITOR_INFO1_LIVE).
Purpose: playing the videos for our tracks. Legal basis: your consent (Art. 6(1)(a) GDPR; for access to your device Art. 399(1) of the Polish Electronic Communications Law – Prawo komunikacji elektronicznej, Section 25(1) TDDDG, Art. 5(3) of Directive 2002/58/EC). You manage this consent in our consent banner (service “YouTube”), where you can withdraw it at any time with effect for the future; a player that has already loaded is then removed from the page. Without consent, you can watch every video directly on YouTube via the “… on YouTube” link; Google's privacy policy alone applies there. Data may be transferred to Google LLC, USA; Google LLC is certified under the EU-US Data Privacy Framework (adequacy decision of the European Commission of 10 July 2023), and standard contractual clauses apply in addition. Further information: policies.google.com/privacy.
17. Backups
To protect against data loss, we back up the database and files daily. Local database backups are kept for 14 days. In addition, backups are stored on an external storage device kept by the controller and – encrypted before transfer – in Google Cloud storage (Google Cloud EMEA Limited, Ireland) in the Warsaw data centre. Only the controller holds the key; Google cannot read the content. Archive backups are reviewed regularly, at least once a year, and backups no longer needed are deleted. Data deleted during normal operation may remain in backups until then; it is not restored from them except to recover from an outage. Legal basis: Art. 6(1)(f) GDPR, Art. 32 GDPR.
18. Recipients at a glance
- Stripe (payment, independent controller) – section 10
- Google Ireland Limited (reCAPTCHA) – section 8
- Google Ireland Limited (YouTube videos, only after consent) – section 16b
- formconfirmed (form protection; a service of the controller on its own servers in Poland, not a third party) – section 8a
- Google Cloud EMEA Limited (encrypted backups, processor) – section 17
- Email service provider, if used (processor) – section 14
- Authorities, courts, tax advisers or lawyers, where we are legally obliged to disclose data or where this is necessary to enforce or defend claims (Art. 6(1)(c) or (f) GDPR)
Technical notifications to the operator (e.g. via a messenger app) do not contain any personal data of visitors or customers.
19. Transfers to third countries
Data is transferred to countries outside the European Economic Area only in connection with the services named in sections 8, 10 and 16b, on the basis of the adequacy decision for the EU-US Data Privacy Framework or the European Commission's standard contractual clauses (Arts. 45 and 46 GDPR). Our own form protection (section 8a) does not transfer any data to third countries.
20. Your rights
Subject to the statutory requirements, you have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20), and the right to withdraw any consent you have given at any time with effect for the future (Art. 7(3)). To exercise these rights, simply write to contact@luky.music. To prevent abuse, we may ask you to verify your identity, e.g. by replying from the email address concerned.
Right to object (Art. 21 GDPR): Where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you may object at any time on grounds relating to your particular situation. We will then no longer process the data unless we can demonstrate compelling legitimate grounds that override your interests, or the processing serves the establishment, exercise or defence of legal claims. You may object to processing for direct marketing purposes at any time without giving reasons.
Right to lodge a complaint: You may lodge a complaint with a data protection supervisory authority, in particular in the Member State of your habitual residence or place of work. The authority responsible for us is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Moniuszki 1A, 00-014 Warsaw, Poland, uodo.gov.pl.
21. Obligation to provide data, automated decisions
You are under no statutory or contractual obligation to provide data. However, without an email address we cannot send you download links, and without the details in the contact form we cannot answer your enquiry. We do not make decisions based solely on automated processing that produce legal effects within the meaning of Art. 22 GDPR. Automated protection mechanisms (reCAPTCHA, formconfirmed, sign-in blocking, download limits, Stripe's risk assessment) may temporarily prevent an action; if this happens, you can contact us at any time to have the case reviewed by a human.
22. Minors
You must be at least 16 years old to open a customer account or sign up for the newsletter. Persons under 16 may use these features only with the consent of their parent or legal guardian. If we learn that a child's data has been collected without such consent, we will delete it.
23. Security
Data is transmitted only in encrypted form (HTTPS/TLS). Passwords are stored only as hashes, administrative access is protected by two-factor authentication, external backups are encrypted, and download links are signed and limited in time and number. Nevertheless, no transmission over the internet can be completely secure. In the event of a personal data breach, we will notify the supervisory authority and, where required by law, you.
24. Changes
We will update this Privacy Policy when the website, our services or the legal situation change. The version published here at any given time applies. We store the version you agreed to when registering or purchasing together with your consent.
Google Tag Manager (GTM) & Google Analytics 4 (GA4)
2026-11-16
GTM loads only after Analytics consent in the applicable consent manager. Google receives the IP address and technical request data. Its purpose is technical management of website tags; the legal basis is Article 6(1)(a) GDPR. A local pageView event is written to the dataLayer on page loads and URL changes within the application. GTM itself does not set analytics cookies. Google signals for analytics and advertising storage initially use denied.
Google Analytics 4 (GA4) is configured through GTM and, where enabled, analyses usage: pages and events, referral sources, browser/device information and pseudonymous identifiers. Analytics cookies (_ga and _ga_*) require consent (Article 6(1)(a) GDPR; Article 5(3) of Directive 2002/58/EC). Their default lifetime is two years; browsers or project settings may shorten it. Retention within GA4 depends on the project configuration. Choices and withdrawal are managed in the consent settings.
Recipients may also include Google LLC and subprocessors in the USA. International transfers are subject to Google’s data processing terms and the safeguards provided there, in particular standard contractual clauses. The Google information linked below explains processing, cookies and transfers.
Google Ireland Limited · Gordon House, Barrow Street, Dublin 4, Ireland.