Privacy Policy
Last updated 17 November 2026
This policy explains what personal information RoofHermit ("we," "us," or "our") collects when you use the RoofHermit websites and web app and our iOS and Android apps (the "Service"), how we use it, who we share it with, and the choices you have.
Information we collect about you
Account information. We use Clerk for sign-in. When you create an account, we receive your email address, your name if you give it, and which sign-in method you used: Sign in with Apple, Google or Microsoft, or a code sent to your email. If you use Apple's "Hide My Email," we receive a relay address instead of your real one.
Subscription information. We use Stripe for payments. Stripe collects your card and billing details directly, and we never receive your card number. From Stripe we receive identifiers for you and your subscription, your plan, its status, and its renewal and end dates. When a free trial starts, we also keep the fingerprint Stripe gives your card, a code that identifies the card without revealing its number, so that each card gets one trial.
Preferences you save. If you change a setting that follows you across devices, such as your default area or map layers, or save an area to reopen later (its name, scope, any boundary you drew and the filters you chose), we store it with your account so that the web app and our iOS and Android apps all use it. We also store addresses you save, their property IDs, and when you saved them, so your saved properties follow your account across devices. Only you can see your saved areas and properties.
Hail alerts. If you turn on hail alerts, we store your choice (your saved places, or anywhere) and, for each browser or app you turn them on in, where to send the alerts. For a browser, that is the push address your browser gives us and its encryption keys, with the browser's user agent (its name, version and operating system); your browser's maker (such as Google, Apple or Mozilla) delivers the alert. For our iOS app, it is the push token Apple gives the app, and whether the app is a development build; Apple delivers the alert. For our Android app, it is the push token Google's Firebase Cloud Messaging gives the app; to give it, Firebase also registers an installation ID for the app on your device. The app registers them only when you turn hail alerts on, and Google delivers the alert. We keep at most 10 browsers and 10 installs of each app for each person, and adding another drops the oldest. We record the storm days we alerted you about, so you get one alert per storm. Signing out of an app removes its push token, and the Android app also has Firebase delete its token and installation ID; in a browser, turning alerts off removes its push address (signing out of the web app does not). We also delete a push address or token that its push service reports is no longer valid, or that keeps failing. Deleting your account deletes all of this.
Notes you record. If you save a note at an address, we store it with your account: the outcome you choose, any text you write, when it happened, and the address. Notes are private unless you log them in a team, bring them into one, or share a visit with one. Current members of that team can read those visits, and, if the team belongs to an organization, so can its owner and managers; everyone on its other teams can see them on the map and in a property's history, with who logged each, when, its outcome and its note. A note can hold information about other people, such as a resident's name or phone number. You decide what goes in your notes, and you are responsible for having the right to record it.
Field work and teams. We store prospect contact details you enter, opportunity stages, assignments, do-not-contact flags, follow-up tasks and due times. Team records are visible to all current members of the team. We keep team memberships, display names and hashed, expiring invitation codes. When whoever runs a team invites someone by email, we keep that email address with the invitation, so that they can see who has not joined yet, send the invitation again or revoke it. We delete the address when the invitation is used or revoked, or 30 days after it expires. While you are on a team, the visits you record on the web and in the iPhone app go to that team and are the team's: they stay with it if you leave, and you can change or delete them only while you are on it. Joining a team does not share the notes you recorded before, or your saved properties; we ask whether to bring the visits you logged on your own into the team, and they become the team's only if you choose to. We record that someone left or was removed from a team, with the name they went by there, so that the team does not take them back automatically and the visits they recorded for it keep their name, until the team or their account is deleted. A team's lead can add the team to an organization, a company over several teams: its owner and managers see each of its teams' members, requests to join, visits and contact details, and run each team as its lead does. An organization's owner can let anyone signed in with a verified email address at the company's email domain (never a free email service) ask to join the organization, or join it at once: those people see the organization's name, and its owner and managers see the name and email address of each person who asks.
Zapier and CRMs. You can connect Zapier, or a CRM we support (JobNimbus or AccuLynx). For Zapier, we make a key for you to give it and keep the web addresses it gives us to send to. For a CRM, we store the API key you give us, encrypted. We then send what you set up. To Zapier: each visit you record (the address and its location, the outcome, your notes, when, and your name and team), each property you save, and hail at your saved properties, with the year of the roof record we estimate roof age from. To a CRM, when you press Send or turn on Send automatically: the property's address, its roof age and hail, the latest visit's outcome and notes, and any contact name, phone number and email address entered for it. On a team, the visits its members record also go, with the same details, to Zapier and the CRMs that the team's lead has connected, and in an organization to those its owner has connected. A team's lead, and its organization's owner and managers, can download the team's visits, with their notes, as a file. So what you write about a visit, and contact details entered for a property, can reach services that your team's lead or your organization's owner chose. Zapier and the CRM handle what they receive under their own terms and privacy policies, which we do not control.
Offline visits. Pending visits stay in account-specific storage on your device until they sync or you remove them. Signing out keeps unsynced work for that account. Deleting an account attempts to remove this device's pending copies, but cannot remotely erase an offline copy on another device; clear that device's app or browser storage to remove it.
Devices and sessions. Clerk keeps a record of each device you sign in on: the kind of device and browser or app, its IP address, the approximate location (city and country) that Clerk works out from that IP address, and when it was last active. We use this to keep you signed in, to enforce the device limit, and to list your devices on your account page so you can sign them out.
App integrity. Our iOS app uses Apple's App Attest to show our servers that its requests come from the genuine app on a real Apple device. The app creates a key on your device, which never leaves it, and Apple certifies it. We store the key's public half, the identifier Apple gives it, a counter that rises each time it is used, whether the app is a development build, and when the key was made and last used, with your account, for at most 10 installs per person, dropping the least recently used. The key contains no personal information. Deleting your account deletes them.
Usage and technical information. When you use the Service, Cloudflare (our network provider) and our servers receive standard request information: IP address, time, the address requested, and browser or app details. For map data, the address requested shows which part of the map you were looking at.
Speed measurements. The web app and our iOS and Android apps report anonymous measurements of how well they work: how long things took to appear, such as the map, map data, a search, a property's card or its roof history, in rounded milliseconds, and how long any slow frame took to draw. They also count how those waits, and a logged visit's trip to our servers, ended: shown within a second, shown later, failed, or given up, with the longest of each. We also count the reports by kind of device. The web app adds the browser's standard page-speed measures and any script error, with the script's file name and position, the error's message with quoted text and numbers removed, and which release of the web app was running. The iOS and Android apps add how smoothly the map moved; the iOS app adds Apple's daily measures of how long the app took to open and to show the map's roof ages, how long it stopped responding, how smoothly it scrolled, and how much of the time it ran at each strength of cellular signal, in bars; and the Android app adds Android's own measure of how long it took to open and to show the map's roof ages. Each measurement carries only fixed labels: phone, desktop, iOS or Android; whether the map was narrowed to a storm or a Hot Spot; whether the answer came from your device, our network's cache or our servers; the screen's refresh rate; and, for the counts of how waits ended, the kind of connection at that moment: Wi-Fi, cellular, a poor connection, or none. They never include your location, addresses, what you searched for, or an identifier for you or your device. The web app sends them when you leave or hide a page, and keeps the counts of how waits ended in your browser until it can; the apps keep them on your device and send a small batch at most every half hour, never in Low Power Mode or Low Data Mode on an iPhone, or with Battery Saver or Data Saver on in Android. We add the measurements into totals as they arrive and write script errors, and the counts of waits that were slow, failed or given up, to our server logs; none of it is stored with your account.
Location. If you turn on "My Location," your device uses its location to show where you are and to center the map. Your location stays on your device: we do not receive or store it. (Clerk's approximate location from your IP address, under Devices and sessions, is separate.) The map then asks for data about the area on screen, which our servers see like any other map request.
Messages. If you email us, we keep your message and our reply.
Cookies and local storage. Clerk sets cookies that keep you signed in, and Cloudflare sets cookies for security and access control. The web app stores the version of the data it last loaded in your browser, so that the map opens faster. We do not use advertising or third-party analytics cookies.
The Service is not for anyone under 18, and we do not knowingly collect information from them.
Information about properties
The Service shows roof records (the building permits that cities and counties publish) and county assessor records: property addresses, parcel and record numbers, dates, types, building facts and values, and the agencies' own descriptions. We do not obtain owners' names or contact details from these public-record inputs. Contact details you enter for a property, and your saved properties and visits, are linked to your account or your team. If you believe a record is inaccurate, tell us at [email protected].
How we use information
- to provide the Service, keep you signed in, and enforce the device limit;
- to process payments and manage your subscription;
- to send messages about your account, such as sign-in codes, receipts, renewal reminders, and notices of changes to our terms (we do not send marketing email unless you agree to it);
- to keep the Service secure, prevent fraud, account sharing, and scraping, and enforce our Terms of Service;
- to understand and improve how the Service performs;
- to comply with the law.
We do not sell your personal information, share it for cross-context behavioral advertising, or use it to build advertising profiles.
Who we share it with
We share personal information only with service providers that process it for us under contract, and only as much as they need. These are the kinds of providers we use:
| Kind of provider | What it does for us |
|---|---|
| Sign-in | sign-in, sessions, and sign-in emails |
| Payments | payments, invoices, receipts, renewal reminders, and tax |
| Network | network delivery, security, caching, search at the network edge, and storage of encrypted database backups |
| Hosting | the servers that run the Service and its database |
| Monitoring | performance monitoring, server logs, and our team's queries of our own database to run and secure the Service |
| Team messaging | telling our team about new accounts and subscription changes, with your email address and plan, and, for a new account at a company's email domain, how many accounts that domain has |
| Push notifications | delivering hail alerts to the Android app |
If you choose Sign in with Apple, Google or Microsoft, that company also knows that you signed in to RoofHermit, under its own privacy policy.
Zapier and a CRM are not our service providers. They receive information only when you, your team's lead or your organization's owner has connected one, as described under "Zapier and CRMs" above.
We may also disclose information when the law requires it, to protect the rights, property, or safety of our users, the public, or RoofHermit, or as part of a merger, acquisition, or sale of assets. In that last case, this policy will continue to apply to the information.
We and our providers store and process information in the United States.
How long we keep it
- Account information, saved preferences, properties and areas, and device information: until you delete your account or sign a device out.
- Push addresses, push tokens, Firebase installation IDs and App Attest keys: until they are removed as described above, or you delete your account.
- Notes you recorded on your own: until you delete them or delete your account. Private prospects and tasks are deleted with the account.
- Team records: visits logged in a team, brought into it or shared with it, and the team's prospects, contact details and tasks, remain with the team when a member leaves or deletes their account; current members can correct contact details and mark opportunities lost. After a member's account is deleted, the visits they logged there carry no name, and their recordings are deleted with the account. If the team's lead deletes their account, the longest-standing member becomes its lead; when no member is left, the team and its records are deleted.
- Billing records: as long as tax and accounting law requires. Stripe keeps invoices, and we keep the identifiers that link to them, along with a record that the account was deleted. Card fingerprints from free trials are kept after an account is deleted, only to tell whether a card has had a trial.
- Server logs: only as long as we need them for security and troubleshooting. The copies in our monitoring service are deleted after 14 days.
- Database backups: encrypted, and replaced as they rotate, so information removed from the database is gone from backups within about 13 months. We use backups only to recover from a failure.
Your choices and rights
- Delete your account from your account page on the web (Delete my account) or in the iOS or Android app's settings. Deleting your account cancels your subscription, signs out every device, and deletes your account information, saved preferences, properties and areas, and the notes you recorded on your own, except the billing records described above. Visits you logged in a team stay with the team, without your name.
- Sign out devices from your account page.
- Access, correct, or get a copy of your personal information, or ask us to delete it, by emailing [email protected].
We offer these rights to every user, wherever they live. We will confirm your request, may need to verify your identity, and will respond within 45 days. If we decline a request, you can appeal by replying to our answer, and we will explain the outcome. We will not treat you differently for exercising your rights.
Security
We protect information with encryption in transit, encrypted backups, restricted access to our servers and database, and providers with strong security practices. No method of transmission or storage is completely secure.
Changes to this policy
We will post changes on this page and update the date at the top. If a change is material, we will tell you by email or in the Service before it takes effect.
Contact
RoofHermit · [email protected]