Privacy Policy
Last updated: September 8, 2026
1. Information We Collect
We collect information you provide directly: your identity-provider name and email for sign-in, company name, optional business contact details, team and role details, billing identifiers, and fire-inspection data such as customer lists, equipment registries, inspection records, photos, signatures, and reports. Public-site forms may also collect waitlist or template-download email addresses and role/team-size information. The application may also record session metadata such as IP address, user-agent, session timestamps, and token identifiers for authentication, abuse prevention, and security operations.
2. How We Use Your Information
We use information to authenticate users, provide the application, store and process inspection records, generate reports, deliver requested emails, provide support, process subscriptions, prevent abuse, measure marketing performance where consent is provided, and improve the beta. We do not sell inspection data. Service providers process data only for the services they provide and under their applicable terms.
3. Service providers and storage
Depending on the environment and feature used, we use third-party providers for identity and authentication, payment processing, hosting and infrastructure, file storage, email delivery, analytics where consent is granted, security and bot protection, and operational notifications. These providers process information only to deliver the relevant service under their applicable terms. We may change providers as the product evolves and will update this policy when a change materially affects how information is handled. The application uses HTTPS and access controls, but this beta page does not promise a particular encryption standard, certification, or data-residency outcome.
4. Retention, export, and deletion
We retain account and organization data while needed to provide the service, meet billing/support obligations, or resolve disputes. Session metadata follows the session and security lifecycle and may be retained longer when needed to investigate abuse or protect the service. The current beta can provide an application export for supported database records, but it may not yet include every photo, signature, generated PDF, provider copy, or backup. Deletion requests are handled through the application or [email protected] and may require an asynchronous operator-assisted process. We will explain any remaining retention needed for legal, security, backup, or dispute purposes rather than promising a fixed deletion window.
5. Your Rights
Subject to applicable law and the product’s current beta capabilities, you may request access, correction, export, or deletion by contacting [email protected]. If your organization uses FireInspected for its own customers or technicians, the organization may be the controller and FireInspected may act as a processor; customers are responsible for their own notices, lawful basis, and requests involving their people.
6. Cookies, analytics, and choices
Essential session and functionality storage may be used when you use the application. The public site asks before loading optional analytics. You can decline analytics or clear the browser’s analytics-consent setting; declining does not prevent access to public content or the waitlist. Analytics events are designed to exclude email addresses and inspection content. We may retain a suppression or opt-out preference so we do not re-contact you.
7. Beta communications
If you explicitly consent when joining the waitlist or requesting a template, we may contact you about product updates and launch notes. The form records the consent version, timestamp, source, and requested context with our operational notification process. You can opt out at any time by contacting [email protected]. Transactional messages, such as account, billing, invitation, or requested report delivery messages, may still be sent when necessary to provide the service.
8. Contact
Questions about this policy? Email [email protected].