DataStoragePolicy

Version 13 (Adrian Georgescu, 06/04/2013 01:32 pm)

1 5 Adrian Georgescu
h1. SIP2SIP Data Privacy and Storage Policy
2 1 Adrian Georgescu
3 7 Adrian Georgescu
SIP2SIP server infrastructure relays and stores information provided by end users. If you are concerned about privacy of your own data and how it is used inside the platform, read below.
4 1 Adrian Georgescu
5 1 Adrian Georgescu
h2. SIP Accounts
6 1 Adrian Georgescu
7 8 Adrian Georgescu
Accounts information is stored in the platform database. SIP account and SIP Settings web page passwords are stored in encrypted form in the database. There is a salt involved but in case of database being compromised the salt can be also retrieved. It is advisable to use strong passwords that cannot be guessed by dictionary brute force attacks.
8 1 Adrian Georgescu
9 9 Adrian Georgescu
h2. SIP Signaling
10 2 Adrian Georgescu
11 2 Adrian Georgescu
Signaling can be done in clear text using UDP and TCP protocols. You may use TLS for encrypting data between the end points and platform SIP servers. There is no guarantee that encryption will work end-to-end, the SIP signaling part of the platform provides only hop-by-hop signaling security.
12 2 Adrian Georgescu
13 9 Adrian Georgescu
h3. Sessions
14 1 Adrian Georgescu
15 10 Adrian Georgescu
All SIP signaling for session establishment (INVITE/BYE/CANCEL/PRACK/ACK methods and their replies) relayed by the platform SIP servers is stored in cleartext for the last 30 days in platform databases. Both end-users and platform operator has access to this information for troubleshooting purposes.
16 1 Adrian Georgescu
17 9 Adrian Georgescu
h3. Registration
18 9 Adrian Georgescu
19 9 Adrian Georgescu
No information is stored in the platform.
20 9 Adrian Georgescu
21 9 Adrian Georgescu
h3. Presence
22 9 Adrian Georgescu
23 11 Adrian Georgescu
Presence dialogs (SUBSCRIBE/NOTIFY methods) and related XML payloads are not stored in the server databases.
24 9 Adrian Georgescu
25 1 Adrian Georgescu
h2. Call Detail Records
26 1 Adrian Georgescu
27 13 Adrian Georgescu
Call Details Records (CDRs) are stored for up to six months in clear text format in platform databases. CDRs contain metadata information about who called whom and what time and for how long. The IP addresses used for signaling and media are also stored in the CDRs. 
28 1 Adrian Georgescu
29 1 Adrian Georgescu
h2. Offline Short Messaging
30 1 Adrian Georgescu
31 2 Adrian Georgescu
Messages sent using SIP MESSAGE method that cannot be delivered to local users of the platform are stored for later delivery in cleartext format in the platform database.
32 1 Adrian Georgescu
33 9 Adrian Georgescu
h2. RTP Media
34 1 Adrian Georgescu
35 13 Adrian Georgescu
RTP streams are relayed by platform RTP media relays. Actual data is not stored anywhere. You may encrypt your data using sRTP but the encryption key is available in the SIP signaling. Whomever has access to the signaling plane (and the server always has access to it) will be able to decrypt any sRTP encrypted stream. If your end-points supports zRTP, is much safer than sRTP as the decryption key is known only by the end-points.
36 2 Adrian Georgescu
37 9 Adrian Georgescu
h2. MSRP Media
38 1 Adrian Georgescu
39 9 Adrian Georgescu
h3. Chat Messages
40 9 Adrian Georgescu
41 2 Adrian Georgescu
MSRP chat sessions are done over TLS connections via the platform MSRP relay servers. The content of the messages is not logged or stored anywhere.
42 2 Adrian Georgescu
43 2 Adrian Georgescu
Blink users can replicate the chat messages between multiple instances configured with the same account. The replicated chat messages are stored for 60 days in encrypted form in platform databases. The encryption key is not known by the server, only Blink clients posses the encryption and decryption key. If you are concerned about privacy you may disable chat replication in Blink.
44 2 Adrian Georgescu
45 9 Adrian Georgescu
h3. File Transfers
46 2 Adrian Georgescu
47 2 Adrian Georgescu
MSRP file transfer sessions are done over TLS connections via the platform MSRP relay servers. The content of the files is not logged or stored anywhere.
48 2 Adrian Georgescu
49 6 Adrian Georgescu
h2. XMPP Gateway
50 1 Adrian Georgescu
51 6 Adrian Georgescu
All chat messages and presence payloads are relayed through the SIP/XMPP gateway. Message content is not stored anywhere. 
52 6 Adrian Georgescu
53 1 Adrian Georgescu
h2. Protecting Privacy
54 1 Adrian Georgescu
55 13 Adrian Georgescu
h3. Ilegal Network Tapping
56 13 Adrian Georgescu
57 12 Adrian Georgescu
To protect your data against being exposed over the Internet (like IP tapping), do the following:
58 2 Adrian Georgescu
59 1 Adrian Georgescu
 * Use TLS for SIP signaling
60 1 Adrian Georgescu
 * Use zRTP for audio and video media if your end-points support it otherwise use sRTP
61 1 Adrian Georgescu
 * Use TLS for MSRP media
62 1 Adrian Georgescu
63 13 Adrian Georgescu
These would protect your data against those who try to illegally sniff your network traffic (like breaking into your LAN WiFi) but have no access to the client or server software. These measures will not protect your data privacy against legal intercept measures if enforced and applied to the server infrastructure that relays the messages (you will likely not know if and when this happens). 
64 13 Adrian Georgescu
65 13 Adrian Georgescu
h3. Legal Intercept
66 12 Adrian Georgescu
67 12 Adrian Georgescu
To minimize the chance of your media data being exposed in case of legal intercept has been enforced do the following:
68 12 Adrian Georgescu
69 12 Adrian Georgescu
 * Use ICE in both end-points, this way RTP streams can flow most of the time peer to peer without passing through the server media relays
70 12 Adrian Georgescu
 * Use zRTP encryption, this way you will know about men in the middle attacks trying to intercept and decrypt your data
71 12 Adrian Georgescu
 * Don't use SIP MESSAGE method
72 12 Adrian Georgescu
 * Don' use MSRP media unless you have a client that has additional media encryption where the key is not known by the network