How Locus handles your data.
Effective and last updated: 20 June 2026
Analytics is optional. Locus does not create a visitor ID or collect device analytics until you select “Accept analytics.” Rejecting analytics does not prevent you from using the site or requesting beta access.
1. Who controls your data
Locus, currently operated as the Locus private beta project, is the controller of the personal data described in this notice. Privacy enquiries and data-rights requests can be sent to privacy@locus.run.
2. Data we collect
When you consent to analytics
- A random persistent visitor ID and a random ID for each page session.
- Pages and pricing sections viewed, tariff selections, expected traffic and displayed price.
- Page URL, referring page and UTM campaign parameters.
- IP address and approximate country, region, city, coordinates, network/ASN and proxy indication obtained from IP2Location.
- Browser and device characteristics: user agent, platform, vendor, languages, timezone, screen and viewport dimensions, pixel ratio, colour depth, logical CPU count, approximate device-memory hint, touch capability and connection hints.
- Browser preferences including dark mode, reduced motion, contrast preference, cookies enabled and Do Not Track value.
When you request beta access
We collect your work email, selected plan, expected traffic and displayed price so that we can manage the waitlist and respond to your request. If you reject analytics, this request is stored without a visitor ID persisted on your device, device telemetry, attribution or retained IP address.
3. Why we use it and our legal basis
- Optional analytics: to evaluate demand, understand the conversion funnel and improve pricing and product design. Legal basis: your consent.
- Beta-access request: to record the plan you requested, contact you about access and take steps in response to your request. Legal basis: steps taken at your request before entering a contract.
- Security: short-lived server and reverse-proxy logs may be processed to protect the service from abuse. Legal basis: our legitimate interest in securing the service.
We do not use this data for automated decisions that produce legal or similarly significant effects.
4. Local storage and similar technologies
| Key | Purpose | Duration | Category |
|---|---|---|---|
locus_consent_v1 | Stores whether you accepted or rejected optional analytics and the consent version. | Until deleted or the notice version changes | Strictly necessary |
locus_visitor_id | Recognises returning visitors for funnel measurement. | Until consent is withdrawn or browser storage is cleared | Optional analytics |
We currently use no advertising cookies. Rejecting or withdrawing analytics deletes locus_visitor_id from your browser. The consent record remains so we can respect your choice.
5. Recipients and international processing
Data is stored in Locus-controlled PostgreSQL infrastructure. After analytics consent, the visitor IP is sent server-to-server to IP2Location.io to obtain approximate geographic and network information. We may also use hosting and infrastructure providers acting under our instructions. Providers may process data in countries outside your country; where required, we use legally recognised transfer safeguards.
We do not sell personal data or share it with advertising networks.
6. Retention
- Optional analytics events: up to 90 days.
- IP geolocation cache: up to 30 days.
- Beta-access requests: up to 12 months, unless access is granted, you ask us to delete them or law requires longer retention.
- Security logs: normally no longer than 30 days.
7. Your choices and rights
You may reject analytics from the first consent layer or withdraw consent at any time using “Privacy settings” in the footer. Withdrawal does not affect processing that occurred before withdrawal. Depending on applicable law, you may request access, correction, deletion, restriction, portability or object to certain processing.
Send requests to privacy@locus.run. You may also complain to the data-protection authority where you live or work.
8. Changes
If we materially change analytics purposes or categories, we will update this notice, change its consent version and ask for a new choice before restarting optional analytics.