Skip to main content
09 Privacy & data use

Privacy, by architecture.

Weight99 is designed to deliver its core comparison without an account, saved profile or personal-weight history. This page describes the current pre-launch beta behavior rather than promising features or data practices that are not connected today.

PRE-LAUNCH STATUS

Operational transparency now. Final legal sign-off still required.

This beta page documents the product as currently implemented. Formal operator/contact details, jurisdiction-specific notices and final legal review must be completed before Weight99 is treated as publicly launched.

ACCOUNTLESS CORE

No account is required for the comparison.

The live product does not currently provide user accounts, cloud profiles or a saved personal comparison-history feature.

What you enter
Weight, display unit and optional country, age and source-defined sex-reference context used to resolve a comparison.
Application history
Weight99 does not currently attach those comparison inputs to an account or intentionally persist a personal comparison history in an application database.
Result storage
The current public Compare and share flows do not provide a user-facing saved-result account or cloud-history feature.
URL STATE

Comparison inputs can appear in the URL.

Weight99 currently uses GET query parameters for the Compare experience so the state can be reproduced and corrected without an account.

A comparison URL can contain values such as weight, unit, country, age and sex-reference selection. That means those values can appear in your browser history, a copied URL and ordinary hosting/request logs.

Do not paste or forward a full comparison URL unless you are comfortable sharing the values visible in that URL. Weight99 share-card and Visual Story assets are generated from an allowlisted result/share contract instead of publishing the intake form as a public share payload.

SHARING

Share the result, not hidden intake state.

The current PNG/share flow is intentionally separate from account storage and public-result URLs.

PNG generation
Share cards and Visual Story images are rendered in the browser from the current authoritative share/story data contract.
Native sharing
If supported, Weight99 hands generated image files to the browser or operating system share sheet. The destination app or service then applies its own privacy terms.
Shared context
A shared asset can intentionally contain the displayed weight, resolved comparison reference, result qualifier, source/reference context and other visible facts selected for that asset. It is not intended to include unrelated hidden personal fields.
Recipient activity
Weight99 does not currently claim that a successful native-share handoff proves a public post, recipient open, activation or reshare.
ANALYTICS

No external analytics transport is attached today.

The current compare/share/story instrumentation is a browser-local semantic event seam, not a connected analytics provider. The same provider-neutral seam now also records coarse Explore hub entry/path categories.

The event contracts allow only coarse product semantics such as compare surface and rendered success/error outcome; Explore hub entry and broad path category; and share/story surface, artifact type, aspect ratio, bounded visible-card count, presentation, customization and action/outcome categories. They are designed not to carry raw weight, age, country/population identity, percentile, result/story IDs, destination URLs, query strings or user/session identifiers.

The current emitters perform no analytics network request, persistence, cookie access or user/session-ID work. If Weight99 later connects an analytics, advertising or consent provider, this page must be updated to describe that real behavior and any consent choices required for the markets served.

INFRASTRUCTURE & THIRD PARTIES

Normal web infrastructure still processes requests.

Accountless does not mean that no technical data exists anywhere in the delivery path.

Hosting
Weight99 is delivered through web-hosting infrastructure that can process ordinary request metadata and operational/security logs. Query-string comparison values can therefore be present in request URLs.
Browser storage
Your browser can independently retain normal history, cache or downloaded files according to your browser/device settings.
External sources
Links to data providers, licence pages or other external sites leave Weight99. Those sites control their own cookies, logging and privacy practices.
AGE & SENSITIVE CONTEXT

Weight99 does not infer demographic identity.

Optional demographic fields exist only to choose a source-defined comparison reference when the production data supports it.

Weight99 does not infer sex-reference or age from names, images, location, language or other proxies. The current comparison models are adult-oriented; under-20 comparison is accepted only where an exact production route explicitly supports that age, currently including Australia ages 18–24.

These references are descriptive statistical contexts, not profile identities, diagnoses or health classifications.

WHEN THIS MUST CHANGE

New storage, analytics, ads or accounts require a policy update.

Weight99 should not silently add a persistence provider, identity layer, third-party analytics transport, advertising tracker or materially different share/public-state behavior while this page continues to describe the current beta architecture.