What We Collect
Half Awake Eyes operates this website. Statistical analytics run by default, using Firebase, a Google service, solely to understand and improve use of this website. They measure page views, content interactions, outbound clicks, signup actions and ticket redirects. You can object free of charge at any time: open Privacy settings on any public page and switch Statistical analytics off. Previous explicit analytics refusals remain effective.
Analytics records contain a timestamp, a recognised public page path, a temporary random session ID, public interaction labels, campaign/source tags, the referring and destination website origins, and broad browser, operating-system and device categories. We remove URL queries and fragments, recipient IDs, exact viewport dimensions and obvious email addresses or numeric identifiers. We do not collect raw IP addresses, precise location, fingerprints, browsing account IDs or session replay in our analytics database. Session IDs are pseudonymous rather than guaranteed anonymous. Temporary individual-level processing produces daily totals with separate page, source, campaign and device breakdowns, rather than linked visitor profiles. Breakdowns with fewer than five events and session metrics with fewer than five sessions are withheld from admin reports. Admins cannot browse individual visitors or journeys. Ticket clicks are not completed purchases.
Mailing List Signups
If you join through our Join Us page, links page or a release smart link, we collect the email address you submit. We may also store basic signup context, such as the page you signed up from, campaign details, referrer, and signup date, so we can understand where signups came from and manage the list.
We use your signup to send Half Awake Eyes news, music releases and show announcements, and to manage your subscription. We rely on your consent for these mailing list emails. Joining is optional, and you can withdraw your consent at any time using the unsubscribe link in a mailing list email or by contacting us below. Withdrawing consent does not affect processing that took place before you withdrew it.
Unsubscribing stops mailing list emails; it does not automatically erase every record. We retain subscription status and an opt-out record, including a hashed version of your email address, to help prevent future sends. Each newsletter includes a personal unsubscribe link associated with your subscription, so please avoid sharing that link.
Other Information You Share
- Public signup forms ask for an email address, not a public account
- We also receive your address, name and message contents if you email us directly
- No sign-up accounts for public visitors
- No sale of visitor data to third parties
Cookies and Browser Storage
Unless you opt out, session storage holds a random tab-session ID and an event counter. It expires after 30 minutes of inactivity, at most one hour, or when the tab session ends. There is no permanent visitor ID or first-party analytics cookie. A preference in local storage remembers analytics objections until you change or clear it; it contains no visitor ID. Marketing consent is separate and expires after 180 days. The analytics switch applies immediately and does not enable marketing. If browser storage is unavailable, analytics fail closed; an unsaved choice is explained on screen. An optional exclusion preference also uses local storage.
Configured ticket, show and smart-link Meta Pixels load only after you separately allow Meta advertising. They may use cookies and share event and device information with Meta. Privacy settings on ordinary pages controls statistical analytics only. The separate Meta option appears on pages configured to use a pixel and on this Privacy page. Use Manage privacy choices below to withdraw marketing consent at any time. Withdrawing advertising consent revokes the pixel, removes known first-party Meta cookies and reloads the page; it cannot erase data already sent to Meta. Do Not Track and Global Privacy Control also prevent statistical analytics and marketing. Spotify is available through ordinary links; no Spotify player loads on this website.
Why We Process This Data
We use statistical analytics under the UK PECR statistical purposes exception where its conditions apply, solely to improve this website, with a simple means to object. We rely on legitimate interests for the temporary processing needed to produce site-improvement statistics; you can object using Privacy settings. Meta advertising requires separate affirmative consent. Mailing list emails rely on separate signup consent, as explained above. We use our legitimate interests to respond to enquiries, operate and secure the site, administer subscriptions and maintain opt-out records. Refusing analytics does not prevent you from using the site, ticket links or signup forms.
Third-Party Processing
Firebase may process technical information, such as IP addresses, as part of providing its infrastructure and security services. We use Firebase to store signup records, analytics, unsubscribe records and cached mailbox information. IONOS provides our band mailbox and email delivery, processing recipient addresses and message contents. These providers may process information outside the UK. You can contact us for information about the arrangements that apply to your data.
If you allow Meta advertising and a ticket or smart-link campaign has a configured Pixel, Meta may receive page views, outbound ticket clicks and technical request information, including IP addresses and its own identifiers. Meta also processes information under its own privacy policy. Ticket providers, music platforms, embedded services and social networks have their own privacy practices when you use their services. Spotify receives a request only if you follow a Spotify link. Our website also requests fonts from Google Fonts on some pages, which sends technical request information to Google.
Keeping and Removing Data
Views, clicks and signups are added to daily totals as events arrive. Every 15 minutes, a backend job processes tab sessions idle for at least 30 minutes, saves session summaries and deletes the processed raw records atomically. Completed visit, bounce and duration summaries normally appear after 30-45 idle minutes; raw records normally remain less than one hour and 45 minutes from the first event. Raw events expire after two hours, with a separate 15-minute cleanup and Firestore TTL as backstops. Deletion can lag during provider or job failures; TTL is asynchronous. Already aggregated statistics expire after 90 days, and reports exclude older totals. Administrative reports are kept in memory rather than a persistent analytics cache. Hosting and provider logs and backups have separate retention arrangements.
Signup records are stored while we manage the mailing list. Unsubscribed contacts and opt-out records may remain so we can respect your preference. Correspondence and signup records do not currently have an automatic expiry; please contact us to request removal or ask what records we hold. We may need to retain a limited opt-out record to avoid contacting you again.
Your Rights
Depending on the circumstances, you can ask to access, correct or erase your personal information, restrict its use, or receive a portable copy. You can object to processing based on legitimate interests and stop direct marketing at any time. Contact us using the address below; we may need enough information to identify the relevant records and verify your request.
You can also raise a concern with the UK's Information Commissioner's Office (ICO).
Contact
Half Awake Eyes is responsible for the personal data described here. If you have questions about this policy, want to request deletion of mailing list data, or want to request deletion of logged data associated with a campaign or identifier, contact halfawakeeyes@gmail.com.
Back to website