Iriszip carries encrypted bytes between two devices and keeps nothing. This page says what that means when something goes wrong — what we can act on, what we can't, and how to reach us.
Very little, by design. A transfer is encrypted in the sender's browser with a key our servers never hold. We do not have the file, the message, the file name or the last three digits of the code. What exists on our side, in memory and only while a session is live, is the six routing digits of the code and the network addresses of the two connections. Nothing is written to disk, so there is no history to look up once a session ends. There are no accounts, so there is no user to identify.
If you believe Iriszip is being used to hurt someone — to spread malware, to harass, to distribute material that exploits children, or to share something that is yours without permission — email [email protected] with the pairing code or link and the time you saw it. A person reads every report and answers within three business days. Where a code is still live we can end it; where a network address is flooding the service we can block it. Because we cannot see content, we cannot confirm what a code was used for, and we cannot remove anything after the fact — there is nothing on our side to remove.
If your report concerns child sexual abuse material, please also report it directly to the hotline in your country; they can act on the material itself, which we cannot. We pass what a reporter gives us on to the relevant authority.
We hold no files, no messages, no account records and no logs of network addresses. A transfer exists only in the memory of two browsers and, for a few minutes, in ours. A valid order can require us to end a pairing code or block a network address from that moment on; it cannot obtain the content or the history of a transfer, because neither exists on our side. We respond to requests that are valid where we operate, we ask for the legal basis of every request, and we say no to anything broader than the law requires. Send requests to [email protected].
Since Iriszip went live we have received no requests from any authority. We update this line at least once a year, with the number of requests received and what we were able to provide.
A vulnerability in Iriszip itself is a different matter and has its own channel: see how to report a security flaw.
Contact: [email protected] · Last updated 26 August 2026
© 2026 Iriszip Open Source