Cuddle Cookie / Tracking Policy

Effective Date: May 8, 2026

1. Introduction, Scope, and Core Commitments

1.1 What This Cookie / Tracking Policy Is

This Cookie / Tracking Policy (“Cookie Policy”) explains how Third Hub US, Inc., a Delaware corporation, d/b/a Cuddle (“Cuddle,” “we,” “us,” or “our”) uses cookies, pixels, tags, scripts, SDKs, local storage, session storage, device identifiers, browser identifiers, analytics tools, security tools, fraud-prevention tools, payment-risk tools, checkout tools, communications tools, consent-management tools, preference-management tools, and similar technologies in connection with Cuddle.

Cuddle is an 18+ online dating and social connection service for eligible adults located in the United States.

This Cookie Policy is Additional Terms under the Cuddle Terms of Service.

1.2 When This Cookie Policy Applies

This Cookie Policy applies when you access or use Cuddle, create or manage an account, use profiles, discovery, matching or connection features, messaging, visibility controls, safety tools, reporting tools, support tools, Legal pages, pricing pages, checkout, billing, Paid Features, privacy choices, cookie choices, consent choices, communication preferences, or related functionality.

This Cookie Policy explains the technologies Cuddle may use, the information those technologies may collect or help process, how Cuddle uses them, how service providers may support them, and the choices that may be available to you.

1.3 Relationship to the Privacy Policy and Other Terms

The Privacy Policy controls how Cuddle collects, uses, discloses, retains, protects, deletes, and otherwise processes personal information generally.

This Cookie Policy controls cookie-specific and tracking-specific subjects, including cookie categories, similar technologies, analytics, security technologies, fraud-prevention technologies, payment-risk technologies, checkout technologies, communications technologies, consent choices, opt-out choices, browser controls, device controls, Global Privacy Control, universal opt-out signals, and cookie-specific records.

This Cookie Policy should be read together with the Terms of Service, Privacy Policy, Purchase, Billing, Cancellation & Refund Terms, Paid Features Terms, Prohibited Services, Payments & Commerce Policy, Community Guidelines, Safety Tips / Dating Safety Notice, Criminal Background Screening Disclosure, State-Specific Terms & Cancellation Notices, Contact / Legal Notices, checkout disclosures, purchase-specific terms, product disclosures, and applicable law.

If there is a conflict regarding personal-information processing generally, the Privacy Policy controls. If there is a conflict regarding cookie-specific or tracking-specific subjects, this Cookie Policy controls to the extent applicable, unless applicable law provides otherwise.

1.4 Core Privacy Commitments

Cuddle does not sell personal information, private messages, sensitive personal information, or payment-related personal information.

Cuddle does not share personal information for targeted advertising, cross-context behavioral advertising, or similar advertising purposes.

Cuddle does not use private messages, sensitive personal information, payment-related personal information, identity-document images, government-ID information, liveness data, face templates, faceprints, facial-geometry data, fingerprints, voiceprints, biometric identifiers, biometric templates, or biometric verification materials for targeted advertising.

Cuddle does not use cookies, tracking technologies, analytics technologies, communications technologies, security technologies, fraud-prevention technologies, payment-risk technologies, checkout technologies, consent-management technologies, preference-management technologies, or related records to provide, support, facilitate, process, route, disguise, or enable user-to-user payments, peer-to-peer payments, tips, donations, payouts, user payouts, creator payouts, cash-outs, revenue sharing, stored value, wallet balances, virtual credits, gift cards, cryptocurrency, digital assets, money transmission, remittance, payment facilitation, marketplace activity, user monetization, creator monetization, adult content monetization, sexual services, escort services, compensated dating, sugar arrangements, paid companionship, or financial products or services.

1.5 Checkout and Paid Feature Context

Cuddle currently offers Paid Features only as one-month or three-month fixed-term, non-renewing access to Cuddle-operated digital Service functionality through Cuddle’s authorized direct checkout flow.

Cuddle does not currently offer subscriptions, recurring billing, automatic renewal, automatic trial-to-paid conversion, automatic repurchase, external purchase channels, or twelve-month Paid Feature access.

Cookie and tracking technologies may support checkout, payment authorization, receipts, activation, expiration, fraud prevention, payment-risk management, statutory-cancellation support, refunds, chargebacks, payment disputes, and purchase records, but they do not create a subscription, renewal charge, wallet, stored-value balance, virtual credit, payment account, or user-to-user transfer right.

2. What Cookies and Similar Technologies Are

2.1 Overview

For purposes of this Cookie Policy, “cookies and similar technologies” means technologies Cuddle may use to recognize a browser, device, session, account, setting, preference, checkout flow, security event, consent choice, or Service interaction.

These technologies may operate through Cuddle websites, applications, Legal pages, pricing pages, checkout pages, account pages, support tools, reporting tools, communications, or Service functionality.

They may be set or supported by Cuddle, service providers, security providers, fraud-prevention providers, payment-risk providers, analytics providers, communications providers, support providers, consent-management tools, or preference-management tools.

2.2 Cookies

A cookie is a small data file that a website or service may place on or read from your browser or device.

Cookies may help keep you signed in, remember settings, operate pages, route traffic, detect errors, remember cookie choices, support checkout, support security, help prevent fraud, manage payment risk, measure performance, and understand how the Service is used.

Some cookies last only during a browser session. Other cookies may remain for a defined period unless they expire, are replaced, are deleted by you, are removed by browser or device controls, or are removed by Cuddle or a provider.

2.3 Pixels, Tags, Scripts, SDKs, and Server-Side Events

Pixels, tags, scripts, software development kits, and similar tools are code or technical components that may help Cuddle load features, measure activity, detect errors, secure the Service, manage fraud risk, support payment-risk review, operate checkout, deliver communications, or understand Service performance.

Server-side events are technical communications between Cuddle-controlled systems and service-provider systems. They may help operate security, analytics, checkout, fraud-prevention, payment-risk, support, communications, consent, or preference-management functions without relying only on browser-based cookies.

2.4 Local Storage, Session Storage, and Similar Storage

Local storage, session storage, app storage, cache files, and similar technologies may store information on a browser or device.

They may help remember settings, language choices, session status, consent choices, cookie preferences, feature states, security signals, device or browser information, or temporary data needed to operate the Service.

Clearing cookies may not clear every similar technology. You may need browser, device, app, or operating-system controls to manage different storage types.

2.5 Device, Browser, Session, and Similar Identifiers

Cuddle or its providers may assign or read device identifiers, browser identifiers, session identifiers, cookie identifiers, local storage identifiers, checkout identifiers, consent identifiers, or similar technical identifiers.

These identifiers may help Cuddle authenticate sessions, maintain settings, apply preferences, prevent abuse, detect suspicious activity, troubleshoot errors, measure performance, manage payment risk, support checkout, and preserve security.

A technical identifier may be personal information when it can reasonably identify, relate to, describe, be associated with, or be linked to a user, account, household, browser, or device under applicable law.

2.6 First-Party and Third-Party Technologies

“First-party” technologies are set or controlled by Cuddle. “Third-party” technologies are set or supported by service providers or other third parties that help Cuddle provide, secure, measure, support, or improve the Service.

A third-party technology does not mean that Cuddle sells personal information or shares personal information for targeted advertising. Cuddle does not sell personal information, private messages, sensitive personal information, or payment-related personal information, and does not share personal information for targeted advertising.

2.7 What These Technologies Are Not

Cookies and similar technologies are not money, stored value, wallet balances, virtual credits, gift cards, cryptocurrency, payment instruments, money transmission, payment facilitation, marketplace activity, or financial products or services.

They do not create a subscription, recurring billing plan, automatic renewal, automatic trial-to-paid conversion, automatic repurchase, external purchase channel, user-to-user payment, cash-out right, payout right, or transfer of value between users.

3. Categories of Cookies and Similar Technologies We Use

3.1 Overview

Cuddle may use different categories of cookies and similar technologies to provide, secure, support, measure, and improve the Service.

Not every category is used in every browser, device, session, page, account, feature, checkout flow, support interaction, report, or communication.

Some technologies are necessary to operate the Service. Others may support preferences, analytics, communications, fraud prevention, payment-risk management, checkout security, legal compliance, or consent management.

Cuddle does not use cookies or similar technologies to sell personal information, share personal information for targeted advertising, provide user-to-user payments, create stored value, operate wallets, issue virtual credits, provide cryptocurrency, facilitate marketplace activity, or provide financial products or services.

3.2 Strictly Necessary and Service-Operation Technologies

Strictly necessary technologies help Cuddle operate the Service and make core functionality available.

They may support page loading, routing, account access, session continuity, Service availability, account settings, profile functionality, discovery features, messaging where available, reporting tools, blocking tools, support tools, Legal pages, pricing pages, checkout pages, privacy choices, cookie choices, and basic technical operations.

Without these technologies, parts of the Service may not function properly, may load incorrectly, may not remember choices, may not route requests, or may not allow users to complete essential Service actions.

3.3 Authentication, Session, and Account-Security Technologies

Authentication and session technologies help Cuddle recognize that a user, browser, device, or session is connected to an account or Service interaction.

They may help keep you signed in, verify session status, prevent unauthorized access, support account recovery, remember login-related settings, detect unusual login activity, protect account integrity, and manage timeouts.

These technologies may also help Cuddle detect suspicious access, account takeover risk, credential misuse, repeated failed login attempts, unusual device changes, unusual browser changes, or attempts to evade account restrictions.

3.4 Security, Abuse-Prevention, Fraud-Prevention, and Payment-Risk Technologies

Security, abuse-prevention, fraud-prevention, and payment-risk technologies help Cuddle protect users, minors, Cuddle, service providers, payment participants, and the Service.

They may support bot detection, rate limits, velocity limits, device checks, IP-address review, session checks, account-linking analysis, suspicious activity detection, scam detection, prohibited-payment detection, external payment signal detection, account takeover prevention, fake-account prevention, re-registration evasion detection, sanctions-related screening where applicable, card-testing prevention, payment-method testing detection, refund-abuse detection, chargeback-abuse review, and transaction-laundering prevention.

These technologies do not guarantee that Cuddle will detect every unsafe user, scam, prohibited payment, external transfer, suspicious link, or harmful interaction.

3.5 Checkout, Billing, Receipt, Activation, Expiration, and Payment-Support Technologies

Checkout and payment-support technologies help Cuddle operate direct checkout, payment authorization, receipts, activation, access-period records, expiration, refund support, statutory-cancellation support, billing-error support, unauthorized-transaction support, chargeback support, payment-dispute support, tax and accounting records, and payment-risk management.

Cuddle currently offers Paid Features only as one-month or three-month fixed-term, non-renewing access to Cuddle-operated digital Service functionality through Cuddle’s authorized direct checkout flow.

These technologies do not create subscriptions, recurring billing, automatic renewal, automatic trial-to-paid conversion, automatic repurchase, external purchase channels, twelve-month Paid Feature access, stored value, wallet balances, virtual credits, gift cards, cryptocurrency, payment facilitation, marketplace activity, user payouts, or financial products or services.

Full payment card details are submitted through processor-hosted or processor-approved payment fields or flows and are not intended to be received or stored on Cuddle-controlled systems.

3.6 Analytics, Performance, Diagnostics, and Product-Improvement Technologies

Analytics, performance, diagnostics, and product-improvement technologies help Cuddle understand whether the Service works as intended.

They may help measure page views, feature use, Service errors, load times, crashes, browser or device performance, referral information, navigation patterns, checkout issues, support-flow issues, report-flow issues, cookie-choice operation, product-test performance, and aggregated Service trends.

Cuddle may use analytics to improve reliability, usability, safety, accessibility, support, fraud prevention, payment-risk management, checkout experience, and Service design.

Cuddle does not use private messages, sensitive personal information, payment-related personal information, identity-document images, government-ID information, liveness data, face templates, faceprints, fingerprints, voiceprints, biometric identifiers, biometric templates, or biometric verification materials for targeted advertising.

3.7 Preference, Consent-Management, Cookie-Choice, and Privacy-Choice Technologies

Preference and consent-management technologies help Cuddle remember choices and apply legal or user-selected settings.

They may support language settings, display settings, notification preferences, privacy choices, cookie choices, consent choices, opt-out choices, Global Privacy Control or similar legally recognized opt-out preference signals where required, communications preferences, and other account or browser-level settings.

If you clear cookies, change browsers, use a different device, reset an advertising or device identifier, block storage, or use private browsing, some choices may need to be reset or may not apply in the same way.

3.8 Communications, Support, Reporting, Safety, and Legal-Notice Technologies

Communications and support technologies may help Cuddle send, route, measure, and manage Service-related communications.

They may support account notices, security notices, safety notices, fraud notices, purchase confirmations, receipts, access-expiration notices, refund communications, statutory-cancellation communications, payment-dispute communications, privacy notices, cookie notices, policy-update notices, support responses, report responses, appeal communications, and Legal notices.

Reporting and safety technologies may help route reports, preserve relevant records, associate reports with accounts or content, manage support queues, document actions, and protect users and the Service.

3.9 Technologies Used for Records, Compliance, and Legal Protection

Cuddle may use cookies and similar technologies to help create, preserve, verify, or reference records relating to account activity, notice delivery, consent, privacy choices, cookie choices, checkout, payment authorization, receipts, activation, expiration, refund requests, statutory-cancellation requests, billing errors, chargebacks, payment disputes, reports, appeals, security events, fraud-prevention events, payment-risk events, moderation, enforcement, and legal compliance.

These records may be used to comply with law, protect rights, manage disputes, support audits, preserve evidence, prevent fraud, manage payment risk, protect users, and protect the Service.

No cookie category, analytics tool, consent tool, security tool, fraud-prevention tool, payment-risk tool, checkout tool, support tool, record, or legal-compliance process authorizes prohibited services, prohibited payments, external payment requests, user-to-user transfers of value, adult content monetization, sexual services, escort services, compensated dating, sugar arrangements, payment facilitation, marketplace activity, stored value, wallets, cryptocurrency, financial products or services, abuse, exploitation, unsafe conduct, or unlawful activity.

4. Information Collected Through Cookies and Similar Technologies

4.1 Overview

Cookies and similar technologies may collect or help process information about your browser, device, session, account, settings, choices, Service activity, checkout activity, communications, security events, fraud-prevention signals, payment-risk signals, and related records.

The information collected depends on the browser, device, page, feature, setting, account status, cookie choice, consent choice, checkout flow, support interaction, report, and technology involved.

Not every user, account, browser, device, session, or feature is associated with every category described in this Section.

4.2 Device, Browser, Network, and Approximate Location Information

Cuddle may collect or process technical information such as IP address, approximate location inferred from IP address or other permitted signals, device type, operating system, browser type, browser version, app or web version, language settings, time zone, referral information, and similar technical details.

This information may help Cuddle load pages, route traffic, apply regional settings, support United States availability, troubleshoot errors, secure accounts, prevent abuse, manage fraud risk, manage payment risk, and comply with applicable law.

Cookies and similar technologies are not used by Cuddle to provide precise-location tracking for off-Service surveillance.

4.3 Identifiers, Sessions, Settings, and Preference Information

Cuddle may use cookie identifiers, device identifiers, browser identifiers, session identifiers, local storage identifiers, consent identifiers, checkout identifiers, support identifiers, or similar technical identifiers.

These identifiers may help Cuddle recognize a browser or device, maintain sessions, remember settings, apply cookie choices, apply privacy choices, support account security, detect repeated activity, operate checkout, and document notice delivery or consent choices.

Cuddle may process settings and preference information, such as language choices, display choices, notification preferences, communications preferences, cookie preferences, consent choices, opt-out choices, Global Privacy Control signals, and similar legally recognized opt-out preference signals where required.

4.4 Service, Feature, Support, and Reporting Activity

Cuddle may collect information about how you interact with the Service, such as pages viewed, links clicked, features used, settings changed, errors encountered, reports submitted, support flows used, Legal pages viewed, pricing pages viewed, checkout steps reached, and similar activity.

This may include information about profile, discovery, matching or connection, messaging-related, visibility-control, blocking, reporting, safety, support, and Paid Feature activity where needed to operate, secure, debug, measure, or enforce the Service.

Cuddle does not use private messages, sensitive personal information, payment-related personal information, identity-document images, government-ID information, liveness data, face templates, faceprints, fingerprints, voiceprints, biometric identifiers, biometric templates, or biometric verification materials for targeted advertising.

4.5 Checkout, Purchase, Billing, Activation, Expiration, and Payment-Risk Information

Cookies and similar technologies may support checkout and purchase-related records, including pricing-page activity, selected access level, selected access period, checkout session, currency, taxes or fees, receipt delivery, payment authorization status, activation status, expiration date and time, refund support, statutory-cancellation support, chargeback support, payment-dispute support, and payment-risk review.

Cuddle currently offers Paid Features only as one-month or three-month fixed-term, non-renewing access to Cuddle-operated digital Service functionality through Cuddle’s authorized direct checkout flow.

Full payment card details are submitted through processor-hosted or processor-approved payment fields or flows and are not intended to be received or stored on Cuddle-controlled systems. Cuddle may receive or process limited payment-related information, transaction identifiers, authorization status, payment method type, risk signals, and records needed for receipts, support, accounting, fraud prevention, payment-risk management, refunds, chargebacks, and payment disputes.

4.6 Security, Fraud-Prevention, Payment-Risk, and Compliance Signals

Cuddle may collect or process security, fraud-prevention, payment-risk, and compliance signals, such as login patterns, session activity, device or browser changes, velocity signals, suspicious activity indicators, bot or automation signals, account-linking signals, card-testing signals, payment-method testing signals, refund-abuse indicators, chargeback-abuse indicators, sanctions-related signals where applicable, and attempts to evade restrictions.

These signals may help Cuddle protect users, minors, Cuddle, service providers, payment participants, and the Service. They do not guarantee that Cuddle will detect every unsafe user, scam, prohibited payment, external transfer, or harmful interaction.

4.7 Records and Information We Do Not Intend to Collect Through Cookies

Cuddle may create records relating to cookie choices, consent choices, opt-out choices, notice delivery, checkout, payment authorization, activation, expiration, reports, support, security, fraud prevention, payment risk, moderation, enforcement, and legal compliance.

Cuddle does not intend to collect full payment card numbers, card security codes, passwords, full bank credentials, private keys, wallet credentials, identity-document images, government identification documents, liveness data, face templates, faceprints, fingerprints, voiceprints, biometric identifiers, biometric templates, intimate content, or information about minors through ordinary cookie or tracking technologies.

No cookie-derived information, technical identifier, security signal, fraud-prevention signal, payment-risk signal, analytics record, consent record, or preference record authorizes prohibited services, prohibited payments, external payment requests, user-to-user transfers of value, adult content monetization, sexual services, escort services, compensated dating, sugar arrangements, payment facilitation, marketplace activity, stored value, wallets, cryptocurrency, financial products or services, abuse, exploitation, unsafe conduct, or unlawful activity.

5. How We Use Cookies and Similar Technologies

5.1 Overview

Cuddle uses cookies and similar technologies to provide, operate, secure, support, measure, improve, personalize non-price Service experiences, document, and enforce the Service.

These technologies may support accounts, sessions, profiles, discovery, messaging where available, visibility controls, reporting tools, blocking tools, safety tools, Legal pages, pricing pages, checkout, billing support, Paid Feature activation, access expiration, fraud prevention, payment-risk management, privacy choices, cookie choices, communications, and legal compliance.

Not every use applies to every user, account, browser, device, session, feature, checkout flow, report, support request, or communication.

5.2 Service Operation, Account Access, and Core Functionality

Cuddle uses cookies and similar technologies to load pages, route traffic, maintain sessions, remember settings, support login status, authenticate requests, operate account features, apply visibility settings, support profile and discovery functionality, operate messaging-related functionality, and make reporting, blocking, support, and Legal pages available.

These technologies may also help Cuddle detect errors, troubleshoot bugs, manage feature availability, apply product configurations, and keep the Service usable across supported browsers, devices, and technical environments.

5.3 Security, Abuse Prevention, Fraud Prevention, and Payment Risk

Cuddle uses cookies and similar technologies to help protect users, minors, Cuddle, service providers, payment participants, and the Service.

These technologies may support account-security checks, login protection, device recognition, session review, rate limits, bot detection, suspicious activity review, account-linking analysis, fake-account prevention, impersonation detection, scam detection, re-registration evasion detection, sanctions-related screening where applicable, payment-method testing detection, card-testing prevention, refund-abuse review, chargeback-abuse review, prohibited-payment detection, external payment signal detection, and payment-risk management.

These technologies may help Cuddle allow, review, delay, restrict, decline, reverse, refund, suspend, revoke, or investigate activity, accounts, payment methods, transactions, or Paid Feature access where permitted by applicable terms and law.

They do not guarantee that Cuddle will detect every unsafe user, scam, prohibited payment, external transfer, suspicious link, or harmful interaction.

5.4 Checkout, Billing, Receipts, Activation, Expiration, and Payment Support

Cuddle uses cookies and similar technologies to support pricing pages, direct checkout, payment authorization, fraud-prevention review, payment-risk review, receipts, tax and accounting records, billing support, refund support, statutory-cancellation support, billing-error support, unauthorized-transaction support, chargeback support, payment-dispute support, Paid Feature activation, and Paid Feature expiration.

Cuddle currently offers Paid Features only as one-month or three-month fixed-term, non-renewing access to Cuddle-operated digital Service functionality through Cuddle’s authorized direct checkout flow.

These technologies do not create subscriptions, recurring billing, automatic renewal, automatic trial-to-paid conversion, automatic repurchase, external purchase channels, twelve-month Paid Feature access, stored value, wallet balances, virtual credits, gift cards, cryptocurrency, payment facilitation, marketplace activity, user payouts, or financial products or services.

Full payment card details are submitted through processor-hosted or processor-approved payment fields or flows and are not intended to be received or stored on Cuddle-controlled systems.

5.5 Preferences, Consent Choices, Privacy Choices, and Communications

Cuddle uses cookies and similar technologies to remember and apply cookie choices, consent choices, opt-out choices, privacy choices, Global Privacy Control signals or similar legally recognized opt-out preference signals where required, language settings, display settings, notification settings, email preferences, and communications preferences.

These technologies may support account notices, security notices, safety notices, fraud notices, purchase confirmations, receipts, access-expiration notices, refund communications, statutory-cancellation communications, payment-dispute communications, privacy notices, cookie notices, policy-update notices, support responses, report responses, appeal communications, and Legal notices.

5.6 Analytics, Performance, Diagnostics, and Product Improvement

Cuddle uses cookies and similar technologies to understand whether the Service works as intended and to improve reliability, usability, accessibility, safety, support, fraud prevention, payment-risk management, checkout experience, and Service design.

These technologies may help measure page views, navigation paths, feature use, load times, crashes, errors, product-test performance, report-flow performance, support-flow performance, cookie-choice operation, checkout issues, and aggregated Service trends.

5.7 Records, Legal Compliance, and Rights Protection

Cuddle uses cookies and similar technologies to help create, preserve, verify, and reference records relating to notice delivery, consent, privacy choices, cookie choices, opt-out choices, checkout, payment authorization, receipts, activation, expiration, refund requests, statutory-cancellation requests, billing errors, chargebacks, payment disputes, reports, appeals, security events, fraud-prevention events, payment-risk events, moderation, enforcement, audits, legal compliance, and rights protection.

These records may help Cuddle comply with law, respond to requests, protect users, manage disputes, prevent fraud, manage payment risk, enforce terms, preserve evidence, and protect the Service.

5.8 Advertising, Price, Sensitive-Data, and Biometric Limits

Cuddle does not sell personal information, private messages, sensitive personal information, or payment-related personal information.

Cuddle does not share personal information for targeted advertising, cross-context behavioral advertising, or similar advertising purposes.

Cuddle does not use private messages, sensitive personal information, payment-related personal information, identity-document images, government-ID information, liveness data, face templates, faceprints, facial-geometry data, fingerprints, voiceprints, biometric identifiers, biometric templates, or biometric verification materials for targeted advertising.

Cuddle does not use fraud-prevention, payment-risk, safety, moderation, verification, account-history, or similar risk signals to personalize the price charged to an individual user.

5.9 No Prohibited Use

Cuddle does not use cookies, tracking technologies, analytics technologies, communications technologies, security technologies, fraud-prevention technologies, payment-risk technologies, checkout technologies, consent-management technologies, preference-management technologies, or related records to provide, support, facilitate, process, route, disguise, or enable user-to-user payments, tips, donations, payouts, user payouts, creator payouts, cash-outs, revenue sharing, stored value, wallet balances, virtual credits, gift cards, cryptocurrency, digital assets, money transmission, remittance, payment facilitation, marketplace activity, user monetization, creator monetization, adult content monetization, sexual services, escort services, compensated dating, sugar arrangements, paid companionship, or financial products or services.

No cookie, tracking technology, analytics tool, consent tool, security tool, fraud-prevention tool, payment-risk tool, checkout tool, communication tool, support tool, record, product test, privacy choice, or legal-compliance process authorizes prohibited services, prohibited payments, external payment requests, user-to-user transfers of value, abuse, exploitation, unsafe conduct, or unlawful activity.

6. Service Providers, Payment Participants, and Third-Party Technologies

6.1 Overview

Cuddle may use service providers, operational vendors, payment participants, and third-party technologies to help provide, secure, support, measure, improve, and enforce the Service.

These parties may support hosting, infrastructure, security, fraud prevention, payment-risk management, analytics, diagnostics, communications, support, consent management, preference management, checkout, payment authorization, receipts, tax and accounting records, refund support, statutory-cancellation support, chargeback support, payment-dispute support, legal compliance, and records.

Not every provider, participant, technology, or processing activity applies to every user, account, browser, device, session, feature, checkout flow, report, support request, or communication.

6.2 Service Providers and Operational Vendors

Service providers and operational vendors may help Cuddle operate Cuddle-controlled or Cuddle-managed systems.

They may provide hosting, cloud infrastructure, storage, security, logging, debugging, analytics, communications delivery, support routing, report routing, consent-management tools, preference-management tools, fraud-prevention tools, payment-risk tools, moderation tools, and legal-compliance tools.

These providers may process cookie identifiers, device identifiers, browser identifiers, session identifiers, IP-address information, approximate-location signals, account identifiers, feature-use records, support records, report records, checkout records, consent records, privacy-choice records, fraud-prevention signals, payment-risk signals, and related records where needed to provide services to Cuddle.

Cuddle does not treat operational service providers as third-party identity-verification vendors, government-ID verification vendors, biometric verification providers, liveness providers, facial-recognition providers, or face-matching providers merely because they help Cuddle operate Cuddle-managed systems.

6.3 Payment Participants and Checkout Technologies

Cuddle may use payment processors, payment-method providers, banks, card networks, fraud-prevention providers, payment-risk providers, tax providers, accounting providers, and related payment participants to support Cuddle’s authorized direct checkout flow.

These parties may help process payment authorization, payment authentication, risk review, fraud review, transaction records, billing descriptors, receipts, refunds, statutory cancellations, billing errors, unauthorized-transaction claims, chargebacks, payment disputes, tax records, accounting records, and compliance records.

Full payment card details are submitted through processor-hosted or processor-approved payment fields or flows and are not intended to be received or stored on Cuddle-controlled systems.

Payments through Cuddle’s authorized direct checkout flow are payments to Cuddle only for Cuddle-operated digital Service functionality. They are not payments to or for another user and do not create stored value, wallets, virtual credits, gift cards, cryptocurrency, payment facilitation, marketplace activity, or financial products or services.

6.4 Analytics and Measurement Providers

Cuddle may use analytics, performance, diagnostics, and measurement providers to understand whether the Service works as intended.

These providers may help measure page views, feature use, navigation paths, load times, crashes, errors, product-test performance, report-flow performance, support-flow performance, checkout issues, cookie-choice operation, and aggregated Service trends.

Cuddle uses analytics to support reliability, usability, accessibility, safety, support, fraud prevention, payment-risk management, checkout experience, and Service improvement.

Cuddle does not use private messages, sensitive personal information, payment-related personal information, identity-document images, government-ID information, liveness data, face templates, faceprints, fingerprints, voiceprints, biometric identifiers, biometric templates, or biometric verification materials for targeted advertising.

6.5 Third-Party Technologies and Third-Party Terms

Some third-party technologies may be governed by the provider’s own terms, privacy notices, cookie notices, security notices, or platform requirements.

Cuddle does not control every third-party browser, device, operating system, network, payment-method provider, bank, card network, analytics provider, communications provider, or security provider.

Your browser, device, operating system, payment method, bank, card network, or provider may offer additional controls, notices, settings, rights, or restrictions. Those controls may affect how cookies, similar technologies, checkout, communications, or Service functionality operate.

6.6 No Sale, No Targeted Advertising, and No Prohibited Use

Cuddle does not sell personal information, private messages, sensitive personal information, or payment-related personal information.

Cuddle does not share personal information for targeted advertising, cross-context behavioral advertising, or similar advertising purposes.

No service-provider relationship, operational-vendor relationship, payment-participant relationship, analytics tool, communications tool, support tool, consent-management tool, preference-management tool, security tool, fraud-prevention tool, payment-risk tool, checkout tool, cookie, tracking technology, server-side event, record, or legal-compliance process authorizes prohibited services, prohibited payments, external payment requests, user-to-user transfers of value, adult content monetization, sexual services, escort services, compensated dating, sugar arrangements, payment facilitation, marketplace activity, stored value, wallets, cryptocurrency, financial products or services, abuse, exploitation, unsafe conduct, or unlawful activity.

7. Analytics, Advertising Limits, No Sale/Share, and No Sensitive-Data Targeting

7.1 Overview

Cuddle may use cookies and similar technologies for analytics, performance measurement, diagnostics, product improvement, security measurement, fraud-prevention measurement, payment-risk measurement, checkout troubleshooting, support-flow measurement, report-flow measurement, and cookie-choice operation.

Analytics helps Cuddle understand whether the Service works as intended and where reliability, usability, accessibility, safety, support, fraud prevention, payment-risk management, checkout experience, or Service design may need improvement.

Not every analytics or measurement technology applies to every user, account, browser, device, session, page, feature, checkout flow, report, support request, or communication.

7.2 Analytics and Measurement Activities

Analytics and measurement activities may include measuring page views, navigation paths, feature use, load times, crashes, errors, referral information, aggregated trends, product-test performance, support-flow performance, report-flow performance, checkout issues, cookie-choice operation, consent-choice operation, opt-out-choice operation, and Service performance.

Cuddle may use aggregated, de-identified, pseudonymous, account-linked, device-level, browser-level, or session-level analytics where permitted by the Privacy Policy and applicable law.

Analytics does not guarantee that Cuddle will detect every unsafe user, technical issue, scam, prohibited payment, external transfer, suspicious link, or harmful interaction.

7.3 No Sale, No Sharing for Targeted Advertising, and Advertising Limits

Cuddle does not sell personal information, private messages, sensitive personal information, or payment-related personal information.

Cuddle does not share personal information for targeted advertising, cross-context behavioral advertising, or similar advertising purposes.

Cuddle does not use cookies, pixels, tags, SDKs, local storage, session storage, analytics tools, communications tools, security tools, fraud-prevention tools, payment-risk tools, checkout tools, consent-management tools, preference-management tools, or related records to build targeted advertising profiles, create advertising audiences, operate cross-context behavioral advertising, or sell or share personal information for targeted advertising.

Cuddle may send Service-related communications, legal notices, safety notices, fraud notices, purchase confirmations, receipts, access-expiration notices, refund communications, statutory-cancellation communications, payment-dispute communications, privacy notices, cookie notices, policy-update notices, support responses, report responses, and appeal communications. Those communications are not targeted advertising.

7.4 Sensitive-Data and Payment-Data Targeting Limits

Cuddle does not use private messages, sensitive personal information, payment-related personal information, identity-document images, government-ID information, liveness data, face templates, faceprints, facial-geometry data, fingerprints, voiceprints, biometric identifiers, biometric templates, biometric verification materials, intimate content, information about minors, medical information, criminal-history records, or court records for targeted advertising.

Cuddle does not use cookies or similar technologies to create biometric templates, perform facial recognition, conduct liveness checks, infer sensitive traits for advertising, or target ads based on sensitive information.

Cuddle does not use payment card information, payment authorization information, chargeback information, billing-error information, unauthorized-transaction information, payment-dispute information, refund information, statutory-cancellation information, or payment-risk information for targeted advertising.

7.5 Price, Checkout, and Paid Feature Limits

Cuddle does not use fraud-prevention, payment-risk, safety, moderation, verification, account-history, or similar risk signals to personalize the price charged to an individual user.

Cookies and similar technologies may support checkout, payment authorization, receipts, activation, expiration, refund support, statutory-cancellation support, chargeback support, payment-dispute support, fraud prevention, and payment-risk management.

They do not create subscriptions, recurring billing, automatic renewal, automatic trial-to-paid conversion, automatic repurchase, external purchase channels, stored value, wallet balances, virtual credits, gift cards, cryptocurrency, payment facilitation, marketplace activity, user payouts, or financial products or services.

7.6 No Prohibited Use and Relationship to Choices

No analytics tool, advertising limit, communications technology, security technology, fraud-prevention technology, payment-risk technology, checkout technology, consent-management technology, preference-management technology, cookie choice, privacy choice, opt-out signal, record, product test, support response, report response, or legal-compliance process authorizes prohibited services, prohibited payments, external payment requests, user-to-user transfers of value, adult content monetization, sexual services, escort services, compensated dating, sugar arrangements, payment facilitation, marketplace activity, stored value, wallets, cryptocurrency, financial products or services, abuse, exploitation, unsafe conduct, or unlawful activity.

Cookie choices, consent choices, browser controls, device controls, Global Privacy Control, and universal opt-out signals are addressed in Section 8.

8. Cookie Choices, Consent, Browser Controls, Device Controls, GPC, and Universal Opt-Out Signals

8.1 Overview

You may have choices about cookies, similar technologies, analytics, communications, consent, privacy preferences, browser controls, device controls, Global Privacy Control, and other legally recognized opt-out preference signals.

Available choices may depend on your state, browser, device, operating system, account status, whether you are signed in, the technology involved, and applicable law.

Some technologies are necessary to operate, secure, support, and protect the Service. Other technologies may support analytics, preferences, communications, consent management, product improvement, or similar functions.

8.2 Cookie and Consent Choices

Cuddle may provide cookie banners, cookie settings, consent tools, privacy settings, account settings, Legal pages, preference centers, or other controls where required or appropriate.

You may be able to accept, reject, limit, withdraw, or change certain cookie or tracking choices, depending on the category of technology and applicable law.

Withdrawing consent or changing a cookie choice generally applies prospectively. It may not remove cookies or similar technologies already stored on your browser or device, delete records already created, undo prior processing, or prevent legally permitted retention.

Strictly necessary, security, fraud-prevention, payment-risk, checkout, legal-compliance, consent-record, and Service-operation technologies may remain active where permitted or required by law.

8.3 Browser Controls and Storage Controls

Most browsers allow you to block, delete, or limit some cookies. Browser settings may also allow you to control local storage, session storage, cache files, pop-ups, redirects, scripts, or other storage and tracking technologies.

Clearing cookies may not clear every similar technology. You may need to use browser, device, app, or operating-system settings to manage different storage types.

Blocking or deleting cookies may affect login, session continuity, account settings, language choices, cookie choices, privacy choices, checkout, fraud-prevention review, payment-risk review, security protections, reporting tools, support tools, or other Service functionality.

8.4 Device Controls and Platform Controls

Your device, operating system, browser, app store, email provider, or communication platform may provide additional privacy, tracking, notification, advertising, security, or device-identifier controls.

These controls are provided by the relevant third party, not Cuddle. Cuddle does not control every browser, device, operating system, network, app store, email provider, payment-method provider, bank, card network, or platform setting.

If you change devices, browsers, accounts, operating systems, privacy settings, identifiers, or cookie storage, your choices may not automatically carry over.

8.5 Global Privacy Control and Universal Opt-Out Signals

Where required by applicable law, Cuddle will honor legally recognized opt-out preference signals, including Global Privacy Control or similar universal opt-out signals, to the extent required and technically feasible.

Because Cuddle does not sell personal information, private messages, sensitive personal information, or payment-related personal information, and does not share personal information for targeted advertising, some opt-out signals may have limited practical effect on Cuddle’s current advertising practices.

Cuddle may still record, apply, or respond to legally recognized signals for compliance, documentation, preference management, consent management, security, fraud prevention, payment-risk management, or privacy-rights purposes.

8.6 Legacy Do-Not-Track Signals

Some browsers or tools may send legacy “Do Not Track” or similar signals.

Cuddle may not respond to every legacy or non-standard signal unless required by applicable law. Where a signal is legally recognized as an opt-out preference signal, Cuddle will handle it as required by applicable law.

Browser or device settings may not communicate every privacy choice to Cuddle. You may need to use Cuddle-provided settings, privacy controls, or contact channels to exercise certain rights.

8.7 Account-Level, Browser-Level, and Device-Level Choices

Some choices may apply at the account level. Others may apply only to a browser, device, session, cookie identifier, consent identifier, or local storage setting.

If you are not signed in, Cuddle may not be able to associate a browser-level or device-level choice with your account. If you later sign in, use a different browser, clear cookies, reset identifiers, use private browsing, or use another device, you may need to repeat certain choices.

Cuddle may use reasonable records to document cookie choices, consent choices, opt-out choices, privacy choices, Global Privacy Control signals, notice delivery, and related compliance activity.

8.8 Communications Preferences

You may have choices about some communications, such as marketing-style or optional communications, where offered.

Service-related communications may still be sent where necessary or permitted. These may include account notices, security notices, safety notices, fraud notices, purchase confirmations, receipts, access-expiration notices, refund communications, statutory-cancellation communications, payment-dispute communications, privacy notices, cookie notices, policy-update notices, support responses, report responses, appeal communications, and Legal notices.

Changing communication preferences does not cancel a purchase, create a refund, stop a statutory-cancellation deadline, resolve a payment dispute, or change a legal notice method unless applicable law or Cuddle’s written confirmation requires that result.

8.9 No Prohibited Use and Non-Waivable Rights

No cookie choice, consent choice, privacy choice, browser control, device control, Global Privacy Control signal, universal opt-out signal, communication preference, support response, privacy response, consent-management tool, preference-management tool, product test, record, or legal-compliance process authorizes prohibited services, prohibited payments, external payment requests, user-to-user transfers of value, adult content monetization, sexual services, escort services, compensated dating, sugar arrangements, payment facilitation, marketplace activity, stored value, wallets, cryptocurrency, financial products or services, abuse, exploitation, unsafe conduct, or unlawful activity.

Nothing in this Section limits any non-waivable privacy, cookie, data-security, breach-notification, opt-out, consent, appeal, deletion, correction, access, portability, payment, refund, statutory-cancellation, billing-error, unauthorized-transaction, chargeback, consumer-protection, court-access, public-injunctive-relief, or other right under applicable law.

9. Retention, Security, Records, Sensitive Information, and Secure Upload

9.1 Retention of Cookie and Tracking Records

Cuddle may retain cookie records, consent records, opt-out records, privacy-choice records, preference records, communications records, checkout records, payment-risk records, fraud-prevention records, security logs, analytics records, support records, report records, moderation records, enforcement records, and related technical records for as long as reasonably necessary under this Cookie Policy, the Privacy Policy, applicable terms, and law.

Retention periods may vary depending on the record type, account status, legal requirements, tax or accounting needs, security needs, fraud-prevention needs, payment-risk needs, dispute needs, reporting needs, and operational needs.

Deleting cookies from your browser may not delete Cuddle records already created, records stored on Cuddle systems, legally required records, security records, payment-risk records, fraud-prevention records, checkout records, chargeback records, or records retained for compliance, safety, dispute, or enforcement purposes.

9.2 Security and Integrity

Cuddle uses reasonable administrative, technical, and organizational safeguards designed to protect cookies, similar technologies, technical identifiers, consent records, preference records, security logs, fraud-prevention records, payment-risk records, checkout records, and related information.

No method of transmission, storage, authentication, checkout, communication, cookie management, analytics, fraud prevention, payment-risk review, or Service operation is perfectly secure.

You are responsible for protecting your browser, device, account credentials, email account, phone number, authentication methods, payment method, and security settings.

9.3 Records for Compliance, Disputes, and Protection

Cuddle may create, use, preserve, disclose, and retain records relating to cookie choices, consent choices, opt-out choices, notice delivery, account activity, checkout, payment authorization, receipts, activation, expiration, refund requests, statutory-cancellation requests, billing errors, unauthorized transactions, chargebacks, payment disputes, reports, appeals, security events, fraud-prevention events, payment-risk events, moderation, enforcement, and legal compliance.

These records may be used to comply with law, respond to requests, protect users, prevent fraud, manage payment risk, enforce applicable terms, support audits, preserve evidence, resolve disputes, protect legal rights, and protect the Service.

9.4 Sensitive Information and Ordinary Channels

Do not send full payment card numbers, card security codes, passwords, authentication codes, full bank credentials, identity-document images, government identification documents, liveness data, face templates, faceprints, facial-geometry data, fingerprints, voiceprints, biometric identifiers, biometric templates, private keys, wallet credentials, intimate content, information about minors, medical records, criminal-history records, court records, or other highly sensitive information by ordinary email, ordinary messages, profile fields, reports, appeals, support channels, cookie-preference tools, consent tools, browser controls, or mail.

Do not use a user-provided link, QR code, payment handle, wallet address, external page, social-media profile, or third-party listing to upload sensitive information or complete a payment.

9.5 Secure Upload and Identity Review

When Cuddle needs identity-document, government-ID, safety, legal, privacy, refund, statutory-cancellation, account-recovery, dispute, Service-integrity, fraud-prevention, payment-risk, billing, chargeback, payment-dispute, moderation, or enforcement information for a specific process, Cuddle will provide a secure upload flow or specific instructions for that process.

Cuddle may use internal, manual, non-liveness photo or selfie review and identity-document or government-ID review for limited verification, safety, fraud-prevention, payment-risk, account-integrity, legal, privacy, refund, statutory-cancellation, dispute, moderation, or enforcement purposes.

Cuddle does not currently use a third-party identity-verification vendor, government-ID verification vendor, biometric verification provider, liveness provider, facial-recognition provider, or face-matching provider. Cuddle does not conduct liveness checks, facial-feature analysis, facial recognition, facial-geometry analysis, face-template creation, faceprint creation, fingerprint verification, voiceprint verification, biometric-identifier processing, biometric-template processing, or biometric verification.

9.6 Limits on Choices, Deletion, and Retention

Cookie choices, browser controls, device controls, Global Privacy Control signals, universal opt-out signals, consent withdrawal, privacy requests, or account deletion may affect future processing but may not remove all cookies, clear all similar technologies, delete all prior records, undo prior processing, or override retention required or permitted for security, fraud prevention, payment-risk management, checkout, tax, accounting, chargebacks, disputes, legal compliance, safety, moderation, or enforcement.

The Privacy Policy controls personal-information retention, deletion, and privacy rights.

9.7 No Prohibited Use and Non-Waivable Rights

No retention period, security process, record, cookie choice, consent record, opt-out record, secure-upload process, service-provider relationship, operational-vendor relationship, payment-participant relationship, fraud-prevention process, payment-risk process, analytics record, checkout record, support response, privacy response, product test, or legal-compliance process authorizes prohibited services, prohibited payments, external payment requests, user-to-user transfers of value, adult content monetization, sexual services, escort services, compensated dating, sugar arrangements, payment facilitation, marketplace activity, stored value, wallets, cryptocurrency, financial products or services, abuse, exploitation, unsafe conduct, or unlawful activity.

Nothing in this Section limits any non-waivable privacy, cookie, data-security, breach-notification, consent, opt-out, appeal, deletion, correction, access, portability, payment, refund, statutory-cancellation, billing-error, unauthorized-transaction, chargeback, consumer-protection, court-access, public-injunctive-relief, or other right under applicable law.

10. Contact, Changes, Relationship to Other Terms, and Non-Waivable Rights

10.1 Contact Channels

For privacy questions, cookie questions, data-rights requests, consent-withdrawal requests, opt-out requests, Global Privacy Control questions, universal opt-out signal questions, authorized-agent requests, privacy appeals where available, or questions about this Cookie Policy, contact:

privacy@cuddle-global.com

For security reports, contact:

security@cuddle-global.com

For general support, contact:

support@cuddle-global.com

For billing questions, refund requests, duplicate-charge concerns, unauthorized-charge concerns, billing-error issues, chargebacks, or payment disputes involving a Cuddle purchase, contact:

billing@cuddle-global.com

For statutory cancellation requests or another cancellation right provided by law, contact:

cancellations@cuddle-global.com

For formal legal notices, contact:

legal@cuddle-global.com

Use the channel that best matches your request. Using the wrong channel may delay review and may not satisfy a legal deadline unless applicable law requires otherwise or Cuddle accepts the communication in writing.

Cuddle channels are not emergency-response channels and may not be monitored in real time. If you are in immediate danger, believe another person is in immediate danger, or need emergency assistance, contact local emergency services immediately.

10.2 Relationship to the Privacy Policy and Other Terms

This Cookie Policy should be read together with the Terms of Service, Privacy Policy, Purchase, Billing, Cancellation & Refund Terms, Paid Features Terms, Prohibited Services, Payments & Commerce Policy, Community Guidelines, Safety Tips / Dating Safety Notice, Criminal Background Screening Disclosure, State-Specific Terms & Cancellation Notices, Contact / Legal Notices, checkout disclosures, purchase-specific terms, product disclosures, and applicable law.

The Privacy Policy controls personal-information processing generally. This Cookie Policy controls cookie-specific and tracking-specific subjects, including cookie categories, similar technologies, analytics, security technologies, fraud-prevention technologies, payment-risk technologies, checkout technologies, communications technologies, consent choices, opt-out choices, browser controls, device controls, Global Privacy Control, universal opt-out signals, and cookie-specific records.

The Purchase Terms control checkout, billing, refunds, statutory cancellations, chargebacks, billing errors, unauthorized transactions, payment disputes, and payment-risk controls. The Paid Features Terms control Paid Feature functionality, access, limits, expiration, availability, no cash value, non-transferability, promotional access, complimentary access, product tests, and feature-specific restrictions.

The Prohibited Services, Payments & Commerce Policy controls prohibited services, prohibited payments, external payment requests, user-to-user transfers of value, adult content monetization, sexual services, escort services, compensated dating, sugar arrangements, payment facilitation, marketplace activity, stored value, wallets, cryptocurrency, and financial products or services.

10.3 Changes to This Cookie Policy

Cuddle may update this Cookie Policy from time to time and will provide notice where required by law.

Notice may be provided through the Service, Legal pages, cookie banners, privacy settings, account notices, email, checkout, product disclosures, or another method permitted by law.

Unless law requires otherwise, updates apply prospectively after they become effective. A change does not eliminate a non-waivable right that applied before the change, create a subscription, create a renewal charge, create stored value, create a wallet balance, create a user payout, authorize targeted advertising, or authorize prohibited activity.

If Cuddle later changes its cookie, analytics, advertising, sale/share, opt-out, checkout, payment-risk, or consent-management practices in a material way, Cuddle will update applicable public disclosures, this Cookie Policy, the Privacy Policy, Legal notices, and other applicable terms where required.

10.4 Non-Waivable Rights

Nothing in this Cookie Policy limits any non-waivable privacy, cookie, data-security, breach-notification, access, deletion, correction, portability, opt-out, consent, appeal, sensitive-data, non-discrimination, payment, refund, statutory-cancellation, billing-error, unauthorized-transaction, chargeback, consumer-protection, accessibility, anti-discrimination, court-access, public-injunctive-relief, or other right under applicable law.

If another Cuddle term, state-specific notice, privacy notice, cookie notice, checkout disclosure, purchase-specific term, payment-participant rule, or applicable law provides a more specific or greater non-waivable right, that term, notice, disclosure, rule, or law controls to the extent required.

10.5 No Prohibited Use

No Cookie Policy term, cookie banner, cookie choice, consent choice, privacy choice, opt-out signal, Global Privacy Control signal, universal opt-out signal, browser control, device control, communication preference, support response, privacy response, security response, billing response, legal response, product disclosure, checkout disclosure, purchase-specific term, Paid Feature, promotion, product test, complimentary access, limited access, secure-upload process, service-provider relationship, operational-vendor relationship, payment-participant relationship, analytics tool, security tool, fraud-prevention tool, payment-risk tool, checkout tool, consent-management tool, preference-management tool, cookie record, tracking record, or legal-compliance process authorizes prohibited services, prohibited payments, external payment requests, user-to-user transfers of value, adult content monetization, sexual services, escort services, compensated dating, sugar arrangements, payment facilitation, marketplace activity, stored value, wallets, cryptocurrency, financial products or services, abuse, exploitation, unsafe conduct, or unlawful activity.