Server-side authorization
Sensitive provider actions are checked on the server rather than trusting what the browser says.
TRUST CENTER
Security, privacy and clear accountability.
Your business relies on private client records, schedules and payment information. Here is how we approach protecting them, and where independent assurance stands.
Tenant isolation
Business data is structured to stay scoped to the provider or organization that owns it.
Account protection
Authenticator MFA is available for business accounts. Platform administrators must verify an authenticator before accessing protected administration tools.
Tokenized payments
RoveLogics does not need to store raw payment card numbers to support hosted payment workflows.
Support access and logging
Delegated support grants are time-limited and revocable, with separate view or edit permissions. Support use and selected security actions are recorded.
Export and deletion
Providers have export tools. Account deletion and privacy requests follow separate workflows; deleting a client login does not automatically erase records held by an independent service business.
ASSURANCE STATUS
Clear about what has been independently verified.
Reviewed October 31, 2026. RoveLogics has not obtained its own SOC 2 report, ISO/IEC 27001 certificate or Cyber Essentials certificate. We have not completed an independent application penetration test or a CSA STAR Level 1 listing. Internal checks are not independent assurance.
Hosting and encryption
Our managed hosting provider documents HTTPS/TLS and provider-level encryption at rest on managed cloud infrastructure. Infrastructure providers' certifications do not certify RoveLogics.
Security and data practicesBackups and recovery
The application includes encrypted backup snapshots and integrity checks. These checks alone do not establish a complete disaster recovery test. We do not publish a guaranteed recovery time or recovery point.
Report a security concern
Contact support@rovelogics.com with a brief description. Please do not email passwords, card numbers, private client records or access tokens. Testing requires prior written authorization.
Service statusPROVIDER SAFETY
Safety tools for people working alone in unfamiliar places.
RoveLogics cannot eliminate the risks of mobile work. It can help providers screen visits, keep a trusted person informed, document incidents, and prevent a reported client from simply booking again with the same business.
IMPORTANT HEALTHCARE BOUNDARY
Do not use the current environment for regulated clinical data.
RoveLogics is not currently positioned for storing PHI or other legally heightened health information in this environment. Use synthetic or non-sensitive information for clinical workflow testing unless RoveLogics explicitly states that your environment is approved for it.
OUR OPERATING PRINCIPLE
Collect less. Expose less. Trust less by default.
Client-facing software should not need broad internal access just because it is convenient to build that way. RoveLogics is designed around scoped data access, short-lived or signed flows where appropriate, and business controls that make the safer path the normal path.