Legal
Privacy Policy
Effective: October 12, 2026
1. What this policy covers
This policy describes how LPAWorks processes information needed to provide its Layered Process Audit software, secure workspaces, deliver notifications, and support paid subscriptions.
2. Information processed
Depending on how you use LPAWorks, information may include:
- account identity, email verification, and authentication information;
- privacy-protected registration-abuse signals, including keyed digests of a signup IP address and a random first-party device identifier;
- organization, site, role, and workspace configuration;
- areas, processes, LPA layers, checklists, and schedules;
- audit responses, notes, findings, corrective-action history, and reports;
- evidence files uploaded to a private evidence store;
- invitation and transactional-notification delivery information; and
- commercial status and limited billing-provider identifiers needed to manage subscription entitlement.
3. Why information is processed
Information is processed to authenticate users, enforce tenant and role boundaries, run the LPA workflow, preserve historical records, deliver requested transactional messages, maintain service security, troubleshoot failures, and administer subscription entitlement.
4. Free-trial eligibility and security signals
When a new workspace is created, we verify the owner's email with our authentication provider. We keep a keyed, non-reversible email token to prevent repeated trial claims using the same verified email, including if the account is later recreated. We do not use your email for hidden third-party profiling.
To recognize unusual repeat registrations, we may process the IP address seen at signup and place a first-party, HttpOnly, random device ID cookie lasting up to 90 days. Our database stores only keyed digests of these signals, not raw IP addresses or browser characteristics. The signal records expire after 90 days. We do not perform canvas, font or cross-site fingerprinting, and a shared IP or device is not an automatic reason to deny a trial. Browser or network blocking does not replace verified-account checks.
5. Payment information
LPAWorks does not store card numbers or CVV data in its application database. Payment details are handled by the third-party payment provider shown at checkout. LPAWorks stores only the limited provider identifiers and event metadata required to keep commercial entitlement synchronized.
6. Service providers
LPAWorks uses specialist service providers to operate the product, including Vercel for application hosting, Supabase for database, authentication, and private storage, Resend for transactional email, and a third-party payment provider for subscription processing. Each provider processes information according to its role in delivering the service.
7. Security and access
LPAWorks uses authenticated access, organization tenant boundaries, role checks, database Row Level Security, restricted private evidence access, and server-side authorization. No security control can eliminate every risk, so users should also protect their credentials and devices.
8. Retention and historical records
Information is retained for as long as reasonably needed to provide the service, preserve the audit and corrective-action history the customer expects, meet security and operational needs, and satisfy applicable legal obligations. Some completed audit and published checklist records are intentionally immutable to preserve historical integrity.
9. Your organization's responsibilities
Workspace administrators are responsible for deciding what business data their organization enters into LPAWorks, assigning appropriate access, and ensuring they have a lawful basis to process personal information they include in audit or evidence content.
10. Requests and questions
Privacy questions or requests can be sent to support@lpaworks.com or through the public Contact / Support page. Applicable rights depend on the person's location and the circumstances of processing.