Privacy Policy

This Privacy Policy describes how Weathertop Studios collects, uses, stores, and shares information when you use MiTRYBE. Our product thesis is Don't guess. Ask. That means we prefer structured answers you choose to give over silent inference from surveillance. It also means we try to explain our data practices in plain language instead of hiding them behind legalese alone.

MiTRYBE is a Florida-first matching layer for people, places, and products. Early versions focus on questions, a personal preference map, and seed Florida recommendations. Privacy commitments here apply to that product surface. Related policies include Accounts, Preference Map, Cookies & Local Storage, and Security.

1. Scope

This policy covers information processed through mitrybe.com and MiTRYBE-related client applications operated by Weathertop Studios. It covers authenticated use, local-only browser use, contact form messages, and support emails. It does not cover third-party websites you visit after leaving MiTRYBE, including venues mentioned in recommendation archetypes, or other Weathertop Studios products unless those products expressly adopt this policy.

If you are located outside Florida or the United States, you understand that Weathertop Studios operates primarily with U.S.-based cloud infrastructure (including Google Firebase / Google Cloud) and that your information may be processed in the United States.

2. Definitions

"Personal information" means information that identifies or can reasonably be linked to you, such as email address, name, Firebase user ID, or IP address when stored with identity."Preference data" means question answers, derived dimension scores, unlock progress, and related explanations."Service providers" means vendors that process data on our behalf, including Google Firebase Authentication and Firestore. "Aggregated or de-identified data" means information that cannot reasonably be used to identify you.

3. Information we collect

3.1 Information you provide

When you create an account, we collect credentials and identity fields needed for Firebase Authentication (typically email address and, if you choose Google sign-in, the Google profile identifiers Google permits us to receive). When you answer questions, we collect your choices and any optional free-text if a question type later allows it. When you contact us, we collect the contents of your message and the topic you select.

We intentionally avoid culture-war or sensitive demographic bait as launch question content. Preference questions are designed to illuminate decision dimensions (for example, food and local-life tradeoffs), not to harvest protected-class dossiers for advertising.

3.2 Information from authentication and cloud services

Firebase Authentication stores authentication state and issues tokens. Firestore may store account-linked documents such as profile settings, answer history, feature unlock markers, and timestamps. Google, as infrastructure provider, processes this data under its terms and our configuration. We configure access rules intended to keep user documents readable and writable only by the owning authenticated user and by authorized Weathertop Studios operators for support and integrity.

3.3 Information stored on your device

MiTRYBE uses browser local storage (notably the mitrybe-profile-v2 key) to persist a working preference profile so refresh does not wipe your run. That store may include answers, recommendation seed selections, and UI state. It lives on your device until you clear it or reset in-product. Details are in the Cookies & Local Storage policy.

3.4 Technical and usage information

Like most web products, our hosting and analytics stack may receive IP address, browser type, device type, referring URL, pages viewed, and approximate timestamps. We may use this information to keep the service reliable, debug errors, understand which question packs people finish, and detect abuse. We do not need a clickstream personality dossier to operate MiTRYBE; the preference map is the primary personalization signal, and it comes from answers you gave.

4. How we use information

We use information to:

• Authenticate you and maintain sessions securely.
• Build, display, and revise your preference map and unlock product features as you answer.
• Generate because-clause explanations for seed Florida recommendations.
• Provide support, respond to contact requests, and improve question quality.
• Protect security, prevent fraud, and enforce Terms and Community Standards.
• Comply with law and respond to lawful requests when required.
• Develop future matching features that use dimensional overlap rather than surveillance guesswork—always subject to additional notice when those features launch.

We will not sell your preference map as a standalone product. We will not use early MiTRYBE as a covert political profiling tool. If advertising products arrive later, they must be consistent with the thesis: show only what would actually interest someone based on an honest map, not a barrage of lookalike guesses.

5. How we share information

We share information with service providers that help us operate MiTRYBE, primarily Google Firebase / Google Cloud for authentication, database, and related hosting. Those providers may only use the data to provide services to us under contractual and policy constraints.

We may share information if you direct us to (for example, future export or friend-overlap features you enable), if required by law, or if needed to protect rights, safety, and integrity. In a merger, acquisition, or asset transfer involving Weathertop Studios, account and preference data may transfer as part of the business, subject to this policy or a successor policy with notice.

We may share aggregated or de-identified statistics (for example, how many Florida users completed a question pack) that do not identify you.

6. Preference map and special handling

Your preference map is personal and revisable. You can reset answers from product controls when available. Ownership and reset rights are detailed in the Preference Map Policy. From a privacy perspective, preference data is treated as personal information when linked to your account or device.

Because MiTRYBE asks structured questions, the map can feel intimate even when individual answers are mundane. We design access so other users do not see your full map by default. Future matching will emphasize overlaps on dimensions relevant to a decision—not a public feed of your entire taste profile.

7. Recommendations and third-party places

Early recommendations are curated seed archetypes, not a live venue database. Clicking outward to a restaurant website or map provider is governed by that third party's privacy policy. See Recommendations.

8. Retention

We retain account and preference data while your account is active and for a reasonable period afterward as needed for backups, dispute resolution, security logs, and legal obligations. Local storage remains until you clear it. Support emails are retained as needed to resolve issues and improve operations. When you request account closure, we delete or de-identify personal information we control, subject to legitimate retention needs described here.

9. Security

We use administrative, technical, and organizational measures appropriate to an early web product, including Firebase Authentication, transport encryption (HTTPS), and access-limited operator practices. No method of transmission or storage is perfectly secure. High-level practices and incident response posture are described in our Security Policy.

10. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, or export personal information, or to opt out of certain processing. MiTRYBE is built to make correction easy for preference data: re-answer questions or reset the map. For account deletion or privacy requests, email privacy@mitrybe.com or use Contact Us. We may need to verify your identity before fulfilling a request.

You can clear local storage in your browser to remove mitrybe-profile-v2 data on that device. Clearing local storage does not automatically delete cloud account data.

If we use non-essential cookies or analytics that require consent in your region, we will present appropriate controls. Essential storage needed to keep a signed-in session or local run functional is described in the Cookies policy.

11. Children

MiTRYBE is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child provided information, contact privacy@mitrybe.com and we will take appropriate steps to delete it.

12. Do Not Track and automated decisions

Some browsers offer Do Not Track signals. There is no consistent industry standard for responding; our personalization is primarily answer-driven. Feature unlocks and recommendation ranking use your preference map and seed logic—not hidden credit-style scoring against third-party dossiers. You can revise inputs that feed those outcomes.

13. International users and Florida context

Weathertop Studios builds MiTRYBE with Florida as the first field: statewide food and local life patterns inform seed content. Privacy expectations still apply uniformly to users who join from elsewhere. Product copy may reference Florida humidity, late dinners, or regional pace without implying we track your physical location by default. If we later request precise location for a feature, we will ask.

14. Changes

We may update this Privacy Policy as the product evolves. The "Last updated" date at the top will change when we do. Material changes will be posted on this page; continued use after the effective date constitutes acceptance where permitted by law. If law requires opt-in consent for a new use, we will seek it.

Questions? Contact privacy@mitrybe.com or visit /contact. Weathertop Studios · MiTRYBE · mitrybe.com.