Cuddle Cookie / Tracking Policy
Effective Date: May 8, 2026
Last Updated: September 9, 2026
1. About This Cookie / Tracking Policy
1.1 Purpose
This Cookie / Tracking Policy explains how Cuddle uses cookies and similar technologies, their purposes, and your choices.
It covers cookies, pixels, tags, scripts, local and session storage, and browser or device identifiers.
1.2 Operator and Scope
Cuddle is operated by Third Hub US, Inc., a Delaware corporation doing business as Cuddle (“Cuddle,” “we,” “us,” or “our”).
This Policy applies to visitors and members using Cuddle-controlled websites and related Service features, including registration, accounts, support, and checkout. Technologies may vary by page, feature, device, or provider.
1.3 Relationship to the Privacy Policy and Other Terms
Our Privacy Policy governs personal-information processing, including disclosure, retention, security, and privacy requests. This Policy supplements its explanation of cookies and tracking.
The Terms of Service and purchase terms govern their respective subjects. Cookie choices do not authorize Premium charges or cancel subscriptions.
1.4 State-Specific Rights
Non-waivable law and applicable state-specific protections prevail over conflicting terms. Our State-Specific Terms & Cancellation Notices provide additional information.
We will provide notices, consent mechanisms, and choices required by applicable law.
2. Cookies and Similar Technologies
2.1 Cookies
Cookies are small text files stored by your browser when you visit a website. They can help maintain sessions, remember choices, and recognize returning browsers.
2.2 Pixels, Tags, and Scripts
Pixels and tags can indicate that content loaded or an event occurred. Scripts can operate features or activate other technologies. Where used, these tools may support functionality, diagnostics, security, or measurement.
2.3 Local and Session Storage
Websites can store information in your browser through local or session storage. This may include settings, session information, or other Service data. How long it remains depends on the storage type and implementation.
2.4 Browser and Device Identifiers
Identifiers may distinguish a browser, device, or session. They may be associated with an account or other information and should not automatically be treated as anonymous.
2.5 Information Collected
Depending on the technology and feature, information may include IP addresses, approximate location, browser and device details, language, time zone, referring pages, identifiers, interactions, errors, and risk signals.
These categories do not mean every technology collects every item. Our Privacy Policy explains personal-information processing; Sections 3 through 7 describe purposes, providers, and choices.
3. Categories and Purposes
We classify technologies by their actual purposes and configuration. A provider may support several functions. Applicable consent requirements and choices depend on the processing involved, as explained in Sections 6 and 7.
3.1 Necessary and Session Technologies
These technologies help load pages, authenticate accounts, maintain sessions, operate requested features, support account recovery, and remember privacy choices.
Blocking or deleting them may interrupt login or prevent requested functions from working. A technology is not classified as necessary solely because a provider supplies it.
3.2 Security and Fraud Prevention
We may use device, browser, IP-address, session, interaction, and risk information to detect bots, suspicious logins, account takeover, account farming, circumvention, card testing, and unauthorized payment activity.
These technologies support security and investigation but cannot prevent every harmful act. Applicable privacy protections continue to apply.
3.3 Preferences and Functionality
Technologies may remember language, display choices, or other settings and support continuity between visits.
Some preference technologies are optional. Their classification depends on the requested function and actual use; available controls are described in Section 6.
3.4 Analytics and Performance
Where implemented, analytics and diagnostic technologies may measure page views, navigation, feature use, errors, loading times, and subscription or checkout problems.
We use this information to maintain, troubleshoot, and improve Cuddle. Section 4 explains analytics restrictions and our policy of not selling personal information or sharing it for targeted advertising.
3.5 Support and Communications
Cuddle and authorized providers may use technologies to operate the Help Center, route requests, maintain support sessions, and manage communications.
Necessary account, security, safety, billing, and legal notices are distinct from optional marketing communications. Cookie settings and communication preferences may operate separately.
3.6 Checkout and Subscriptions
Technologies may support checkout, payment authentication, subscription administration, receipts, renewals, cancellations, and payment-risk controls.
Full payment-card information is intended to be entered through processor-hosted or processor-approved fields. Cookie consent does not authorize Premium charges, and deleting cookies does not cancel Premium. Purchase and cancellation procedures remain governed by our applicable purchase terms.
4. Analytics, Advertising, and Sensitive Information
4.1 Analytics Practices
Where implemented, analytics and diagnostic tools help us understand Service usage, identify errors, evaluate performance, and improve features.
We limit collection to information reasonably needed for these purposes and use aggregated or de-identified information where appropriate. An identifier, shortened IP address, or aggregated report does not automatically make all underlying information anonymous.
Required consent and privacy choices apply to the actual processing, as described in Sections 6 and 7.
4.2 No Sale or Targeted-Advertising Sharing
Cuddle does not sell personal information or share it for cross-context behavioral advertising or targeted advertising.
Calling a technology “analytics,” “measurement,” or “security” does not override this commitment. Its configuration, recipients, and actual uses must remain consistent with our Privacy Policy.
We will provide any required notice and obtain any required consent before introducing materially different processing.
4.3 Sensitive Information and Private Content
General analytics must not collect private message contents, passwords, authentication codes, full payment-card details, or identity-review documents and images.
Tools capable of capturing page content or user input must be configured to exclude these materials from general analytics. Event names, page URLs, and diagnostic data must also be reviewed to avoid unnecessary disclosure of sensitive information.
Processing needed to deliver messages, operate checkout, investigate reports, or conduct an authorized account review remains governed by the Privacy Policy.
4.4 Provider Use Restrictions
Providers acting for Cuddle must process information within their authorized role and applicable contractual restrictions. We do not authorize unrelated advertising, independent user monetization, or use outside that role, subject to independent legal obligations.
A provider’s separate policy does not replace Cuddle’s obligations or your applicable rights. Section 5 describes providers and technology details.
5. Providers and Cookie Details
5.1 First-Party and Third-Party Technologies
Cuddle may use its own technologies and technologies supplied by other providers. Third-party components may operate within Cuddle pages or through another domain.
A first-party cookie or identifier may still be processed by a service provider. The labels “first-party,” “third-party,” “payment,” or “security” do not alone determine whether consent or an opt-out is required. Actual purposes, configuration, and data use control.
5.2 Operational and Payment Providers
Our Privacy Policy identifies possible operational providers, including Amazon Web Services, Twilio, Intercom, Typeform, and Google reCAPTCHA. These providers may support hosting, communications, support, forms, security, and related functions.
Their inclusion does not mean every provider places cookies on every page. Technologies used depend on the feature and configuration.
Authorized payment processors and related participants may use technologies for checkout, payment authentication, subscription administration, and fraud prevention. Their roles may include processing under Cuddle’s instructions or fulfilling independent payment, security, or legal responsibilities.
Each technology’s classification depends on its actual use. A payment or security function does not automatically make all associated tracking necessary.
5.3 Cookie and Technology Details
We will maintain details for technologies actually deployed and make them available through this Policy, a linked list, or an available choice tool.
These details will identify, as applicable:
- the cookie, storage entry, or technology name;
- the provider and relevant domain;
- its category and specific purpose;
- whether it lasts for a session or persists, with its duration or expiration criteria; and
- applicable consent, opt-out, or other controls.
Details must reflect Cuddle’s implementation. A provider’s general documentation does not establish that every listed technology is used by Cuddle.
We will update the details when material implementation changes occur. Browser storage duration and retention of information received by servers may differ, as explained in Section 8.
5.4 External Services
External links may take you to services governed by their own privacy and cookie policies. Your Cuddle preferences may not carry over to those services.
Embedded providers acting for Cuddle remain subject to the restrictions described in Section 4. A provider’s separate policy does not replace Cuddle’s obligations or your applicable rights.
6. Consent and Cookie Choices
6.1 When Consent Is Required
Where applicable law requires prior consent, we will obtain it before activating the relevant optional technologies or processing information for that purpose.
Consent must be informed and affirmative where required. Merely visiting, scrolling, or continuing to use Cuddle does not replace required consent. Necessary processing may continue only as permitted by law.
6.2 Available Choice Tools
We will provide legally required choices through appropriate mechanisms, which may include a banner, settings panel, or privacy request channel.
Available controls will explain the purposes and choices they address. Where required, accepting and rejecting optional technologies will be comparably straightforward, without misleading design or unnecessary steps.
A choice applies to the technologies and purposes identified by that control. Recognized opt-out signals are addressed in Section 7.
6.3 Changing or Withdrawing Consent
You may change available preferences or withdraw consent through the relevant controls. Contact privacy@cuddle-global.com if you need assistance.
Where required, withdrawal will be as easy as giving consent. We will stop processing that depends on withdrawn consent without undue delay and within any applicable legal deadline.
Withdrawal does not automatically delete previously collected information. Applicable deletion rights and retention rules remain governed by our Privacy Policy and Section 8.
6.4 Browser and Device Controls
Browser or device settings may let you block cookies, clear stored information, restrict third-party technologies, or use privacy signals.
Choices may be specific to a browser or device. Clearing storage, using private browsing, or changing devices may require setting preferences again. Loss of a stored preference is not itself consent. We will continue to honor legally recognized signals as required.
6.5 Effects on Functionality
Blocking necessary technologies may affect login, security, saved settings, support, or checkout. Rejecting an optional technology may affect a feature that depends on it.
We will not require Premium to exercise a statutory privacy right or unlawfully discriminate against you for exercising that right.
6.6 Subscription and Communication Choices
Cookie choices are separate from Premium payment authorization and subscription cancellation.
Rejecting or deleting cookies does not by itself cancel Premium, stop renewals, delete your account, or create a refund. Use subscription management or the applicable cancellation procedure.
Optional marketing communications have separate preference or unsubscribe controls. Necessary account, security, safety, billing, and legal notices may continue as described in our Privacy Policy.
7. U.S. State Rights and Privacy Signals
7.1 Applicable State Rights
Depending on applicable law, you may have rights to opt out of personal-information sales, sharing, targeted advertising, or certain profiling, and to exercise other privacy rights.
Cuddle does not sell personal information or share it for cross-context behavioral advertising or targeted advertising. An opt-out may therefore have limited practical effect. Our Privacy Policy and State-Specific Terms & Cancellation Notices explain applicable rights.
7.2 Global Privacy Control and Recognized Opt-Out Signals
Global Privacy Control (“GPC”) is a browser or extension signal communicating an opt-out preference.
Where required by law, we will treat GPC and other legally recognized signals as valid opt-out requests for the covered processing. We will not require an additional confirmation as a condition of honoring a legally sufficient signal.
7.3 Signal Scope and Limitations
We will apply recognized signals to the browser or device and any associated account or other identifiable profile to the extent required by law. You need not create an account to exercise a legally required opt-out.
A signal does not automatically delete information or disable every technology. Necessary processing for authentication, security, fraud prevention, payments, Service operation, and legal compliance may continue where permitted.
7.4 Do Not Track
Do Not Track (“DNT”) differs from GPC. A DNT setting may not activate the choices described here. Use Section 6’s controls or a recognized opt-out signal. We will honor any legally required signal.
7.5 Requests and Non-Discrimination
Contact privacy@cuddle-global.com for privacy requests or assistance. We will request only information permitted and reasonably necessary for the request, honor applicable deadlines, and provide appeal instructions where required.
Privacy rights do not require Premium. We will not unlawfully discriminate against you for exercising them.
8. Duration, Retention, and Deletion
8.1 Session and Persistent Technologies
Session technologies generally last for a browser or browsing session. Persistent technologies may remain until expiration or deletion. Browser settings and session restoration may affect their actual duration.
8.2 Cookie Expiration and Server Records
Expiring or deleting a cookie does not automatically delete information already received by Cuddle or a provider.
Cuddle’s server records follow the Privacy Policy’s retention criteria and applicable law. Section 5’s technology details will identify applicable browser-storage durations or expiration criteria.
8.3 Consent and Preference Records
We may retain records of consent, withdrawal, preference changes, opt-out signals, and applicable notice versions to implement your choices and demonstrate compliance.
These records are retained only as long as reasonably necessary and legally permitted. Loss of a stored preference does not itself constitute consent.
8.4 Deletion and Privacy Requests
You may clear browser storage through available controls. For deletion requests concerning information held by Cuddle, contact privacy@cuddle-global.com.
We will honor applicable deletion rights, deadlines, and lawful exceptions. Mandatory deletion, return, or certification requirements control conflicting general retention provisions. Deleting cookies does not itself cancel Premium or delete your account.
9. Changes and Contact
9.1 Policy Updates
We may update this Policy as our technologies, Service, or legal requirements change. We will revise the Last Updated date and keep technology details consistent with material implementation changes.
9.2 Required Notices and Consent
We will provide notices required by law, including advance notice where applicable. Processing that requires new consent will not begin until that consent is obtained.
Continued use does not replace required affirmative consent. An update does not itself withdraw your opt-out or authorize previously rejected optional processing.
9.3 Privacy and Support Contacts
For cookie questions, privacy choices, or rights requests, contact privacy@cuddle-global.com.
For general support or accessibility assistance, contact support@cuddle-global.com.
Include only information reasonably needed to identify the issue. Do not send passwords, authentication codes, full payment-card details, or identity documents through ordinary email.
Our Privacy Policy explains additional request procedures.
