Your property research should stay under your control.

What we process

Account information

Your email address, authentication records, session information, and any display name you choose to provide.

Property and analysis information

The address you submit, the matched location and coordinates, orientation values, terrain samples, generated analysis, confidence notes, scoring details, and structured property evidence or free-text notes you choose to submit.

Terms acknowledgment

For newly created accounts, authentication metadata records the version and time of the Terms acknowledgment.

Usage protection information

Account-linked request timestamps used to enforce hourly and daily analysis limits.

First-party product measurement

The application does not include advertising or third-party analytics code. Fluxreading records limited first-party events in Supabase to understand registration and reading completion, report interactions, performance, cache use, content engagement, return use, sharing, and controlled interface experiments.

Event records may contain a pseudonymous account ID, random browser and session IDs, broad referral category, campaign label, public landing path, normalized page type, device class, experiment assignment, timing, token counts, cache status, and coarse interaction counts or score-change ranges. They do not contain the submitted address, coordinates, email, name, full referrer, report text, free-text property notes, satellite URLs, share token, or full share URL.

First-party HTTP-only cookies remember attribution for up to 30 days, a random browser ID for up to 30 days, and a session ID for 30 minutes. They are not used to follow activity on other websites. Global Privacy Control and browser Do Not Track are honored by the client tracker.

How the information is used

• Authenticate your account and protect private readings.
• Locate the submitted property and retrieve satellite and terrain context.
• Generate, stabilize, and score the property reading.
• Cache repeat analyses to reduce cost and unnecessary external requests.
• Automatically save completed readings and reuse your confirmed orientation and property details for the same property.
• Create an immutable share snapshot only when you request a share link.
• Prevent automated abuse and enforce usage limits.
• Measure product funnels, reading completion, performance and external-service use, content engagement, return use, and interface experiments.

Storage and retention

Authentication and application records are stored in Supabase. Analysis results are cached per account; the default finished-result cache lifetime is seven days and supporting evidence is normally reused for up to 30 days. Usage timestamps older than seven days are removed when the limiter runs.

Event-level product analytics are retained for up to 180 days. Long-term daily aggregate counters may be retained for up to 540 days. Analytics access is denied to public and ordinary authenticated database roles.

Each completed address is kept automatically as the current property reading until you delete it. Later orientation corrections and structured property details update that current record. Deleting a property also removes its associated share records; previously issued share links then stop working.

Sharing controls

Share links use high-entropy tokens; only a hash of the token is stored. Anyone who obtains an active link can open it, so treat it as sensitive.

You can set an expiration or revoke the active share link from your saved reading controls. Public share pages are marked noindex, but that is not a substitute for keeping the URL private.

Service providers

Fluxreading currently relies on the following services to perform the requested functionality:

• Mapbox ↗ receives the submitted address for geocoding and serves map or satellite imagery.
• USGS ↗ receives coordinate-based elevation requests.
• OpenAI ↗ receives the satellite images and structured context needed for visual analysis when AI analysis is enabled.
• Supabase ↗ provides authentication and database storage.
• Vercel hosts the web application and may process ordinary request and operational logs.

Your choices

• Do not submit an address you do not want processed by the providers above.
• Do not upload or enter documents, notes, or property details you are not authorized to use.
• Delete auto-saved properties from your account when you no longer need them.
• Use hidden-location sharing, choose an expiration, or revoke sharing at any time.
• Sign out to end the active browser session.

Self-service account deletion and full data export are not yet available in the current product interface. This privacy description should be reviewed again before a commercial public launch or whenever providers and retention behavior change.

Access, correction, deletion, and privacy requests

Depending on where you live and whether applicable legal thresholds are met, you may have rights concerning access, correction, deletion, portability, or use of personal information. We will verify requests before acting to protect the account and property data involved.

A public request address must be configured before broad commercial launch. Until then, use the existing controls to delete saved readings, revoke share links, and avoid submitting information you do not want retained.