Privacy Notice (Cookies & Telemetry)

This notice is the authoritative privacy source for HyperUp Suite: a concrete data map, straightforward controls, and clean routing for privacy requests.

Effective: December 29, 2025 · Last updated: December 29, 2025 · Built to reduce confusion, prevent misroutes, and keep support fast.

Open the data map Support Hub Email privacy

At a glance

Operational rationale: a single authoritative notice prevents duplicated wording across pages and keeps updates centralized.

This page is the privacy authority. Other pages should link here instead of publishing shortened versions. That protects consistency, reduces maintenance, and gives search engines one canonical target for privacy content.

Primary uses: purchases, delivery, customer support, security, performance measurement.
Cookies and telemetry: used for functionality, security, and aggregated analytics with clear controls.
Fast routing: privacy requests go to privacy@hyperupsuite.com; product issues go to the Support Hub.

What this page protects

One privacy source means fewer contradictions, faster responses, and a stable reference for audits, customers, and support. If you see a privacy excerpt elsewhere, it should point back here.

Hub HyperUp Trust Center Hub Terms Refunds Security Support Hub About

Data map

Operational rationale: a concrete “what / why / how long” map removes ambiguity and speeds compliant responses.

Category	Examples	Primary purpose	Typical retention
Account and identity	Email address, account identifiers	Authentication, access control, support routing	While active, plus a reasonable period for security and audit
Commerce and billing records	Order history, receipts, transaction references	Fulfillment, billing support, accounting	As required for financial records and dispute handling
Support communications	Messages you send, attachments you provide	Issue resolution, documentation improvements	As needed to complete support and maintain service history
Device and usage signals	IP-derived region, browser type, performance events	Security, fraud prevention, reliability	Short-lived where feasible; aggregated where appropriate
Cookies and telemetry	Session cookies, preference cookies, analytics tags	Core functionality and measurement	Varies by category; see the matrix below
Local attribution (non-PII)	UTM parameters, referrer hostname, lead token	Support context and aggregated analytics	Seven days (local storage)

Cookies and telemetry

Operational rationale: clear categories and controls keep measurement minimal, honest, and non-invasive.

Cookies are small browser files. Telemetry refers to limited technical signals that help keep the site secure and stable. We avoid placing personal information into URLs or telemetry fields.

Type	What it does	Examples	Your control
Strictly necessary	Enables core site and session reliability	Session and security cookies	May be required for the site to function
Preferences	Remembers choices that improve usability	Language or UI preferences	Clear via browser controls
Security	Detects abuse, fraud, and suspicious activity	Rate limiting signals	Clearing cookies may log you out
Analytics	Aggregated measurement of usage and performance	Page views, performance timings	Adjust browser settings; use privacy controls where available
Local attribution (non-PII)	Stores non-PII campaign/referrer context locally	UTM tags, referrer hostname, lead token	Use the “Clear local data” control below

Lead token: loading Copy token Clear local data

Retention and security

Operational rationale: retention rules reduce over-collection while preserving the minimum needed for disputes and audits.

We retain data for as long as needed to deliver services, maintain security, resolve disputes, and meet legal obligations. Security practices include access controls, least-privilege handling, and monitoring for abuse.

Your choices and requests

Operational rationale: clear request intake prevents delays and keeps responses consistent across channels.

You can request access, correction, or deletion depending on your jurisdiction and the nature of the data. Some records may be retained for legal or security reasons. To submit a privacy request, email privacy@hyperupsuite.com.

Use your purchase email for identity verification and faster resolution.
Include only what is necessary; avoid sending sensitive personal details.
For product help, use the Support Hub instead of privacy email.

Children

Operational rationale: scope statements reduce accidental collection and clarify intended audience.

HyperUp Suite products and services are intended for a general business audience and are not directed to children. If you believe a child has provided personal data, contact us so we can review and address the request appropriately.

Trust and contact

This Trust Center entry is designed to be the single reference point. For live contact routes and operational support links, use the site footer and the Trust Center hub.

We store non-PII attribution for 7 days to improve support and analytics.