Last updated: 24 October 2026
This Privacy Policy describes how SOKEN LTD collects, uses, shares and retains personal data in connection with the SOKEN Contract Review service (the "Service"). It applies to all persons who use the Service or interact with the Connector.
Terms defined in our Terms of Use have the same meaning when used in this Privacy Policy.
For the processing of personal data in connection with other SOKEN LTD services and the soken.dev website generally, please refer to the Privacy Policy published at soken.dev/privacy-policy.html.
1. Data Controller
The data controller for the personal data described in this policy is:
SOKEN LTD
Company number: 15253906 (England and Wales)
Registered office: 86-90 Paul Street, London, EC2A 4NE
Data protection contact: hello@soken.dev
2. Categories of Personal Data
2.1 Review job data
When you use the Service, the following data is transmitted to the Connector as tool arguments from your AI client session:
- The review Target: a deployed contract address and blockchain network, a repository URL and commit, source files provided in the conversation, or an uploaded source archive.
- The requester role you declare (owner, authorised representative, or third-party reviewer of public code).
- Findings, challenge responses, dismissal reasons, and report sections that your AI client session writes and submits as tool arguments.
- Project context documents you supply: URLs to whitepapers, project websites, applications, documentation, terms or privacy pages, or inline text. When you provide a URL, the Connector fetches it in a sandboxed environment (HTTPS only, subject to per-document and per-job size limits).
- Job metadata: timestamps, processing states, build outputs and analysis outputs.
2.2 Network identifiers
For direct connections, the Connector receives the client IP address. It is stored only as a keyed cryptographic hash (HMAC), never in raw form. No personal identifier is derived from it; it is used solely for enforcing usage limits and aggregate product metrics.
For requests relayed through shared AI platform infrastructure, the Connector receives the platform's egress IP address, not your personal IP address. In that case, usage limits are applied per reviewed Target.
2.3 Ownership verification data
If you use the verification mechanism on soken.dev to prove code ownership, we process the blockchain address, the cryptographic signature or memo transaction you submit, and (for repository inputs) the commit reference. Only a SHA-256 hash of the signature is stored.
2.4 Publication consent data
If you consent to publication, we log the party name, the authorising person's name, the consent statement, and the timestamp you provide. This consent record survives deletion of the underlying review job and is retained as a legal record.
2.5 Support and correspondence data
If you contact us by email, we process the information you provide in your correspondence, including your email address, name and message content.
2.6 Data we do not collect
The Service does not read your chat history, conversation memory, session summaries, or other files on your device or in your AI client. Source code is received only as tool arguments that your AI client session transmits at your request. We do not use submitted code or findings for marketing, model training, or benchmarking.
3. Purposes and Lawful Bases
We process personal data for the following purposes, on the lawful bases indicated:
| Purpose | Categories of data processed | Lawful basis (UK GDPR) |
|---|---|---|
| Delivering the review Report you requested | Review job data, network identifiers, job metadata | Performance of a contract (Article 6(1)(b)): processing is necessary to provide the Service you have requested under our Terms of Use |
| Enforcing usage limits and preventing abuse | Hashed network identifiers, job metadata | Legitimate interests (Article 6(1)(f)): maintaining the integrity, security and fair availability of the Service |
| Publishing a Report at your request | Report content, publication consent record | Consent (Article 6(1)(a)): you provide explicit consent through the publication tool |
| Verifying code ownership | Blockchain address, cryptographic proof (stored as hash), repository commit | Legitimate interests (Article 6(1)(f)): ensuring the accuracy of ownership records and enabling access to the full Report |
| Aggregate product analytics | Job metadata, anonymised event logs (no source code, findings or raw IP addresses) | Legitimate interests (Article 6(1)(f)): understanding usage patterns and improving the Service |
| Responding to support, takedown and security reports | Contact information and correspondence you provide | Legitimate interests (Article 6(1)(f)): handling enquiries and fulfilling our obligations |
| Compliance with legal obligations | Consent records, tombstone records (hashes and status only) | Legal obligation (Article 6(1)(c)): retaining records required by applicable law |
Where we rely on legitimate interests, we have carried out a balancing assessment and concluded that our interests are not overridden by your rights and freedoms. You may request further details of this assessment by contacting us.
4. Recipients of Personal Data
In the course of providing the Service, we share limited data with the following categories of third-party recipients. Only data strictly necessary for the stated purpose is shared; your findings and Report text are never transmitted to these recipients.
| Category of recipient | Data shared | Purpose |
|---|---|---|
| Public source-code verification services | Contract address and chain identifier; deployed bytecode hash (where required for source matching) | Retrieving verified source code for the Target |
| Public blockchain nodes and data services | Contract address, read-method calls only (no transactions are signed or sent) | Reading on-chain state, bytecode and account data for the Target |
| Decentralised storage gateways | Content identifiers referenced in contract metadata | Retrieving source code referenced in on-chain metadata |
| Public code repositories you direct us to | Repository URL, commit reference and branch you specify | Cloning the source code you submitted for review |
| External URLs you supply as project context | The URLs you provide (fetched in a sandboxed environment via HTTPS) | Ingesting project documentation at your request |
| Our public report library at soken.dev/audits and its public mirror repository | The Report PDF and associated metadata | Publication, only when you have given explicit consent |
| Infrastructure and hosting providers acting on our instructions | All data processed by the Service (encrypted in transit and at rest) | Hosting, operating and backing up the Service |
We do not sell personal data. We do not share personal data with third parties for their own marketing purposes.
5. International Transfers
All primary processing occurs in the United Kingdom. Encrypted backup copies are stored in the European Economic Area.
When the Connector contacts the third-party services described in section 4 (for example, public blockchain nodes or source-code verification services), limited data (such as contract addresses and chain identifiers) may be transmitted to services located outside the United Kingdom. Where such transfers occur, we rely on appropriate safeguards, including UK adequacy regulations, standard contractual clauses, or equivalent measures recognised under the UK GDPR.
6. Retention
We retain personal data only for as long as necessary to fulfil the purposes for which it was collected, or as required by law. The following table sets out our retention periods by data category:
| Data category | Retention period |
|---|---|
| Incomplete or failed review jobs (including jobs awaiting upload, stuck in processing, or terminated with an error) | 7 days from creation |
| Interactive review jobs awaiting your session | 24 hours from last activity |
| Completed Report (hosted page and PDF) | 30 days from completion; may be extended once to the configured maximum (extension not available for third-party code reviews) |
| Published Report (public report library) | Indefinitely, until removed in accordance with the Report Removal Policy |
| Build and compilation cache (may contain source text) | 30 days |
| Code ownership proofs (stored as cryptographic hashes only) | Lifetime of the associated Report |
| Publication consent records | Retained as a legal record; survives deletion of the review job |
| Job event logs | 13 months (aggregate statistics retained after purge) |
| Report tombstone records (hashes and status only, no content) | Indefinitely for withdrawn Reports; 13 months for all others |
| Administrative audit logs | 12 months |
| Application and infrastructure logs | 14 days |
| Sandbox build output | Lifetime of the review job (limited excerpt retained on build failure) |
| Database backups (point-in-time recovery) | 7 days |
| Encrypted database archives | 35 days |
| Backup copies of Report files | Removed within one hour of Report deletion; fully purged within 7 days |
Automated retention sweeps run daily. When a review job is deleted or expires, its source code, findings, artefacts and Report files are removed. Tombstone records (containing only hashes and the deletion reason, not content) are retained for the periods stated above.
7. Your Rights
Under the UK General Data Protection Regulation (UK GDPR) and, where applicable, the EU General Data Protection Regulation (EU GDPR), you have the following rights in relation to your personal data:
- Access: the right to request a copy of the personal data we hold about you.
- Rectification: the right to request correction of inaccurate or incomplete personal data.
- Erasure: the right to request deletion of your personal data, subject to our legal retention obligations.
- Restriction: the right to request that we restrict the processing of your personal data in certain circumstances.
- Data portability: the right to receive your personal data in a structured, commonly used and machine-readable format.
- Objection: the right to object to processing based on legitimate interests. Where you object, we will cease processing unless we can demonstrate compelling legitimate grounds that override your interests.
- Withdrawal of consent: where processing is based on consent (for example, publication), you have the right to withdraw consent at any time, without affecting the lawfulness of processing carried out before withdrawal.
8. How to Exercise Your Rights
8.1 Deleting your review data
You can delete a review job and all associated data (source code, findings, Report and PDF) at any time using any of the following methods:
- Call the
review_delete_jobtool through your AI client with the job identifier and explicit confirmation. - Email hello@soken.dev with the Report identifier or job identifier.
Deletion removes the source code, findings, hosted Report page and PDF from our servers. Tombstone records (containing only hashes and the deletion reason, not content) are retained for the periods stated in section 6. Publication consent records survive job deletion as they serve as the legal record of consent to publication.
8.2 Removing a Published Report
Deleting a review job does not remove a copy that has already been published. To request removal of a Published Report, please follow the procedure described in our Report Removal Policy.
8.3 Other requests
For all other data subject requests, please contact us at hello@soken.dev. We will respond within one month of receiving your request, as required by applicable law. We may ask you to verify your identity before processing a request.
9. Right to Complain
If you are not satisfied with how we handle your personal data or respond to your request, you have the right to lodge a complaint with the Information Commissioner's Office (ICO):
Information Commissioner's Office
ico.org.uk
Telephone: 0303 123 1113
If you are located in the European Economic Area, you may also lodge a complaint with the supervisory authority in your member state of residence.
10. Cookies
The Connector itself does not set cookies. It operates as an MCP server endpoint and does not serve web pages to end users in the ordinary course of operation.
If you visit pages on soken.dev (such as the hosted Report page, the verification page, or the landing page), those pages are subject to the cookie practices described in the Privacy Policy at soken.dev/privacy-policy.html.
11. Children
The Service is not intended for use by anyone under 18 years of age. We do not knowingly collect personal data from children.
12. Changes to This Policy
We may update this Privacy Policy from time to time. The "Last updated" date at the top of this page indicates when the current version took effect. Material changes will also be noted on the Connector landing page. We encourage you to review this page periodically. Your continued use of the Service after any change constitutes your acceptance of the revised policy.
13. Language
This Privacy Policy is published in English and may be made available in other languages for convenience. In the event of any inconsistency between the English version and a translation, the English version prevails.
14. Contact
For questions about this Privacy Policy or to exercise your data protection rights, please contact us at hello@soken.dev.