# Privacy Policy

Source: https://analytics.5h3ll.site/privacy

Effective 27 October 2026 · Version 2.1

This policy explains what personal data Analytics by 5H3LL handles, why, who sees it and what your rights are. We try to write it in plain English. If something is unclear, tell us at [support@5h3ll.site](mailto:support@5h3ll.site) and we will improve it.

**Service operator:** 5H3LL · Analytics by 5H3LL

Correspondence address

5H3LL Analytics - 27663

PO BOX 6945

London

W1A 6US

United Kingdom

support@5h3ll.site

## 1.Who we are

Analytics by 5H3LL (“**5H3LL**”, “we”, “us”) provides a web analytics service at analytics.5h3ll.site. We are based in the United Kingdom and process personal data in line with the UK GDPR and the Data Protection Act 2018, which apply throughout the UK, including **Northern Ireland**, Scotland, Wales and England.

For your own **account, billing and support data**, we are the **controller**. For the **visitor data** our customers collect on their websites using our tracker, the customer is the controller and we are their **processor**. Section 4 and our [Data Processing Agreement](https://analytics.5h3ll.site/dpa) cover that second role.

You can reach us at [support@5h3ll.site](mailto:support@5h3ll.site).

## 2.The short version

What matters most

- We collect only what is needed to run your account, bill you, answer support requests and keep the service secure.
- The tracker on your website does **not store IP addresses** and uses first-party cookies. You decide whether to link visitors to customers.
- We **never sell** personal data and never use it for advertising.
- Your data is hosted on Cloudflare. You can delete a website and all of its data from its settings at any time.
- You have rights over your data, including access, correction and deletion. See section 11.

## 3.Personal data we handle as controller

The table sets out each category, why we use it, our lawful basis under UK GDPR, and how long we keep it.

| What | Why we use it | Lawful basis | How long we keep it |
| --- | --- | --- | --- |
| Account details: name, email address, profile picture and sign-in provider identifiers (Google, GitHub or an email link) | Create and secure your account, identify you, contact you about the service | Contract | While your account is open, then deleted on request or within a reasonable period after closure unless the law requires us to keep it |
| Plan and billing status: plan, subscription status, payment provider customer and subscription IDs. We never see full card numbers | Provide your plan, apply usage limits, handle refunds and invoices | Contract; legal obligation | As long as needed for tax and accounting law, which is typically six years in the UK |
| Support tickets: subject, topic, your messages, our replies and internal notes, linked to your account email | Answer your questions and fix problems | Contract; legitimate interests in running good support | Eligible for deletion 365 days after closure; removed during the next support activity cleanup |
| Service emails: sign-in links, invitations and replies to support tickets | Deliver the service you asked for | Contract | Not stored as content beyond delivery; delivery outcomes are kept in short-lived operational records |
| Website settings and encrypted integration credentials you add (for example a read-only Stripe key and webhook secret) | Provide the features you enable, such as revenue attribution | Contract | Until you remove the integration or delete the website |
| Team invitations and roles: invited email address and role | Let you share a website with teammates | Contract | Until the invitation expires (seven days) or access is revoked |
| Agent connection records: authorisations you approve for AI agents, with names, scopes and times | Let approved agents read reports and let you revoke them | Contract; consent where you approve a connection | Until you revoke the connection or the refresh period (up to 30 days) ends |
| Security and usage data: rate-limit counters, sign-in attempts, audit entries for owner actions and operational logs. IP addresses are used transiently | Protect accounts, prevent abuse, investigate problems | Legitimate interests in security | Short-lived counters; audit entries are kept as a security record |
| Analytics about visits to this service, only if you accept optional cookies | Understand visits, referral sources and conversions on our own site | Consent | Cookies last up to one year (visitor) and 30 minutes (session); you can withdraw consent at any time |

When you sign in with Google or GitHub we receive your name, email address and profile picture from that provider. If you sign in with an email link, we receive the email address you give us.

We do not ask for special category data and ask you not to put it into support tickets, passwords or API keys into messages.

## 4.Visitor data collected for our customers

When a customer installs our tracker on their website, it records, for that website: the pages viewed, referrers, campaign tags, button clicks and goals the customer chooses to track, approximate location (country, region, city, with coordinates rounded to about one kilometre), browser, operating system and device type.

The tracker uses **two first-party cookies** on the customer’s website (a random visitor identifier for up to one year and a session identifier for 30 minutes, renewed during use). **We do not store visitor IP addresses.** Email addresses that appear in page URLs are removed before the data is sent. We do not sell this data or use it for advertising or to build profiles across websites.

The customer decides whether to link visitors to customers, for example through payment metadata or by calling `identify()`, and is responsible for telling their visitors about this and for any consent they need. The customer is the controller of this data; we process it only on their documented instructions as set out in our [Data Processing Agreement](https://analytics.5h3ll.site/dpa). If you are a visitor to a website that uses our tracker, please contact that website’s owner about your data. We will help them respond to you.

**Crawler tracking (optional).** If a customer turns on crawler tracking, their server sends us the user agent, the requested page path, the response status and the requesting IP address for requests that match a known AI, search or training crawler. We use the IP address only to check it against the crawler operator’s published address ranges and **do not store it**. We keep daily counts by crawler, page and status, without cookies or visitor identifiers, for up to 400 days. Requests from other user agents, including people’s browsers, are discarded.

Customers can optionally generate a consent banner in website settings or connect their own consent manager, so that the tracker only loads after analytics consent. The banner controls our tracker only and does not certify a website’s legal compliance.

## 5.Connected payments and agents

**Payments.** If a customer connects their own Stripe account, we use a restricted read-only key and a signed webhook to verify captured payments and successful refunds for the configured website, remove duplicate events and credit revenue to the visit that brought the customer, where consent and metadata allow it. Keys are encrypted at rest and are never shown again after saving. Dodo Payments and the server-side payments API work in the same way. The customer controls the connection, its permissions, privacy notices and lawful basis.

**AI agents.** You can authorise an AI agent to read aggregate reports and public installation details for the websites you choose, using OAuth. We store authorisation records and encrypted token properties on Cloudflare. Access tokens expire after ten minutes and refresh access after up to thirty days. Permissions and suspensions are checked on every request, and you can revoke connections in Account settings. The customer analytics interface does not expose individual visitor identities, API keys or payment secrets, and offers no write or delete tools. Once data reaches an agent you chose, that agent’s provider handles it under its own terms.

**Owner admin agents.** A separate owner-only connector can read business reports and registered customer account names and email addresses. The owner may explicitly allow campaign tracking link creation and live Stripe coupon management. Connections are named and revocable; administrative changes are audited. Payment execution, payouts, credential changes and deletion are not available through this connector. The agent provider may share a connection across agents on the same account.

**Shared websites.** Owners can invite teammates as Viewers or Editors. Invitation links are bound to the invited email address. Credentials, billing, invitations and deletion remain owner-only.

## 6.Cookies and device storage on this service

This website uses **necessary** cookies and browser storage: the signed-in session (up to 30 days), short-lived sign-in and verification context (typically 10 to 15 minutes), and local preferences such as your chosen theme, plan selection and dismissed notices. The installed app caches a public offline page and icon, never private dashboard data. These do not need consent because the service cannot work without them.

With your permission, we also use **our own analytics** to understand visits, referral sources, campaigns and conversions on this service. It starts only after you accept optional cookies. It uses a random visitor cookie for up to one year and a session cookie for 30 minutes. Where your account identity is linked after consent, we use it to understand account journeys, not for advertising.

The Cookie settings control remembers your choice for 180 days. Rejecting or withdrawing stops future tracking and clears the analytics identifiers, without removing your essential sign-in session. Clearing your browser storage also clears the stored choice.

## 7.Support tickets

When you open a support ticket we store its subject, topic, your messages and our replies, linked to your account email so we can respond and keep a history. Only you and the 5H3LL team can see a ticket. Our team may add internal notes that you cannot see. We email you when we reply. Tickets are text only; please do not send passwords, API keys or payment card details.

A ticket and all of its messages are **eligible for deletion 365 days after it is closed**. Cleanup runs during support activity, so removal takes place on a subsequent support request rather than at an exact scheduled time. If you reply to a closed ticket it reopens and the period restarts when it closes again. You can ask us to delete a ticket sooner at [support@5h3ll.site](mailto:support@5h3ll.site).

## 8.Who we share data with

We use a small number of service providers (processors) to run the service and share only what each needs.

| Provider | What they do | Data involved |
| --- | --- | --- |
| Cloudflare | Hosts the application, the database and edge network | All service data, including visitor data processed for customers |
| Stripe | Takes payment for plans and handles refunds and invoices | Billing details you give them; we receive plan and payment status |
| Google and GitHub | Optional sign-in | Name, email address and profile picture, only if you choose them |
| Email delivery provider | Sends sign-in links, invitations and support replies | Recipient email address and message content |
| OpenFreeMap and OpenStreetMap | Map tiles for the live view in your browser | Your browser requests tiles directly, so they see standard request data such as your IP address; they do not receive analytics data |

We may also disclose data where the law requires it, to protect our rights or users, or to a successor if the business is sold, in each case with appropriate protection. **We do not sell personal data.**

## 9.International transfers

Our providers operate globally, so personal data may be processed outside the United Kingdom. Where that happens we make sure the transfer is covered by an adequacy regulation or appropriate safeguards required by UK GDPR, such as the UK International Data Transfer Addendum to standard contractual clauses.

## 10.How we protect data

We use encryption in transit, encryption at rest for integration credentials, signed sessions, same-origin protection on state-changing requests, rate limiting, least-privilege access and an audit log of owner actions. Support access to a customer website is read-only, time-limited and recorded with a reason. No system is perfectly secure; if a breach affects you we will tell you and the regulator where the law requires.

## 11.Your rights

Under UK data protection law you have the right to access your personal data, have it corrected or erased, restrict or object to its use, receive it in a portable form and withdraw consent at any time where we rely on it. To use a right, email [support@5h3ll.site](mailto:support@5h3ll.site). We will reply within one month.

You can delete a website and all of its data in its settings. If you are a visitor to a customer’s website, please contact that customer first.

You also have the right to complain to the UK Information Commissioner’s Office (ICO), which regulates data protection across England, Wales, Scotland and Northern Ireland, at [ico.org.uk/make-a-complaint](https://ico.org.uk/make-a-complaint/) or on 0303 123 1113. We would appreciate the chance to put things right first.

## 12.Children

The service is intended for businesses and is not directed at anyone under 18. We do not knowingly collect data from children. If you believe a child has given us personal data, contact us and we will delete it.

## 13.Changes to this policy

We may update this policy as the service changes. We will change the effective date above and, for material changes, tell account holders by email or in the app before they take effect. Earlier versions are available on request.

## 14.Contact

Privacy questions, requests and complaints: [support@5h3ll.site](mailto:support@5h3ll.site). See also our [Terms of Service](https://analytics.5h3ll.site/terms) and [Data Processing Agreement](https://analytics.5h3ll.site/dpa).

Questions about this document? Email [support@5h3ll.site](mailto:support@5h3ll.site).

See what changed recently