You trust Lapsewise with sensitive paperwork: certificates, contracts, insurance, and more. Here is how we keep it safe.
All traffic to and from Lapsewise is encrypted with TLS. Your documents and data are never sent over the open internet unprotected.
Every record and document belongs to a single workspace. Database row-level security and storage access rules enforce that only members of your workspace can read your data - other customers cannot.
Uploaded files are stored in a private bucket, not on a public URL. Documents are served only through short-lived, signed links generated for authenticated members of the owning workspace.
Your data is hosted in the European Union (Ireland), under GDPR. We choose providers and regions that keep your data within the EU.
Passwords are stored only as secure hashes, never in plain text. Access to your workspace requires authentication, and roles control who can change what.
You can delete a document or record at any time, and it is removed from the live service. Close your account and your personal data is removed in line with our Privacy Policy.
To run the service, our systems store and serve the documents and data you add to your workspace. Access is limited to what is needed to operate Lapsewise: keeping the service running, debugging issues, and protecting against abuse. We do not sell your data, we do not show you ads, and we do not use your documents or records to train machine-learning models.
We believe in being honest about limits. Today, documents are stored encrypted at rest by our infrastructure provider and protected by strict access controls, but they are not yet end-to-end encrypted in a way that would make them unreadable to us. Client-side encryption for the most sensitive documents is on our roadmap, and we will say so clearly here when it ships.
If you believe you have found a security issue, we want to hear from you. Please email hello@lapsewise.com with the details and we will respond as quickly as we can. Please give us a reasonable chance to address the issue before disclosing it publicly.
See also our Privacy Policy and Terms of Service.