Policies & Security
How we handle accounts, maps, and trust
Plain-language policies for an early product — written so you can actually read them.
This Learn More page expands on Program Policies with full long-form documents. If something conflicts as the product evolves, the posted Program Policies page is the canonical short form; each topic below links to the detailed policy.
Accounts
How MiTRYBE accounts work, what you’re responsible for, and how Weathertop Studios protects credentials through Firebase Authentication. Covers usernames, session security, and account suspension.
Privacy
What data we collect, how Firebase Auth and Firestore are used, and what we do not do with your preference map. Written for a Florida-first product that asks instead of surveilling.
Preference Map
Ownership of your answers and taste dimensions, how the map unlocks features, and your right to reset or revise. Your map is yours — not a product we sell.
Recommendations
Early Florida recommendations are seed archetypes with because-clauses — not a live venue database. Safety, dietary, and accessibility judgment stays with you.
Community Standards
Rules for future matching and friend overlaps: dimensional alignment, no harassment, and how Weathertop Studios may respond when standards are broken.
Security
High-level security practices, access controls, and how we think about incident response. Serious without security theater.
Terms of Use
The agreement between you and Weathertop Studios for using MiTRYBE: acceptable use, disclaimers, Florida context, and how terms may change.
Cookies & Local Storage
Transparency on cookies, browser storage, and the mitrybe-profile-v2 key that keeps your local run intact between sessions.