Perlo supports project and portfolio delivery across complex developments, which means security, access control, and transparency matter from day one. Here you can see what is in place today and request more detailed documentation where needed.
A clear overview of how Perlo handles security, access, and customer data today. If you need the detail, use the request form below and we'll be in touch.
Customer data is geofenced, and the hosting region is agreed at onboarding. It is not changed without customer approval.
Data is encrypted at rest and in transit. Storage uses AES-256, and transport is protected with TLS 1.3.
Access is controlled by role and workspace, so leadership, PMO, project managers, and external collaborators only see the information relevant to them.
Key user actions and changes are logged with user, timestamp, and action history, giving teams a clear record of what changed and when.
Customer data remains protected within its own environment and is not exposed across customers. Where data is used to improve models or features, it is structured and anonymized so it cannot be traced back to an individual customer.
Customers retain ownership of their data and can request exports of project data, risk registers, and audit history in standard formats.
Perlo is built on infrastructure providers that operate with certifications such as SOC 2 Type II and ISO 27001.
Fields marked with * are required. We'll reply within 2 business days with confirmation of what we can share.
Thank you. We'll review your request and get back to you within 2 business days with the next step — typically an NDA and a confirmation of what we'll share.
If your team uses a standard security questionnaire (SIG, CAIQ, or a custom one), email it straight to us. We'll turn it around alongside the documentation request, usually in the same 2-business-day window.