KYC & Identity Verification Policy – Clinkt.me

Last updated: February 10, 2026

This KYC & Identity Verification Policy (the "Policy") explains how Clinkt.me ("Clinkt.me", "we", "us") verifies the identity of certain users in order to (i) prevent fraud and illegal use of the Service, (ii) protect the platform and its users, and (iii) meet compliance and risk-control expectations commonly required by payment processors and financial partners.

This Policy forms part of, and must be read together with, the Terms of Use, the Privacy Policy, and the Content Monitoring Policy. Capitalized terms not defined here have the meaning given in the Terms of Use.

1. What "KYC" Means on Clinkt.me

"KYC" (Know Your Customer) refers to identity and risk checks we may require before allowing certain activities (notably payouts), and to detect and prevent fraud, abuse, money laundering, exploitation, and other prohibited activity.

KYC is risk-based: the level of verification may vary depending on account type, transaction patterns, geography, content category risk, and signals of fraud or abuse.

2. Who Must Complete KYC

We may require KYC from:

Creators who request payouts, monetize content, or reach certain volume/thresholds.
Users (Creators or Clients) flagged by our systems or partners for risk, fraud, chargebacks, or suspicious behavior.
Users whose activity suggests the need for enhanced verification (e.g., repeated disputes, unusual payment behavior, multiple accounts, mismatched details).
Any user where KYC is required to comply with legal obligations, payment partner rules, or law enforcement requests.

If you refuse or fail KYC, we may restrict your use of the Service (including monetization and payouts).

3. Our Verification Provider (Veriff)

We use Veriff as our identity verification provider to perform document and selfie-based identity verification. During verification, Veriff typically captures:

Photos and/or video of the verification session and the identity document(s) provided, and
Data extracted from the session, such as face scans and other measurements (which may be treated as biometric data in some jurisdictions).

Veriff also describes that it examines information such as metadata and device/network information as part of verification and fraud checks.

Retention (Veriff): Veriff publicly describes default retention for certain Enterprise arrangements as 90 days in active service and then 3 years in archive (with variations depending on plan/features and customer configuration). Clinkt.me configures retention to the extent available and appropriate for our compliance needs.

4. What We Collect for KYC (Typical Data Categories)

Depending on the verification flow and risk level, we (and/or Veriff on our behalf) may collect and process:

4.1 Identity Information

Full name, date of birth, nationality (as shown on the document)
Document type, document number, issuing country, expiry date
Address details where relevant (e.g., for payout setup or compliance checks)

4.2 Document & Biometric Verification Data

Images of government-issued ID (e.g., passport, national ID card, driver's license, residence permit)
A live selfie and/or short video for liveness/real-person checks
Extracted facial measurements/face scans (may be biometric/sensitive data under certain laws)

4.3 Technical & Fraud-Prevention Signals

Device and network information, metadata, timestamps, IP-related signals, and session attributes used for fraud prevention and integrity checks

4.4 Business / Payout Information (Creators)

Payout account details (e.g., IBAN/beneficiary details) and basic payout profile information
Supporting documents where required (e.g., proof of relationship to the payout account)

Note: The exact fields collected depend on the verification flow enabled and the circumstances of your account.

5. How KYC Works (High-Level Steps)

A typical verification flow includes:

Document capture (front/back if applicable)
Selfie / liveness check to confirm the person is present and matches the document
Automated and/or human review by Veriff as needed
Decision output (approved, resubmission needed, or declined)

If verification fails, we may allow resubmission or request additional information, at our discretion.

6. Why We Do KYC (Purposes)

We process KYC data for the following purposes:

Identity verification for account integrity, payout access, and platform safety
Fraud prevention and detection, including chargeback and account abuse risk reduction
Compliance with payment partner requirements and applicable legal obligations (where relevant)
Prevention of prohibited activity, including exploitation, trafficking, CSAM, and other illegal activity (in coordination with our enforcement policies)
Dispute handling, investigations, and audit trails where necessary

7. Risk-Based Approach and Enhanced Due Diligence

We may apply additional controls ("Enhanced Due Diligence") for higher-risk scenarios, which can include:

Requesting additional documents or clarifications (e.g., second ID, proof of address)
Additional verification attempts or manual review
Additional checks related to fraud patterns, repeated disputes, or unusual transaction activity

Where permitted and relevant, we may also conduct screening checks through approved providers (e.g., fraud prevention databases). (Any such screening is performed only when necessary and proportionate.)

8. Outcomes, Restrictions, and Enforcement

8.1 If KYC Is Not Completed or Fails

If you do not complete KYC, fail verification, or provide inconsistent/false information, we may:

restrict access to monetization features,
block or delay payouts, or freeze balances pending review,
suspend or terminate your account,
remove or restrict access to related content/links,
require re-verification at a later time.

8.2 Suspicious Activity

If we reasonably suspect fraud, identity theft, money laundering, exploitation, or any illegal activity, we may take immediate action under our Terms, including account suspension/termination and cooperation with competent authorities.

9.1 With Veriff

KYC data is shared with Veriff for the purpose of providing identity verification services. Veriff's privacy notice explains it shares identity verification data with the customer (i.e., the business using Veriff for verification).

9.2 With Payment and Risk Partners

We may share limited KYC status signals (e.g., verified/not verified, risk outcomes) and necessary information with payment processors, fraud prevention partners, and service providers strictly for:

fraud prevention,
transaction risk management,
compliance and audit requirements,
dispute handling.

We do not sell KYC data.

9.3 With Authorities

We may disclose relevant information where required by law, court order, or lawful request, or where necessary to report suspected illegal activity.

10. Data Minimization and Security

We apply reasonable administrative, technical, and organizational measures designed to protect KYC data, including access controls and least-privilege handling.

We collect and retain KYC data only as necessary for the purposes described in this Policy and as required by applicable law and partner obligations.

11. Retention

KYC/verification data is retained only for as long as necessary for:

fraud prevention and platform safety,
compliance and audit requirements,
dispute handling and investigations,
legal obligations.

Where Veriff is involved, Veriff publicly describes retention defaults (which may vary by plan and enabled features) such as 90 days in the service and 3 years in archive for certain Enterprise configurations. Clinkt.me's retention may be shorter or longer depending on our obligations and the configuration available for our plan/features.

12. User Responsibilities

You agree to:

provide accurate, current, and complete information,
use only your own identity documents (unless explicitly authorized by law and approved by us),
not attempt to bypass or manipulate verification (e.g., altered documents, deepfakes, impersonation),
promptly update material information if it changes.

Providing false information is a material breach of the Terms.

13. Re-Verification

We may require re-verification:

periodically,
when payout details change,
after suspicious activity, disputes, or high chargeback rates,
when required by payment partners or legal obligations.

14. Rights and Contact

To exercise applicable data protection rights or ask questions about this Policy, contact: [email protected]

If your verification is conducted through Veriff, Veriff's privacy notice explains that providing personal data is voluntary but may prevent verification if not provided.

15. Policy Updates

We may update this Policy to reflect changes in:

legal/regulatory requirements,
payment partner expectations,
fraud patterns and security needs,
our verification provider's capabilities.

Material changes may be communicated via the Service or by reasonable notice.