← OddMissions

Privacy Policy

Draft for human legal and policy review. The public beta must remain closed until the operator reviews and finalizes these terms, identifies the legal operator, and sets an effective date.

Draft scope: the San Antonio free beta. Operator identity, effective date, applicable privacy rights, and retention schedule require human review. Questions and account/data requests: usecryptomap@gmail.com.

Supabase handles account email, authentication credentials, sessions, and recovery. The application stores profile names, bio, avatar URL, XP, levels, account status, mission history, listings, assignments, completion notes, messages, reports, and moderation records.

Profiles and mission listings are public. Do not publish home addresses, sensitive information, or phone numbers. A required approximate mission pin is validated within the San Antonio service area and rounded to neighborhood precision before storage. Public area labels are generated; use private messages for exact meeting details. Participants can see their private mission conversations; authorized moderators can review them for safety. Reports and moderation records are restricted.

First-party analytics record signup, mission creation, acceptance, submission, approved completion, and at most one active-day event per signed-in account per UTC day. Events include an account identifier, timestamp, and mission identifier where relevant. We use these to measure marketplace activity and retention. There are no advertising trackers or payment processing in this beta.

Authentication uses essential cookies/browser storage. Hosting and authentication providers may keep operational security logs. Map tiles come from OpenStreetMap and requests disclose network information to its tile provider. Remote avatar images may also be fetched from their provider. Review provider contracts, subprocessors, international transfers, and tile-provider policy before launch.

We use access controls to limit data access. No service can promise absolute security. Email support for access, correction, or deletion requests; the operator must establish a response process and reviewed retention/deletion schedule before launch. Required safety or legal records may need different retention rules.

Do not submit sensitive personal data or information about children. The beta is intended for adults. Changes to this policy and any additional consent requirements must be reviewed before publishing.