netsends
账户

Legal

Cookie Consent & External Tools Register

This page explains how we classify cookies, first-party browser storage, and similar technologies, execute region-aware consent modes, and disclose third-party tools.

Last updated: March 8, 2026

How this cookie consent model is aligned with regulations

Your choices and controls

  • On first visit, you can choose Accept all, Reject non-essential, or Manage preferences.
  • You can reopen Cookie settings at any time and change or withdraw consent.
  • Strictly necessary technologies stay active because they are required for security and essential service operation.
  • Theme and language storage are treated as strictly necessary because they persist settings you explicitly request.
  • Consent changes apply going forward and do not invalidate processing completed before withdrawal.
  • If you withdraw analytics or marketing consent after those scripts were already loaded, the page refreshes immediately so the change takes effect on the current page too.

Questions about this page or data handling: legal@netsends.com

This page is a transparency notice about implementation and controls, and does not constitute legal advice.

First-party browser storage used on this site

netsends:cookie-consent:v1

Strictly Necessary: Stores your consent choices, policy version, and decision timestamp so we can honor and prove your preference state.

netsends:theme-preference

Strictly Necessary: Stores the theme you explicitly selected so the interface renders in that mode on later visits.

netsends:preferred-locale

Strictly Necessary: Stores the locale you explicitly selected so we can open the site in that language on later visits.

External tool registry and classification

How region policy is executed

  • strict_opt_in: when CF-IPCountry indicates EEA/UK/CH, only strictly necessary technologies run before consent.
  • opt_out_with_gpc: for configured opt-out regions (currently US), preferences and analytics may run by default; marketing respects GPC where available.
  • global_strict_fallback: when country signal is unavailable or unreliable, strict mode is used by default.
  • Regardless of regional mode, you can update preferences at any time from Cookie settings.

Strictly Necessary

Required for security, consent-state persistence, and user-requested settings such as theme or language. Always active.

1

Stripe Clover.js

Strictly Necessary

Service provider: Stripe

Provider legal entity: Stripe, Inc.

What this tool does: Provide Stripe client-side payment capabilities and risk controls required for checkout and payment workflows.

Why this category was assigned: Classified as Strictly Necessary for payment-enabled workflows because payment processing and fraud prevention are core service functions.

What data may be involved:

  • Payment session context, browser/device metadata, and anti-fraud telemetry signals.
  • Event-level integration signals required to initialize and complete secure checkout flows.

How it stores or reads data: May access browser-side storage or identifiers as part of fraud detection and secure payment processing.

EEA / UK / CH legal basis: When used strictly for requested payment service and security, processed as necessary to provide the service.

Legal basis in other regions: Applied to deliver requested payment functionality, with transparency obligations maintained in policy disclosures.

Cross-border transfer notes: Data may be processed through Stripe global infrastructure; controller should implement transfer safeguards required by applicable law.

Retention approach: Retention is governed by Stripe account settings, compliance requirements, and transaction record obligations.

Preferences

Stores optional enhancements or personalization features when enabled. It does not include theme or language choices.

0

No active external tools in this category.

Analytics

Measures traffic and performance trends. Requires consent in opt-in regions.

3

Cloudflare Web Analytics

Analytics

Service provider: Cloudflare

Provider legal entity: Cloudflare, Inc.

What this tool does: Measure traffic, high-level usage trends, and performance signals for our website operations.

Why this category was assigned: Classified as Analytics because it measures visits and traffic patterns and is not strictly required to deliver core service functionality.

What data may be involved:

  • HTTP requests metadata such as URL, referrer, browser, device and operating system.
  • Aggregated visit metrics such as page views, visits, and estimated bandwidth.

How it stores or reads data: Provider documentation states Web Analytics does not rely on client-side state like cookies or localStorage.

EEA / UK / CH legal basis: Consent prior to activation in EEA/UK/CH contexts where analytics technologies are treated as non-essential.

Legal basis in other regions: User choice and transparency by default, with region-specific controls where local law requires opt-in or opt-out mechanisms.

Cross-border transfer notes: Data may be processed through Cloudflare global infrastructure; contractual safeguards and regional law requirements should be assessed by controller.

Retention approach: Retention depends on provider and account configuration. Review Cloudflare account settings and privacy terms for current limits.

Google tag (gtag.js) / Google Analytics 4

Analytics

Service provider: Google

Provider legal entity: Google LLC

What this tool does: Collect website analytics events and measurement signals for product and growth analysis.

Why this category was assigned: Classified as Analytics because it tracks usage patterns and is not strictly required for core service delivery.

What data may be involved:

  • Page view and event metadata such as URL path, referrer, browser, and device context.
  • Approximate geolocation and pseudonymous identifiers used for analytics reporting.

How it stores or reads data: Uses Google measurement technologies that may read/write browser-side identifiers depending on configuration.

EEA / UK / CH legal basis: Consent before activation for analytics in EEA/UK/CH contexts.

Legal basis in other regions: Legitimate compliance path depends on local law; this implementation supports opt-in and opt-out policy modes.

Cross-border transfer notes: Data may be processed on Google global infrastructure; controller should maintain transfer impact assessment and contractual safeguards.

Retention approach: Retention period depends on Google Analytics property settings controlled by the site operator.

Microsoft Clarity

Analytics

Service provider: Microsoft

Provider legal entity: Microsoft Corporation

What this tool does: Analyze user behavior patterns such as click, scroll, and interaction signals to improve product usability.

Why this category was assigned: Classified as Analytics because it measures usage behavior and experience patterns rather than delivering core service functionality.

What data may be involved:

  • Interaction events such as clicks, scroll depth, session timing, and page path metadata.
  • Technical context such as browser, device, and approximate location or network-derived signals.

How it stores or reads data: May use browser-side identifiers and telemetry storage mechanisms depending on Clarity configuration.

EEA / UK / CH legal basis: Consent before activation for analytics in EEA/UK/CH contexts.

Legal basis in other regions: Handled through region-aware opt-in/opt-out controls with user choice and transparency.

Cross-border transfer notes: Data may be processed via Microsoft global infrastructure; controller should maintain transfer safeguards as required by applicable law.

Retention approach: Retention depends on Microsoft Clarity account settings and policy; review current dashboard configuration for effective periods.

Marketing

Used for advertising attribution and cross-site campaign measurement when enabled.

0

No active external tools in this category.

Unclassified

Under review. Blocked until classification and consent controls are validated.

0

No active external tools in this category.