Security and privacy come first in everything Pearlixa adds.
This page sets out where a fund's data is held, who can sign in and act on it, and how each step is recorded.
Pearlixa holds only what the figures need, and keeps each fund apart.
No investor names leave the fund. Pearlixa works from positions and funding statements alone, and nothing of one fund is visible to another.
The platform runs on Amazon Web Services, on infrastructure that AWS has certified to ISO 27001 and audited under SOC 2, and before each release it is tested internally against attacks.
Signing in takes a moment, with a code or a passkey.
People sign in with their email address, a password and a code from an authenticator app, or with a passkey on their laptop or phone, which needs no password at all.
Passwords are checked against known breached passwords and never stored in readable form, and each person can see and end their own sessions.
From the moment it arrives, a fund's data stays encrypted.
Every step happens on Amazon Web Services, in the EU or in the US, depending on where a fund's data needs to be held.
A second person approves, and the log keeps every step.
Each person holds one of six roles, and a fund or mandate can be walled off so that only the people granted it see it. A report or a limit change waits for a second person, and nobody approves their own work.
Sign-ins, approvals, reports sent and exports are written to an audit log that cannot be edited or deleted, each entry linked to the one before it. Issued reports carry a signature the fund's auditor can check.
For the fund's due diligence.
A data processing agreement under Article 28 of the GDPR is available to every fund. Further documents for a fund's due diligence, questions on security and reports of a suspected vulnerability go to security@pearlixa.com.
Start with a call.
A short conversation about your fund's due diligence, followed by a live demo of sign-in, roles and the audit log.
Book a call