←BUMIS

BUMIS · Privacy Policy

Privacy Policy.

The short version.

You give BUMIS something private. We owe you transparency about what we do with it. Here is the whole list. BUMIS is operated by BUMIS, Inc. (“we”, “us”).

  • We store your assessment answers, your portrait, and your Mirror conversations on Supabase (a US-hosted database).
  • When the Mirror replies, your message + portrait get sent to Anthropic Claude. Anthropic doesn't train their model on it (per the API terms we use).
  • We never sell your data. We never share it with advertisers. We never let third parties scrape conversations.
  • We only use your conversations to improve BUMIS if you explicitly opt in. Off by default.
  • You can delete your account + all data any time. Email [email protected] or use Settings → Delete account.

The longer version below covers the same ground with the specifics.

Where BUMIS is allowed to be used.

BUMIS currently operates from the United States and is intended for users in the United States and Canada. We are not yet equipped to handle European Union or United Kingdom GDPR obligations and do not actively market the product outside North America. If you are in the EU or UK, please don't create an account; we'll add proper support when we're ready.

What we collect.

From you, by you giving it to us:

  • Identity: name, email, age, gender (or "prefer not to say"). Captured at signup. Stored on your profile row.
  • Assessment answers: your 38 responses on the 5-point scale. Stored in your portrait row.
  • Mirror conversations: every message you send the Mirror and every reply the Mirror sends back. Stored in your conversation log.
  • Attachments: screenshots and voice notes you choose to share with the Mirror. Voice notes are transcribed on your device; the audio itself never reaches our servers, only the text you review and send. We do not scan your camera roll or microphone in the background.
  • Sign-in identifier: Apple or Google's opaque identifier (not your password). Used so you can sign back in.
  • Pattern observations: each nightly reflection records which of your patterns showed up that day, along with the short quotes it already surfaces from your own messages. Over time these observations let your Self-Portrait reflect recent weeks instead of staying frozen at your first assessment. They are recorded for every account, including free accounts, where they are stored but not shown until you subscribe. They live in your account, are never shared or shown to anyone else, never appear on a shared portrait link, and are deleted with your account.

Automatic, minimum-needed:

  • IP address: kept transiently for rate limiting and abuse prevention.
  • User agent: the browser / app version string. Used to debug crashes and serve the right asset.
  • Crash logs: if the app crashes, the stack trace is sent to us. Sanitized to remove your messages before storage.
  • Subscription state: Apple or Google tells us when you subscribe, cancel, or your subscription renews. We store your current tier (free, premium, plus). We never see your credit card.

What we do not collect:

  • Your contacts, calendar, photos library, microphone, or location are never accessed in the background. We ask for them only when you take an action that needs them (sharing a screenshot, voice-noting the Mirror).
  • We don't use advertising cookies or cross-site marketing trackers anywhere in the BUMIS app. One page on the website, getbumis.com/download, carries a campaign attribution script so we can tell which creators and ads actually bring people to BUMIS. See "Cookies and trackers" below for exactly what it sends and what it does not.
  • We don't collect protected health information. BUMIS is not a covered entity under HIPAA and shouldn't be used as one.

Why we collect each thing.

One reason: to deliver the product you signed up for.

Your assessment answers feed the portrait. The portrait grounds the Mirror. The Mirror needs your conversation history to be coherent across sessions. Your tier determines what limits apply. Crash logs help us fix bugs. None of these are negotiable for the product to work.

One optional additional reason: with your explicit opt-in (Settings → Data), we may use a curated subset of your conversations to improve future Mirror behavior. Opt-in is off by default and reversible at any time.

Who we share data with. The full list.

Anthropic (Claude model). Every Mirror reply is generated by Claude. Your portrait, your conversation history, and your new message are sent to Anthropic's API as part of the request. Anthropic processes them to generate the reply, then returns it. Per Anthropic's commercial API terms, your data is not used to train their models. Anthropic retains API request data for a limited period for abuse monitoring (currently 30 days).

Supabase. All your stored data lives on Supabase (database + storage). They are a data processor; we control what's stored and how long. Their infrastructure is US-hosted.

Vercel. The website and API are hosted on Vercel. Vercel sees the HTTP requests transit through their edge network. They do not retain your message bodies; only metadata for performance monitoring and the response served.

Apple App Store + Google Play. They handle your subscription. They tell us your active tier; they don't tell us your payment details. They retain billing records per their own terms.

RevenueCat. We use RevenueCat to reconcile subscription state across iOS + Android. They see the same tier signal Apple/Google sees and nothing else.

Trybe (campaign attribution). We work with creators who make videos about BUMIS, and we need to know which of them bring people who actually stay. Trybe measures that. Two things reach them. First, if you arrive at getbumis.com/download from a creator link or an ad, a script on that page sends Trybe the campaign tag in the link, the page address, the site you came from, your browser and screen size, and a random visit id kept in a cookie on your device for up to a year. Second, if you later subscribe, our server tells Trybe that a subscription happened, using a scrambled one-way code in place of your account id, along with the plan, price, currency, store, and time. Trybe never receives your name, your email, your account id, your IP address, your portrait, or anything you have written in the app. The script runs on that one page and nowhere else.

PostHog (US). We use PostHog for product analytics on the mobile app: funnels (assessment → portrait → upgrade), retention curves, screen-level usage counts, and cost telemetry for our Anthropic API spend. PostHog receives event names (like "mirror_message_sent"), your Supabase user id, and event-specific metadata like tier or screen. To enable cohort analysis (how the experience differs across demographics), PostHog also receives your age, birth year, and gender, all collected at signup. PostHog never receives your name, your email, the contents of your Mirror conversations, the names of people you're tracking, your portrait text, your daily reflection text, or the day or month of your birthday. IP addresses are anonymized at collection and geolocation is disabled on our server-side events. When you delete your account, your PostHog data is purged at the same time. We use the US region.

Firebase Crashlytics (Google). If the app crashes, Crashlytics receives the crash stack trace and your Supabase user id so we can fix the bug. It does not receive message contents or any portrait text. Collection is disabled in development builds; only production crashes flow to Google. We do not use Firebase Analytics.

Crisis-pathway hotlines. When BUMIS detects self-harm or abuse signals in your messages, we surface 988 / NDVH / similar resources in-app. We do not contact these hotlines on your behalf. We do log that a safety event occurred (and which rule fired) so we can audit our own detection. The matched text is logged; not the full message.

That's the whole list. We do not sell, rent, or trade your data to anyone. We do not share it with advertisers or analytics brokers.

How long we keep things.

Free accounts: assessment answers + portrait + Mirror conversation history kept for up to 12 months of inactivity. After 12 months with no Mirror activity, we may delete the conversation history.

Paid accounts: same data kept for up to 24 months of inactivity. After 24 months with no activity, we may notify you and then delete.

If you delete your account: all of the above is removed immediately (for in-app deletion) or within 7 days (for email-requested deletion). We retain only what we're legally required to: anonymized billing references for tax / financial-record requirements (typically 7 years), and anonymized safety event logs for our own compliance review.

Crash logs: 90 days, then deleted.

Rate-limit and IP logs: 30 days, then deleted.

Your rights.

You have the right to:

  • Access: see what we have about you. Email [email protected] and we'll send you a copy within 14 days.
  • Delete: remove your account and data entirely. Instructions on the Account Deletion page.
  • Correct: change your name, age, gender, or email from Settings.
  • Opt out of training: Settings → Data → disable "Use my conversations to improve BUMIS." This is off by default; if you turn it on you can turn it off. Future conversations stop being eligible for training use immediately. Past conversations are excluded from future training runs.
  • Take it elsewhere: request an export of your portrait + conversation history in JSON format. Email [email protected]; we'll deliver within 14 days.

California residents have additional rights under the CCPA (right to know, delete, correct, opt-out of "sale", which we already don't do). All requests use the same email above.

Security.

Data is encrypted in transit (TLS 1.3) and at rest (Supabase's managed AES-256 encryption). All BUMIS traffic to Anthropic, Supabase, Vercel, and Cloudflare is over encrypted channels.

We use Supabase Row Level Security so a signed-in user can only read their own rows through the public API. Anyone authenticated to BUMIS sees their own conversations and their own profile data, never anyone else's.

What this does not mean. Access to the production database for operational purposes (debugging a stuck account, investigating a safety event, responding to a deletion request) is technically possible for the BUMIS operator using a privileged Supabase service role. This is how every consumer LLM product on the market is built today (ChatGPT, Claude.ai, Replika, Wysa, Character.AI, others). We do not routinely read individual conversations and we do not have any business reason to. If you would like a stronger commitment in writing for an enterprise or clinical context, email [email protected].

Application-layer encryption of conversation contents (so that even the BUMIS operator cannot read messages without a separate decryption key) is on our roadmap and will land before broader scale. Until then, the layers above are the security posture.

No system is perfectly secure. If we ever experience a breach that affects your data, we'll notify you within 72 hours of discovery and tell you what was affected and what we're doing.

Children.

BUMIS is for 17 and older. We don't knowingly collect information from anyone under 17. If you believe someone under 17 has created an account, please email [email protected] and we'll delete it immediately.

Cookies and trackers.

The BUMIS website sets no tracking cookies on any page you would normally read. There is one exception, and it is worth being precise about. getbumis.com/download is the page a creator link or an ad sends you to in order to install the app. That page runs Trybe's attribution script, which sets a cookie on your device so the same visit can be recognised, and tells Trybe which campaign sent you. It is not used to follow you around other websites. It does not run on the home page, on this page, on the Terms, on the account deletion page, on our articles, or on a shared Portrait link.

Our hosting provider (Vercel) may set technically necessary cookies for security; these don't track you across other sites.

The BUMIS mobile app uses two analytics subprocessors, listed in the section above: PostHog for product analytics (which screens you visit, which patterns convert) and Firebase Crashlytics for crash reports. Neither tracks you across other apps. We do not use Firebase Analytics and we do not collect your iOS IDFA (Identifier for Advertisers); the app will not prompt you for ad-tracking permission.

AI processing in plain language.

Three things happen when you talk to the Mirror:

  1. Your message is sent to our server (Vercel) along with your session token.
  2. Our server packages your message + your portrait + recent conversation history into a request to Anthropic's Claude API. Claude generates a reply. The reply comes back to us.
  3. We send the reply to your phone and log the exchange (for you to read later and, with your opt-in consent, to improve future model behavior).

That's it. The Mirror does not have memory beyond what's in your portrait + conversation history. It does not have access to anything outside the request you sent it. It does not contact other services on your behalf.

Changes to this Policy.

We update this Policy when our practices change. We won't change it retroactively. If we make material changes, you'll see a notice in-app or by email at least 14 days before the new Policy applies. Continued use after that means you accept the updated Policy.

Last updated: 2026-11-16.

Contact.

For privacy questions, deletion requests, access requests, training-consent disputes, or anything in this Policy you don't understand: [email protected].

Definitions (formal).

  • "BUMIS," "we," "us," and "our" refer to BUMIS, Inc., the entity operating BUMIS.
  • "Personal information" means information that identifies you, relates to you, or could reasonably be linked to you.
  • "Process" means any operation performed on personal information, including collection, storage, use, sharing, and deletion.
  • "Data processor" means a third party that processes personal information on our behalf (Anthropic, Supabase, Vercel, RevenueCat, Trybe, Apple, Google).

Terms of Service · Privacy Policy · Account Deletion
Questions: [email protected]