This policy explains how CandidCodes may use cookies and similar technologies for site operation, preferences, measurement, security, and eligible affiliate attribution. It also explains what can happen after a reader follows a link to an independent merchant or service.
The short version: some technologies can be necessary to deliver a page securely or remember a privacy choice. Other technologies may support analytics, content performance, or affiliate attribution. The exact technology active can depend on the page, integration, location, browser settings, and consent choice.
CandidCodes is an independent editorial publisher, not an online merchant. When a reader deliberately follows an affiliate-supported link, a merchant or affiliate network may use a click identifier, cookie, or comparable technology to determine whether an eligible action followed that referral. This does not increase the price set by the merchant and does not give CandidCodes access to the merchant’s checkout or payment-card system.
CandidCodes does not treat continued browsing by itself as consent to non-essential cookies where a clear consent choice is legally required. Where a consent or preference control is presented, the selection made through that control should determine which optional categories can operate.
Plain-English summary
Strictly necessary technology supports a requested service or essential site operation. Optional analytics, preference, embedded-content, advertising, or attribution technology may require a separate choice depending on the visitor’s location and the way the service is configured.
A cookie is a small text file that a website or connected service can store through a browser. Cookies can help a website recognize the same browser during a session or across later visits. A cookie does not always contain a name or email address, but its identifier and related data may still be treated as personal information under applicable privacy law.
First-party and third-party cookies
A first-party cookie is set in connection with the domain being visited. A third-party cookie is associated with another provider used by the page, such as an analytics, embedded-content, advertising, merchant, or affiliate service.
Session and persistent cookies
A session cookie is normally removed when the browser session ends. A persistent cookie remains for a defined period or until it is deleted. The duration should match the purpose and may be set by CandidCodes or an independent provider.
Similar technologies
Local storage, pixels, tags, software development kits, server-side identifiers, and tracking parameters can perform functions similar to cookies. References to cookies in this policy include comparable technologies where the context requires it.
The categories below describe possible functions rather than claiming that every category operates on every page. CandidCodes should not publish a specific cookie name, provider, or duration unless that technical detail has been confirmed.
Supports a service the visitor requests or an essential technical function such as security, load distribution, session continuity, fraud prevention, or storing a consent choice. Blocking necessary technology can prevent a page or control from working correctly.
May remember a setting such as a display preference, language, region, dismissed message, or interface choice. A preference is not automatically strictly necessary merely because it makes the site more convenient.
May measure page visits, navigation paths, referral sources, device or browser trends, loading behavior, and broad content performance. Configuration, consent status, aggregation, and provider terms determine what data is processed.
May associate an intentional outbound click with CandidCodes so a merchant or network can determine whether an eligible purchase or other approved action followed the referral. Attribution rules and duration are controlled by the applicable program.
A video, social post, map, widget, or other external feature may allow its provider to set or read technology when the content loads or is used. If no such content appears on a page, this category may not apply to that visit.
Some CandidCodes links are affiliate-supported. When a reader chooses to follow one of these links, the destination may receive information needed to route the visit, such as a publisher or campaign identifier, click reference, destination, timestamp, and basic technical information. The merchant or affiliate network may then use a cookie or similar method to determine whether a later action qualifies under its program terms.
Intentional outbound action
CandidCodes does not use forced clicks, adware, automatic cookie placement for an unselected merchant, or a misleading redirect to manufacture a referral. The reader decides whether to leave CandidCodes and visit the merchant.
Program-specific rules
A merchant or network determines its attribution period, qualifying actions, exclusions, cross-device rules, and whether another referral can replace an earlier one. Those terms can vary by program, market, browser, and consent status.
No checkout access
CandidCodes does not receive a buyer’s full payment-card number through an affiliate link and cannot view or change the merchant’s private order, shipping, return, refund, or warranty records.
Editorial separation
Affiliate attribution may support the publisher when an eligible action occurs. It does not make a code valid, a sale valuable, a merchant suitable, or an editorial limitation less relevant.
The commercial model is explained in Affiliate Disclosure: How CandidCodes Makes Money and the Disclosure Policy.
CandidCodes may connect with services operated by other organizations. Depending on the page and configuration, these could include hosting or security services, analytics providers, embedded-content platforms, affiliate networks, and merchants reached through outbound links.
An independent provider may process data under its own privacy and cookie terms. CandidCodes does not control every cookie placed after a reader leaves CandidCodes or interacts with external content. Provider names, purposes, and retention periods can also change when integrations or program terms change.
Before leaving CandidCodes
Review the destination domain and any affiliate disclosure near the link. Browser privacy settings, consent choices, content blockers, and private-browsing modes can affect whether a referral or external feature works as expected.
After reaching a merchant
The merchant’s own privacy notice, cookie policy, consent interface, checkout terms, and account settings apply. Cookie choices made on CandidCodes may not automatically control the independent merchant website.
When external content is embedded
The provider may receive the page URL, IP address, browser or device details, and interaction information. Where consent is required, optional embedded technology should not be treated as necessary merely because the content is useful.
Where applicable law requires consent, a non-essential cookie or similar technology should not be activated solely because a visitor opened a page or continued browsing. A valid choice should be clear, informed, and made through a positive action.
May operate where it is genuinely required to transmit a communication, protect the service, remember a privacy choice, or provide a feature specifically requested by the visitor, subject to applicable rules.
Analytics, preference, embedded-content, advertising, or affiliate-related technology may require a choice before activation, depending on configuration, purpose, and location.
Where a consent interface is shown, accepting and rejecting optional categories should be understandable. A visitor should not have to infer that closing a notice means consent.
A visitor can use any available site preference control or browser settings to withdraw or adjust a choice. Removing a consent cookie may cause the site to ask again on a later visit.
Rejecting optional technology should not block ordinary editorial content, although analytics, personalization, embedded media, or affiliate attribution may not work in the same way.
Cookie duration depends on purpose and provider. A session cookie may end when the browser closes. A persistent cookie can remain until its configured expiration, until the visitor deletes it, or until the provider replaces or withdraws it.
CandidCodes does not assign one retention period to every technology because necessary, preference, analytics, affiliate, and external-provider uses are different. Affiliate attribution periods are normally determined by the merchant or network. Analytics and embedded-service durations depend on the active configuration and provider terms.
Where a current consent interface or technical cookie register identifies an active cookie, the name, provider, purpose, category, and duration shown there should be treated as the implementation-specific detail. CandidCodes should review that record when a provider, integration, consent setting, or purpose changes.
Depending on the technology and configuration, data may include an IP address, browser or device type, operating system, page URL, referral source, approximate region inferred from network information, timestamps, interaction events, consent choice, campaign identifier, click reference, and an identifier assigned to a browser or device.
This information may be combined by an independent provider with data it receives from other sites or services, subject to that provider’s terms and the visitor’s choices. CandidCodes cannot describe an external provider’s entire data operation through this policy alone.
CandidCodes does not ask readers to provide passwords, one-time codes, full payment-card numbers, or merchant account credentials through cookies. If a third-party checkout collects payment or order data, the merchant’s privacy and security practices govern that transaction.
Use available CandidCodes preferences
Where a cookie or privacy control is displayed, use it to accept, reject, or adjust optional categories. The control may store a necessary preference record so the choice does not need to be requested on every page.
Use browser settings
Most browsers allow cookies to be viewed, deleted, blocked, limited by site, or restricted in private-browsing mode. Blocking all cookies can also remove saved choices and cause some technical or external features to stop working.
Review independent providers
A merchant, affiliate network, analytics service, or embedded-content provider may offer its own preference, opt-out, or account controls. Deleting a CandidCodes cookie does not necessarily remove a cookie set by an independent domain.
Browser privacy signals
Browsers and extensions may send Do Not Track, Global Privacy Control, or other signals. There is no single response that applies to every technology and jurisdiction. Use the site controls and browser settings available to you, and contact CandidCodes if a required choice appears not to work.
CandidCodes may update this policy when site functionality, providers, affiliate relationships, consent controls, legal requirements, or the purposes of processing change. The review date at the top should be updated when a material revision is published.
A policy update does not by itself provide valid consent for a new non-essential purpose where consent is required. Material changes should be reflected in the live choice presented to affected visitors and in the technical configuration that follows that choice.
Related information is available in the Privacy Policy, Terms of Use, and About CandidCodes.
Founder, CEO & Editorial Lead
Nguyen Van Dinh operates CandidCodes and is responsible for maintaining the publisher’s policy framework, affiliate disclosures, contact route, and the accuracy of statements made on CandidCodes about its own use of cookies and similar technologies.
A policy should be checked against the live site, active integrations, consent behavior, and provider settings. Generic policy language should not be used to conceal an unlisted tracking purpose.
When a service is added, removed, or repurposed, CandidCodes should reassess its category, data, duration, consent requirement, and third-party disclosure before treating the policy as current.
A reader can ask which category or provider appears relevant to a page, report a consent-control problem, or request clarification through the published contact address.
CandidCodes may use cookies and similar technologies for necessary site operation, preferences, analytics, performance, and eligible affiliate attribution. The active technology can vary by page, integration, consent choice, browser, and location.
Not by itself where applicable law requires a clear consent action. When a consent control is presented, use that control to accept, reject, or adjust optional categories.
The destination may receive a publisher or click identifier. A merchant or affiliate network may use a cookie or similar method to determine whether an eligible action followed the referral. The destination’s own privacy and cookie terms then apply.
Available choices depend on the live consent control, browser settings, provider, and applicable rules. Rejecting or blocking optional technology may prevent analytics, embedded content, or referral attribution while leaving ordinary editorial content available.
No. CandidCodes cannot directly delete a cookie controlled by an independent merchant or network domain. Use browser controls and any privacy or opt-out tools offered by that provider.
Email contact@candidcodes.com with the page URL, country or region, browser, approximate time, the choice made, and what happened. Do not include passwords, payment information, or unnecessary identity documents.
Privacy & cookie questions
Include the affected URL, browser, country or region, approximate time, choice selected, and the behavior observed. Specific technical context helps CandidCodes distinguish a site problem from an independent merchant or browser setting.