Dark pop, clean intent Single source of truth
Trust Center

Privacy Notice (Cookies + Telemetry)

This notice explains what data HyperUp Suite processes, why it exists operationally, and how you can control cookies, telemetry, and contact routing.

Effective: December 29, 2025 · Last updated: December 29, 2025 · Written for clarity, fast support, and audit-ready consistency.

Rose-gold primary (#A66F6F) No truncation at 320px No phone displayed
View the data map Support Hub Email privacy

At a glance

Operational rationale: a concise summary reduces misrouting and keeps privacy requests focused on verifiable categories.

HyperUp Suite processes data to deliver products, handle billing records, secure access, and keep site performance reliable. This page is the authoritative Privacy Notice; other pages should link here instead of repeating shortened versions.
  • Primary uses: purchases, delivery, customer support, security, performance measurement.
  • Cookies and telemetry: used for functionality, security, and aggregated analytics; controls are described below.
  • Fast routing: privacy requests go to privacy@hyperupsuite.com; product issues go to the Support Hub.

Authority decision

This notice is designed to be the single source of truth for privacy across the site: consistent wording, one update point, and a stable reference for audits, support, and search.

Data map

Operational rationale: a concrete “what / why / how long” map prevents vague assumptions and speeds compliance 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: explicit categories and controls reduce confusion while keeping measurement honest and minimal.

Cookies are small files stored by your browser. Telemetry refers to limited technical signals used to 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

How we share data

Operational rationale: explicit sharing pathways prevent surprises and make risk legible for real operations.

We share data with service providers only when needed to run the site and deliver products—such as payment processing, hosting, email delivery, and security tooling. We do not publish your personal data. We do not include personal data in public URLs.
  • Service providers: limited access for specific functions (payments, hosting, email, security).
  • Legal and safety: disclosure if required by law or to protect users, the service, or the public.
  • Business operations: a change in ownership may transfer records under continuity and confidentiality safeguards.

Retention and security

Operational rationale: retention rules reduce over-collection while keeping the minimum needed for disputes and audit trails.

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 reduces 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 and handling.

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

HyperUp Suite keeps privacy communication clean: one authoritative Privacy Notice, minimal duplication elsewhere, and direct routing to the right channel to reduce delays and confusion.

For the rest of the trust stack, use the hub so updates remain centralized and consistent.
Trust Center Terms Refunds

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