Privacy Policy

Privacy at a glance

• Anonymous core account: You can create and use a Z.ID without providing a name, email address, telephone number, postal address or password. IDZ does not link a Z.ID to a real-world identity.
• No tracking or profiling: IDZ does not use advertising or analytics trackers, retain IP-address histories, upload address books, or build device-to-account or behavioural profiles.
• Encrypted content stays private: ZCloud files, ZChat messages, indexes, memories and saved MetaCortex results are designed to remain encrypted. IDZ does not hold the private keys needed to read them.
• Private and Boost are visibly different: Private Mode runs locally where supported. Boost sends only the sanitised content you approve for remote processing.
• Technical data is transient: Device, operating-system and connection information may be handled temporarily to provide the Service, but is not retained or associated with your Z.ID by IDZ.
• Limited voluntary exceptions: If you contact IDZ, enter into a business relationship or use a payment provider, the information you choose to provide is handled only for that purpose.

1. Who is responsible for information?

For the anonymous core service, IDZ does not maintain an identity profile for an individual account. Where IDZ receives personal information because you voluntarily contact us, enter into a business or billing relationship, or submit information for support, IDZ is responsible for that information as controller under applicable law. For Teams or other business workspaces, the organisation that provides or administers the workspace may be the controller of information relating to its members, and IDZ may act as its processor. A separate business agreement or data processing addendum may apply. IDZ remains responsible for any business contact, billing, legal or support information it receives for its own purposes.

2. Information IDZ handles

IDZ distinguishes between: (a) encrypted or opaque service information that IDZ cannot use to identify you in the real world; (b) information handled transiently to deliver a feature but not retained or associated with your Z.ID; and (c) information you voluntarily provide outside the anonymous core account, such as a support request or business enquiry.

• Core account and cryptographic state: Your Z.ID, public keys, encrypted account record, plan and entitlement flags, settings and quota counters. IDZ does not require or retain conventional personal identifiers for the core account, does not link the Z.ID to a real-world identity, and does not receive your private Master Key or private encryption seeds.
• Optional aliases: An email address or telephone number may be processed only to verify the alias and create the privacy-preserving lookup needed for matching. IDZ does not retain the raw alias in readable form, cannot use it to contact you, and does not treat it as an account-recovery method.
• Contact matching: If you allow contact access, matching is performed on the device or through temporary privacy-preserving processing. IDZ does not upload or retain your address book and does not use contact data for advertising.
• Encrypted User Content: Files, folders, messages, chats, notes, artifacts, saved MetaCortex outputs, indexes, memories and receipts are stored or synchronised as encrypted content. IDZ does not possess the keys needed to read them.
• Minimal service state: Opaque object and source identifiers, file type and size, timestamps, delivery or sharing state, quota counters, workspace identifiers and cryptographic hashes may be retained where required to route, synchronise and administer the Service. IDZ does not combine this state with a real-world identity or use it for behavioural profiling.
• MetaCortex requests: Private Mode remains on the device. For Boost or web assistance, only the sanitised content or query approved by the user is relayed externally. IDZ does not retain readable prompts, source content or outputs in its backend; saved results and receipts remain encrypted.
• Transient device and connection information: Device type, operating-system version, app version and connection data may be processed temporarily to determine compatibility, route traffic or complete a request. IDZ does not retain this information or associate it with a Z.ID. Diagnostics are received only when you choose to submit them.
• Purchases and subscriptions: Apple, Stripe or another authorised payment provider processes payment and identity information under its own privacy terms. IDZ receives only the product, entitlement, status and transaction reference needed to administer access, and does not receive complete card details.
• Support, sales and business communications: If you voluntarily contact IDZ, we receive the contact details and information you provide. We use them only to respond, administer the relationship or meet legal obligations, and do not link them to a Z.ID unless you ask us to or this is necessary to address the matter.
• Teams and business administration: Organisation name, roles, seat allocation, policy settings, pooled usage and audit events may be handled to administer a business workspace. Workspace content remains encrypted. Any named business or billing contacts are processed only where the organisation chooses to provide them.

3. How information reaches the Services

• From your device when it creates cryptographic identifiers, encrypts and synchronises content, applies settings, delivers messages or creates receipts. The readable content and private keys remain under user control.
• Through temporary processing when you use optional features such as alias verification, contact matching, device compatibility checks, Boost or web assistance. Except where this Policy states otherwise, IDZ does not retain that transient information or associate it with your Z.ID.
• From payment providers and app stores when they confirm a purchase, renewal, cancellation, refund or entitlement. IDZ receives only the information needed to activate and administer the relevant plan.
• Directly from you if you choose to contact IDZ, request support, submit feedback, make a sales enquiry or provide business or billing information.
• From an organisation administrator where they invite you to or administer a Teams or business workspace.

4. How and why information is used

Where information handled by IDZ is personal data under applicable law, IDZ uses it only for the purposes and lawful bases described above. IDZ does not use encrypted User Content for advertising, profiling or training a general-purpose IDZ model, and does not use personal information to make solely automated decisions that produce legal or similarly significant effects. MetaCortex outputs are tools for your review and do not make binding decisions on behalf of IDZ.

• Provide the anonymous account and operate the Services: Performance of our contract with you, or steps taken at your request before entering into a contract.
• Store, synchronise, deliver and share encrypted content: Performance of our contract and your instructions. IDZ cannot read the protected content.
• Provide optional alias verification and contact matching: Performance of the requested feature and, where required, your consent or device permission.
• Provide MetaCortex Private Mode, Boost, web assistance, indexing, memory, citations and receipts: Performance of our contract and your feature selections, approvals and instructions.
• Administer purchases, subscriptions and entitlements: Performance of our contract and compliance with tax, accounting and consumer-law obligations.
• Respond to support, sales, complaints and business communications: Taking steps at your request, performance of a contract, compliance with legal obligations and our legitimate interest in responding and administering the relationship.
• Maintain security, compatibility and service availability: Our legitimate interest in operating a secure and reliable service, using transient or non-identifying technical information wherever possible.
• Comply with law and protect legal rights: Compliance with legal obligations and our legitimate interest in establishing, exercising or defending legal claims.
• Send marketing communications: Only where you separately opt in or another lawful basis permits it. IDZ does not use encrypted User Content or core account activity for marketing.

5. Encryption and what IDZ can see

ZCloud files and ZChat messages are designed to be encrypted before leaving your device. IDZ stores ciphertext and does not hold the private keys required to decrypt it. Client-side indexes, MetaCortex memories, saved outputs and receipts are also designed to remain encrypted where they are synchronised through IDZ. IDZ does not maintain a real-world identity profile for a Z.ID and does not retain IP-address histories, address books, readable aliases, advertising identifiers or device-to-account analytics profiles. Limited technical information may pass through IDZ or its infrastructure providers temporarily to establish a connection, determine compatibility, route a request or deliver the Service, but IDZ does not retain it or associate it with a Z.ID unless you deliberately submit it as part of a support or diagnostic report. Recipients you choose, people with access to your devices or keys, and anyone who receives a public or private share may be able to access the content you make available. Because IDZ does not possess your private keys, it generally cannot recover lost keys or restore encrypted content if every valid recovery method is lost. Keep your Master Key and recovery material secure.

6. MetaCortex Private Mode

Private Mode is available only on supported desktop devices. The selected local model and relevant source content are processed on the device. MetaCortex does not send the content of a Private Mode request to an external AI model. Private Mode may still use encrypted IDZ synchronisation to access sources, save results or keep a conversation available across devices. If a request requires Boost or web assistance, MetaCortex does not silently cross that privacy boundary; it follows the consent and policy controls described below.

7. MetaCortex Boost and sanitisation

Boost uses remote computing and an approved cloud model to provide more capable processing. If a Boost request needs context from files, chats or other User Content, the app extracts the relevant text and replaces detected personal or sensitive details with placeholders before external processing. Depending on your settings, MetaCortex shows a summary or detailed text preview of the sanitised prompt and context before it is sent. You may approve one request or, where available, approve Boost for a thread. MetaCortex may ask again if the sources or shared data change materially. Sanitisation reduces disclosure risk but is not guaranteed to detect or remove every personal, confidential or sensitive detail. You are responsible for reviewing the preview and deciding whether to approve it. If you approve Boost, IDZ temporarily relays the approved sanitised content solely to complete that request. IDZ does not retain the readable prompt, source content or model response in its backend; any result you choose to save is stored in encrypted form. At the effective date, IDZ routes Boost requests through IDZ-controlled backend services hosted on Amazon Web Services, including Amazon Bedrock. Model technology may be supplied through Amazon Bedrock by providers such as Anthropic or Amazon. The exact model or route may be shown in a MetaCortex receipt. IDZ may change a provider for availability, performance, safety, legal or product reasons and will provide notice where a change is material. IDZ does not use files, chats, prompts or outputs to train a general-purpose IDZ model. External providers process approved content under their applicable service terms and retention configuration. IDZ seeks to use configurations that minimise or eliminate durable retention where available, but provider-specific security or abuse-prevention handling may apply and can change over time.

8. Web-assisted queries

When you request current external information or approve web assistance, MetaCortex may send a sanitised search query through IDZ-controlled services to an approved search provider. IDZ does not attach your name, contact details or an identity profile to the query, and does not retain the readable query after the request is completed. At the effective date, web-assisted queries may use Amazon Web Services and DuckDuckGo. Opening a web result takes you to an external website governed by that site’s own privacy policy and technologies. IDZ does not control the external site or the information it collects.

9. Indexing, OCR and memory

To provide encrypted search and MetaCortex retrieval, the apps may create indexes or text chunks from supported files and chats on your device. Where synchronised, those indexes are stored in encrypted form and are not readable by IDZ. If OCR or transcription is used, the extracted text may contain recognition errors. The interface will identify where content was extracted from a scan, image, audio or video where relevant. If memory is enabled, MetaCortex may retain selected useful details across sessions for the period you choose or that your plan or organisation permits. Memory is separate from chat history and is stored under the same encrypted, user-controlled model. Where available, you can view, add, edit, delete or exclude memories and sources, or turn memory off. Turning memory off does not automatically delete existing memories unless you choose to clear them.

10. Sharing and public links

You control who you share content with and the permissions you select. When you create a public link, anyone who obtains that link may be able to access the shared content in accordance with the selected permissions. IDZ cannot control copies made outside the Services. If you share content with another IDZ user, the recipient may retain access or a copy according to the permissions and product behaviour shown at the time. Deleting your account or the original item does not necessarily delete copies already downloaded, exported or retained by recipients.

11. Service providers and disclosures

IDZ does not sell personal information, build advertising profiles or disclose User Content for advertising. Because IDZ does not retain a real-world identity profile or possess the keys to encrypted User Content, it cannot disclose information it does not hold or decrypt. Limited information may nevertheless be handled by the following categories of recipient when required to provide a feature: IDZ does not disclose information to data brokers and does not use encrypted User Content, sanitised Boost content or web queries for targeted advertising.

• Cloud and infrastructure providers may transmit or store encrypted content, opaque service records and user-approved sanitised Boost or web-query content.
• AI model and web-search providers process only the sanitised content or query approved for the relevant Boost or web-assisted request.
• Payment processors and app stores, including Apple and Stripe where applicable, process purchases, subscriptions and refunds. IDZ receives only the entitlement and transaction information needed to administer the plan and does not receive complete card details.
• Operating-system and platform providers may process information for app distribution, purchases, notifications and device permissions under their own privacy terms.
• Professional advisers, auditors, insurers and contractors may receive business, legal, billing or support information that IDZ actually holds, subject to confidentiality and data-protection obligations. They are not given decryption keys for User Content.
• Public authorities, regulators or courts may receive information that IDZ is legally required and technically able to provide. IDZ cannot provide plaintext encrypted content where it does not possess the keys.
• A buyer, investor or successor may receive limited corporate, contractual or operational information in connection with a proposed or completed financing, reorganisation or sale, subject to appropriate confidentiality and legal safeguards.

12. Current core service providers

This list may change as the Services evolve. We will update this Policy or provide another clear notice before a material new use of information begins.

• Amazon Web Services: Cloud hosting, encrypted storage, compute, security, AWS Lambda and Amazon Bedrock. AWS may process ciphertext, opaque service state and user-approved sanitised Boost or web-query content, depending on the feature used.
• Foundation models accessed through Amazon Bedrock: Generation of Boost responses from the sanitised content approved by the user. Models may include technology supplied by Anthropic or Amazon. IDZ does not send a name, contact details or an identity profile with the request.
• DuckDuckGo or another disclosed search provider: Processing a sanitised search query for web-assisted results. IDZ does not attach a real-world identity profile to the query.
• Apple and other app-store/platform providers: App distribution, in-app purchases, entitlement validation, refunds, notifications and platform services. These providers act under their own privacy policies.
• Stripe or another authorised payment provider: Direct subscription and payment processing, fraud prevention, invoices, refunds and chargebacks. IDZ does not receive complete card details.

13. International processing

Encrypted content, opaque service information, user-approved sanitised Boost or web-query content, and information voluntarily supplied for payments, support or business communications may be processed outside the United Kingdom, including in the European Economic Area and the United States, depending on the provider, region and platform used. Where information is personal data under applicable law and is transferred to a country not covered by UK adequacy regulations, IDZ uses an appropriate safeguard where required, such as the UK International Data Transfer Agreement, the UK Addendum to the EU Standard Contractual Clauses or another lawful mechanism, together with any required transfer assessment.

14. Retention

IDZ retains only the encrypted, opaque or voluntarily supplied information needed for the relevant purpose. The core service does not retain conventional personal identifiers or build an identity history for a Z.ID. When encrypted content or an account is deleted, encrypted copies may remain temporarily in backup or disaster-recovery systems until overwritten in the ordinary course. Such copies are restricted to recovery and security purposes and remain inaccessible without the relevant user-held keys.

• Encrypted User Content: Retained as ciphertext until you delete it, close the account, or the account is deleted under the inactivity policy, subject to encrypted backup and synchronisation cycles. Content copied or retained by a recipient remains under that recipient’s control.
• Free inactive accounts: A Free account may be permanently deleted after 365 consecutive days without login, following any notice required by the Services or law.
• Raw aliases and address-book data: Not retained by IDZ. Any privacy-preserving lookup representation used for matching is not readable as the original email address or telephone number.
• Device, operating-system and connection information: Processed transiently and not retained or linked to a Z.ID by IDZ. Optional diagnostics are retained only for the period needed to investigate the submitted issue, then deleted unless a legal need requires longer.
• Boost and web-processing content: Not retained by IDZ in readable form after the request is completed. Provider-specific security or abuse-prevention handling may apply under the selected model and retention configuration.
• Indexes, memories and receipts: Stored locally or in encrypted IDZ storage according to the available feature, plan and organisation policy. IDZ cannot read them without the user-held keys.
• Subscription and transaction state: Opaque entitlement and transaction references are retained for the period needed to administer access and meet legal or accounting obligations. Full payment details remain with the payment provider.
• Support, sales and business communications: Retained only for as long as needed to answer the request, administer the relationship or meet a legal requirement, and then deleted or anonymised.

15. Your choices and controls

• Use the core IDZ account without providing a name, email address, telephone number, postal address or password.
• Choose whether to add an optional alias or allow contact matching; raw aliases and address-book data are not retained by IDZ.
• Grant or withdraw device permissions, such as contacts, files, photos, microphone or notifications, through your operating-system settings.
• Choose Private Mode where supported, review Boost previews, approve Boost once or for a thread, reject a request, or change Boost consent preferences.
• Enable, disable, clear and manage MetaCortex memory where available.
• Choose recipients, link settings and sharing permissions.
• Cancel subscriptions and manage app-store purchases through the applicable billing channel.
• Delete content or request account deletion through the Services, subject to technical, recipient and legal limitations.

16. Your data-protection rights

Depending on where you live and the circumstances, you may have rights to access personal information, correct inaccurate information, request deletion, restrict processing, receive portable information, object to processing, withdraw consent and complain to a regulator. IDZ cannot normally locate an anonymous core account from a name, email address or telephone number because it does not maintain that mapping. To exercise a right relating to an IDZ account, you may need to prove control of the relevant Z.ID or device. IDZ cannot search, decrypt or provide plaintext copies of User Content where it does not possess the necessary keys. Rights relating to information voluntarily supplied for support, sales or billing can be exercised by contacting us using the details below. We will respond within the period required by applicable law. We may ask for clarification, pause the response period where the law permits, or refuse a request where an exemption applies, the request is manifestly unfounded or excessive, or we cannot verify the requester.

17. Account and data deletion

You may delete individual content and, where available, initiate account deletion through the Services. Account deletion removes or schedules deletion of the encrypted and opaque records controlled by that account, subject to backup cycles and copies retained by recipients. Because IDZ does not maintain an identity mapping, deleting the app alone does not identify or delete the corresponding account. Deleting the app from a device does not cancel a subscription. App-store subscriptions must be cancelled through the relevant store; direct subscriptions must be cancelled through the IDZ billing process.

18. Security

IDZ uses technical and organisational measures designed to protect the Services, including client-side encryption for User Content, encryption in transit, access controls, least-privilege permissions, secure development practices and independent security testing. IDZ does not rely on behavioural tracking or identity profiling to secure the core account. No service can guarantee absolute security. You are responsible for protecting devices, credentials, Master Keys and recovery material, installing security updates and reviewing sharing and Boost approvals. If you believe your account or information is at risk, contact us promptly.

19. Children

The Services are not directed to children. You must be at least 18 years old, or the age of legal majority where you live, to create an account or purchase a subscription unless a lawful organisational arrangement expressly permits otherwise. If we learn that personal information was voluntarily provided by a child contrary to this Policy, we will take appropriate steps to delete or restrict it.

20. Privacy complaints

You may raise a privacy complaint by emailing [email protected] with the subject line "Privacy complaint". We will use the information you provide only to investigate and respond to the complaint and will not link it to a Z.ID unless you ask us to do so or this is necessary to address the issue. You also have the right to complain to the UK Information Commissioner’s Office. Information is available at https://ico.org.uk/. If you live outside the UK, you may also have the right to contact your local data-protection authority.

21. Changes to this Policy

We may update this Policy to reflect changes in the Services, providers, technology, law or business practices. We will change the effective or last-updated date and, where required, provide prominent notice or obtain consent before a material change takes effect.

22. Contact us

• IDZ LTD
• Company number: 10737703
• Registered office: 128 City Road, London, United Kingdom, EC1V 2NX
• Email: [email protected]
• Website: https://idz.com/