vvelara

Your data, with context.

Velara research preview · Updated October 20, 2026

Free calculations

Your insurance inputs are calculated locally in your browser. No email is required. Explicit source searches send coordinates, radius, dates and release version to Velara’s server, without persisting the unsaved point in analytics or sending it to a third-party provider. Other inputs are transmitted to Supabase only when you choose to save a revision. Saving source evidence stores its exact geographic query and observations against a tenant-owned immutable site revision.

Accounts and saved revisions

Supabase Auth processes your sign-in email and credentials. Saved inputs, assumptions and outputs belong to your workspace and are protected by tenant access rules. Revisions are immutable; account deletion and formal retention tooling are not available in this preview. Avoid submitting confidential client information during research use.

Shared estimates

Sharing is optional. A link grants anyone holding it access to the displayed premiums, state, asset type, phase, synthetic hazard scores and version provenance of one revision. Names, exact coordinates, capacities, replacement values and full snapshots are excluded. Premiums and public mock formulas may still allow project values to be inferred; treat a share link as confidential. Links expire within 30 days and can be revoked. Tokens appear in the URL fragment, which browsers do not send as a request path or referrer. We store only their SHA-256 hashes. Browser history, copied links and recipient screenshots can still retain them; revocation cannot erase existing copies.

Optional feedback

We store only the comparison choice, whether you used a paid premium or broker quote, whether coverage is similar, and the UTC day. Shared-page responses also reference the share record. We do not request names, email, policy numbers, documents, precise costs or free text. Feedback is unverified research, not market evidence. The preview retains feedback until deliberate administrative cleanup; there is no automated retention job yet.

Simple usage counts

First-party counters measure landing and estimator views, calculations, share creation and opening, and feedback submissions by UTC day. They are event counts, not unique visitors. Our analytics tables contain no IPs, user IDs, emails, cookies, referrers, full URLs, share tokens or insurance inputs. There are no analytics cookies or third-party trackers. Do Not Track and Global Privacy Control disable browser analytics events. Essential share records and explicit feedback submissions still occur when requested.

Infrastructure and limits

Hosting, authentication and database providers may process IP addresses and operational request logs independently of our minimal analytics tables. Public counters and feedback can be spoofed and are globally capped to limit stored data; stronger abuse controls and operational log retention need review before public deployment. Aggregate counters are retained until administrative cleanup. This application has not been publicly deployed.

Synthetic by design

Insurance premiums and demonstration-model indices in this preview remain clearly labeled synthetic fixtures. The separate NOAA historical hail archive contains real source reports; source verification does not validate each report, establish a loss probability or calibrate pricing. USFS context is modeled hazard potential, not an observed fire or current site probability. Synthetic premium fixtures are not insurance quotes, observed hazards, real market evidence or underwriting advice.

Try a free estimate →