Phasivo
Security

Your project data is business-critical. We treat it that way.

How Phasivo protects the data of every project on the platform.

Multi-tenant architecture

Every organisation's data is separated. Each request is checked against the signed-in user's organisation and project before anything is read or written.

Project-level access control

Access is granted per organisation and project. Contractors see only their own contracts, progress bills and defects in a separate portal, and each buyer sees only their own apartment.

Role-based access

Organisation admins, project team members and contractors have different permissions; read-only access exists for demonstrations.

Database-level protection

Row-level security policies are enabled on every table, and the database is not reachable for reading or writing through the public API with a user session.

Private document storage

Documents, receipts, contracts, situation documents, defect photos and each apartment’s progress photos are stored privately and opened only through short-lived signed links. Only the images of a public project website are public.

Secure authentication

Sign-in is handled by Supabase Auth; passwords are never stored by Phasivo. Accounts are created by invitation, and public forms are protected by rate limiting and bot verification.

Staff access is logged

When Phasivo staff view a client's organisation to help, the access is read-only, limited to 60 minutes and recorded.

Infrastructure

The database runs on Supabase in the EU (Frankfurt), the application on Vercel. Every code change passes an automated check that blocks secrets from being committed.

Backups

A full copy of the database is taken every week, and restoring such a copy has been tested.

Data export

Budget, units, contracts and payments, and PDV records can be exported to Excel at any time.

Access to the buyer’s page

A buyer opens their page with a personal link; a new phone or computer also needs a six-digit code sent to the buyer’s e-mail. A confirmed device is remembered for 30 days, and a link unused for six months stops working.

Automatic document reading

A document is read only when a user uploads it for that, and nothing is written before a person confirms what was read. An organisation’s administrator can switch the reading off.

Questions about security?

Ask us anything about how your project's data is handled — we'll answer plainly.

Ask a security question