Fetch
Privacy notice
Effective August 29, 2026
Sales and access inquiries
When you request access on this website, we store the contact and company details you provide, your message, submission time, and follow-up status so we can respond and arrange onboarding. These inquiries are accessible to authorized Fetch sales administrators. Submitting a request does not create an account or grant access to another company's workspace. We use short-lived, hashed request-rate identifiers to help prevent abuse. Contact privacy@getfetchroofing.com to request correction or deletion of an inquiry. Please do not include homeowner information, passwords, or sensitive claim details.
What the app stores
Fetch stores property pins, editable contact fields, canvassing attempts and opportunity stages, inspection and claim fields, optional project and collected values, notes, assignments, routes, follow-ups, territories, priority-score factors, saved storm-report snapshots, generated evidence cases, and generated drone-report records. Each signed-in member may save the name that homeowner reports should list as the first contact. Photos are stored in private object storage. Online JPG and PNG uploads are stored as the verified bytes supplied by the member, so embedded image metadata such as camera details or coordinates can remain; photos compressed through the offline queue are re-encoded and ordinarily do not retain the original embedded metadata. Members should remove metadata they do not want their authorized company workspace to retain. A timestamped activity log records important property, status, pipeline, follow-up, and evidence-report changes. Support communications can include the requester's name, contact email, company, issue details, attachments, status, and submission time.
Product reliability and outcome measurement
Fetch records a limited set of authenticated product events—such as app opens, storm-scan success and duration, report and evidence-case generation, routes, navigation launches, appointments, and recorded inspection outcomes—to measure field reliability and improve the workflow. Navigation events record that directions were launched for a workspace pin but do not copy the address or coordinates into product-event metadata. Event metadata is restricted and does not accept homeowner names, addresses, phone numbers, email addresses, notes, claim numbers, or photo content. Events remain associated with the workspace and acting member so authorized analytics can be scoped correctly; departing-member attribution is deidentified. Fetch uses these records for operations, pilot validation, and aggregate evidence-to-inspection calibration, not advertising.
Homeowner and contact information
Fetch does not automatically retrieve homeowner identities from public-record databases. Homeowner names, phone numbers, and email addresses are entered manually by authorized workspace members based on direct contact, permission, or another lawful source. Workspace members are responsible for entering and using contact information lawfully and honoring do-not-knock and do-not-contact instructions.
Location data
Fetch requests a one-time precise location when an authorized member opens the field map so it can start at the member's current area. If the member turns on live tracking, the app continues using device location while Fetch is open to follow the map, order nearby stops, and show recent team presence. Turning tracking off clears the saved live-presence coordinate, and stale live presence is cleared after approximately two minutes without an update. The web app, prepared native iPhone shell, and prepared Android Trusted Web Activity use location only while Fetch is open; none requests Always or background location or runs continuous background GPS. Fetch does not use location for advertising.
Notifications
If a member enables background alerts, Fetch stores that device's Web Push subscription or native APNs device token, alert coordinates, radius, and selected hail and wind minimums. Android Web Push is delegated through the browser that owns the verified Fetch host; the Android shell does not add Firebase or a separate FCM token. When the 24/7 scheduler is connected, the server checks public storm sources every five minutes and uses those settings only to deliver requested storm and follow-up notifications. Lock-screen notifications use generic wording and do not include homeowner names, property addresses, notes, claim information, or the member's saved alert coordinate. Alert deliveries are deduplicated and retry through a bounded outbox. Turning alerts off deactivates the registration; notification permission can also be removed in browser, Android, or iPhone settings.
Weather, maps, and address matching
The app requests weather, geocoding, and map imagery from third-party sources. Queries may include a map coordinate or address. Mapbox supplies the primary satellite and street map, with USGS/USDA and OpenStreetMap imagery available as a fallback. Address suggestions use the OpenStreetMap-based Photon service and may use the current map coordinate to infer nearby city and state context for a partial street address; submitted U.S. street addresses may be checked with the U.S. Census Geocoder, and dropped points may use OpenStreetMap reverse geocoding to attach a nearby address. Address matching does not retrieve homeowner identity. Before navigation, Fetch may recheck the entered address against those free address sources solely to warn when it appears materially separated from the saved roof pin. A member's preferred navigation app is stored only in that browser on that device and is not a company-wide setting; launching directions sends the saved pin coordinate to the selected maps provider. If live tracking is enabled while Fetch remains open, the current coordinate can also reveal the arrival actions when the device is near the active route stop. Address reports query NOAA/NWS/NCEI, Iowa Environmental Mesonet, CoCoRaHS, and, for Texas addresses, the Texas Water Development Board's TexMesonet. Fetch also archives storm reports and radar-cell snapshots it observes so later reports can show a timeline. Mapbox, Apple Maps, Google Maps, NOAA/NWS/NCEI, Iowa Environmental Mesonet, CoCoRaHS, TWDB/TexMesonet, OpenStreetMap/Photon, the U.S. Census Bureau, and USGS/USDA imagery services apply their own privacy practices.
Sharing and retention
Workspace data is shared with members authorized for that workspace and with infrastructure providers needed to operate the app. Fetch requires service providers that process user data for the service to protect it consistently with this notice and applicable privacy and security obligations. Each company workspace keeps separate properties, settings, evidence cases, drone reports, analytics, photos, invitations, and team access. Fetch does not sell workspace data or use it for third-party advertising. An evidence case freezes the selected property, saved public-weather report, workflow, inspection checklist, verified photo index, and activity history at generation time. A drone report freezes the selected verified-photo manifest, contractor-entered inspection observations, saved report-contact name, and exact address-storm snapshot; each report's SHA-256 integrity reference is verified before download. Deleted properties and photos are first moved to Recently Deleted so an owner or administrator can correct an accidental deletion; their private photo objects are not publicly accessible. Recently Deleted records, evidence cases, drone reports, and product events remain in private workspace storage until the workspace is permanently deleted; Fetch does not currently promise automatic purging after a fixed number of days. Pending invitation records expire after seven days; raw invitation secrets are never stored. In-app support requests are visible only to the Fetch site owner and are automatically removed 90 days after resolution; support email may remain as reasonably needed to resolve the request, protect the service, and meet legal obligations. Complete Fetch account deletion removes the identity's memberships across all companies, saved presence, notification registrations, consent records, and direct attribution; retained company business records are deidentified. Permanent workspace deletion closes access immediately and uses a retrying deletion job to remove workspace memberships, field records, evidence cases, drone reports, product events, invitations, consent records, plan records, and private photo objects. The separate public storm archive is not user or workspace data.
Your controls
Members can edit field records, turn off tracking, disable notifications, switch among companies where they have active membership, and initiate complete deletion of their Fetch identity across all company memberships from account controls. Deletion is blocked while the identity owns a workspace; every owned workspace must first be transferred to an active administrator or permanently deleted. Owners and administrators control roster membership, secure invitations, workspace filters, bulk exports, Recently Deleted recovery, and property or photo removal. The portable workspace archive includes structured records and a private-photo manifest, but not the photo files themselves; some history sections are preservation-only and its in-app restore is not a full provider backup. Deleting a Fetch account does not delete the separate ChatGPT account. The public account-deletion page explains each path. For workspace access, export, correction, or deletion questions, contact the workspace owner or administrator.
Security
Fetch relies on ChatGPT-authenticated identity headers, server-side role checks, workspace-scoped database queries, private object storage, expiring email-bound invitation tokens stored only as SHA-256 hashes, request-rate limits, no-store API responses, and an activity log for important changes. Security measures reduce risk but no internet service can guarantee absolute security. Do not share invitation links, exported reports, or downloaded archives with unauthorized people. Report suspected unauthorized access through the Support page and remove the affected member or invitation promptly.
Children
Fetch is a business service for adults and is not directed to children under 13. Workspace owners must not invite children or knowingly enter children's personal information into the service. If you believe a child's information was submitted, use the Support page so the record and workspace authority can be verified and addressed.
Changes and contact
Material changes to this notice will carry a new effective date and may require signed-in members to acknowledge the updated notice before continuing. The workspace owner is the primary contact for company-controlled field records. For product security, access, or privacy help, use the public Support page.
Important weather limitation
Fetch displays qualifying records returned by its selected public sources for the requested area and rolling 365-day window, but no public archive captures every hailstone or guarantees complete geographic coverage. The map starts at 0.75-inch hail and 50 mph wind. Address reports include hail from 0.50 inch and wind from 50 mph, and only return point reports, radar signatures, or archived swaths within 1.0 mile of the property coordinate. The hard one-mile geodesic zones drawn around 1-inch-or-greater radar signatures visualize that distance rule. A star marks the episode's maximum-size signature center, while dark-to-light shading encodes distance from that point; neither the star nor the shading is a measured impact, damage, or hail-intensity swath. Radar guidance and preliminary storm reports do not prove that hail, wind, or damage occurred at a specific structure and should not be treated as an insurance or engineering determination.
Publisher and contact
Fetch is operated by The Cross & Company LLC.
2500 Dallas Hwy, Suite 200Marietta, GA 30064
United States
Phone: (470) 652-0023
Support: support@getfetchroofing.com
Privacy: privacy@getfetchroofing.com
Security: security@getfetchroofing.com
Fetch uses collected information to provide, secure, support, and improve the service—not to sell personal information or build advertising profiles.