Accounts Policy

This Accounts Policy explains how MiTRYBE accounts are created, used, secured, and—when necessary—suspended or closed. MiTRYBE is a product of Weathertop Studios. It is built for a Florida-first audience and for a simple thesis: Don't guess. Ask. That thesis applies to how we treat people as well as how we treat taste. We ask you for credentials so we can protect your preference map; we do not invent a social identity for you based on surveillance of your browsing habits.

By creating or using a MiTRYBE account, you agree to this policy together with our Terms of Use and Privacy Policy. If you do not agree, do not create an account and do not continue using authenticated features.

1. Scope

This policy covers accounts used to access MiTRYBE on the web at mitrybe.com and related Weathertop Studios environments where MiTRYBE is offered. It applies to email-and-password sign-up, Google sign-in where enabled, and any future authentication methods Weathertop Studios may introduce. It also covers guest or local-only use that later becomes linked to an authenticated account, including migration of browser-stored preference data into a signed-in profile when that path is available.

This policy does not govern third-party platforms, Florida venues named in seed recommendations, or other Weathertop Studios products that are not MiTRYBE. If you use MiTRYBE alongside other Weathertop products, each product's account rules apply to that product unless we say otherwise in writing.

2. Definitions

"Account" means the authenticated identity tied to your email address (or Google identity) that lets you sign in to MiTRYBE. "Credentials" means passwords, session tokens, recovery emails, and any second factor Weathertop Studios may enable. "Preference map" means the structured taste dimensions and answer history produced when you respond to MiTRYBE questions. "We," "us," and "Weathertop Studios" mean the operator of MiTRYBE."You" means the individual who creates or controls the account.

"Firebase Authentication" refers to Google Firebase's authentication service that MiTRYBE uses to verify identity and issue sessions. "Firestore" refers to Google Cloud Firestore, which may store account-linked profile fields and progress when cloud sync is enabled. Local browser storage (including the mitrybe-profile-v2 key) may hold a working copy of your run even before or without full cloud sync; see our Cookies & Local Storage policy.

3. Eligibility and accurate information

You must be old enough to form a binding contract in your jurisdiction and able to lawfully use an online service. MiTRYBE is not directed at children under 13, and we do not knowingly create accounts for them. If you are between 13 and the age of majority where you live, you may use MiTRYBE only with permission from a parent or guardian who accepts this policy on your behalf.

Provide accurate registration information. Do not create an account using someone else's email without authorization. Do not create accounts in bulk to manipulate unlock thresholds, farm recommendations, or evade prior enforcement. Weathertop Studios may require email verification before certain features unlock.

4. Creating and signing in

Accounts are created through Firebase Authentication. Depending on what we enable at a given time, you may register with an email address and password or continue with Google. When you choose Google sign-in, Google authenticates you and shares a limited identity token with MiTRYBE so we can establish a session. We do not receive your Google password.

After sign-in, MiTRYBE may create or update a user record associated with your Firebase UID. That record can include display preferences, answer progress, feature unlock state, and timestamps needed to operate the product. Dashboard features may appear greyed out until you answer enough questions; that is intentional product design, not an account defect.

If you begin answering questions before signing in, your local profile may live in browser storage. Linking that local run to an account is a convenience feature when offered. You remain responsible for reviewing what merges and for resetting answers if the combined map no longer feels true.

5. Usernames, display names, and impersonation

Where MiTRYBE shows a username or display name, choose something you are comfortable associating with your preference map and future matching features. Do not impersonate other people, brands, public officials, or Weathertop Studios. Do not use abusive, hateful, or sexually exploitative language in names. Do not include personal contact information you are not willing to make public in a social context later.

Weathertop Studios may require a name change, hide a display name, or suspend an account when a name violates this policy or our Community Standards. Reserved or confusingly similar names may be held for brand integrity even if not currently in use.

6. Your responsibilities

You are responsible for safeguarding your credentials. Use a unique password that is not reused from other sites. If we offer multi-factor authentication, enable it. Do not share your account. Do not leave an open session on a shared or public device without signing out. Notify us promptly at support@mitrybe.com if you believe your account was accessed without authorization.

You are responsible for the answers you submit and for reviewing your preference map. MiTRYBE is designed so inferences are revisable; use that design. If an unlocked recommendation or future match feature feels wrong, re-answer the questions that fed it or reset as described in the Preference Map Policy.

You must comply with applicable law. Do not use an account to harass, stalk, defraud, scrape at abusive volumes, reverse engineer with intent to harm, or circumvent technical limits. Do not use MiTRYBE to build a competing preference model by systematically exporting other users' data if social features later expose limited overlaps.

7. Weathertop Studios obligations

Weathertop Studios will use commercially reasonable efforts to keep authentication available and to protect account credentials using Firebase Authentication and related Google Cloud controls. We will not ask for your password by unsolicited email or chat. Official support channels are listed on our Contact page.

We will provide mechanisms, where product maturity allows, to reset passwords, verify email ownership, and close accounts. We will process account closure requests in good faith, subject to retention needed for security, fraud prevention, legal compliance, and backup cycles described in our Privacy Policy.

We will not sell your preference map as a standalone product. Account data is used to operate MiTRYBE, unlock features honestly, improve question quality, and—when launched—support matching that respects dimensional alignment rather than surveillance guesses. That commitment is part of why we ask you questions instead of inferring taste from clickstreams alone.

8. Sessions, devices, and sign-out

Firebase issues session tokens that keep you signed in across visits. Tokens can expire or be revoked. Clearing browser storage, switching devices, or using private browsing can end a local session and may remove or isolate local profile data. Sign out when finished on shared machines. Weathertop Studios may invalidate sessions if we detect abuse, credential stuffing, or compromised accounts.

9. Suspension, restriction, and termination

We may suspend, restrict, or terminate accounts that violate this policy, the Terms of Use, Community Standards, or applicable law; that present a security risk; or that appear abandoned after prolonged inactivity when retention is no longer appropriate. We may act with or without prior notice when urgency requires it (for example, ongoing harassment or credential compromise).

Suspension may disable sign-in, hide profile surfaces, or freeze feature unlocks while we investigate. Termination removes access; some records may remain as described in the Privacy Policy. You may appeal in good faith by contacting support with context. Appeals are reviewed when capacity allows; they are not a guarantee of reinstatement.

You may close your account by contacting us through Contact Us. Closing an account does not automatically erase every local browser copy on every device you used; clear local storage on those devices if you want a clean local slate.

10. Account recovery and support

Use Firebase's password reset flows when available. Keep recovery email access current. Support can help with account access issues but will not bypass security checks that protect other users. We may ask verifying questions or require actions from the registered email. We will not restore access to an account we reasonably believe is contested between parties without a clear showing of rightful control.

11. Florida-first and experimental field context

MiTRYBE is an early product. Feature unlocks, authentication options, and cloud sync behavior can change as we learn from Florida users. Account features that appear greyed out are waiting on your answers or on product maturity—not on a secret social graph. We will not pretend live matching exists before it does. When matching arrives, the same account identity will be the basis for consentful overlap features described in Community Standards.

12. Changes to this policy

Weathertop Studios may update this Accounts Policy as MiTRYBE evolves. Material changes will be reflected on this page with an updated "Last updated" date. Continued use of an account after changes take effect constitutes acceptance. If you disagree, stop using the account and request closure.

For questions, write to support@mitrybe.com or use /contact. For privacy-specific account questions, use privacy@mitrybe.com.