Whitepaper

Raios360 Security Overview

Version 1.0 — June 2026

This document summarizes how Raios360 protects customer data: tenant isolation, encryption, durability, access control, and the deployment options available to organizations with heightened compliance requirements. It is intended for security, IT, and procurement reviewers.

1. Multi-Tenant Isolation

Raios360is a multi-tenant SaaS platform: many organizations are served from shared infrastructure, with each organization's data logically isolated. Isolation is enforced independently at six layers, so a defect in any single layer is caught by the others:

  1. Database security rules — every collection is scoped to an organization; reads and writes require verified membership in that organization. Enforced on the server; a client cannot bypass it.
  2. Organization-context validation — the active organization is verified before any operation executes.
  3. Data-access layer — every query requires an organization identifier; cross-organization reads are not expressible.
  4. Collection-group filters — platform-wide queries are constrained by organization identifier.
  5. Server-side function checks— backend functions re-validate the caller's organization membership before acting.
  6. Row-level security— the analytics/reporting database enforces per-tenant row-level security, so even the application database account cannot read another tenant's rows.

The net guarantee: an organization can only ever access its own data.

2. Encryption

All customer data is encrypted by default — there is no “unencrypted mode.”

  • At rest: AES-256 across the document database, file storage, and analytics database, using managed keys on Google Cloud.
  • In transit: TLS for all client–server and service-to-service communication.

Organizations needing to control their own encryption keys can do so via the dedicated deployment option (Section 6).

3. Data Durability — Built So Nothing Is Lost

For a system of record, the most important promise is that submitted data and its attachments are never lost. Raios360 layers several protections:

  • Soft delete + Recycle Bin. Deleting a submission moves it to a Recycle Bin rather than erasing it. The record and its media are retained and an administrator can restore them for 90 days; only after that window does an automated, audited process permanently remove them.
  • Point-in-time recovery on the primary database, plus daily full backups retained for a year.
  • File versioning on media storage, so an overwritten or deleted file can be recovered, and a continuous backup mirror of all media to a separate location.
  • Deletion protection on the database instances themselves, preventing accidental teardown.
  • Offline-capture integrity. Media captured offline in the field is queued and uploaded when connectivity returns, with the stored record updated to reference the uploaded file — including media nested inside repeatable form sections.

4. Access Control & Auditability

Within an organization, access is governed by configurable roles and permissions. Administrative and irreversible actions are restricted and recorded:

  • An optional audit logcaptures create, update, delete, approve, and reject events across major record types, with field-level before/after history and the acting user's identity preserved even if their account is later removed.
  • Permanent deletions and storage cleanups are recorded to an internal operations trail for forensics.
  • Restoring a deleted submission is limited to organization administrators.

5. Infrastructure & Compliance

Raios360 runs on Google Cloud Platform and inherits its physical security, network protections, and compliance certifications (including ISO 27001, SOC 2, and others maintained by Google for its infrastructure). Raios360's own isolation, durability, and access controls are built on top of that foundation. We are happy to discuss our security practices and roadmap, including independent certification, as part of a procurement review.

6. Options for Heightened Requirements

The controls above apply to every customer on the shared platform. For organizations with stricter regulatory or contractual needs, we offer:

  • Dedicated single-tenant deployment — your own isolated database, file storage, and analytics instances, separate from other customers.
  • Customer-managed encryption keys (CMEK) — bring your own key, held in your cloud key-management service, with the ability to revoke access.
  • Field-level encryption for specific sensitive fields, on request.

These are available as part of an enterprise agreement. Contact us to discuss which option fits your requirements.

This overview is provided for informational purposes and may evolve as the platform does. For the most current details or a tailored security questionnaire response, contact the Raios360 team.