This notice explains what storage and tracking technologies AliasQR uses on its marketing website at aliasqr.com (the “Site”). It supplements our Privacy Policy.
1. What we use, and why
The table below lists every storage or tracking mechanism the Site uses today. There are no advertising trackers, no third-party analytics cookies, no cross-site identifiers, and no fingerprinting beacons.
| Mechanism | Type | Purpose | Lifespan | How to opt out / clear |
|---|---|---|---|---|
aliasqr-theme |
First-party localStorage entry on your device |
Remembers whether you chose the light or dark theme so the Site renders the same way next time | Persists until you clear it | Clear site data in your browser settings, or use a private/incognito window. The Site works without it; it just defaults to light mode. |
| Vercel Web Analytics | First-party, cookieless analytics beacon (loaded from /_vercel/insights/script.js) |
Counts page views and basic navigation events to help us understand how the Site is used. Does not set cookies. Does not build a cross-site profile. | No persistent identifier set by us | Block the beacon with any standard content blocker (e.g., uBlock Origin, Brave Shields), enable Do Not Track, or use a privacy-respecting browser. The Site continues to work normally. |
| Vercel Speed Insights | First-party, cookieless performance beacon (loaded from /_vercel/speed-insights/script.js) |
Reports page-load and Core Web Vitals timing so we can spot performance regressions | No persistent identifier set by us | Same as above |
| Server logs | Standard HTTP request logs at our hosting provider | Debugging, security, and abuse-prevention. Includes timestamp, path, status, IP, and User-Agent for each request. | Retained per the hosting provider’s default (a rolling window measured in days to weeks) | You cannot opt out of basic server logging. If you do not want a request logged, do not make it. |
| Google Fonts CDN | Outbound request to fonts.googleapis.com and fonts.gstatic.com when the Site loads |
Delivers the Fraunces, DM Sans, and JetBrains Mono typefaces. Loading a font exposes your IP address and User-Agent to Google as part of the HTTP request. | Not stored by us; subject to Google’s caching | Block third-party fonts with a content blocker; the Site falls back to system fonts. We may self-host fonts in a future release to remove this dependency. |
2. What we do not use
For the avoidance of doubt, the Site does not use any of the following:
- advertising cookies, retargeting pixels, or ad-attribution tags;
- third-party analytics suites such as Google Analytics, Adobe Analytics, Mixpanel, Segment, Amplitude, or Hotjar;
- social-network “Like,” “Share,” or “Login With” widgets that track on page load;
- device fingerprinting beyond what is inherent in the standard
User-Agentstring and request metadata; - session-replay, click-heatmap, or scroll-tracking tools; or
- any cross-site or cross-context behavioral tracking.
3. Why there is no cookie consent banner
Because the Site does not set non-essential cookies and does not engage in cross-context behavioral tracking, we have concluded that a cookie consent banner is not required under the laws we have reviewed today, including:
- the EU ePrivacy Directive (Article 5(3)) and equivalent member-state implementations, which require consent for non-essential storage on or access to a user’s device — the only first-party storage we use is the
aliasqr-themepreference, which is set only in response to an explicit user action (clicking the theme toggle) and is reasonably necessary to provide the appearance you selected; - the UK Privacy and Electronic Communications Regulations (PECR), on the same basis;
- the California Consumer Privacy Act, as amended by the California Privacy Rights Act, which requires opt-out signals for “sale” or “sharing” of personal information — AliasQR does neither.
We will revisit this position whenever the Site’s tracking surface changes — for example, if we add a third-party analytics tool, an advertising tag, or a feature that depends on non-essential cookies. If we add anything that requires consent, we will deploy a consent banner before the change goes live.
4. Browser controls and signals
You can control storage and tracking on the Site using your browser:
- Clear site data to remove the
aliasqr-themeentry. - Use a content blocker (uBlock Origin, Brave Shields, etc.) to suppress the Vercel analytics and Google Fonts requests; the Site still works.
- Use private or incognito browsing to avoid persistent storage between sessions.
- Send a “Do Not Track” or “Global Privacy Control” signal; we honor these signals to the extent that the underlying processing requires consent under applicable law. Because the Site does not engage in “sale” or “sharing” under the CCPA, the GPC signal does not need to suppress anything we do today.
5. Changes
We may update this notice when we change the Site’s tracking surface. Material changes will be reflected in the “Effective” date at the top of this page. If a change introduces a new technology that requires your consent, we will request consent at the time of the change.
6. Contact
Questions about this notice can be sent to founder@aliasqr.com.