Legal document versions

Last updated 2026-09-29

Every version of the agreements that govern the Cubre application. If you are looking for the version you accepted, its identifier is shown in the application under Settings → Workspace → Agreement, and it matches an entry here. When a new version is published, an admin of your workspace is asked to accept it in the application; everyone else is told it is waiting.

Application Terms of Service

About 2026-09-11. For one day, the signup form recorded acceptance of a version identifier before an application agreement existed. The link on that form pointed to our Website Terms of Use — a document that governs this website and expressly does not govern the Cubre application.

We are not going to pretend otherwise. If your account records 2026-09-11, you have not accepted an application agreement, and we will ask you to accept the current one. Nothing was enforced against anyone on the strength of that record, and nothing will be.

What changed in 2026-09-29. The Data Processing Addendum gains Location services: the outside services the application sends location information to — Google for address suggestions and geocoding, the U.S. Census Bureau, Open-Meteo, Zippopotam.us, the U.S. National Weather Service, and the map images your staff’s browsers request from OpenStreetMap and, on the map used to confirm where a roof report is ordered, Esri — with exactly what each receives. We do not treat them as subprocessors: the Addendum does not bind them. The Addendum also names Cloudflare Turnstile, which checks public-form submissions for bots. The Addendum’s thirty days’ notice — before a subprocessor is added or replaced — now also applies before we add a location service or a bot check, and before we add to what a service you connect, a location service or a bot check receives; a new service you connect is described in the Addendum before it is offered, and receives nothing until you connect it. Terms §12 gains the Google Maps notice. Terms §16.4 and DPA §7 now say that messaging-consent and opt-out records — including proof that someone originally agreed to receive messages: the communication-consent acknowledgement in contracts signed on Cubre’s service-contract template — are kept for five years after your workspace is deleted, and longer only if we have been told that a claim about them is pending, to establish or defend claims about messages sent before deletion; that an administrator of a former workspace can ask us for its records; and that, to verify such a request, we keep the email addresses of the workspace’s administrators with those records for as long as the records are kept.

These are changes to the application itself, not only to the text:

• Esri satellite imagery is new. It appears on the map used to confirm where a roof report is ordered, from this release.
• OpenStreetMap map images now reach your staff’s browsers. Until this version the application’s security settings blocked them, so those maps showed no map at all.
• Consent and opt-out records are now kept after a workspace is deleted. Before this version they were deleted with the workspace.
• Administrators’ email addresses are now kept after a workspace is deleted, with those records and for as long as they are kept, so that a request for them can be verified.
• Open-Meteo now receives only a place name containing no numbers — so never a ZIP code or a numbered street address.
• Public-form bot checks no longer send the submitter’s IP address from our servers to Cloudflare; only the check’s token.
• Public pages at /go/ now show the bot check, so visitors’ browsers contact Cloudflare there too.
• The weather widget no longer sends a job’s name to the location services when the job has no address.

Three changes about the payments you collect. Terms §6.5 (now titled “Processing fees”) and the Fee Schedule now cover a fee you add to a bank payment as well as a card surcharge, and §6.5 makes you responsible for the law that applies to a bank processing fee: the application does not check it. §16.5 now lists §6.5 among the sections that survive termination. And Terms §6.2, the Refund Policy §2a and the Fee Schedule now say that a refund returns any processing fee your customer paid — all of it on a full refund, and the same share of it on a partial refund. Terms §6.2 and the Refund Policy §2a also say that if you refund outside the application — for example in your Stripe Dashboard — we return that share of the fee for you, from the same account, and retry it if Stripe refuses. That sentence does not survive termination: §16.5 now excepts it from §6.2. The Fee Schedule’s prices are unchanged.

What changed in 2026-09-24. The Terms gain one paragraph in §14 (Intellectual property): Xactimate® and EagleView® are named as their owners’ registered trademarks, and Cubre states it is not affiliated with, sponsored by, or endorsed by either. The Data Processing Addendum now lists, under “Services you connect”, Google Drive (importing files you choose) and exactly what EagleView receives when you ask for a price or order, upgrade, answer or cancel a measurement report — including insurance-claim details you choose to enter for a claims-ready report — and what we keep of it; §2 lists insurance-claim information (including claim notes and carrier estimate documents you upload) as a category we process. The Fee Schedule and Refund Policy are unchanged and re-listed only so every Terms version has the copy accepted with it.

What changed in 2026-09-22. Terms §6.2 and the Fee Schedule now say the $15 dispute fee applies whether or not you win a dispute (it had said “returned if you win”; the platform stopped returning it on 2026-09-16). Terms §16.4 and DPA §7 now state how long records are kept after a workspace is deleted: activity entries naming your customers go with the workspace, account-security entries are kept up to about twelve months from when each was recorded, and deleted data can persist in our encrypted backups for ordinarily about fourteen days. The DPA states the security-log retention as our own choice rather than a legal obligation, because it is one. Nothing else changed; the Fee Schedule and Refund Policy are unchanged and are re-listed only so every Terms version has the copy accepted with it.

Data Processing Addendum

Fee Schedule

Superseded fee schedules are archived here as well, so you can see what a price was and when it changed.

Refund, Dispute & Cancellation Policy

This policy is part of the Application Terms, so a copy is kept for each version of the Terms it was accepted with.

Other documents

The Website Terms of Use and Privacy Policy carry a last-updated date rather than a version identifier, because they are not part of the application agreement and acceptance of them is not recorded per account.

Questions about a version: support@cubre.app