Privacy Guarantee
This isn't a privacy policy full of legal hedging. It's a clear statement of what Signal does and doesn't do with data.
Our promise
Signal is designed to give you useful analytics without compromising your users' privacy. We achieve this through technical constraints, not policy promises. The data simply doesn't exist to be misused.
What Signal does NOT collect
These are technical facts, not policy choices. Signal's architecture makes these impossible to collect.
IP addresses
Never stored, logged, or transmitted. Used only ephemerally for country lookup.
Cookies
Signal sets zero cookies. No first-party, no third-party, none.
Browser fingerprints
We don't combine device characteristics into unique identifiers.
User identifiers
No user IDs, session IDs, or persistent identifiers of any kind.
Personal information
No names, emails, or any PII from your visitors.
Cross-site tracking
Each property is isolated. We never link data across sites.
What Signal DOES collect
All data is aggregated and anonymous. Nothing can be traced back to individual users.
Page URLs and referrers
Which pages were viewed and where traffic came from, aggregated.
Event names and metadata
Custom events you choose to track, with any properties you send.
Country of origin
Derived from IP at the edge, then IP is discarded.
Device type, browser, and OS
Aggregate statistics only (e.g., "45% mobile"). Not used to identify users.
Timestamps
When events occurred, for time-series analytics.
How we handle IP addresses
IP addresses are used ephemerally for one purpose only: deriving the country of origin. Here's exactly what happens:
- 1Event arrives at our edge with an IP address attached by the network.
- 2We look up the country from the IP using a local database (no external API).
- 3We store the country code (e.g., "US", "DE") with the event.
- 4The IP address is discarded. It is never stored, logged, or transmitted.
This process happens in memory at our edge. There is no IP address in our database, our logs, or anywhere else.
No cookies, no consent required
Why no cookies?
Cookies are used to identify returning users across sessions. Signal doesn't track returning users — we count visits, not visitors. Each page view is an independent, anonymous event.
What about consent banners?
GDPR and similar regulations require consent for tracking technologies. Since Signal doesn't use tracking technologies, no consent is required. Your users never see a cookie banner because of Signal.
No fingerprinting
Browser fingerprinting creates unique identifiers by combining device characteristics (screen size, fonts, WebGL renderer, etc.). It's often used to track users without cookies.
Signal does not fingerprint browsers. We collect basic, non-identifying technical data (browser name, OS, device type) for aggregate statistics only. We never combine these into a unique identifier.
There is no way to identify an individual user from Signal's data, even if you had access to our entire database.
Data retention
- Aggregated analytics data is retained indefinitely (or until you delete your account).
- Raw event data may be retained for up to 90 days for debugging and aggregation, then deleted.
- When you delete a property, all associated data is permanently deleted within 30 days.
- You can export your data at any time in standard formats (JSON, CSV).
Third-party access
We do not sell, share, or provide access to your analytics data to any third party. Your data is yours.
We may use third-party infrastructure (cloud hosting, CDN) to operate Signal. These providers have no access to your analytics data — they see only encrypted traffic.
Questions?
If you have questions about our privacy practices, contact us at [email protected]. We read every email and respond to legitimate questions.