Addressable helps you understand who your users are and enrich what you know about them. Our crypto identity graph recognises high-value users and adds context from their first visit. The tag is a super-lightweight snippet that reads one piece of information: the Addressable ID — the lightest footprint for the understanding it delivers.
It turns unrecognized traffic into understood users: you see who your most valuable users are early and enrich your own view of them, without expanding your data exposure.
No. It reads only one piece of information: the Addressable ID, and any optional custom properties you define. It never touches names, emails, or contact details. Minimal data, maximum understanding.
An incredibly short list of just one piece of information: the Addressable ID.
It collects nothing else under the sun, including names, email addresses, contact details, home addresses, national IDs or SSNs, passport or government ID numbers, form submissions, communications, or passwords.
We use pixel tagging, and do it in accordance with the IAB's Transparency and Consent Framework, so it is designed to comply with the consent requirements of the ePrivacy Directive and the UK PECR. We rely on the customer setting up an IAB Consent Management Platform on the customer's website.
It is our proprietary map of on-chain identity — over 130 million wallet owners matched to the devices and behaviour behind them, and what we're best known for. It is built separately and independently from any client engagement. The honest, high-level version, with examples so it isn't a black box:
What the output looks like: when a long-active trader lands on your platform, you can recognise them as a serious, high-intent user from the first visit rather than an anonymous signup.
We'll show you: we're glad to walk your team through worked, real examples of the crypto identity graph under NDA — seeing it is the fastest way to get comfortable.
It collects nothing else under the sun, including names, email addresses, contact details, home addresses, national IDs or SSNs, passport or government ID numbers, form submissions, communications, or passwords.
We can share a client-safe description and our accuracy on request.
For the single piece of data we collect through your website about your users, you are the controller and Addressable is the processor, acting solely on your documented instructions to search for enriched data matching the user's device. Separately, we maintain our crypto identity graph as a controller in our own right — our asset, not shared with you, and outside your project's scope.
When we act as a processor for the single piece of information collected from users through the customer's website, the customer, as the controller, determines the legal basis. When we act as a controller for our crypto identity graph data, we rely on Article 6(1)(f) GDPR - legitimate interests of Addressable, and third parties (customers) in developing business leads.
The enriched data provided to the customer forms a controller-controller transfer.
Addressable is GDPR-aligned and SOC 2 attested, with security measures aligned to Article 32.
Within the EU/EEA, UK, Switzerland, or other adequate jurisdictions.
Any transfer beyond those jurisdictions is covered by Standard Contractual Clauses and the UK IDTA.
A SOC 2 Type II report and GDPR-aligned measures, with a penetration test available on request.
Measures are aligned to Article 32. Access is strictly need-to-know and under confidentiality obligations.
The tag is a static JavaScript file. Whether it is deployed via localization or a self-hosted method depends on your own security and deployment policies — we're happy to work with your team on the right approach.
On termination, your data is deleted or anonymized within 60 days.
Yes — our sub-processors are published in advance, and any change comes with prior notice and a right to object. The current list is available with our DPA.
As your processor, we support you in meeting access, erasure and objection requests under the DPA. As a controller of the identity graph database, we maintain responsibility for data subject requests relating to the graph.
The tag reads the do-not-track signal and relies on user consent under the IAB TCF.
Not necessarily. Where a tag doesn't fit your review sequencing, we can start without tag integration and structure a low-commitment pilot — which is how we've moved forward with regulated platforms on their own legal timelines.
A first evaluation takes about 1–2 weeks and needs only a simple implementation after your approval.
The DPA and published sub-processor list, our Privacy Policy, the SOC 2 Type II report, a penetration-test summary, and a GDPR compliance pack — plus a live walkthrough and worked graph examples under NDA.
Yes — connecting DPOs directly is often the fastest way to finalise and sign the DPA.
