1. Introduction
This Policy explains information handling in connection with ClicksBounty. The responsible operator is [Owner decision required: legalEntityName], based in [Owner decision required: registeredCountry], with registered address [Owner decision required: registeredAddress]. These details must be completed before production processing. Privacy contact: [Owner decision required: privacyEmail].
2. Scope
This Policy covers visitors, applicants, account users and information processed through ClicksBounty tracking and operations. Third-party campaign destinations and providers may process information under their own notices. Affiliates must give appropriate notices for information they collect through their own promotion.
3. Information We Collect
We seek to collect only information reasonably necessary for application review, identity verification, account operation, tracking, payments, security, compliance and legal obligations. Categories depend on how you interact with the service. Do not submit unrelated sensitive information or extra identification merely because it is available.
4. Information You Provide
You may provide your name, company name, email, phone and alternative contact details, address, country, timezone and communication preference. Support enquiries may contain information you choose to include. Provide only the details needed for the request and avoid sending identity documents through ordinary email.
5. Affiliate Application Information
Applications collect affiliate experience, a promotion plan, promotional URLs, optional campaign interests and how you heard about the network, alongside contact and address details. We also record application status, review information and relevant agreement acknowledgements. Application drafts are saved in local browser storage; avoid shared devices and clear site data to remove an unfinished local draft.
6. Identity Verification Information
Purpose, restricted access and retention
Applications currently request a passport, national identity card or driver’s licence, including the relevant page or sides. Another document should be provided only if specifically approved through a secure process. Documents may contain a photograph, document identifier and other information shown on the submitted copy. Do not upload unrelated documents.
Verification helps us review identity, prevent fraudulent accounts, protect advertisers and affiliates and support network integrity. Applicable legal or compliance requirements may also justify verification; the operator must confirm the legal basis: [Owner decision required: identityVerificationLegalBasis]. Documents are not intended for advertising purposes.
Uploaded files are stored outside the public website directory with restricted filesystem permissions. The document download route requires staff administrator authentication. Access is restricted to authorised personnel and necessary service providers for the stated purposes. The specific retention decision remains unresolved: [Owner decision required: identityDocumentRetention]. A scheduled deletion process must be verified before launch; no fixed deletion deadline is promised by this draft.
7. Account Information
We process login identifiers, password hashes, affiliate identifiers, account status and relevant account timestamps. We record the document versions and times of legally relevant acceptances. We do not need your password in correspondence.
8. Technical and Usage Information
Requests may expose an IP address, browser or device information, referrer and timestamps. Click records store a hashed IP value, user agent and referrer; security and operational processing may use request IP addresses. Infrastructure logs may also contain technical information and require review in the deployment inventory.
9. Tracking and Attribution Information
We record campaign access, generated tracking links, click identifiers, conversion and transaction identifiers, statuses, commission records and payment records. Partner notifications may include tracking parameters such as Sub IDs where supported; these must not contain unnecessary personal information. This information associates activity with campaigns and affiliates, supports reporting and helps investigate duplicate or invalid activity.
10. Communications
We use contact information to respond to enquiries and send application, account, security and other operational messages. Marketing communications, if introduced, require a separate applicable permission and opt-out process. Agreement acceptance is not a blanket permission for marketing.
11. How We Use Information
We use relevant information to assess applications, verify identity, administer accounts and campaign access, attribute activity, calculate and reconcile commissions, record payments, provide support, investigate misuse and meet applicable obligations. New incompatible purposes require assessment and appropriate notice or permission before use.
12. Legal Bases Where Applicable
Where applicable law requires a legal basis, processing may depend on steps requested before a contract, contractual performance, a legal obligation, legitimate interests subject to a balancing assessment, or consent where appropriate. The applicable basis must be assessed per purpose and jurisdiction; these are not interchangeable permissions. Acknowledging this Policy is not blanket consent. Identity verification and any sensitive information require specific operator review before launch.
14. Service Providers
Hosting and infrastructure providers support operation and storage; email providers support messages. Payment providers may handle payment delivery. Security, analytics or identity-verification providers should receive information only if introduced for an assessed purpose under appropriate arrangements. This Policy does not imply that every category is currently deployed or name an unselected provider.
15. Advertisers and Network Partners
Campaign partners may receive relevant attribution and conversion information to operate campaigns, validate events and investigate quality. They may return conversion, rejection or adjustment information. Affiliate identity documents are not routinely campaign reporting data and should not be disclosed merely to promote an offer. Partners’ independent processing may be subject to their own notices.
16. International Data Transfers
Hosting, service provision or campaign relationships may involve information crossing borders. The operator must identify actual locations and any safeguards required by applicable law before such processing. Approved transfer arrangements: [Owner decision required: internationalTransfers]. No particular country, adequacy decision or contractual safeguard is assumed.
17. Data Retention
Information should be retained only as long as reasonably necessary for its stated purposes and applicable requirements, considering account operation, payment reconciliation, disputes and lawful preservation needs. Internal schedules must distinguish application documents, accounts, tracking, financial and audit records.
General schedule: [Owner decision required: generalRetentionSchedule]. ID-document schedule: [Owner decision required: identityDocumentRetention]. These require approval and an operational deletion process before production. A stored deletion date is not proof that deletion occurs. Local browser drafts remain until submitted, cleared or removed through browser site-data controls.
18. Security
Safeguards include private document storage, authenticated staff access to document downloads, hashed account passwords and signed HTTP-only session cookies. Reasonable administrative, technical and organisational measures also require operator access review and secure deployment practices. No system is completely secure. Notify suspected exposure promptly through the contact route without reproducing the sensitive material.
19. Your Privacy Rights
Depending on your location and applicable law, you may have rights to access, correction, deletion, restriction, objection, portability, withdrawal of consent and complaint to a relevant supervisory authority. Not every right applies in every situation. Withdrawing consent does not undo prior lawful processing.
Contact [Owner decision required: privacyEmail] to request assistance. We may need proportionate information to verify a request and explain any lawful limitation, such as records needed for an unresolved payment dispute. The owner must establish the request-handling procedure: [Owner decision required: privacyRightsProcess]. Do not submit a fresh identity document unless reasonably necessary and requested through a secure route.
21. Children's Privacy
ClicksBounty is intended for persons able to enter into a binding agreement and is not designed for children. If you believe information was submitted by someone without the required capacity, contact us so we can assess appropriate action. No universal statutory age is asserted; the applicant age policy requires review.
22. Changes to This Policy
Updates display a version, last updated date and effective date. Material changes will be communicated through an appropriate platform or account notice. Where consent is required for a new use, a policy update alone does not substitute for obtaining it.
23. Contact
Privacy enquiries: [Owner decision required: privacyEmail]. General support: support@clicksbounty.com. Responsible operator: [Owner decision required: legalEntityName]. A working privacy contact must be configured before production; general enquiries can be directed to support pending designation of the privacy contact. Do not email passwords or verification documents.
Contact ClicksBounty