Account access
PestLog supports email/password authentication, password reset, email verification, Google sign-in, and team invitation codes. Dashboard data is meant to be available only to authenticated users with access to the relevant account or team workspace.
Application data handling
Treatment logs, customer records, photos, signatures, inventory details, and exports are handled inside the PestLog application workflow. Photo uploads use private storage with signed access URLs rather than a public asset folder.
Operational safeguards
PestLog uses hosted infrastructure, SSL on the production domain, row-level data access policies in the database layer, rate limits on sensitive export and feedback workflows, and server-side checks for authenticated API routes.
Security contact
To report a security concern or ask how PestLog handles application record data, email support@pestlog.app with a clear description and reproduction details if available.
PestLog publishes this page so customers can understand how the app is operated today and where to send security concerns.
The support channel is monitored for product, account, and security questions: support@pestlog.app.
How do I report a security concern to PestLog?
Email support@pestlog.app with the affected page, account context, timestamps, screenshots if safe to share, and steps to reproduce the concern.
Does PestLog make formal compliance or assurance claims on this page?
No. This page describes the current product posture and support path in plain language without claiming third-party assurance programs or regulated-industry attestations.
Are uploaded photos public by default?
No. PestLog stores service photos in private storage and uses signed access URLs so photos are not served as simple public static files.