TREXXER DEVELOPMENT DRAFT

FOR DEVELOPMENT AND TESTING ONLY
NOT FINAL PRODUCTION TERMS/POLICY

Development Privacy draft

Version: trexxer-dev-draft-2026-09-21

This describes the bounded development implementation for registration testing. It is not a final production privacy policy. Use test accounts and synthetic content; do not submit sensitive personal data.

Development data flows

Configured account registration and login use Supabase Auth. Registration sends the supplied email, password and acknowledgement of the configured Terms and Privacy versions and acceptance time. The app uses the Auth session to access the TREXXER API. The API can store an account profile.

Routes, recordings, drafts and anonymous activity can be stored locally on the device. Supported account sync or publication flows can send account-owned content to the backend. Signing in does not automatically upload or publish all local content. Location is used by supported map and ride features subject to device permissions.

Deletion testing

The account deletion flow requests backend account-data deletion and then clears account-bound local data and the local session. Acceptance of the request does not mean Auth identity deletion is complete. Operator completion and a minimal deletion receipt are separate. Account-neutral device content can remain. This draft does not promise a deletion deadline or define a production retention period.

Hosting and unresolved production matters

These static development documents are prepared for Cloudflare Pages hosting. Final legal identity, privacy contacts, retention periods and production disclosures require separate approval. No production privacy readiness is asserted.