|
| 1 | +<!doctype html> |
| 2 | +<html lang="en"> |
| 3 | + <head> |
| 4 | + <title>MiroTalk - Privacy Policy</title> |
| 5 | + |
| 6 | + <meta charset="UTF-8" /> |
| 7 | + <meta http-equiv="X-UA-Compatible" content="IE=edge" /> |
| 8 | + <meta |
| 9 | + name="viewport" |
| 10 | + content="width=device-width, height=device-height, initial-scale=1.0, maximum-scale=1.0, user-scalable=0" |
| 11 | + /> |
| 12 | + <meta |
| 13 | + name="description" |
| 14 | + content="MiroTalk C2C Privacy Policy – learn how we handle your data with minimal collection and end-to-end encryption." |
| 15 | + /> |
| 16 | + |
| 17 | + <link rel="apple-touch-icon" href="../images/favicon.png" /> |
| 18 | + <link rel="icon" type="image/x-icon" href="../images/favicon.ico" /> |
| 19 | + <link rel="stylesheet" href="../css/home.css" /> |
| 20 | + <link rel="stylesheet" href="../css/common.css" /> |
| 21 | + <link rel="stylesheet" href="../css/privacy.css" /> |
| 22 | + |
| 23 | + <script async src="../js/stats.js"></script> |
| 24 | + </head> |
| 25 | + <body> |
| 26 | + <div class="privacy-container"> |
| 27 | + <div class="privacy-header"> |
| 28 | + <div class="privacy-logo"> |
| 29 | + <a href="/"><img src="../images/logo.svg" alt="MiroTalk C2C" /></a> |
| 30 | + </div> |
| 31 | + <h1>Privacy Policy</h1> |
| 32 | + </div> |
| 33 | + |
| 34 | + <div class="privacy-body"> |
| 35 | + <p> |
| 36 | + <strong>Minimal Data Collection</strong><br /> |
| 37 | + We collect only the minimal data required to provide real-time communication functionality in |
| 38 | + <strong>MiroTalk</strong>. |
| 39 | + </p> |
| 40 | + <p> |
| 41 | + <strong>Signaling Data</strong><br /> |
| 42 | + <strong>MiroTalk</strong> is a real-time peer-to-peer WebRTC application. Establishing a connection |
| 43 | + requires temporary signaling data such as |
| 44 | + <a |
| 45 | + href="https://developer.mozilla.org/en-US/docs/Web/API/RTCIceCandidate" |
| 46 | + target="_blank" |
| 47 | + rel="noopener noreferrer" |
| 48 | + >RTCICECandidates</a |
| 49 | + > |
| 50 | + and |
| 51 | + <a |
| 52 | + href="https://developer.mozilla.org/en-US/docs/Web/API/RTCSessionDescription" |
| 53 | + target="_blank" |
| 54 | + rel="noopener noreferrer" |
| 55 | + >RTCSessionDescription</a |
| 56 | + >. This data is used only to negotiate the connection between peers. |
| 57 | + </p> |
| 58 | + <p> |
| 59 | + <strong>No Persistent Storage</strong><br /> |
| 60 | + This signaling data is not stored in any persistent database and is discarded immediately after the |
| 61 | + session ends or the user leaves the call. <strong>MiroTalk</strong> does not retain chat, audio, |
| 62 | + video, or file transfer content. |
| 63 | + </p> |
| 64 | + <p> |
| 65 | + <strong>Encryption</strong><br /> |
| 66 | + Media streams are transmitted directly between peers using WebRTC and are encrypted using |
| 67 | + <a |
| 68 | + href="https://en.wikipedia.org/wiki/Secure_Real-time_Transport_Protocol" |
| 69 | + target="_blank" |
| 70 | + rel="noopener noreferrer" |
| 71 | + >Secure Real-time Transport Protocol</a |
| 72 | + > |
| 73 | + (SRTP). Data channels used for chat and file sharing via |
| 74 | + <a |
| 75 | + href="https://developer.mozilla.org/en-US/docs/Web/API/RTCDataChannel" |
| 76 | + target="_blank" |
| 77 | + rel="noopener noreferrer" |
| 78 | + >RTCDataChannel</a |
| 79 | + > |
| 80 | + are secured using |
| 81 | + <a |
| 82 | + href="https://en.wikipedia.org/wiki/Datagram_Transport_Layer_Security" |
| 83 | + target="_blank" |
| 84 | + rel="noopener noreferrer" |
| 85 | + >Datagram Transport Layer Security</a |
| 86 | + > |
| 87 | + (DTLS). |
| 88 | + </p> |
| 89 | + <p> |
| 90 | + <strong>Peer-to-Peer Architecture</strong><br /> |
| 91 | + <strong>MiroTalk</strong> does not act as an intermediary for user communications. Audio, video, |
| 92 | + chat messages, and file transfers are exchanged directly between users and are not routed through or |
| 93 | + stored on <strong>MiroTalk</strong> servers. |
| 94 | + </p> |
| 95 | + <p> |
| 96 | + <strong>Recordings</strong><br /> |
| 97 | + Meeting recordings (if enabled by the user) are temporarily stored in the user's browser as a |
| 98 | + <a |
| 99 | + href="https://developer.mozilla.org/en-US/docs/Web/API/Blob" |
| 100 | + target="_blank" |
| 101 | + rel="noopener noreferrer" |
| 102 | + >Blob</a |
| 103 | + > |
| 104 | + and downloaded locally to the user's device. <strong>MiroTalk</strong> does not have access to or |
| 105 | + store these recordings. |
| 106 | + </p> |
| 107 | + <p> |
| 108 | + <strong>Analytics</strong><br /> |
| 109 | + We use Umami to collect aggregated, non-personal usage statistics to improve the service. This data |
| 110 | + is not used to identify users and is not sold or shared with third parties. |
| 111 | + </p> |
| 112 | + </div> |
| 113 | + |
| 114 | + <div class="privacy-footer"> |
| 115 | + <a class="btn-agree" href="/">AGREE</a> |
| 116 | + </div> |
| 117 | + </div> |
| 118 | + </body> |
| 119 | +</html> |
0 commit comments