Layerwise Analytics Privacy

Last updated: September 20, 2026

1. What this notice covers

This notice explains the built-in Layerwise Analytics service on websites published by our customers. It covers that service only, not the website’s forms, accounts, payments, or other tools added by its operator. Please also read the website’s own privacy notice.

The website operator manages its project and use of Analytics. Layerwise processes Analytics data to provide that operator with reports. Use of the Layerwise website and app is covered separately by our platform Privacy Policy.

2. Information used for Analytics

When collection is enabled, pageview events can include:

The project, website domain, page path, and time of the visit.
The referring website’s domain and campaign values named utm_source, utm_medium, and utm_campaign.
Country derived from the connection’s IP address, and browser, operating-system, and device categories derived from the browser’s User-Agent.
A random event identifier and a project-specific daily visitor identifier used to estimate visitor counts and visits.

The tracker removes URL fragments and query parameters other than the campaign values listed above before sending an event. It sends the page path, which is then checked on our servers to exclude certain sensitive routes and redact recognizable identifiers before storage. These rules cannot detect every kind of personal information. Website operators should avoid putting personal or confidential information in page paths and campaign values.

IP addresses and User-Agent information are processed to derive these fields and a visitor identifier. Raw IP addresses and complete User-Agent strings are not stored in Analytics events. The visitor identifier changes each UTC day and is scoped to the project. This reduces long-term tracking but does not mean all collected data is anonymous. Hosting and security processing are separate from these stored Analytics events.

3. Cookies and browser storage

Layerwise Analytics is cookie-free: its tracker does not set tracking cookies or use browser storage to keep a persistent visitor identifier. It does not capture session recordings, form contents, or keystrokes. The website may use its own cookies or other analytics services, which are outside the scope of this notice.

4. Purpose and access

Analytics helps website operators understand pageviews, estimated visitors, traffic sources, countries, device categories, bounce rate, and visit duration. Authorized project team members can view reports and export statistics. We also use rate limits to protect the collection service from abuse.

5. Collection settings

Analytics is enabled by default for published projects. Authorized project members can turn off Collect visits in Analytics settings. The change stops collection as it reaches our serving infrastructure; requests already in progress may still be processed. Turning collection off does not delete previously collected history.

This project setting is not a visitor consent mechanism. Website operators are responsible for their own privacy notices and any consent or other requirements that apply to their use of Analytics.

6. Retention and deletion

Our Analytics retention policy is three calendar years plus a 30-day cleanup buffer. Scheduled maintenance removes events older than that period. Subscription plans limit the history visible in reports, rather than determining when events are deleted. An upgrade can unlock older data that was already collected and retained; it cannot recover data from before collection began or after deletion.

Deleting a project or team requests cleanup of its Analytics data. Cleanup runs asynchronously and repeats for 30 days to catch delayed events. Older storage snapshots may retain deleted records until snapshot expiration and file cleanup complete, so deletion is not immediate. Copies of reports exported by project members are managed separately by their recipients.

7. Infrastructure and processing locations

We use Cloudflare to receive, process, and store Analytics data. Processing may occur outside your country of residence. Cloudflare describes its processing arrangements in its Data Processing Addendum.

8. Questions and privacy requests

For questions about a website or its handling of your information, contact the website operator using its privacy notice. For questions about Layerwise Analytics or assistance with a privacy request, contact support@layerwise.app. Please include the website domain and relevant dates, but do not send passwords or other secrets. We may need the website operator’s assistance to handle a request. Because visitor identifiers change daily, we may not be able to associate particular events with you.

We will update this notice and its date when our Analytics data practices change. Website operators should keep their own privacy notices up to date.