Privacy Policy

CandidCodes Privacy
Privacy Policy

What information CandidCodes may process, why it may be used, which external providers may be involved, how long it may be retained, and which choices or rights may apply.

The short version: CandidCodes may process limited information needed to operate, secure, measure, and improve the publication, respond to messages, remember privacy choices, and attribute eligible affiliate referrals. CandidCodes does not operate merchant checkout systems and does not receive full payment-card details through ordinary affiliate links.

Who is responsible for this notice

CandidCodes is an independent editorial publication operated by Nguyen Van Dinh. This notice describes information processed in connection with candidcodes.com. It does not govern an independent merchant, affiliate network, embedded provider, or other external service.

Nguyen Van Dinh, Founder, CEO and Editorial Lead at CandidCodes
Founder, CEO & Editorial Lead

Nguyen Van Dinh

Nguyen Van Dinh is responsible for maintaining the CandidCodes privacy contact, aligning public policy language with the services the site actually uses, reviewing supported privacy requests, and updating this notice when processing purposes or integrations materially change.

Information that may be processed

Information you provide

Name, email address, message content, correction evidence, business affiliation, and attachments you deliberately send through an available contact route.

Technical and usage data

IP address, browser and device type, operating system, page URL, referral source, approximate region inferred from network information, timestamps, error records, and interaction events, depending on configuration.

Preference information

Cookie or privacy choices, language or display preferences, and identifiers used to remember a selection where a site control is available.

Affiliate referral data

A campaign, publisher, click, or transaction reference and limited conversion information that a merchant or network makes available under its program terms. CandidCodes generally does not need the buyer's full payment details or private order history for attribution.

Where information can come from

  • Directly from you: when you email CandidCodes, report an error, make a privacy request, or communicate as a merchant, network, or media contact.
  • From your browser or device: when technical logs, security controls, analytics, or preference systems receive data during a visit.
  • From affiliate partners: when a merchant or network reports that an eligible referral or action occurred under its rules.
  • From service providers: when hosting, security, analytics, email, or embedded services process data on behalf of or independently from CandidCodes.
  • From public or professional sources: when a correction, press, merchant, or policy inquiry includes publicly available business information relevant to the request.

Why information may be used

Operate and protect the site

Deliver pages, manage traffic, diagnose errors, prevent abuse, protect forms, and maintain service security and availability.

Respond and correct

Answer messages, review evidence, process correction or privacy requests, document decisions, and communicate necessary follow-up.

Measure and improve

Understand page performance, referral sources, general interaction patterns, and whether editorial content or technical features are useful.

Support affiliate attribution

Allow a merchant or network to determine whether an eligible action followed a deliberate CandidCodes link, subject to its program and privacy terms.

Remember choices

Store a necessary record of a privacy or cookie selection so the same choice does not need to be requested on every page.

Meet legitimate obligations

Preserve evidence of consent or requests where required, enforce site terms, protect rights, and respond to lawful process where applicable.

Where data-protection law requires a legal basis, the basis depends on the purpose and context. It may include consent for optional technology, necessity to respond to a request, legitimate interests in secure editorial publishing, or compliance with an applicable legal obligation. This notice does not claim that one basis applies in every country.

Cookies and similar technologies

CandidCodes may use cookies or comparable technologies for necessary operation, privacy preferences, analytics, performance, embedded features, and eligible affiliate attribution. The active technology can vary by page, provider, region, consent choice, and configuration.

Where applicable law requires a choice before non-essential technology operates, continuing to browse should not by itself be treated as consent. Use any available site preference control and browser settings to manage choices.

For categories, third-party boundaries, duration, and controls, read the Cookie Policy.

Who may receive information

CandidCodes does not publish a contact message or privacy request merely because it was submitted. Information may be made available only as reasonably needed for the relevant purpose.

Infrastructure providers

Hosting, security, content delivery, error monitoring, and technical providers may process data needed to deliver and protect the site.

Communication providers

Email or form services may process names, addresses, message content, metadata, and attachments used to handle a request.

Analytics or embedded services

Where active and permitted, a provider may process device, page, referral, and interaction data under its own terms or service arrangement.

Affiliate networks and merchants

A deliberate outbound referral may carry a publisher or click identifier. The destination independently determines its checkout, account, attribution, and privacy practices.

Professional or legal recipients

Information may be disclosed where reasonably necessary to obtain advice, protect rights or security, investigate abuse, or comply with a valid legal requirement.

CandidCodes does not sell personal information as a standalone data product. This statement does not replace any more specific opt-out or disclosure right that may apply under a particular law or to an independent provider's activity.

How long information may be kept

CandidCodes does not apply one fixed period to every data category. Retention should be limited to what is reasonably needed for the purpose, technical security, correction history, request handling, contractual requirements, dispute prevention, or applicable legal obligations.

  • Routine technical logs may be kept for a limited operational or security period and then deleted, aggregated, or overwritten according to provider configuration.
  • Contact and correction records may be retained while the request is active and longer where needed to document the resulting editorial decision or protect against repeated abuse.
  • Consent or preference records may remain while needed to remember and demonstrate a choice, subject to renewal, deletion, or configuration changes.
  • Affiliate attribution periods and transaction-reference retention are determined in part by the independent merchant or network and its program rules.

Security and data minimization

CandidCodes aims to limit collection to information relevant to the stated purpose and to use reasonable organizational and technical safeguards. No website, email system, provider, or internet transmission can be guaranteed completely secure.

International services and external websites

CandidCodes can be visited from different countries, and service providers may process or store information in jurisdictions different from the visitor's own. Privacy rights, government access rules, and safeguards can vary. Where a transfer mechanism or additional safeguard is legally required for a specific processing arrangement, it should be assessed against the relevant provider and location.

When a reader follows a merchant link, the destination's privacy notice, cookies, account, and checkout terms apply. CandidCodes cannot access or control all data collected independently by that destination.

Your choices and privacy rights

Depending on location and applicable law, a person may have rights to request access, correction, deletion, restriction, objection, portability, withdrawal of consent, or information about processing. Not every right applies to every type of data or request.

  1. Send the request from a contact route that reasonably allows CandidCodes to understand which information may relate to you.
  2. State the right or outcome requested and the interaction, email, page, or approximate date involved.
  3. Provide only the minimum additional information reasonably needed to verify the request. CandidCodes may ask focused questions when identity or scope cannot otherwise be established.
  4. CandidCodes may refuse or limit a request where the law permits, including where identity cannot be verified, the request is manifestly unfounded or excessive, or retention is required to protect legal rights.
  5. Where applicable, a person may contact the relevant data-protection authority. CandidCodes cannot select an authority without knowing the person's jurisdiction and the processing involved.

Withdrawing consent does not make earlier processing unlawful where it was valid at the time, and it does not necessarily delete data held under another applicable basis.

Children's privacy

CandidCodes is not directed to children under 13 and does not knowingly seek personal information from them. If a parent or guardian believes a child has provided personal information to CandidCodes, they may contact CandidCodes with enough context to locate and review the information without sending additional sensitive data.

Changes to this Privacy Policy

This policy may be updated when purposes, providers, site features, affiliate arrangements, legal requirements, or contact practices materially change. The review date should change when a material revision is published.

A policy update does not by itself create consent for a new non-essential purpose where consent is required. The live technical configuration and available choices should remain consistent with the published explanation.

Frequently asked questions

Does CandidCodes receive my payment-card number?

Not through an ordinary affiliate link. Payment and private order information are handled by the independent merchant or its payment providers.

Can I use CandidCodes without optional cookies?

Ordinary editorial content should remain available, although analytics, personalization, embedded features, or affiliate attribution may operate differently. Use any available consent control and browser settings.

Can CandidCodes delete merchant data?

No. A merchant or network controls data in its own account, checkout, and tracking systems. Submit a separate request to that organization.

How do I make a privacy request?

Email the purpose of the request, the relevant interaction, and enough limited context to locate the record. Do not send passwords or complete payment details.

Privacy contact

Ask a privacy question or make a request

State the relevant interaction, page, email, approximate date, and the right or outcome requested. Provide only the minimum information needed to locate and assess the request; do not send passwords or complete payment details.