Privacy Policy

Reliefinstitute.com follows strict security protocol for our servers and the information kept on them.

All information collected is encrypted and only non-essential information can be seen by authorized persons.

When you send a message, Relief Institute will log an encrypted version of incoming information and the date and time of the transaction. We use this data to analyze the message request and future requests in order to improve the end user experience.

Our secure platform stores basic contact information required by you and provided by persons wanting to interact with your program. Once captured it is encrypted by our system and can be viewed only by authorized members of your team.

Relief Institute will never rent or sell your program collected information to any third party, nor will we use this information to initiate a call or SMS message to them without your permission. Your wireless carrier and other service providers also collect data about your SMS usage, and their practices are governed by their own privacy policies.

Our security practices include but are not limited to:

  • Our logins are disabled by root
  • Only one single user is permitted to ssh user log in
  • Our ssh is set to listen on 22
  • We have a secondary administrative IP/subnet to the nic and we have set ssh to listen on this only.
  • We have set samba to listen only on the relevant internal network and ssh.
  • We are very sure of our port forwarding rules
  • We have iptables running, with a complex configuration.
  • All unrequired services are turned off.
  • We only permit sudo/su by one specific user
  • Our system is up to date via apt.
  • All custom daemons are running with lowly user privs, not root privs
  • All administrative tools such as webmin, phpmyadmin, phpsysinfo, webalizer, etc are not readily visible.
  • Secure the ‘shm’ and ‘tmp’ areas to limit script exploits

We use SSL certificates with 256-bit encryption to transfer data over the internet:

Encryption Protects Data During Transmission

Web servers and Web browsers rely on the Secure Sockets Layer (SSL) protocol to create a uniquely encrypted channel for private communications over the public Internet. Each SSL Certificate consists of a public key and a private key. The public key is used to encrypt information and the private key is used to decipher it. When a Web browser points to a secured domain, a level of encryption is established based on the type of SSL Certificate as well as the client Web browser, operating system and host server’s capabilities. That is why SSL Certificates feature a range of encryption levels such as “up to 256-bit”.

Strong encryption, at 128 bits, can calculate 288 times as many combinations as 40-bit encryption. That’s over a trillion times a trillion times stronger. At current computing speeds, a hacker with the time, tools, and motivation to attack using brute force would require a trillion years to break into a session protected by an SGC-enabled certificate. To enable strong encryption for the most site visitors, choose an SSL Certificate that enables at least 128-bit encryption for 99.9% of Web site visitors.