ProxyLife
Privacy placeholder

Privacy structure for counsel review.

This placeholder outlines the intended data practices for the MVP. It should be reviewed and replaced with final privacy language before launch.

Operating standard

Structured placeholder for counsel review.

These pages establish product intent and user-facing structure. Final legal language should be reviewed before launch.

Account data

Profile, language, city, role status, and notification preferences support the product workflow.

Request data

Requests include structured scope, messages, media, proof, payment state, and review records.

Service providers

Core services include authentication, database, storage, payments, email, AI translation, and maps.

Access control

Private request media and messages are limited to participants and operations workflows.

Data categories

The privacy page should explain what the platform collects and why.

Account identity and contact details.
Requester and Proxy profile settings.
Request details, proof media, messages, translations, and moderation flags.
Payment, dispute, audit, notification, and email delivery records.

Controls and retention

Final policy should describe user rights and operational retention.

How users update profile and notification preferences.
How request participants access proof and message history.
How private files are stored and accessed through signed paths.
How deletion, export, legal retention, and safety exceptions are handled.

Related standards

Safety, platform rules, and legal placeholders are connected so users can understand the operating model without reading a wall of policy text.