Live payroll data comes later — after the security work is ready.
SecondProof is still being prepared for its first live-data pilots. Early development partner sessions therefore use realistic fictional payrolls and non-personal examples, so bureaux can judge the product without handing over employee data.
What we use now
Realistic fictional payrolls and non-personal examples from your current process are enough to test whether SecondProof is useful and easy to work with.
Security is a separate go/no-go step
Real payroll data — even if names or identifiers have been masked — will only be considered after the hosted product, user access, backups, data handling, contracts and independent security checks are ready.
What needs to be in place first.
This list shows the work SecondProof is requiring of itself before a live-data pilot. It is not a claim that every item is already complete.
We prefer clear explanations to vague security claims.
As each production safeguard is completed, this page will describe exactly what is in place — where data is hosted, who can access it, how it is protected, how backups work, how long information is kept and how it is deleted.
Have a security question about SecondProof?
Ask what is ready today, what is still being completed and what would need to be true before we accepted live payroll data.
Book a demo