Privacy Policy

Effective Date: 13 January 2026 Version: 1.0 Jurisdiction: Switzerland

1. Introduction and Commitment

Convro is built on a fundamental principle: privacy is a human right, not a feature. This Privacy Policy explains how we protect that right through our zero-knowledge architecture, what minimal data we process to operate the Service, and what rights you have regarding your information.

Unlike traditional messaging services that collect extensive user data and metadata, Convro is architecturally designed to know as little as possible about you. We cannot read your messages. We cannot see who you communicate with. We cannot track when you are online. This is not a policy choice—it is a technical reality enforced by cryptography.

This Privacy Policy should be read in conjunction with our Terms of Service. By using Convro, you acknowledge that you have read and understood both documents.

Our Privacy Commitment We believe that private communication is essential to human dignity and freedom. Convro is designed so that even we—the operators—cannot access your private conversations. Your secrets remain yours.

2. Data Controller

The data controller responsible for processing activities described in this Privacy Policy is:

Convro Ltd Registered in England and Wales
Companies House Registration Number: [To be inserted upon registration]

Data Processing Location: Switzerland
Privacy Inquiries: KillTheBug@convro.eu

While Convro Ltd is incorporated in the United Kingdom, all technical infrastructure for data processing is located exclusively within the Swiss Confederation. This structure ensures that any data processing benefits from Switzerland's robust constitutional and statutory privacy protections.

4. Data We Collect

Convro operates on a principle of radical data minimization. We collect only what is technically essential to route encrypted messages between users. The following table details the limited data elements we process:

Data Element Purpose Retention Accessible to Convro
Convro Virtual Number Unique account identifier for message routing Until account deletion Yes (identifier only)
Public Cryptographic Keys Enable end-to-end encryption key exchange Until account deletion Yes (public keys only)
Device ID (derived) SHA-256 hash of Ed25519 public key for device identification Until device deregistration Yes (hash only)
Encrypted Message Payloads Temporary storage for message delivery Until delivered (max 30 days) No (encrypted)
Encrypted Media Files Temporary storage for media delivery Until delivered (max 30 days) No (encrypted)
Recipient Virtual Number (per message) Message routing to correct recipient Transient (routing only) Yes (for routing)
Rounded Timestamp Message ordering (5-minute precision with jitter) Transient Yes (imprecise)

4.1 Account Information

When you create a Convro account, the following occurs entirely on your device:

Only your public keys and derived Device ID are transmitted to our servers. Your private keys never leave your device under any circumstances.

4.2 Convro Virtual Number

Upon successful registration, our server assigns you a permanent Convro Virtual Number in the format +99 XXX XXX. This number:

5. Data We Do Not Collect

The following data is explicitly never collected, stored, or processed by Convro. This is not merely a policy—our technical architecture makes collection of this data impossible.

🛡️ Never Collected

  • Message content (end-to-end encrypted)
  • Email addresses
  • Phone numbers
  • Real names or identity documents
  • IP addresses
  • Physical location or GPS data
  • Device identifiers (IMEI, UDID, etc.)
  • Contact lists or address books
  • Call logs or communication history
  • Sender identity (Sealed Sender)
  • Social graph (who talks to whom)
  • Precise message timestamps
  • Message sizes (64KB padding)
  • Online/offline status
  • Typing indicators
  • Read receipts
  • Usage analytics or telemetry
  • Advertising identifiers
  • Biometric data
  • Financial information

📋 Minimal Processing

  • Convro Virtual Number (random ID)
  • Public encryption keys
  • Device ID (cryptographic hash)
  • Encrypted payloads (transient)
  • Recipient ID (for routing)
  • Rounded timestamps (5-min precision)

5.1 No IP Address Logging

Convro does not log, store, or process IP addresses of users connecting to our service. Our server infrastructure is configured to discard connection metadata immediately after processing. We cannot determine your physical location, internet service provider, or network identity.

5.2 No Social Graph

Due to our implementation of Sealed Sender technology, our servers cannot determine who is communicating with whom. We see only the recipient of each message (necessary for routing); the sender's identity is cryptographically hidden and revealed only to the recipient upon decryption.

5.3 No Analytics or Telemetry

Convro does not implement any analytics, telemetry, crash reporting, or usage tracking systems. We do not use third-party analytics services such as Google Analytics, Firebase, Mixpanel, or similar tools. We have no visibility into how you use the application.

6. Purposes of Processing

The minimal data we process is used exclusively for the following purposes:

6.1 Service Provision

Processing of Convro Virtual Numbers, public keys, and encrypted payloads is necessary to provide the core messaging functionality—routing encrypted messages from senders to recipients.

6.2 End-to-End Encryption

Public cryptographic keys are stored to enable the key exchange necessary for end-to-end encryption. When you send a message, your device retrieves the recipient's public keys to encrypt the message such that only the recipient can decrypt it.

6.3 Multi-Device Support

Device IDs and associated public keys are stored to support operation across multiple devices registered to the same account. Each device maintains independent keys.

6.4 Message Delivery

Encrypted message payloads and media files are temporarily stored on our servers until the recipient's device retrieves them. This temporary storage is essential for asynchronous messaging when the recipient is offline.

We do not process any data for: advertising, marketing, profiling, behavioral analysis, sale to third parties, or any purpose other than direct service provision.

8. Encryption and Privacy Architecture

Convro implements multiple layers of cryptographic protection through the proprietary Convro6Protocol (C6P). This section explains how these protections work to ensure your privacy.

8.1 End-to-End Encryption

All messages, media, and files transmitted through Convro are end-to-end encrypted. This means:

8.2 Cryptographic Primitives

The Convro6Protocol employs the following cryptographic standards:

Function Algorithm Standard
Key Derivation HKDF-SHA256 RFC 5869
Authenticated Encryption ChaCha20-Poly1305 / XChaCha20-Poly1305 RFC 8439
Digital Signatures Ed25519 (EdDSA) RFC 8032
Key Agreement X25519 (ECDH) RFC 7748
Session Binding 63-byte AAD Proprietary
Password Hashing Argon2id RFC 9106

8.3 Sealed Sender

Convro implements Sealed Sender technology, which cryptographically hides the identity of message senders from our servers. When you send a message:

8.4 Open Source Verification

The Convro6Protocol specification and client applications (iOS and Android) are open source. This enables independent security researchers, cryptographers, and the public to verify our privacy claims. We invite scrutiny because we have nothing to hide.

9. Metadata Protection

While many services claim end-to-end encryption for message content, they often still collect extensive metadata—data about your communications that can be just as revealing as the content itself. Convro implements comprehensive metadata protection.

9.1 Metadata Comparison

Metadata Type Typical Messengers Convro
Sender Identity Visible to server Hidden (Sealed Sender)
Recipient Identity Visible to server Visible (for routing)
Message Content Encrypted Encrypted (C6P)
Message Size Variable (analyzable) Fixed 64KB (padded)
Precise Timestamp Exact time recorded 5-minute precision + jitter
Social Graph Full exposure Recipient-only
IP Address Logged Not logged
Online Status Tracked Not tracked

9.2 Message Padding

All messages transmitted through Convro are padded to a fixed size of 64 kilobytes, regardless of actual content length. This prevents traffic analysis attacks that could otherwise infer information about your communications based on message sizes (e.g., distinguishing a short text from a long document).

9.3 Timestamp Obfuscation

Message timestamps are deliberately imprecise:

9.4 No Timing Side Channels

Convro does not expose read receipts, typing indicators, or online/offline status. These features, while convenient, create significant privacy leaks that we have chosen to eliminate entirely.

10. Data Retention

Convro follows a strict data minimization approach to retention:

10.1 Account Data

Your Convro Virtual Number and public cryptographic keys are retained for as long as your account exists. Upon account deletion, this data is permanently erased from our servers.

10.2 Message Data

Encrypted messages and media files are stored on our servers only until they are delivered to the recipient's device. Once delivery is confirmed, the encrypted payload is deleted from our servers. Messages to offline recipients are retained for a maximum of 30 days, after which they are automatically deleted if undelivered.

10.3 No Message Archives

Convro does not maintain any archives, backups, or historical records of messages. Once a message is delivered or expires, it exists only on the devices of the sender and recipient. We have no ability to recover deleted or expired messages.

10.4 Server Logs

Our servers do not maintain access logs, connection logs, or any other logs that could identify users or their activities. This is a deliberate architectural decision—logs that don't exist cannot be subpoenaed.

Retention Summary
  • Account identifiers: Until account deletion
  • Public keys: Until account deletion
  • Encrypted messages: Until delivery or 30 days maximum
  • IP addresses: Not retained (0 days)
  • Usage logs: Not retained (0 days)

11. Data Location and International Transfers

11.1 Swiss Infrastructure

All Convro servers and data processing infrastructure are located exclusively within the Swiss Confederation. Switzerland was chosen for its:

11.2 No International Transfers

Your data is not transferred to, processed in, or accessible from any country outside of Switzerland. We do not use cloud providers, content delivery networks, or other services that would result in your data leaving Swiss jurisdiction.

11.3 Corporate Structure

While Convro Ltd is incorporated in the United Kingdom for administrative purposes, this corporate structure does not affect the location of data processing. UK authorities have no direct access to data stored on Swiss servers, and any requests for data would be subject to the mutual legal assistance treaty (MLAT) process and Swiss legal standards.

12. Third-Party Data Sharing

12.1 No Commercial Data Sharing

Convro does not sell, rent, lease, trade, or otherwise share any user data with third parties for commercial purposes. We do not:

12.2 No Third-Party Services

Convro does not integrate with or send data to third-party services such as:

12.3 Infrastructure Providers

Our Swiss server infrastructure is operated on dedicated hardware. We do not use shared cloud platforms where third parties could potentially access server data. All infrastructure administration is performed directly by Convro personnel.

13. Law Enforcement and Legal Requests

13.1 Our Response to Legal Requests

Convro will comply with valid legal requests from Swiss authorities issued pursuant to Swiss law. However, due to our zero-knowledge architecture, we can provide only extremely limited information in response to any request.

13.2 What We Can Provide

In response to a valid Swiss legal process, we may be compelled to provide:

13.3 What We Cannot Provide

Due to our technical architecture, we cannot provide the following even if legally compelled:

13.4 Transparency

Where legally permitted, Convro will notify users if their account data has been requested by legal authorities, allowing them to seek legal counsel or take other protective measures.

13.5 No Backdoors

Convro does not implement, and will never implement, encryption backdoors, key escrow systems, or any mechanism that would allow us or any third party to access encrypted communications. We will resist any legal or governmental pressure to compromise the security of our encryption.

14. Your Privacy Rights

Under the Swiss Federal Act on Data Protection (DSG) and, where applicable, the EU General Data Protection Regulation (GDPR), you have certain rights regarding your personal data. However, due to our zero-knowledge architecture, the practical exercise of some rights is limited by the nature of our service.

14.1 Right of Access (Article 25 DSG)

You have the right to request confirmation of whether we process your personal data and to receive a copy of such data. In practice, we can confirm the existence of your account and provide your Convro Virtual Number and public keys. We cannot provide message content, metadata, or communication history because we do not have access to this information.

14.2 Right to Rectification (Article 6 DSG)

You have the right to request correction of inaccurate personal data. Since we do not collect personal information such as names, addresses, or contact details, there is typically nothing to correct. Your Convro Virtual Number is system-generated and cannot be changed.

14.3 Right to Erasure (Article 6 DSG)

You have the right to request deletion of your personal data. You can exercise this right immediately and completely through the Critical Data Wipe function in the application (see Section 15). This deletion is irreversible and comprehensive.

14.4 Right to Data Portability (Article 28 DSG)

You have the right to receive your personal data in a portable format. We can provide your public keys and Convro Virtual Number upon request. Message content cannot be exported from our servers because we do not have access to it—messages exist only in encrypted form on your device.

14.5 Right to Object (Article 30 DSG)

You have the right to object to processing of your personal data. Since our processing is limited to what is technically necessary for service provision, objecting to processing is equivalent to discontinuing use of the service.

14.6 Right to Lodge a Complaint

You have the right to lodge a complaint with a supervisory authority. The competent authority for Convro is:

Federal Data Protection and Information Commissioner (FDPIC)
Eidgenössischer Datenschutz- und Öffentlichkeitsbeauftragter (EDÖB)
Feldeggweg 1, CH-3003 Bern, Switzerland
Website: www.edoeb.admin.ch

14.7 Exercising Your Rights

To exercise any of the above rights, please contact us at KillTheBug@convro.eu. We will respond to valid requests within 30 days. Due to our privacy architecture, we may be unable to verify your identity through traditional means; we may request that you demonstrate control of the Convro account in question through cryptographic proof.

15. Account Deletion

15.1 Standard Deletion

You may delete your Convro account at any time by uninstalling the application. Because we do not retain personal identifiers linking your account to you, and because message history exists only on your device, uninstalling effectively removes your presence from our systems.

15.2 Critical Data Wipe

For situations requiring immediate and comprehensive data destruction, Convro provides a Critical Data Wipe function accessible through application settings. Activation requires biometric confirmation (Face ID, fingerprint, or equivalent). This function immediately and irreversibly:

⚠️ Warning The Critical Data Wipe function is designed for emergency situations. Once activated, your account, messages, and all associated data are permanently and irreversibly destroyed. We cannot recover any data after a Critical Data Wipe. Use this function only when you are certain you want to permanently eliminate all traces of your Convro usage.

15.3 Effect on Sent Messages

When you delete your account, messages you previously sent to other users remain on their devices (encrypted with their keys). We cannot remotely delete messages from recipients' devices. If you require complete message erasure, you should use the disappearing messages feature before sending sensitive content.

16. Cookies and Local Storage

16.1 Mobile Application

The Convro mobile application does not use cookies. The application stores the following data locally on your device:

This local data never leaves your device and is not accessible to Convro.

16.2 Website

The Convro website (convro.eu) uses minimal functional cookies solely to:

We do not use analytics cookies, advertising cookies, or any third-party tracking cookies. No personal data is collected through cookies.

16.3 Cookie Management

You can manage cookies through your browser settings. Blocking all cookies will not affect your use of the Convro mobile application, though some website features may not function correctly.

17. Children's Privacy

17.1 Age Requirement

Convro is not intended for use by individuals under the age of sixteen (16). By using Convro, you represent that you are at least 16 years old.

17.2 No Collection from Children

We do not knowingly collect personal data from children under 16. Due to our privacy architecture, we cannot verify the age of users and do not collect information that would allow us to do so.

17.3 Parental Responsibility

Parents and guardians are responsible for monitoring their children's use of electronic devices and online services. If you believe a child under 16 has created a Convro account, please contact us at KillTheBug@convro.eu.

18. Security Measures

18.1 Technical Security

Convro implements comprehensive technical security measures including:

18.2 Organizational Security

Our organizational security measures include:

18.3 Security Limitations

While we implement strong security measures, no system is perfectly secure. We cannot protect against:

18.4 Reporting Security Issues

If you discover a security vulnerability in Convro, please report it responsibly to KillTheBug@convro.eu with "[SECURITY]" in the subject line. We appreciate security researchers who work with us to protect our users.

19. Changes to This Privacy Policy

19.1 Policy Updates

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or for other operational reasons. When we make changes, we will update the "Effective Date" at the top of this policy.

19.2 Notification of Changes

For material changes that significantly affect how we process your data, we will provide notice through the Convro application or other appropriate means at least fourteen (14) days before the changes take effect.

19.3 Continued Use

Your continued use of Convro after any changes to this Privacy Policy constitutes your acceptance of the updated policy. If you do not agree with changes, you should discontinue use of the service and delete your account.

19.4 Version History

Previous versions of this Privacy Policy may be requested by contacting us at KillTheBug@convro.eu.

20. Contact Information

For any questions, concerns, or requests regarding this Privacy Policy or our privacy practices, please contact:

Convro Ltd - Privacy Inquiries

Email: KillTheBug@convro.eu

For security vulnerabilities, please include "[SECURITY]" in the subject line.
For data protection inquiries, please include "[PRIVACY]" in the subject line.

We aim to respond to all inquiries within 30 days.

If you are not satisfied with our response, you have the right to lodge a complaint with the Swiss Federal Data Protection and Information Commissioner (FDPIC) at the address provided in Section 14.6.

End of Privacy Policy

Last Updated: 13 January 2026 | Version 1.0
© 2026 Convro Ltd. All rights reserved.