Skip to main content

Privacy & Compliance guide for Uxify

Written by Vasil Dachev
Updated over a month ago

Do I need to list Uxify in my Privacy/Cookie Policy?

Short answer: Yes. Even though Uxify does not collect IP addresses, device fingerprints, or usernames, it still processes "Network and Device Metadata" (such as browser type, screen resolution, and event timings). To comply with the GDPR (Europe), CCPA (California), and other global laws, you must disclose the third-party services used to improve your site.

Why?

Transparency is a legal requirement under most data protection frameworks.

  • Accuracy: Even if data is anonymous, laws require you to state who is processing data on your site and for what purpose.

  • Data privacy by design: By using a tool that avoids IPs and fingerprints, you are already following "Data Minimization" principles - this is a great selling point to your users!

  • Legal shield: Clearly stating that your analytics tool is non-identifiable helps protect you from modern "anti-tracking" litigation.

Where do I need to list it?

1. Your Privacy Policy

You must include a section describing your use of performance monitoring tools. Since Uxify is privacy-focused, you can explicitly state that no personal identifiers are collected.
​

2. Your Data Processing Agreement (DPA)

Under GDPR, you are the "Data Controller" and Uxify is the "Data Processor." A DPA is required to confirm that Uxify only processes data according to your instructions.

View our documentation here: Uxify Privacy Policy.
​

3. Your Consent Banner

Because Uxify avoids persistent fingerprinting and IP tracking, it often falls under the "Performance" or "Analytics" category. In some jurisdictions, this type of "clean" analytics may be exempt from strict opt-in requirements, but listing it in your banner’s "Analytics" section remains the industry gold standard for safety.

What to include?

When describing Uxify to your users, highlight the following:

  • The goal: Improving site speed, fixing technical errors, and understanding general user engagement.

  • Privacy-first approach: Explicitly mention that no IP addresses, personal identifiers, or persistent device fingerprints are stored.

  • Data categories: Browser version, device model (for performance benchmarking), and interaction metrics (e.g., bounce rate, load times).

What does Uxify store in the browser?

Uxify uses browser storage (localStorage and sessionStorage) strictly for technical purposes. These entries allow the system to predict navigation, optimize loading strategies, and measure user experience.

Uxify does not store:

  • IP addresses

  • Email addresses

  • Usernames

  • Account identifiers

  • Persistent cross-site tracking IDs

  • Device fingerprint hashes

All stored values are technical and scoped only to the current website.

1. Navigation prediction & prerender cache

Uxify stores short-lived metadata about predicted or prefetched URLs in order to make future navigation instant.
​

Examples of stored keys:

  • Uxify:prefetchedUrls

  • Uxify:prerendering/<page-url>

  • Uxify:targetUrl:*

  • Uxify:tabNav:*

These entries may contain:

  • The predicted URL

  • The navigation type (e.g., prerender, prefetch)

  • A technical initiator label (e.g., AI prediction)

  • Navigation event metadata (e.g., new tab, soft navigation)

These values are:

  • Domain-scoped

  • Non-identifiable

  • Used solely to optimize navigation speed

2. Performance & benchmarking metadata

Uxify stores anonymized technical metadata to understand performance across device classes.

Examples:

  • Uxify:NPTelemetryMeta

  • Uxify:deviceSpeed

  • Uxify:browserTimeOffset

  • Uxify:initTTL

  • Uxify:lastCleanup

These may include:

  • Browser version

  • Number of CPU cores

  • Available device memory

  • Performance classification score

  • Core Web Vitals timing data

  • Technical expiration timestamps (TTL)

This data:

  • Does not uniquely identify a user

  • Is used only for aggregated performance benchmarking

  • Helps analyze load speed across different device categories

3. Temporary session identifiers

Uxify may create short-lived session identifiers to group navigation events within a single visit.

Examples:

  • Uxify:visitor

  • Uxify:visitorSession

  • Uxify:visitorSessionNumber

These identifiers:

  • Are random, technical session tokens

  • Are scoped to a single domain

  • Do not contain personal information

  • Are not shared across websites

  • Are not used for advertising or behavioral profiling

They exist solely to measure user experience across a single browsing session.

4. Expiration & cleanup logic

Uxify includes internal TTL (time-to-live) and cleanup mechanisms to automatically remove outdated technical entries.

Examples:

  • Uxify:initTTL

  • Uxify:lastCleanup

This ensures browser storage is not used as persistent tracking infrastructure.

Example texts

For your Privacy Policy

Website Performance & Experience Optimization We use Uxify to monitor the technical health of our website and improve the user experience. Uxify analyzes technical metadata such as page load speeds (Core Web Vitals), device types, and general engagement patterns. To protect your privacy, Uxify is configured to not collect IP addresses, usernames, or persistent device fingerprints. All data is processed in an aggregated format to help us optimize site performance across different device classes.

For your Consent Banner

Analytics & Performance: We use Uxify to measure website performance and user experience. This tool does not track your IP address or identify you personally; it is used strictly to improve, track and analyze site stability and speed.

Need more help? For more technical details on how we protect user privacy while delivering high-quality insights, don't hesitate to contact us.

Related Articles
Why is a web platform required?
LCP by tab navigations
INP by browser timezone
TTFB by CPU performance
How to add team members?
Did this answer your question?