Legal
Privacy Policy
This Privacy Policy explains how RoofCommand CRM collects, uses, stores, and protects information when roofing companies, owners, managers, sales representatives, prospects, and visitors use our website, sales pages, demo environment, application, communications, and related services.
Effective date: May 2, 2026
Operational software notice: RoofCommand CRM is a roofing business software platform. It does not provide legal, accounting, tax, insurance, engineering, building-code, payroll, or certified roof-measurement advice. Users are responsible for verifying business, customer, measurement, pricing, and project information before relying on it.
1. Who we are
RoofCommand CRM is a web-based customer relationship management platform built for roofing companies. The service helps users manage leads, inspections, sales pipeline, maps, GPS-assisted address capture, roof size estimates, proposals, purchase orders, job documents and photos, job costing, team activity, support requests, dashboards, account information, and related roofing business workflows.
Contact: info@roofcommandcrm.com
Support: support@roofcommandcrm.com
2. Scope of this policy
This policy applies to the RoofCommand CRM website, application, sales landing pages, demo environment, customer-facing CRM, support workflows, transactional email workflows, and internal business outreach processes.
Customer CRM data and RoofCommand CRM internal prospecting data are separate operational categories. Customer-entered homeowner data is used to provide the CRM service to that customer company. RoofCommand CRM’s own B2B prospecting records are used for RoofCommand CRM’s sales and business development operations.
3. Information we collect
Account, company, and user information
- Name, email address, company name, company contact information, role, account status, login identity, team membership, invited users, active user count, account settings, plan selection, trial status, and subscription status.
- Profile information such as owner, manager, or sales representative role, company address, state, service area, logo, and business contact details.
CRM and roofing business information
- Lead records, homeowner names, phone numbers, email addresses, property addresses, city, state, ZIP code, lead source, status, assigned rep, damage type, insurance claim context, estimated value, follow-up dates, notes, activity history, inspections, and pipeline information.
- Roof type, roof age, layers, square footage, damage checklist, severity, inspection notes, proposal details, estimate inputs, price per square, upgrades, add-ons, warranty notes, payment terms, and signed-job status.
- Purchase order information, material lists, distributor or supplier names, PO status, received quantities, supplier credits, material cost synchronization, job closeout notes, job costing, gross profit, gross margin, and commission information when used by the customer company.
Documents, photos, and uploaded files
- Documents, photos, PDFs, contracts, signed agreements, insurance paperwork, claim documents, estimates, material lists, permits, HOA documents, supplier documents, inspection photos, and other files uploaded or attached to a lead or job.
- Metadata such as file name, file type, category, notes, size, storage path, upload date, and user or company association. Photos may be compressed or optimized to improve performance.
Location, map, GPS, and roof measurement information
- Property addresses, GPS coordinates, latitude, longitude, address lookup results, geocoding results, GPS capture timestamps, map view information, directions links, and property-location context when a user chooses to use these features.
- Roof size estimate inputs and outputs, including manual squares, quick calculator inputs, pitch, waste percentage, measured or estimated areas, external report references, map-assisted takeoff values, and related notes.
Proposal, purchase order, and communication information
- Proposal drafts, proposal totals, customer-facing proposal content, email recipient information, PO email information, support messages, onboarding messages, trial messages, and related delivery or event records when available.
- When email workflows are used, we may process sender, recipient, subject, message body, timestamps, provider IDs, delivery status, bounce status, open or click events if enabled, and related operational logs.
B2B prospecting and sales outreach information
- For RoofCommand CRM’s own business development, we may store information about roofing companies and business contacts, including company name, owner or contact name, phone number, email address, website, city, state, source, priority, notes, outreach status, follow-up date, and email/SMS interaction history.
- Prospecting records are used to contact roofing companies about RoofCommand CRM and are independent from the CRM data that paying customer companies enter about their own homeowners and jobs.
Support, operational, and technical information
- Support ticket subject, category, priority, description, status, resolution notes, account context, and communications sent to RoofCommand CRM for support, billing, onboarding, or product questions.
- Browser, device type, IP address, session information, authentication events, error logs, usage activity, app installation/PWA signals, language preference, demo mode state, local storage/session storage values, and basic analytics or operational logs.
Payment-related information
- When payments are enabled, payment processing may be handled by Stripe or another payment processor. RoofCommand CRM does not intend to store full credit card numbers on its own servers.
- We may store billing status, selected plan, payment confirmation, Stripe customer ID, subscription ID, invoice ID, checkout session ID, webhook event references, billing email, cancellation status, renewal status, and related billing records as needed to operate the service.
4. How we use information
- To create and manage user accounts, company accounts, teams, roles, permissions, trials, subscriptions, and support access.
- To provide CRM functionality, including leads, pipeline, inspections, maps, GPS-assisted address capture, roof size estimates, proposals, purchase orders, documents, photos, job costing, commissions, support tickets, dashboards, and account profile features.
- To secure accounts, authenticate users, apply role-based access, maintain company-level data separation, and enforce Row Level Security or similar access controls.
- To send transactional, support, onboarding, trial, billing, proposal, purchase order, system, and account-related communications.
- To conduct RoofCommand CRM’s own B2B prospecting and follow-up with roofing companies that may be interested in the service.
- To process payments, manage trials, subscriptions, renewals, failed payments, cancellations, invoices, and billing records when payment features are enabled.
- To monitor performance, troubleshoot bugs, improve the product, prevent abuse, detect security issues, and maintain operational logs.
- To comply with legal, tax, accounting, security, contractual, and business obligations.
5. Customer data and homeowner data
Roofing companies may enter information about homeowners, properties, inspections, estimates, insurance claims, documents, photos, purchase orders, and sales opportunities. The customer company is responsible for having appropriate authority, permission, legal basis, or business reason to enter that data into RoofCommand CRM.
RoofCommand CRM uses customer-entered homeowner and job data to provide CRM services to the customer company. We do not use customer-entered homeowner lead data to market RoofCommand CRM directly to those homeowners unless separately authorized.
6. Internal prospecting data
RoofCommand CRM may maintain its own internal prospecting database for B2B outreach to roofing companies. That prospecting database is used to track companies, contacts, outreach, follow-ups, email events, and sales opportunities for RoofCommand CRM itself.
The internal prospecting workflow is operationally separate from the customer-facing SaaS CRM used by roofing companies to manage their own leads and jobs.
7. Service providers and third parties
We may use third-party service providers to operate RoofCommand CRM. These providers may process information only as needed to provide their services to us or to you through the platform.
- Supabase: authentication, database, storage, backend services, Edge Functions, and security controls.
- Google Maps Platform: maps, geocoding, address lookup, GPS-related property location features, aerial or satellite map views, and map display.
- Stripe: payment processing, subscriptions, invoices, customer billing records, fraud prevention, and payment-related compliance when payments are enabled.
- Email providers, including Brevo or similar providers: transactional emails, onboarding emails, support emails, trial emails, proposal emails, purchase order emails, and B2B prospecting emails.
- Hosting, domain, scheduling, support, analytics, and security providers: website hosting, scheduled tasks, operational messages, uptime, logging, and basic security monitoring.
We do not sell full credit card numbers or intentionally store payment card data in RoofCommand CRM. Payment card details should be handled by the payment processor.
8. Location, GPS, maps, and roof size workflows
GPS capture is optional and must be initiated by the user. Browsers and devices may ask for permission before sharing location. When location is used, RoofCommand CRM may store coordinates and a timestamp to support address capture, maps, lead location, inspections, routing-related workflows, property aerial views, and roof size workflows.
Users should verify any address, coordinate, map view, roof size estimate, pitch, waste percentage, or measurement value before using it for proposals, material ordering, production, insurance documentation, or business decisions.
9. Documents and photos
Users may upload job files such as photos, insurance documents, claim documents, contracts, signed agreements, estimates, material lists, permits, HOA documents, supplier documents, and other job-related records. Users are responsible for ensuring those files are lawful, appropriate, accurate, and necessary for roofing CRM operations.
Users should avoid uploading unnecessary sensitive information, including Social Security numbers, bank passwords, medical records, unrelated personal documents, or protected health information.
10. Communications
RoofCommand CRM may send or help users send transactional, operational, support, billing, trial, proposal, purchase order, and account-related communications. For B2B prospecting, RoofCommand CRM may send commercial outreach about its own services to roofing companies and business contacts.
Where required or appropriate, recipients may request that outreach stop by replying to the message or contacting info@roofcommandcrm.com.
11. Data security
We use administrative, technical, and organizational safeguards designed to protect information. These may include authentication, role-based access, Row Level Security, company-level data separation, restricted API keys, HTTPS, backups, logging, and limited administrative access.
No internet-based system is completely risk-free. Users are responsible for protecting login credentials, using strong passwords, managing invited users carefully, and promptly notifying us of suspected unauthorized access.
12. Data retention
We retain account, CRM, homeowner, job, support, billing, prospecting, communication, and operational information for as long as needed to provide the service, comply with legal obligations, resolve disputes, maintain business records, enforce agreements, support backups, and operate security or audit logs.
If an account is cancelled or terminated, some records may remain in backups, audit logs, billing records, legal archives, or business records for a reasonable period.
13. User choices and rights
Depending on where you are located, you may have rights to request access, correction, deletion, portability, or limits on certain processing of personal information. To make a request, contact info@roofcommandcrm.com.
We may need to verify your identity, company relationship, account role, and authority before fulfilling a request. Some requests may be limited by legal, security, contractual, billing, operational, or backup requirements.
14. Cookies, local storage, and PWA features
RoofCommand CRM may use cookies, local storage, session storage, authentication tokens, or similar technologies to keep users signed in, remember language settings, operate the demo, support PWA/app installation behavior, preserve UI preferences, and support security and performance.
15. Children
RoofCommand CRM is intended for business use and is not directed to children under 13. Users should not provide information from children through the service.
16. Changes to this policy
We may update this Privacy Policy from time to time. The effective date will be updated when material changes are made. Continued use of RoofCommand CRM after changes means the updated policy applies.