GDPR
Matsivo is built and operated for use under the GDPR: lawful processing on your instructions, EU hosting, and support for data subject requests received through your organisation.
Security overview
Six control areas describe how Matsivo protects customer data. Each one opens a detailed page.
Application Security
Security is designed into the application layer: hardened HTTP responses, validated inputs and server-enforced business rules.
Read moreAuthentication
Managed identity, strong password requirements, throttling of repeated attempts and optional multi-factor authentication.
Read moreAuthorization
Role-based access control, per-establishment scoping and database-level row security applied to every request.
Read moreEncryption
TLS in transit, encryption at rest on managed infrastructure, modern password hashing and centrally managed secrets.
Read moreMonitoring
Security audit events, application error capture and platform telemetry that make unusual activity visible.
Read moreBusiness Continuity
Managed backups, recoverable infrastructure and a documented approach to incidents and planned maintenance.
Read moreSecurity architecture
Matsivo is a multi-tenant platform where isolation and permission checks are enforced in the database, not only in the interface.
Multi-tenant architecture
One hardened platform, strictly partitioned per organisation.
Tenant isolation
Every record is bound to an organisation and filtered by membership.
Role Based Access Control
Granular permissions resolved per organisation and establishment.
Row Level Security
Access rules live in the database and apply to every query.
Audit logging
Append-only security events that users cannot alter or remove.
Secure authentication
Managed identity, neutral errors and server-side throttling.
Multi-factor authentication
TOTP support with organisation-level enforcement.
Least privilege
Minimal grants for people, services and database roles.
Security headers
CSP, frame denial, cross-origin isolation on every response.
Secure APIs
Validated inputs, size limits and server-side authorisation.
Browser
TLS + hardened response headers
Application
Authenticated session, input validation
Domain action
Permission and MFA checks, audit entry
Database
Row Level Security, tenant scoping
Implementation details, provider names and configuration values are deliberately not published here.
Privacy
Matsivo processes workforce data on behalf of your organisation. You stay in control of it.
Data ownership
Your organisation remains the controller of the data it records. Matsivo does not sell customer data and does not use it for advertising or profiling.
Data portability
Planning, attendance, people and procurement data can be exported in structured, machine-readable formats at any time.
Right to deletion
Records can be deleted in the application, and an administrator can request full deletion of a workspace. Audit records follow a defined retention horizon.
User privacy
The product collects the data required to plan and pay for work. It does not track private location, personal messaging or off-duty activity.
Data minimisation
Fields are limited to operational needs, and access is scoped to the establishments a user is responsible for.
Data processing terms and a subprocessor list are available on request at contact@matsivo.com.
Infrastructure
Matsivo runs on managed European cloud infrastructure, deployed from version-controlled code.
- Cloud platform
- Managed cloud hosting and a managed PostgreSQL database, both operated in the European Union.
- Production environment
- A single production environment, separated from development and demo workspaces, with production data protected by server-side safety guards.
- Backups
- Automated backups of the production database, managed by the database platform.
- Monitoring
- Platform, database and application error monitoring reviewed by the engineering team.
- Disaster recovery
- The application layer is stateless and redeployable; recovery combines a redeploy with the most recent platform backup.
- Scalable architecture
- Edge-served application code and a managed database that scales with load, without per-customer infrastructure.
Encryption
Data is encrypted in transit and at rest, and credentials never leave the systems designed to hold them.
- Encryption in transit
- All traffic uses TLS. HTTP requests are redirected to HTTPS, and internal service connections are encrypted.
- Encryption at rest
- Databases, backups and uploaded files are stored with provider-managed encryption at rest.
- Password hashing
- Passwords are stored only as salted one-way hashes by the managed authentication service and cannot be read by Matsivo staff.
- Secure session management
- Sessions expire after inactivity, have a maximum lifetime, and can be revoked across all devices.
- Secret management
- API keys and application secrets are held in a managed secret store, injected at runtime and never shipped to the browser.
Report a security issue
We welcome reports from security researchers and customers.
If you believe you have found a vulnerability in Matsivo, email security@matsivo.com with a description of the issue, the affected URL or endpoint, and the steps required to reproduce it. Please include enough detail for our team to validate the finding.
- Report privately first and give us reasonable time to investigate.
- Use only accounts and data you own — never access other organisations' data.
- Avoid denial-of-service testing, spam, social engineering and physical attacks.
- We acknowledge reports and keep you informed while we work on a fix.
- We do not operate a paid bug bounty programme.
Machine-readable policy
Our contact details and disclosure policy are published as an RFC 9116 file:
/.well-known/security.txtCompliance
Our current objective is to operate to enterprise expectations and to document our controls honestly.
In place
GDPR Ready
EU hosting, data ownership, export and deletion support.
In place
Enterprise Security
MFA, RBAC, row level security, audit logging and hardened headers.
In place
Security by Design
Authorization enforced in the database; secure defaults for every new tenant.
Planned
Future certifications
Formal certification work is on the roadmap, not yet completed.
Planned
SOC 2
Planned. Matsivo is not SOC 2 certified today.
Planned
ISO 27001
Planned. Matsivo is not ISO 27001 certified today.
Items marked Planned are future initiatives. Matsivo does not currently hold SOC 2, ISO 27001, ISO 27701 or CSA STAR certification, and makes no certification claim.
Availability
We monitor the platform continuously and communicate clearly when something changes.
- Monitoring
- Application errors, database health and API performance are monitored by the engineering team.
- Incident response
- Incidents are triaged by severity; customer-impacting issues are communicated to organisation administrators.
- Planned maintenance
- Maintenance is scheduled outside peak operating hours where possible and announced in advance.
- Status page
- A public status page at status.matsivo.com is planned — coming soon. Until it is live, subscribe to updates by contacting us.
Frequently asked questions
Straight answers to the questions procurement and security teams ask most often.
Where is my data stored?
Matsivo runs on managed European cloud infrastructure. Customer data — including your database, uploaded files and backups — is hosted in the European Union. If you need the specific hosting region for a procurement review, contact security@matsivo.com.
Who owns my data?
You do. Your organisation remains the owner and controller of the operational data it records in Matsivo. Matsivo processes that data to deliver the service and does not sell it or use it for advertising.
Can I export my data?
Yes. Planning, attendance, people and procurement data can be exported from the application in structured formats (CSV/Excel) and as PDF documents. For a complete extract of an organisation's data, an administrator can request one at contact@matsivo.com.
Can I permanently delete my data?
Yes. Records can be deleted in the application by users with the appropriate permission, and an organisation administrator can request full deletion of the workspace. Security audit records are kept for a defined retention period before automatic purge, because they are required for accountability.
How do I report a vulnerability?
Email security@matsivo.com with enough detail to reproduce the issue. Our published policy is available at /.well-known/security.txt. We acknowledge reports and keep researchers informed; we do not currently operate a paid bug-bounty programme.
Is MFA supported?
Yes. Users can enrol a TOTP authenticator application, and organisations can require multi-factor authentication for their members. The requirement is checked on the server for sensitive operations.
How are passwords protected?
Passwords are handled by a managed authentication service and stored only as salted one-way hashes. A minimum length of 12 characters is enforced, repeated failed attempts are throttled, and Matsivo staff cannot read your password.
How are backups managed?
The production database is backed up by the managed database platform, and the application itself is reproducible from version-controlled code. Restores are performed by the Matsivo engineering team; customers do not have direct access to backup files.
Contact
Talk to the people who build and operate Matsivo.