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 and similar technologies in connection with Cuddle.

These technologies may include cookies, pixels, tags, scripts, local or session storage, browser, device, or session identifiers, security tools, and consent tools. Section 2 explains them in more detail.

This Cookie Policy addresses cookie-specific practices and choices. Cuddle’s Privacy Policy explains broader personal-information processing. Your use of the Service does not replace separate consent where applicable law requires it.

1.2 Cuddle Operator, United States Availability, and Adults Only

Cuddle is an 18+ online dating and social connection service.

Cuddle currently offers the Service only to eligible adults located in the fifty states and the District of Columbia. U.S. territories and other locations are excluded unless Cuddle states otherwise.

Minors may not create accounts, use the Service, complete checkout, purchase or use Premium, appear in member content, or otherwise participate.

1.3 When This Cookie Policy Applies

This Cookie Policy applies to cookies and similar technologies used through Cuddle’s websites, request-an-invite forms, registration, accounts, profiles, discovery, Likes, Matches, messaging, support, security, fraud prevention, payment-risk management, direct checkout, billing, privacy choices, communications, analytics where implemented, and related functionality.

The “Service” means Cuddle’s online dating and social connection service and related functionality provided by or on behalf of Cuddle.

Not every technology applies to every person, device, browser, page, feature, form, support interaction, or checkout flow. This Cookie Policy does not govern an independent third-party service that Cuddle does not own or control. Such services may follow their own privacy practices.

1.4 Relationship to the Privacy Policy and Other Terms

This Cookie Policy is an Additional Term under Cuddle’s Terms of Service and should be read with the Privacy Policy, Purchase, Billing, Cancellation & Refund Terms, Paid Features Terms, State-Specific Terms & Cancellation Notices, Contact / Legal Notices, and applicable notices.

The Privacy Policy controls personal-information processing generally. This Cookie Policy controls cookie- and similar-technology-specific subjects. A more specific consent request, cookie setting, checkout disclosure, provider notice, state-specific notice, or non-waivable law controls the subject it addresses.

1.5 Core Privacy Commitments

Cuddle does not sell personal information or share it for cross-context behavioral advertising or targeted advertising. Cuddle does not currently use cookies or similar technologies to serve targeted advertising.

Cuddle does not use private-message content, sensitive personal information, or payment-related information for targeted advertising. Cuddle also does not use cookie, device, security, fraud-prevention, payment-risk, or similar information to personalize a user’s price.

Where law requires notice, consent, an opt-out, or another choice for an optional technology, Cuddle will provide the required process. Technologies reasonably necessary for Service operation, authentication, security, fraud prevention, payment risk, privacy-choice records, or direct checkout may operate as permitted by law.

Blocking or deleting necessary technologies may prevent login, security protections, forms, checkout, or other functionality from working correctly. No technology guarantees detection or prevention of every security, fraud, abuse, or payment-risk event.

1.6 Current Service and Purchase Context

Cuddle provides Free Access and optional Premium. Purchased Premium is one thirty-day, fixed-term, non-renewing access period offered through Cuddle’s authorized direct checkout as a one-time transaction.

Cuddle does not currently offer subscriptions, recurring billing, automatic renewal, automatic repurchase, automatic trial-to-paid conversion, or external purchase channels. Cookies or similar technologies used for checkout, payment authentication, transaction status, receipts, Premium activation or expiration, refunds, statutory cancellations, disputes, or payment-risk controls do not create any such billing model.

Full payment card details are intended to be submitted through processor-hosted or processor-approved fields and are not intended to be received or stored on Cuddle-controlled systems. A Cuddle purchase is payment to Third Hub US, Inc., d/b/a Cuddle for Cuddle-operated digital functionality, not payment to or for another member.

2. What Cookies and Similar Technologies Are

2.1 Overview

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

They may operate through Cuddle websites and browser-based Service components, including Legal, pricing, checkout, account, request-an-invite, support, reporting, and communications pages or tools.

Not every technology applies to every user or interaction.

2.2 Cookies

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

Cookies may help keep you signed in, maintain sessions, remember settings, operate pages, detect errors, apply privacy choices, support checkout, protect accounts, prevent fraud, manage payment risk, measure performance, and understand Service use.

A session cookie generally lasts for a browser session. A persistent cookie may remain for a defined period unless it expires, is replaced, is deleted through controls, or is removed by Cuddle or a provider.

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

Pixels, tags, scripts, and similar web components may help load features, record interactions, measure activity, detect errors, secure the Service, prevent abuse, manage fraud or payment risk, support checkout, deliver communications, or evaluate performance.

Server-side events are technical communications between Cuddle-controlled systems and provider systems. They may support security, checkout, fraud prevention, payment-risk management, analytics where implemented, support, communications, consent management, or preferences without relying only on browser-stored cookies.

2.4 Local Storage, Session Storage, Cache Files, and Similar Browser Storage

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

They may maintain technical state, remember settings, support authentication, preserve consent or cookie choices, operate support tools, reduce repeated requests, or temporarily store information needed for web functionality.

Clearing cookies may not clear all browser storage. Browser or device controls may separately manage site data, storage, or cache files.

2.5 Device, Browser, Session, and Similar Identifiers

Cuddle or its providers may assign, receive, or read browser, session, cookie, local-storage, consent, checkout, security, fraud-prevention, payment-risk, or similar identifiers, together with device-related information available through a browser or provider technology.

These identifiers may help authenticate sessions, apply settings and choices, connect related technical events, detect suspicious activity, troubleshoot errors, support transactions, and protect the Service.

A technical identifier may be personal information where applicable law treats it as linkable to a person, account, household, browser, or device. It does not, by itself, prove identity, age, account ownership, payment authority, eligibility, or safety.

2.6 First-Party and Third-Party Technologies

“First-party” technologies are generally set or controlled by Cuddle through a Cuddle-controlled domain or web component.

“Third-party” technologies are generally supplied or operated by service providers or payment participants supporting the Service.

A third-party technology does not mean that Cuddle sells personal information or shares it for targeted advertising. A third party may process information on Cuddle’s behalf or independently under its own terms and privacy practices.

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, 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.

Ordinary cookies and similar web technologies are not intended to collect full payment credentials, passwords, authentication codes, government-identification or account-review images, private-message content, or other submitted highly sensitive content.

3. Categories of Cookies and Similar Technologies We Use

3.1 Overview

Cuddle may use the categories of cookies and similar technologies described below. A single cookie, identifier, script, storage item, or server-side event may support more than one purpose. Cuddle classifies a technology based on its primary function and context.

Not every category applies to every person, browser, device, page, account, form, feature, support interaction, or checkout flow. Some technologies are operated by Cuddle; others are provided by authorized service providers or payment participants.

Technologies reasonably necessary to operate, authenticate, secure, or protect the Service may operate as permitted by law. Optional analytics or preference technologies are used only where implemented and subject to any legally required notice, consent, or choice.

Cuddle does not currently maintain an advertising-cookie category because it does not currently use cookies or similar technologies to sell personal information, serve targeted advertising, or share personal information for cross-context behavioral advertising.

3.2 Strictly Necessary and Service-Operation Technologies

Strictly necessary and service-operation technologies help make Cuddle and essential functionality available. They may load and route pages; maintain technical state; deliver Legal pages, pricing, and notices; operate registration, profiles, discovery, Likes, Matches, messaging, settings, reporting, blocking, and unmatching; preserve permitted form entries; apply account status and feature availability; support accessibility; and prevent duplicate submissions or technical conflicts.

Blocking or deleting these technologies may prevent pages, forms, settings, security protections, account functionality, or checkout from operating correctly.

3.3 Authentication, Session, and Account-Security Technologies

These technologies help Cuddle recognize and protect an authenticated session. They may support sign-in and sign-out; session creation, continuation, expiration, and invalidation; email confirmation; phone-number and new-device verification; password reset; account recovery; account permissions and restrictions; and detection of unusual login, credential misuse, session reuse, or possible account takeover.

They may use session identifiers, browser or device information, IP-address information, authentication events, and related security signals. They do not, by themselves, prove identity, age, account ownership, eligibility, or safety.

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

Cuddle may use these technologies to protect users, accounts, Cuddle, service providers, payment participants, and the Service. They may help detect, prevent, investigate, or respond to:

• bots, scraping, spam, automation, and rate-limit evasion;
• fake, duplicate, related, or farmed accounts;
• suspicious registrations, unusual device or network activity, and location evasion;
• credential misuse, account takeover, impersonation, and recovery abuse;
• scams, prohibited commercial activity, and coordinated deceptive conduct;
• card testing, payment-method testing, unauthorized payment use, and billing inconsistencies;
• transaction laundering, sanctions risk, refund abuse, and chargeback abuse; and
• attempts to evade safety, moderation, checkout, payment-method, or enforcement controls.

Cuddle may combine account, device, browser, IP-address, session, transaction, billing, support, safety, moderation, and risk information for these purposes where permitted by law.

A risk signal does not necessarily establish wrongdoing or ineligibility. These technologies may be incomplete, delayed, inaccurate, unavailable, or circumvented and do not guarantee detection or prevention of every harmful act.

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

Cuddle and authorized payment participants may use technologies to support direct checkout and related purchase processes. They may:

• load processor-hosted or processor-approved payment fields or flows;
• maintain checkout state and associate a transaction with the correct account;
• authenticate a payment method and communicate authorization status;
• prevent duplicate or unauthorized transaction attempts;
• provide purchase confirmations and receipts;
• activate, administer, and expire a thirty-day Premium period;
• support refunds, statutory cancellations, reversals, billing questions, chargebacks, and payment disputes; and
• maintain transaction, fraud-prevention, payment-risk, tax, accounting, and audit records.

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

These technologies do not create a subscription, recurring billing, automatic renewal, automatic repurchase, automatic trial-to-paid conversion, user-to-user payment, wallet, stored value, or external purchase channel.

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

Where implemented, Cuddle may use analytics, performance, diagnostics, and product-improvement technologies to understand and improve Service operation. They may measure page views, navigation, general feature use, load times, availability, browser or device compatibility, technical errors, failed requests, registration or invitation flows, support flows, checkout issues, controlled tests, and aggregated Service trends.

Cuddle does not use the substance of private in-Service messages, full payment credentials, submitted account-review materials, or other submitted highly sensitive content for targeted advertising.

These technologies remain subject to applicable notice, consent, opt-out, and data-minimization requirements.

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

Cuddle may use these technologies to remember and apply language, display, accessibility, interface, cookie, consent, communication, notification, and privacy choices. They may also recognize Global Privacy Control or another legally recognized universal opt-out signal where required, distinguish signed-in from signed-out choices, and prevent repeated or unnecessary prompts.

Some choice-record technologies may be necessary to remember that an optional technology was declined. Deleting them may cause the notice or choice request to appear again.

A changed choice generally applies prospectively and does not automatically delete previously created information or records Cuddle may lawfully retain.

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

Cuddle may use technologies to operate the Help Center and support interfaces; maintain a request session; route requests to the appropriate support, billing, privacy, safety, security, cancellation, appeal, or legal channel; preserve ticket, delivery, status, and troubleshooting information; support invitation, account, security, purchase, billing, refund, cancellation, privacy, policy, and Service communications; prevent automated or abusive submissions; and deliver required state-specific, cookie, privacy, safety, screening, or checkout notices.

These technologies do not make ordinary email, support, messaging, or form channels appropriate for full payment credentials, passwords, authentication codes, government-identification images, medical records, information about minors, or other highly sensitive information.

3.9 Records, Compliance, and Legal-Protection Technologies

Cuddle may use cookies, identifiers, logs, storage items, and server-side records to document policy and notice display; acceptance, acknowledgment, consent, withdrawal, opt-out, and privacy choices; purchase authorization, activation, expiration, refund, cancellation, and dispute events; and security, fraud-prevention, payment-risk, support, moderation, or enforcement events.

These records may also support legal compliance, evidence preservation, lawful requests, audits, dispute resolution, and the establishment, exercise, or defense of legal claims.

They are retained only as described in the Privacy Policy, this Cookie Policy, applicable notices, and law. Their use does not waive any non-waivable privacy, payment, cancellation, consumer-protection, court-access, or other right.

4. Information Collected Through Cookies and Similar Technologies

4.1 Overview

Depending on how you interact with Cuddle, cookies and similar technologies may collect, receive, generate, infer, or associate technical, usage, security, preference, support, and transaction-related information.

Not every item described below is collected from every person, browser, device, page, feature, form, account, or checkout flow. Some information may be stored in a browser or device. Other information may be transmitted through scripts, provider tools, processor-hosted flows, or server-side events and associated with an account, session, request, purchase, or security event.

Describing a category does not mean that Cuddle uses it for every purpose. Section 5 explains how Cuddle uses this information.

4.2 Device, Browser, Network, and Approximate-Location Information

Cuddle or its providers may collect or receive information such as:

• IP address and approximate location inferred from an IP address;
• device type, operating system, browser type and version, language, and time zone;
• referring page, requested page, Service or web version, and general navigation information;
• network, request, connection, and response information;
• page-load timing, availability, compatibility, error, and diagnostic information; and
• technical signals associated with suspicious, automated, unusual, or potentially evasive access.

Approximate location does not mean precise geolocation. Cuddle does not intend to collect precise geolocation through ordinary cookies unless a feature requires it and Cuddle provides any notice, choice, or consent required by law.

4.3 Identifiers, Sessions, Settings, and Preference Information

Cookies and similar technologies may create, receive, or use:

• cookie, local-storage, session-storage, browser, device, account, and session identifiers;
• authentication, login, sign-out, session-expiration, password-reset, account-recovery, email-confirmation, phone-verification, and new-device records;
• language, display, accessibility, notification, communication, and interface settings;
• cookie-banner interactions, consent status, withdrawal, opt-out, and privacy-choice records;
• Global Privacy Control or another legally recognized universal opt-out signal where applicable; and
• identifiers used to apply settings, prevent repeated prompts, maintain technical state, or connect related Service events.

An identifier does not, by itself, establish identity, age, eligibility, account ownership, payment authority, or safety.

4.4 Service, Feature, Support, and Reporting Activity

Cuddle or its providers may collect information about interactions with the Service, including:

• pages viewed, links selected, forms opened or submitted, and settings changed;
• registration, invitation, profile, discovery, Like, Match, messaging, blocking, unmatching, reporting, and account-management events;
• general feature use, timestamps, request status, delivery status, and technical outcome;
• Help Center use, support-interface activity, ticket or conversation identifiers, routing information, and request status;
• safety, security, privacy, billing, cancellation, appeal, or legal-notice workflow events; and
• errors, failed requests, repeated submissions, anti-spam limits, and technical troubleshooting records.

Ordinary cookies are not intended to collect the substance of private in-Service messages. Message content may still be processed through the Service as described in the Privacy Policy.

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

When you view pricing or use Cuddle’s authorized direct checkout, Cuddle and payment participants may collect or associate:

• checkout, order, transaction, authorization, receipt, and billing identifiers;
• product, price, currency, applicable taxes, payment-method type, and limited billing information;
• charges imposed independently by a payment participant, where made available to Cuddle;
• checkout step, payment-authentication status, authorization result, failure, reversal, refund, statutory-cancellation, chargeback, or dispute status;
• Premium activation and expiration information;
• the account, browser, device, IP address, and session associated with a transaction;
• billing-descriptor, receipt-delivery, and purchase-support records; and
• fraud-prevention and payment-risk signals related to an attempted or completed transaction.

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

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

Cuddle or its providers may collect or generate signals concerning bots, automation, scraping, rate-limit evasion, unusual login activity, credential misuse, account takeover, duplicate or related accounts, suspicious registrations, device or network changes, location inconsistencies, card testing, payment-method testing, unauthorized payment use, transaction laundering, sanctions risk, refund or chargeback abuse, prohibited commercial activity, and attempts to evade account, safety, moderation, checkout, payment, or enforcement controls.

These signals may be based on account, device, browser, IP-address, session, transaction, billing, support, safety, moderation, and Service-activity information.

A signal does not necessarily prove fraud, wrongdoing, ineligibility, or a violation.

4.7 Information Not Intended to Be Collected Through Ordinary Cookies

Cuddle does not intend ordinary cookies or similar technologies to collect:

• full payment card numbers, card security codes, or full bank credentials;
• passwords, authentication codes, private keys, or wallet credentials;
• identity-document images, government-identification images, or account-review images;
• the substance of private in-Service messages;
• medical records, information about minors, or intimate content; or
• other submitted highly sensitive content.

Do not enter such information into cookie settings, ordinary forms, support interfaces, profile fields, reports, messages, or other channels not specifically designed and authorized for it.

5. How We Use Cookies and Similar Technologies

5.1 Overview

Cuddle uses cookies and similar technologies for the purposes described in this Section, the Privacy Policy, applicable notices, and law.

Not every purpose applies to every person, browser, device, page, feature, account, or checkout flow. A technology may support more than one purpose, and Cuddle may combine information collected through those technologies with related Service information where reasonably necessary and permitted by law.

Cuddle applies applicable data-minimization, purpose-limitation, notice, consent, and choice requirements.

5.2 Service Operation, Account Access, and Core Functionality

Cuddle may use cookies and similar technologies to provide, operate, maintain, and deliver the Service.

These uses may include loading pages; maintaining technical state; supporting request-an-invite forms, registration, profiles, discovery, Likes, Matches, messaging, reporting, settings, and account management; keeping an eligible user signed in; maintaining sessions; applying account status and permissions; remembering permitted entries; preventing duplicate submissions; and delivering Legal pages, pricing, disclosures, and notices.

They may also support accessibility and compatibility.

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

Cuddle may use cookies, identifiers, logs, storage technologies, and server-side events to secure accounts and the Service and to detect, prevent, investigate, document, or respond to abuse, fraud, and payment risk.

These purposes may include identifying bots, scraping, spam, unusual login or device activity, credential misuse, account takeover, related accounts, account farming, impersonation, card testing, unauthorized payment use, transaction laundering, refund or chargeback abuse, prohibited commercial activity, and attempts to evade account, safety, moderation, checkout, payment, or enforcement controls.

Cuddle may use account, device, browser, IP-address, approximate-location, session, transaction, billing, support, safety, moderation, and risk information for these purposes where permitted by law.

A risk signal does not necessarily establish fraud, wrongdoing, ineligibility, or a Terms violation. These technologies may be incomplete, delayed, inaccurate, unavailable, or circumvented.

5.4 Checkout, Purchases, Premium Activation, and Expiration

Cuddle and authorized payment participants may use cookies and similar technologies to support Cuddle’s authorized direct checkout.

These uses may include loading processor-hosted or processor-approved payment fields; maintaining checkout state; associating a transaction with the correct account; supporting authentication and authorization; preventing duplicate or unauthorized attempts; documenting material terms displayed before authorization; providing receipts; activating and expiring a thirty-day Premium period; and supporting refunds, statutory cancellations, reversals, chargebacks, and payment disputes.

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

These technologies do not create a subscription, recurring billing, automatic renewal, automatic repurchase, automatic trial-to-paid conversion, stored value, a wallet, or a user-to-user payment.

5.5 Preferences, Consent, Privacy Choices, and Communication Choices

Cuddle may use cookies and similar technologies to remember and apply language, display, accessibility, interface, notification, communication, cookie, consent, and privacy choices.

They may record that a notice was displayed; that a choice, consent, withdrawal, or opt-out was submitted; or that Global Privacy Control or another legally recognized universal opt-out signal was received where applicable.

They may prevent repeated prompts and apply a choice to the relevant browser, device, session, or account.

Deleting a choice record may cause a notice to appear again. A changed choice generally applies prospectively and does not automatically delete records Cuddle may lawfully retain.

5.6 Analytics, Diagnostics, Testing, and Improvement

Where implemented, Cuddle may use analytics, performance, diagnostics, and testing technologies to understand and improve Service operation.

These uses may include measuring page views, navigation, general feature use, registration, support, and checkout flows, load times, availability, compatibility, errors, failed requests, product tests, and aggregated Service trends.

Cuddle may use the resulting information to troubleshoot, maintain, test, secure, and improve the Service, including safety, fraud-prevention, payment-risk, and technical systems.

Cuddle does not use the substance of private in-Service messages, full payment credentials, or submitted highly sensitive materials for targeted advertising. Cuddle does not sell personal information or share it for targeted advertising.

5.7 Support, Reporting, Safety, and Service Communications

Cuddle may use cookies and similar technologies to operate Help Center and support interfaces; maintain a request session; route requests to the appropriate channel; preserve ticket and troubleshooting information; and prevent automated or abusive submissions.

They may also support invitation, account, security, safety, purchase, billing, refund, cancellation, privacy, policy, support, report, appeal, and legal communications.

These technologies do not make ordinary email, support, messaging, or form channels appropriate for full payment credentials, passwords, authentication codes, government-identification images, medical records, information about minors, or other highly sensitive information.

5.8 Legal Compliance, Records, and Protection of Rights

Cuddle may use cookies, identifiers, logs, storage items, and server-side records to comply with applicable law, court orders, lawful government requests, and regulatory, tax, accounting, audit, and recordkeeping requirements.

Cuddle may also use them to document notices, acceptance, consent, withdrawal, opt-outs, purchase authorization, Premium activation and expiration, refunds, cancellations, disputes, security, fraud-prevention, payment-risk, support, moderation, and enforcement events.

These records may support evidence preservation, legal claims, enforcement of applicable terms, and protection of users, minors, Cuddle, service providers, payment participants, and the public.

5.9 Use Restrictions, No Price Personalization, and No Prohibited Use

Cuddle does not use cookie, device, browser, security, fraud-prevention, payment-risk, safety, moderation, account-history, eligibility, location, or similar information to personalize the price charged to an individual user.

Cuddle does not use cookies or similar technologies to provide credit, lending, insurance, employment, housing, consumer reporting, banking, brokerage, securities, money transmission, payment facilitation, marketplace payments, stored value, wallets, cryptocurrency, or other financial products or services.

Nothing in this Section authorizes Prohibited Services, Prohibited Payments, user-to-user transfers of value, adult-content monetization, sexual or escort services, compensated dating, sugar arrangements, paid companionship, abuse, exploitation, unsafe conduct, or unlawful activity.

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

6.1 Overview

Cuddle may use service providers, contractors, vendors, and payment participants to help operate, secure, support, maintain, and improve the Service.

Depending on their role, these parties may provide cookies, local or session storage, scripts, hosted forms, support interfaces, security tools, processor-hosted checkout fields, server-side events, infrastructure, communications, analytics where implemented, consent management, fraud prevention, or payment-risk services.

Not every provider uses cookies or similar technologies, and not every provider applies to every person, page, browser, device, account, form, support interaction, or transaction.

6.2 Cuddle-Controlled and Provider-Supported Technologies

Some technologies are set or controlled through a Cuddle-controlled domain or Service component. Others are supplied or operated by an authorized provider.

A provider may process information on Cuddle’s behalf under Cuddle’s instructions, configurations, agreements, and applicable law. A provider or payment participant may also process information independently under its own legal obligations, terms, privacy practices, security procedures, or network rules.

The Privacy Policy provides broader information about Cuddle’s service providers and disclosures of personal information.

6.3 Support, Form, and Security Technologies

Where Intercom functionality is available, Intercom may use cookies, local storage, session information, browser or device information, and related technologies to provide the Help Center, support communications, request routing, ticket management, and troubleshooting.

A request-an-invite link may direct you to a form hosted by Typeform. Depending on the form and settings, Typeform may use cookies or similar technologies and process browser, device, interaction, submission, and form information.

Cuddle uses Google reCAPTCHA for bot prevention and registration security. Google may process IP-address, browser, device, interaction, and related security information under its applicable terms and privacy practices.

Do not submit payment information, account-review images, medical information, information about minors, or other highly sensitive information through ordinary support tools or invite forms.

6.4 Checkout and Payment Participants

Cuddle may use authorized payment processors, payment-method providers, banks, card issuers, card networks, fraud-prevention providers, and payment-risk providers to support direct checkout and related transaction processes.

These parties may use hosted fields, scripts, cookies, identifiers, authentication tools, device or browser information, transaction records, and server-side events to support authorization, fraud prevention, payment-risk management, receipts, refunds, statutory cancellations, reversals, chargebacks, and payment disputes.

Processor-hosted or processor-approved fields or flows are part of Cuddle’s authorized direct checkout. Their use does not make the processor the contracting seller or create a separate external purchase channel.

Full payment card numbers and card security codes are intended to be submitted through those fields or flows and are not intended to be received or stored on Cuddle-controlled systems.

6.5 Infrastructure and Communications Providers

Cuddle uses AWS to host and operate portions of the Service and may use other infrastructure, storage, logging, security, communications, email-delivery, or SMS providers.

An infrastructure or communications provider may receive technical logs, delivery records, identifiers, diagnostic information, or service-status information without necessarily placing a cookie on your browser.

For example, Twilio supports phone-number validation and SMS verification-code delivery. This operational role does not necessarily mean that Twilio sets a browser cookie through every Cuddle interaction.

6.6 Independent Third-Party Terms and Privacy Practices

A third-party service that Cuddle does not own or control may use its own cookies or similar technologies and process information under its own terms and privacy practices.

Review applicable third-party information before using an external service or providing information. Cuddle does not control every independent third party’s cookie duration, settings, security, availability, or legal obligations.

Cuddle does not authorize providers acting for Cuddle to use personal information for unrelated advertising, user monetization, or purposes outside their authorized role, subject to independent legal obligations.

6.7 Provider Limits and Provider Changes

Cuddle may add, replace, remove, or change providers, integrations, payment participants, technical configurations, or processing locations as the Service evolves.

Cookie names, storage keys, domains, and retention periods may change. Cuddle will update this Cookie Policy, the applicable cookie inventory, notices, settings, consent process, or other disclosures where a material change or applicable law requires it.

A provider relationship does not guarantee uninterrupted operation, complete security, successful payment authorization, fraud prevention, message delivery, support response, or another outcome.

7. Analytics, Advertising Limits, No Sale or Sharing, and No Sensitive-Data Targeting

7.1 Analytics Where Implemented

Where implemented, Cuddle may use analytics, performance, diagnostic, and product-improvement technologies to understand how the Service operates and to maintain and improve it.

These technologies may measure page views, navigation, general feature use, invitation and registration flows, support interactions, load times, compatibility, errors, failed requests, checkout issues, controlled tests, and aggregated Service trends.

Cuddle may use analytics results to troubleshoot, secure, test, maintain, and improve the Service, including account security, safety, fraud prevention, payment-risk management, accessibility, and technical performance. Cuddle may also use aggregated or de-identified information as described in the Privacy Policy.

Analytics where implemented are not used to serve targeted advertising.

7.2 No Sale of Personal Information

Cuddle does not sell personal information.

Cuddle does not exchange personal information for money or other value in a manner treated as a sale under applicable privacy law. Operational disclosures to authorized service providers, payment participants, professional advisers, lawful authorities, or recipients you direct remain governed by the Privacy Policy, provider roles, applicable agreements, and law.

Nothing in this Section changes a legally required definition, exception, notice, or right.

7.3 No Sharing for Targeted Advertising

Cuddle does not share personal information for targeted advertising.

Cuddle does not currently use cookies or similar technologies to create advertising audiences, deliver advertisements based on activity across nonaffiliated websites or services, or permit an advertising network to target a person based on Cuddle activity.

Where applicable law uses a specific definition of “sharing” or “targeted advertising,” that definition controls.

7.4 No Cross-Context Behavioral Advertising

Cuddle does not use cookies or similar technologies for cross-context behavioral advertising.

Cuddle does not currently retarget users across unrelated websites or online services based on profiles, Likes, Matches, messages, purchases, support activity, or other Cuddle interactions.

Service-related notices, account communications, security messages, purchase communications, and contextual information displayed within Cuddle are not targeted advertising merely because they relate to your account or Service activity.

7.5 No Sensitive-Data, Private-Message, or Payment-Data Targeting

Cuddle does not use the substance of private in-Service messages, sensitive personal information, account-review materials, or payment-related information for targeted advertising.

This restriction includes sexual orientation you choose to provide; relationship or marital-status information; precise geolocation if collected; government-identification or account-review materials; and billing, refund, statutory-cancellation, chargeback, payment-dispute, fraud-prevention, or payment-risk information.

Cuddle will not use your profile photo, name, likeness, or private in-Service direct messages in public-facing advertising or marketing without separate consent.

7.6 No Individual Risk-Based Price Personalization

Cuddle does not use cookie, device, browser, security, fraud-prevention, payment-risk, safety, moderation, account-history, eligibility, location, or account-review information to personalize the price charged to an individual user.

This does not prevent prospective changes to publicly offered prices, applicable taxes, or clearly disclosed promotions, discounts, complimentary access, or product tests governed by their terms and applicable law.

7.7 Future Material Changes and Required Choices

If Cuddle materially changes the practices described in this Section, Cuddle will update this Cookie Policy and any applicable cookie inventory, notice, banner, setting, or consent process.

Where law requires advance notice, consent, an opt-out, recognition of Global Privacy Control or another universal opt-out mechanism, or another choice, Cuddle will provide or process it as required.

A change applies prospectively from its stated effective date unless law requires otherwise. Continued use does not replace separate consent where law requires consent for materially different processing.

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

8.1 Overview

Depending on the technology and applicable law, you may be able to accept, decline, withdraw consent for, block, delete, or otherwise control certain cookies and similar technologies.

Available methods may include a Cuddle cookie banner or settings tool, browser or storage controls, device controls, communication preferences, Global Privacy Control, or another legally recognized universal opt-out mechanism.

Technologies reasonably necessary for Service operation, authentication, security, fraud prevention, payment-risk management, direct checkout, privacy-choice records, or legal compliance may continue as permitted by law.

A choice generally applies prospectively. It does not automatically delete existing information, cancel a purchase, create a refund, end Premium, delete an account, or remove lawfully retained records.

8.2 Cookie Banners, Settings, and Consent Choices

Where required or otherwise provided, Cuddle may present a cookie banner, settings interface, or consent tool.

Available choices may depend on the technologies implemented, whether you are signed in, the page or feature involved, and applicable law.

You may be able to accept or decline optional technologies, make category-level choices, or withdraw prior consent. Cuddle may use a cookie, storage item, account setting, consent identifier, or server-side record to remember the choice.

Withdrawal applies prospectively and does not make prior lawful processing unlawful. Deleting a choice record may cause the notice to appear again.

Consent to optional technologies is separate from acceptance of the Terms of Service, acknowledgment of the Privacy Policy, payment authorization, or consent required for another activity.

8.3 Browser and Storage Controls

Most browsers provide controls to block, limit, or delete cookies, local storage, session storage, or site data.

Controls vary by browser, device, and configuration. A choice in one browser may not affect another browser, device, account record, or information already transmitted to Cuddle or a provider.

Blocking or deleting necessary technologies may affect sign-in, sessions, settings, support tools, invitation forms, security protections, checkout, receipts, Premium activation, or other functionality.

Browser deletion does not necessarily delete server-side logs, transaction records, consent records, fraud-prevention records, payment-risk records, or other information retained under the Privacy Policy and law.

8.4 Device, Operating-System, and Platform Controls

A device, operating system, browser, or supported platform may provide privacy, storage, tracking, or permission controls.

Those controls operate under the provider’s terms and privacy practices. Cuddle does not control their design, interpretation, accuracy, availability, or continued operation.

A device-level choice may not apply to every browser, account, provider, server-side event, or Cuddle-controlled record.

8.5 Global Privacy Control and Universal Opt-Out Mechanisms

Where applicable law requires Cuddle to recognize Global Privacy Control or another legally recognized universal opt-out mechanism, Cuddle will process a valid signal as required.

A signal may communicate an opt-out preference concerning sale, sharing, targeted advertising, or another covered activity. Its effect depends on applicable law, browser or device configuration, and Cuddle’s current practices.

Cuddle may use technical or server-side records to apply and document a required signal. Where permitted, Cuddle may request information needed to apply an account-level request.

8.6 Effect of Signals Under Cuddle’s Current Practices

Cuddle does not sell personal information, share it for cross-context behavioral advertising or targeted advertising, or currently use cookies or similar technologies to serve targeted advertising.

Because Cuddle does not currently engage in those activities, a related opt-out signal may have limited practical effect.

A signal does not require Cuddle to disable processing reasonably necessary for authentication, security, fraud prevention, payment-risk management, Service operation, direct checkout, legal compliance, or protection of users and the Service where permitted by law.

Cuddle will not use receipt of a valid signal to unlawfully discriminate, personalize an individual price, or deny a protected right.

8.7 Signed-In, Signed-Out, Cross-Browser, and Cross-Device Limits

A browser-based choice may initially apply only to the browser or device from which it was submitted.

If you are signed in, Cuddle may associate an applicable choice with your account where technically feasible and legally appropriate. A signed-out choice may not be associated with an account.

Choices may not automatically transfer across browsers, devices, private-browsing sessions, deleted storage, or separate accounts. You may need to submit the choice again after changing browsers or devices, clearing site data, using private browsing, or creating a new account.

8.8 Communications Preferences

Cookie and privacy choices are separate from communication preferences.

Where offered, you may change preferences for optional or marketing communications. Cuddle may still send Service-related communications concerning accounts, security, safety, purchases, billing, refunds, statutory cancellations, Premium activation or expiration, privacy, policy changes, support, reports, appeals, or legal matters where necessary or permitted.

Changing a communication preference does not cancel Premium, reverse a charge, create a refund, delete an account, withdraw another required consent, or replace a statutory-cancellation or privacy-request process.

8.9 Choice Records and Non-Waivable Rights

Cuddle may retain records showing that a notice was displayed; a choice, consent, withdrawal, opt-out, or signal was received; and related date, browser, device, account, category, version, or technical-result information.

These records may support compliance, troubleshooting, audits, dispute resolution, fraud prevention, security, and protection of rights, subject to the Privacy Policy and law.

For questions or an applicable privacy request, contact:

privacy@cuddle-global.com

Nothing in this Section limits any non-waivable cookie, privacy, consent, opt-out, authorized-agent, appeal, non-discrimination, data-security, consumer-protection, public-injunctive-relief, court-access, or other right under applicable law.

9. Retention, Security, and Cookie-Choice Records

9.1 Retention Criteria

Cuddle retains information associated with cookies and similar technologies only for as long as reasonably necessary and proportionate to the purposes described in this Cookie Policy, the Privacy Policy, applicable notices, and law.

Retention may vary based on the technology, category, provider, browser or device setting, account status, transaction, security event, request, and legal requirement. Cuddle may consider:

• whether a cookie, identifier, storage item, log, or server-side record remains necessary to operate or secure the Service;
• the duration of a session, setting, consent, opt-out, support interaction, checkout, purchase, dispute, or investigation;
• fraud-prevention, payment-risk, account-integrity, and abuse-prevention needs;
• tax, accounting, audit, legal-hold, recordkeeping, and dispute-resolution requirements; and
• reasonable backup, recovery, indexing, deletion, and provider-processing cycles.

Cuddle does not retain every category for the same period. Where available, the applicable cookie inventory may provide current duration information for particular browser-side technologies.

9.2 Cookie, Consent, Opt-Out, and Notice Records

Cuddle may retain records showing that a cookie or privacy notice was displayed; a settings interface was opened; a consent, withdrawal, opt-out, or preference was submitted; or Global Privacy Control or another legally recognized universal opt-out signal was received.

Records may include the applicable category, policy or notice version, date and time, browser or device information, session or account identifier, state of residence where relevant, technical result, and whether the choice was applied.

These records may support compliance, troubleshooting, audits, non-discrimination, dispute resolution, and proof that a choice was honored.

9.3 Browser Deletion and Server-Side Record Limits

Deleting cookies, local storage, session storage, or site data through a browser or device may remove information stored on that browser or device.

It may not delete information already transmitted to Cuddle or a provider, including server-side logs, consent records, transaction records, security records, fraud-prevention records, payment-risk records, support records, or records retained under the Privacy Policy and law.

Deleting a choice record may cause a notice or settings request to appear again. Browser deletion does not cancel Premium, reverse a charge, create a refund, delete an account, or complete a privacy-law deletion request.

9.4 Security and Integrity

Cuddle uses administrative, technical, and organizational safeguards designed to protect information associated with cookies and similar technologies against unauthorized access, use, disclosure, alteration, loss, or destruction.

Safeguards may include access controls, authentication, logging, provider controls, monitoring, rate limits, bot prevention, session controls, backup and recovery measures, and incident-response procedures.

No safeguard, cookie setting, browser control, consent tool, fraud-prevention system, or payment-risk system eliminates every risk or guarantees uninterrupted, error-free, or fully secure operation.

Report a suspected security issue to:

security@cuddle-global.com

Cuddle’s security channel is not an emergency-response channel.

9.5 Sensitive-Information Limits

Ordinary cookies and similar technologies are not intended to collect full payment credentials, passwords, authentication codes, government-identification images, account-review images, private-message content, medical records, information about minors, intimate content, or other submitted highly sensitive information.

Do not place such information in cookie settings, ordinary forms, support interfaces, profile fields, reports, messages, or other channels not specifically designed and authorized for it.

If Cuddle requests sensitive supporting information for a specific lawful process, follow the request-specific instructions and use only the authorized submission method.

9.6 Payment-Card and Checkout Information

Full payment card numbers and card security codes are intended to be 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 retain limited checkout, transaction, authorization, receipt, refund, statutory-cancellation, chargeback, payment-dispute, fraud-prevention, and payment-risk records as described in the Privacy Policy and Purchase Terms.

Retention of those records does not create a subscription, recurring billing, automatic renewal, automatic repurchase, stored value, wallet, or future charge.

9.7 Privacy Rights and Deletion Requests

Depending on applicable law, you may have rights concerning information associated with cookies and similar technologies, including access, deletion, correction, portability, consent withdrawal, opt-outs, appeals, and authorized-agent requests.

To submit an applicable privacy request, contact:

privacy@cuddle-global.com

A request may be subject to reasonable confirmation, exceptions, limitations, and retention permitted or required by law. Account deletion, browser deletion, cookie-choice withdrawal, statutory cancellation, refund requests, and privacy-law deletion are separate processes.

Nothing in this Section limits any non-waivable privacy, cookie, consent, opt-out, data-security, breach-notification, non-discrimination, consumer-protection, public-injunctive-relief, court-access, or other right under applicable law.

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

10.1 Contact Channels

For questions about this Cookie Policy, cookies, similar technologies, cookie settings, consent, Global Privacy Control, universal opt-out signals, or applicable privacy rights, contact:

privacy@cuddle-global.com

For suspected security issues, contact:

security@cuddle-global.com

For general technical or account support, contact:

support@cuddle-global.com

For billing, refunds, duplicate or unauthorized charges, chargebacks, payment disputes, or purchase-related support, contact:

billing@cuddle-global.com

For statutory cancellation 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. A general support message is not automatically a privacy request, cookie-choice request, statutory-cancellation request, payment dispute, or formal legal notice. The Contact / Legal Notices control current routing.

Cuddle’s channels are not emergency-response channels and may not be monitored in real time. If there is immediate danger, contact local emergency services.

Do not send full payment card numbers, card security codes, passwords, authentication codes, bank credentials, government-identification images, account-review images, private keys, information about minors, medical records, or other highly sensitive information through ordinary email or support channels.

10.2 Relationship to the Privacy Policy and Other Terms

This Cookie Policy is an Additional Term under the Terms of Service.

The Privacy Policy controls personal-information processing generally. This Cookie Policy controls cookie- and similar-technology-specific subjects, including categories, purposes, provider technologies, choices, Global Privacy Control, and cookie-choice records.

The Purchase, Billing, Cancellation & Refund Terms control checkout, payment authorization, billing, refunds, statutory cancellations, chargebacks, and payment disputes. The Paid Features Terms control Premium functionality, limits, activation, and expiration. The State-Specific Terms & Cancellation Notices govern applicable state-specific and non-waivable requirements.

10.3 Order of Priority

A more specific cookie banner, settings interface, consent request, privacy choice, provider notice, checkout disclosure, state-specific notice, purchase-specific term, or legally required notice controls the subject it specifically addresses.

The Privacy Policy controls a conflict concerning personal-information processing generally. This Cookie Policy controls a conflict concerning cookies or similar technologies, subject to a more specific notice and non-waivable law.

10.4 Changes, Effective Date, and Prior Versions

Cuddle may update this Cookie Policy, its cookie settings, provider technologies, or the applicable cookie inventory.

For a material change, Cuddle will update the Effective Date or Last Updated date and provide any notice, consent request, opt-out, acknowledgment, or other process required by law.

Updated practices apply prospectively from the stated effective date unless law requires otherwise. Continued use may acknowledge an updated policy where permitted, but does not replace separate consent where law requires consent for materially different processing.

Cuddle may retain prior versions and records of notices, consents, withdrawals, opt-outs, settings, and policy acknowledgments for compliance, troubleshooting, audits, dispute resolution, and legal claims.

An update does not retroactively authorize materially different processing where prior notice, consent, or another protection is required.

10.5 State-Specific and Non-Waivable Rights

Depending on applicable law, you may have rights concerning cookies and similar technologies, including consent, withdrawal, access, deletion, correction, opt-outs, authorized-agent requests, appeals, and recognition of Global Privacy Control or another universal opt-out mechanism.

The State-Specific Terms & Cancellation Notices and applicable law supplement this Cookie Policy. A greater or more favorable non-waivable right controls to the extent required.

Nothing in this Cookie Policy limits any non-waivable privacy, cookie, consent, opt-out, data-security, breach-notification, non-discrimination, consumer-protection, public-injunctive-relief, court-access, or other right.

10.6 Accessibility and Non-Discrimination

Cuddle will provide cookie notices and available choice methods in a reasonably accessible manner where required.

Cuddle will not unlawfully discriminate or retaliate against a person for exercising an applicable cookie or privacy right. Receipt of a valid choice or signal will not be used to personalize an individual price.

10.7 Final No-Prohibited-Use Provision

No cookie, identifier, provider technology, consent process, privacy choice, support response, checkout process, policy update, or legal right authorizes Prohibited Services, Prohibited Payments, external payment requests, user-to-user transfers of value, adult-content monetization, sexual or escort services, compensated dating, sugar arrangements, paid companionship, payment facilitation, marketplace activity, stored value, wallets, virtual credits, cryptocurrency, money transmission, financial services, abuse, exploitation, unsafe conduct, or unlawful activity.