Information collected through forms
FireGridOps form placeholders collect information that users choose to submit for contact, demo, newsletter, and resource workflows.
- Name, company, work email, phone, job title, company size, current tools, preferred contact method, selected modules, and message content may be collected through lead forms.
- Gated resource forms may collect requested resource details, resource category, interested module, and consent confirmation.
- Authentication placeholder pages do not create accounts, store passwords, or connect to the future FireGrid app yet.
Contact, demo, newsletter, and resource submissions
Submissions are currently mock workflows. Future production use may route records to CRM, sales, support, marketing, or email notification systems after the appropriate integrations are selected.
- Contact and demo requests may be used to respond to product, pricing, implementation, or enterprise rollout inquiries.
- Newsletter submissions may be used for product updates and fire protection operations content.
- Resource downloads may be used to provide the requested material and related FireGridOps follow-up.
Analytics and tracking placeholders
The site includes consent-gated analytics and marketing placeholders. Real analytics scripts and marketing pixels should remain disabled until cookie consent, privacy review, and provider configuration are complete.
- Analytics placeholders may measure page views, CTA clicks, pricing interest, form submissions, and resource download events after consent.
- Marketing placeholders may support future LinkedIn, Meta, or campaign measurement after consent.
- Missing analytics or pixel IDs do not activate tracking and should not break the site.
CRM lead capture and email notifications
CRM and email integrations are not live yet. Future integrations may send submitted lead data to HubSpot, Salesforce, Zoho, FireGrid internal CRM, Resend, SMTP, or other approved services.
- CRM mappings should include contact fields, company fields, lead source, lifecycle stage, interested modules, requested resources, and demo notes.
- Email notification recipients and templates must be reviewed before launch.
- Consent, opt-out handling, retention, and deletion processes must be finalized before production use.
Cookies and preferences
Essential cookies are used for site operation and consent storage. Analytics and marketing cookies are optional and controlled through the cookie preferences interface.
- Users can accept all, reject non-essential cookies, or manage preferences.
- Cookie preferences are stored locally in the user's browser.
- A footer cookie settings button allows users to reopen preferences.
Data retention, third parties, and user rights
Retention periods, third-party processors, regional user rights, and request handling processes are placeholders pending legal and operational review.
- A production policy should define how long lead, analytics, resource, and support records are retained.
- A production policy should list third-party providers and their processing roles.
- A production policy should define how users may request access, correction, deletion, or opt-out.
Contact information placeholder
Privacy questions should route through an approved FireGridOps or EmberCore Technologies contact method before launch.
- Placeholder contact: privacy@firegridops.com
- Final contact information must be verified before production use.