Security and data handling
Roofpeace is built to keep roofing-company activity scoped to the correct workspace while giving field teams the information needed to act.
Updated July 15, 2026
01
Workspace access
Signed-in product routes require an authenticated session. Workspace membership and operator roles separate owner, manager, and field-rep actions, while administrative operations remain restricted.
02
Customer-safe surfaces
Territory checks and town scans return readiness and aggregate availability, not individual homeowner records. Property and CRM details remain inside authenticated workspaces.
03
Operational boundaries
Browser contracts expose the product information needed to work a route. Operational configuration, upstream provenance, and internal diagnostics remain on trusted services and administrative surfaces.
Production traffic uses HTTPS. Paid-plan checkout and payment-method management are handled by Stripe; Roofpeace does not store full payment-card numbers.
Property and storm signals can vary by territory and record. Roofpeace keeps unavailable fields visible and provides ranking context so teams can verify critical information before outreach or inspection.
Workspace owners can request data access, correction, export, or deletion. Security concerns and suspected account misuse should be reported to hello@roofpeace.com.