Privacy Policy

ClaimForge is a software tool for roofing and restoration contractors. It assists with reviewing insurance estimates and preparing supplement documents. This policy explains, in plain language, what information we collect and what we do with it.

This policy describes our current practices. It does not claim any certification, audit, or regulatory approval.

When you request a demo or contact us, we collect the business details you type in: first and last name, company name, your role, business email, business phone, company website, primary operating state, company type, how often you work insurance roofing claims, your monthly estimate volume, and a free-text description of what you need help with.

We also store the fact that you agreed to be contacted, the version of the consent wording you agreed to, and the date and time you agreed.

We do not ask for claim documents, policy information, or property-owner information on our marketing or contact forms. Please do not submit those through a public form. If you send them anyway, we may delete them.

If you arrive from an advertisement or a campaign link, the link may contain campaign identifiers (for example utm_source, utm_campaign, and advertising campaign, ad set, and ad identifiers). We read these from the web address and keep them for your browser session only, so we can tell which campaign a request came from.

These identifiers are stored in your browser’s session storage as first-party data. They are cleared when you close the tab. We do not use them to build a profile about you.

We do not currently run any third-party advertising or analytics tracker on our public pages. If we add one in the future, it will only run after you are asked for consent and you agree, and it will never receive claim contents, line items, property data, policy data, carrier data, or free text.

If you create an account, we store your name, email, role, and company membership so the product can work and so your team sees only your company’s records.

When you use the product, we store the estimate files and photos you upload, the notes you add, and the analysis output the tool produces. This content belongs to your company and is restricted to your company’s users and our administrators.

For purchases, payment card details are entered on our payment provider’s checkout page — not on ClaimForge, and we never receive or store your full card number. We store a payment record containing the checkout session identifier, the amount, the status, and the date, so we can unlock what you paid for.

We use third-party service providers to operate: Base44 for application hosting, database, file storage, and email delivery; Wix Payments (offered as Base44 Payments) for checkout and payment processing; and third-party AI model providers to generate estimate-review output from the documents you upload.

Uploaded estimate documents and photos are transmitted to an AI model provider in order to produce the review output. If your ad-campaign integrations are enabled in the future, campaign identifiers may also be shared with the relevant advertising platform — never claim contents.

Lead and contact records are kept until you ask us to remove them, or until they are no longer useful for follow-up.

Account, claim, and payment records are kept for as long as your account is active, and afterwards where we need them for financial records or to resolve a dispute.

Attribution identifiers are kept only for the browser session, as described above.

You can ask us to show you the information we hold about you, correct it, delete it, or stop contacting you. Use the contact form on our Contact page and tell us what you would like done.

We will confirm your request and act on it within a reasonable period. If we cannot delete something — for example a payment record we need to keep for accounting — we will tell you why.

You can also delete your own account from the Account screen inside the product.

We restrict access to records by company, require authentication for product screens, verify payment notifications before granting access, and limit administrative access. No system is perfectly secure, and we do not claim that it is.

If we change this policy we will update the version below. Lead records store the policy version that was in effect when the record was created.