Privacy Policy

Draft outline

Draft only — not final legal text. This is a plain summary of how ropeus2 is built to handle data. The final, binding Privacy Policy will be prepared with a lawyer before launch. Nothing here is legal advice.

The one fact that matters most

ropeus2 is end-to-end encrypted. The operator cannot read your messages, cannot view your photos or videos, and cannot listen to or watch your calls. Content is encrypted on one device and decrypted only on the other end's device.

What is collected — and what is not

Collected, kept to the minimum needed to run the service:

Not collected:

The waitlist

If you enter your email in the waitlist form, we collect only that email address, and only to send you a single notification when ropeus2 launches on iOS. We don't use it for marketing, we don't sell or share it, and there is no tracking attached to it.

Metadata

Some metadata is unavoidable to deliver messages and calls — for example, that two paired devices communicate, and the timing and size of what passes between them. We keep this to the minimum and will name the exact categories and retention in the final policy. We will not claim metadata does not exist.

No sale of data, no ad tracking

Personal data is not sold, and the app does not track you across other apps or websites for advertising.

Your rights, deletion, and recovery

You can unpair at any time, which deletes the server-side data for that rope. Content already on the other person's own device is on that device — we can't reach into it. Because your keys live only on your device, there is no password reset: if you lose your phone and passphrase, only the other end approving your new device can restore access.

Contact

A working privacy and support contact will be published here before launch.