Real People,
Zero Data
Prove that the users on your site are real, verified people — without ever seeing their identity. The Turkish ID number never reaches your systems.
What's in it for you?
Designed for forums, polls/voting sites, dating and social platforms, communities and marketplaces. No complex integration, heavy infrastructure or legal team required.
Bot / fake-account prevention
Behind every account there's a real person verified via NFC with proven liveness. Mass fake sign-ups end.
"Verified Human" badge
Put a trust badge on profiles. Your users know who they're talking to or dealing with.
Age / identity verification
You get an answer like "18+" — you don't even need to store a date of birth.
Dating / social safety
The strongest barrier against catfishing and fake profiles: real face + real identity + liveness.
Duplicate-account detection
When the same person returns you get a stable pseudonymous code — you can say "same person" without seeing their identity.
Two big differences
Integration in minutes — one script on your page
You add a single script line and a box to your site; the widget draws the QR code, sends the user to their phone, and returns the result to you.
<script src="https://cdn.verifyblind.com/sdk/v1.0.0/verifyblind.js"
integrity="sha384-TRoHlSq3GSFXepiilMFxyyVsHt23aFYuk03hDTFZGMCYSU6qQckiEFjVk8Nssixe"
crossorigin="anonymous"></script>
<div id="verifyblind-container"></div>
<script>
window.VerifyBlind.init({
generateUrl: '/generate-nonce',
payload: { validations: { age: '18+' } },
containerId: 'verifyblind-container',
onSuccess: (data) => { /* verified */ },
});
</script>The only extra requirement: a tiny ~10-line "nonce" endpoint on your server so your API key never appears in the browser. We give you copy-paste examples (PHP, Node.js, .NET). The server-side webhook is optional — it works fully with just the widget too.
You never see the user's identity → your KVKK surface shrinks
The Turkish ID number is processed only in end-to-end encrypted form, inside an isolated secure environment (AWS Nitro Enclave); it never appears in the clear on the network nor is stored anywhere (including by VerifyBlind).
You only get the answer to the question you asked (e.g. age: true, a pseudonymous user code).
Because you never process/store the most sensitive personal data (ID number, ID photo), the data-processing burden and risk surface you carry under KVKK shrink significantly.
Legal note: VerifyBlind is designed to reduce your KVKK burden by keeping the most sensitive data away from you; however, the final compliance assessment depends on your processing purpose and is not a substitute for legal advice.
Two steps for the user
First time — one-time setup
The user installs the VerifyBlind app, taps their ID card once via NFC and does a short liveness (face) check. This step happens only once per user.
Every later verification — one tap
The user scans the QR on your site with their app and completes it with a single approval; no need to re-scan their ID or face.
You — a result in seconds
You only get the result: verified / age 18+ and a stable pseudonymous code per person — you match "same person" against your own records using that code.
A win for your users too
- They don't have to "hand over" their identity details to a forum/site they don't know.
- Because their ID numbers and ID photos don't pile up at third parties, the fear of data breaches drops.
- The "verified" badge increases trust and engagement on your platform.
Our pilot offer: Free
We want to see VerifyBlind in the field, and you want to try it without taking on risk.
- Ready copy-paste integration code (PHP, Node.js, .NET) and documentation
- Free verification quota
- Direct email support for your questions
One script tag plus a small server endpoint, zero identity data, real users. Let's start the pilot together.
Questions? support@verifyblind.com