Privacy Policy
1. Overview
Shape Beacon provides behavioral analytics for websites. We aim to collect a limited summary of browser interaction rather than replay visitors or record what they type. Some collected information, including page paths, timestamps, and session identifiers, can be linkable to a visitor or other information held by a site operator. Do not treat all telemetry as anonymous.
2. Information We Collect
- Account information: Email and account identifiers used for magic-link or Google sign-in. Google sign-in requests the
openidandemailscopes; it does not request Google profile, contacts, Drive, or Gmail data. - Behavioral telemetry: The SDK sends a per-page session identifier, a domain-session identifier, page URL origin and path (without query string or fragment), timestamps, and summarized interaction metrics and classifications. It does not send typed text, individual key values, or a screen recording. Site operators should avoid personal or sensitive information in URL paths.
- Browser storage: The SDK stores its domain-session identifier and start time in first-party
sessionStorage, scoped to the configured project and endpoint, to associate pages in the same tab for a limited session window (currently two hours). If storage is unavailable, the identifier is limited to that document. The identifier is pseudonymous, not proof of anonymity, and can link page activity within that scope. - Technical information: Requests necessarily expose network and HTTP metadata such as IP address, user-agent, and request time to the edge and service infrastructure handling them. Application-level rate limiting, bot detection, and security filtering for visitor ingestion are not represented here as guaranteed controls. Infrastructure provider logging and retention may also apply; we have not established a universal expiry period for those logs.
3. How We Use Information
We use account information to authenticate users and operate account services. We use telemetry to provide analytics, APIs, service operation, and accounting. The service does not promise to identify or reliably detect every bot or abusive request.
4. Service Providers
Shape Beacon uses Cloudflare for edge and database infrastructure, Google when an account holder chooses Google sign-in, Resend for account email delivery, and Stripe for payment services. These providers process information needed for their respective services under their own systems and terms. This list describes providers visible in the current implementation; it is not a complete legal assessment of provider roles, locations, or onward processing. Shape Beacon does not sell telemetry.
5. Cookies and Storage
The visitor SDK uses first-party tab-scoped sessionStorage as described above; it does not use a persistent third-party tracking cookie. Account authentication uses browser storage for account sessions, and sign-in flows may use short-lived security cookies. Whether a particular site's use requires notice or consent depends on applicable circumstances and law; this policy does not claim a general consent exemption.
6. Retention and Security
Detailed Page Session records are currently eligible for cleanup after five days for Evaluation and the reviewed paid catalog. This is a retention eligibility window, not a guarantee that deletion occurs at the exact five-day mark: cleanup is processed by scheduled systems, may be delayed, and some records can be held when required proof or integrity conditions are not met. Aggregated historical analytics, archival proofs and provenance, and accounting or entitlement records can remain longer. We have not established a single expiry period for all such records.
We use HTTPS for supported public service connections. Optional customer-configured proxy installations can introduce additional processing and transport risks depending on their configuration; HTTPS to Shape Beacon alone does not secure every hop between a visitor and the service.
7. Requests and Account Removal
To submit an access, correction, or deletion request, email anthony@shapebeacon.com and identify the account and domain concerned. We can receive and review a request, but there is not currently a complete self-service or verified end-to-end erasure process or a guaranteed response or completion time. We may need to verify the requester and assess applicable exceptions. Detailed telemetry, derived aggregates, archival proofs or provenance, and accounting records are not all covered by the five-day detail cleanup and may require separate review; some integrity-protected or legally required records may remain.
Removing an inactive domain from the account view only dismisses it from that view. It does not delete its telemetry or archival records. Closing or removing an account likewise must not be understood as confirmation that all associated stored data has been erased. We will not describe a request as completed without authoritative verification of its scope and outcome.