No fingerprinting
Standard Smart Link routing does not need to recognise a person or recreate a device identity.
ZipQuantum routes ordinary link opens without browser fingerprinting, probabilistic matching, advertising IDs, or persistent cross-app identifiers. Routing decisions use the link configuration and broad technical categories required to select the right destination.
What normal routing does not do
- No canvas, audio, font, or hardware fingerprint collection
- No probabilistic device matching
- No identity graph across websites or applications
- No raw IP address or complete user-agent stored for link analytics
- No SDK running inside your mobile application
Useful analytics without individual profiles
For aggregate reporting, ZipQuantum may record that a link was opened, when it was opened, and broad categories such as device type, operating system, browser family, platform, and language. These events help teams understand link performance without turning a visitor into a persistent advertising profile.
A clear boundary for deferred recovery
ZipQuantum also provides a separate, optional Android deferred-recovery workflow. It may process additional device context only when an integration sends an explicit tracking-consent signal through the authenticated recovery flow. It is not activated by an ordinary Smart Link click, is not used for advertising or cross-app profiling, and should be enabled only when the customer has established an appropriate legal basis and consent experience.
Why this matters
Less identification means a smaller privacy surface, simpler technical review, and fewer hidden dependencies inside your app. The result is routing that is easier for product, engineering, security, and legal teams to understand.
Read the Privacy Policy · Explore Security & Privacy · View the documentation