Policies

Security Statement

Recite Me gives you peace of mind that all data is fully available, fully secure and fully backed up across our secured local servers. 

Security is our priority

Our SaaS solution allows you the peace of mind that all data is fully available, fully secure and fully backed-up in our secure servers.

The Recite hosting provider facilities are physically secure, authentication of users is highly sophisticated, and the software solution itself provides a high degree of security. Strict measures are in place to monitor and counter denial of service and virus attacks.

Technical Details

N-tier Architecture: To protect clients’ data, an absolute minimum of the extranet application is available on the Internet. Those parts of the system that are by necessity available are extremely secure. The Recite hosting provider facilities are physically secure, authentication of users is highly sophisticated, and the software solution itself provides a high degree of security. Strict measures are in place to monitor and counter denial of service and virus attacks.

System Integrity: Our system is built using n-tier architecture and at the heart of the system is a secure database.

Always Accessible

In order to ensure your web users can access your website 24/7 from every device we make sure our software is always operational. We use RAID configurations, redundant power supplies and UPS. Complementing the hardware infrastructure is a manned 24x7x365 pre-emptive monitoring service, and 4 hour on-site support contracts with hardware vendors.

Contact Security

If you think you’ve found a security problem with one of our products or online services you should report it, as soon as possible, to our Security Team by email: security@reciteme.com

We take the security of our online systems very seriously and will investigate all reported vulnerabilities, taking action where necessary.

When you report a security issue to us, you should provide enough information to help us understand:

  • the type of problem
  • where you found the bug (web address, IP address or domain name)
  • potential impact of the issue
  • how an attacker could exploit the vulnerability