🔒 Privacy-first KYC — your data stays yours

This is the real output of the blurring step — not an illustration.

You place one box around your portrait. Everything else on the card is blurred out on your phone, before the image is sent. That always covers:

• Your ID number — every digit, not just the middle ones
• Your full date of birth — we only ask you to type the year, which is all we need to confirm you're 18+
• Your place of origin and home address printed on the card
• Any QR code or barcode — it encodes your full ID data

What we check: a quick liveness selfie matched to the portrait on your ID — enough to confirm it's really you, and that one person opens only one account.

One exception, on purpose: you also frame the single line showing your ID number. That narrow strip is read on our server only to confirm it matches the number you entered, then discarded in memory — it is never written to disk and never shown to anyone. Without it, the number would be whatever you typed, and one person could open any number of accounts.

What we keep: the bare minimum. We never ask for your address at all, and never for the back of your card. The ID number is turned into a one-way, unreadable value the moment it is confirmed, and the original is discarded immediately — it is never written to disk. Verification images are encrypted and deleted after review, along with your name and year of birth.

One thing we keep for good, and you should know before you start: a face template — a short list of numbers derived from your selfie. It is biometric data. We keep it encrypted, after approval and after account deletion, for one purpose only: to flag it for a human if someone later applies with the same face under a different document. The one-way ID value cannot catch that on its own, because one person can hold more than one valid document number. No API returns the template and no staff member can view it. We will not claim it is impossible to reverse — research on reconstructing approximate faces from templates like this exists. If you would rather not have one held, don't start verification; nothing else on TCC requires it. Full detail in our Privacy Policy, section 4.

Your data, your control. — @TCC Core team

📝 Complete your profile first