Security Overview
Updated: 21 November 2026. Scope: meteorppm.com, app.meteorppm.com, api.meteorppm.com and connected AI assistants. This overview distinguishes published product policies from controls that require deployment-specific evidence. It is not a certification or an independent penetration-test report.
Encryption
The website, application and API use HTTPS. The published privacy policy states that passwords are stored as hashes and sessions and tokens are signed. Encryption at rest, key ownership and key rotation must be confirmed for the contracted deployment; this public website repository does not establish them.
Authentication and MFA
The published policy describes account sign-in, Google sign-in, sessions and verification codes. Verification codes alone do not establish enforced multi-factor authentication. Available MFA factors, enforcement for administrators and users, SSO and recovery procedures must be confirmed during the enterprise review.
Organisation separation and access control
The published policy states that requests from users and assistants are checked against the user’s access level within their company. Project data is controlled by the customer organisation. An enterprise review should obtain evidence of tenant-scoped authorisation and negative tests for access across organisations, including documents, exports, APIs and BIM files.
AI assistant access
Users authorise connected assistants and can disconnect them in their profile. The published policy describes read-only access, permission to make changes, action logs retained for 180 days and undo values retained for 7 days. AI providers process the data shared with them under their own policies and customer settings. Review permitted AI providers before sharing confidential project documents.
Backups and recovery
Backup frequency, locations, encryption, retention, restore-test results and recovery objectives (RPO/RTO) are not specified in the public policy. Request documented values and evidence for the customer deployment before relying on a recovery commitment.
Storage, retention and deletion
The privacy policy identifies DigitalOcean for servers and file storage in the United States, managed MongoDB and Redis, and Google Firebase for web hosting. Account and project data are retained while the company account is active. Exact deletion deadlines, backup expiry, data residency and export arrangements must be agreed with the customer. Submit access, export or deletion requests to support@meteorppm.com; project-data requests may require the company administrator.
Website analytics
Optional Google Analytics and Amplitude analytics run only after the visitor enables analytics in cookie preferences. Session replay is disabled. The public website loads fonts from Google Fonts. These website integrations are separate from the customer application.
Enterprise security review
Request the contracting entity and registration details, a data processing agreement, current subprocessor list, deployment architecture, MFA/SSO configuration, tenant isolation test evidence, privileged-access procedures, incident response arrangements, vulnerability assessment, and backup and deletion evidence. Security, privacy and procurement contact: support@meteorppm.com.