Security

1. Security program

Ranx maintains commercially reasonable administrative, technical, and physical safeguards designed to protect Customer Data and service operations. Our controls are risk-based and evolve as the product, customer base, and regulatory expectations change.

2. Hosting and data location

• Ranx runs on Microsoft Azure: the application on Azure App Service and the database on Azure SQL Database.
• Customer data is stored in the United States. The database is in Azure's East US region; the application and file storage are in East US 2.
• The database is backed up automatically and can be restored to any moment in the last 35 days. Backups are copied to a second Azure region in the United States, and files are kept in two US regions, East US 2 and Central US.

3. Data protection

• Encryption in transit: Ranx accepts HTTPS only and tells browsers to use HTTPS only (HSTS). Connections to the database and to service providers are encrypted too.
• Encryption at rest: Azure SQL Database transparent data encryption and Azure Storage encryption, with Microsoft-managed keys.
• Credentials you give Ranx to connect an HR or CRM system are encrypted by the application before they are saved, and each use is logged.
• Passwords are never stored; only salted, iterated hashes are kept.
• Development and testing use a separate database, on its own server, with made-up data.
• Data retention and deletion workflows tied to customer instructions, agreements, and legal obligations.

4. Sign-in and access

• Multi-factor authentication is required for every user and every role, including Ranx staff: each sign-in needs the password and a six-digit code from an authenticator app. It can't be turned off, and text messages are never used for sign-in.
• Five failed sign-ins lock the account for five minutes, and reCAPTCHA protects sign-in, password reset, invitation acceptance, and workspace setup.
• A session ends after five days without use, and within five minutes when a user is disabled or their authenticator is reset.
• Single sign-on (SAML or OpenID Connect) is not available yet; it is planned for 2027. Until then, every user signs in with a password and an authenticator code, as above.
• Role-based access controls in customer workspaces.
• Administrative access limited to authorized personnel with a business need.
• Audit and diagnostic logs used to monitor access, changes, and security events.

5. Leadership scope and confidentiality thresholds

Ranx analytics for Rank, Drivers, Act, and Lift are scoped to the authorized organization or leadership view of the user. Customers can configure response limiting groups and confidentiality thresholds for their account. For employee, patient, and student surveys, and research panels drawn from a named list, at least 5 responses must be present before analysis for a group is rendered; an account can raise this minimum but not lower it. Customer experience and public research results show at any count.

6. Application safeguards

Ranx includes product safeguards such as respondent aggregation, authorized-scope filtering, configurable confidentiality thresholds, publication controls, consent capture, and administrative review surfaces. These safeguards reduce privacy and misuse risk but do not remove the customer's obligation to use Ranx lawfully and responsibly.

7. Operational security

• Security and availability monitoring for production services.
• Dependency, infrastructure, and configuration review as part of ongoing maintenance.
• Least-privilege access practices for systems that process Customer Data.
• Vendor and subprocessor review proportional to the sensitivity of the processing.

8. Certifications and roadmap

Ranx doesn't have a SOC 2 report or ISO 27001 certification yet. Ranx runs on Microsoft Azure, which holds those certifications for the services Ranx uses; Microsoft's audit reports are available from its Service Trust Portal. Until Ranx has its own, the security pack above describes current controls.

Planned for 2027, without set dates yet:

• Single sign-on with SAML or OpenID Connect.
• A SOC 2 audit.
• FISMA readiness: documenting Ranx's controls against the NIST standards that FISMA requires of federal systems, so a federal customer's security authorization can start from them. Ranx is not FedRAMP authorized.

9. Incident response

Ranx maintains procedures for identifying, investigating, responding to, and notifying affected customers of security incidents as required by law and applicable agreements.

10. Customer responsibilities

Customers are responsible for managing authorized users, source-system permissions, exported data, internal notices and consents, appropriate human review, and lawful use of survey outputs.

11. Report a security issue

Report suspected vulnerabilities or security incidents to security@ranx.app. Please include enough detail to reproduce or assess the issue and avoid accessing or disclosing data that does not belong to you.