Security

Last updated: Jan 8, 2026

At Adventure 33, we take the security of our Prism platform and our customers’ data seriously. This Security Overview provides a high-level summary of the technical and organizational measures we use to protect the Service.

This page is for general information only and does not create a contractual commitment. Specific security obligations, if any, may be set out in a separate written agreement (such as a Master Service Agreement) with a customer.


1. Infrastructure and hosting

Prism is hosted on modern infrastructure in Canada and the United States, with additional regions to be added as we expand to serve customers globally.

We work with reputable hosting providers and use their built-in security features (such as physical security, network controls, and redundancy).


2. Network and data in transit

All access to the Prism web application is protected using TLS 1.3

We recommend that customers access the Service only through supported, up-to-date browsers and secure networks.


3. Data at rest

Databases and storage used by the Service are encrypted at rest using industry-standard encryption technologies.

Access to production systems is restricted to authorized personnel who require it for operational purposes.


4. Access control and authentication

Role-based access control (RBAC) is used to manage user permissions within the Service.

Optional multi-factor authentication (MFA) functionality is available and encouraged for Users where supported.

Administrative access to production environments is limited, logged, and subject to appropriate access controls.


5. Logging and monitoring

We maintain application and security logs to:

  • Monitor service health and performance;

  • Detect suspicious or unauthorized activity;

  • Support troubleshooting and incident investigation.

Logs are retained for a limited period consistent with our security and operational practices.


6. Backup and continuity

Customer Data is backed up regularly as part of our standard operations.

Backups are stored and protected in line with our security controls and are tested periodically for restoration.


7. Security of Customer Data

Customer remains in control of its data and configuration within Prism, including which Users have access.

We process Customer Data only to provide the Service, to maintain and improve it, and as otherwise agreed with Customer or required by law.


8. Incident response

We maintain internal procedures to respond to security incidents.

If we become aware of a security incident that affects Customer Data, we will:

Investigate the incident;

Take reasonable steps to contain, mitigate, and remediate it; and

Notify affected customers without undue delay, consistent with our legal and contractual obligations.


9. Compliance and future improvements

We design our practices with reference to accepted industry security principles for SaaS and B2B platforms.

As we grow, we may evolve our security program further and may pursue additional security/compliance frameworks. Any such developments will be communicated to customers where relevant.


10. Contact

For security-related questions or to report a potential security issue, please contact:

Email: security@adventure33.com