Privacy Policy

1. Introduction

BeSeen is a mood journaling app for couples, built by MBOA, Inc. (“we,” “our,” or “BeSeen”), a Delaware corporation. This policy explains what we collect, how we use it, and the rights you have over it. It covers the BeSeen iOS app and this website.

BeSeen is built so that most of your data stays on your device. An account is optional and only needed for partner features. BeSeen is a personal journaling and relationship tool — it is not a medical or mental-health service, and your data is not covered by HIPAA.

2. Data Stored Only on Your Device

The following is created and stored locally on your device (a SQLite database and a private app folder). It is not sent to us unless you explicitly choose to share a check-in with a partner (see Section 4):

• Your check-ins — mood level and label, emotion tags, activities, people, locations, body-map sensations, and notes
• Photos and voice recordings attached to check-ins
• Reminder schedules and notification preferences
• Theme and display preferences
• Streak history and weekly insights
• Onboarding survey responses

3. Account Data (Optional — Partner Features)

An account is required only to connect with a partner. If you sign in, we receive and store on our servers:

• Authentication identifier — an Apple identity token (Sign in with Apple) or your email address (for a one-time sign-in code).
• Display name — the name you choose, shown to your partner and used in service emails.
• Partner code — a 6-character code we generate so a partner can connect to you. Stored in plain text because partner discovery requires it.
• Profile photo (optional) — stored in a private bucket and served through expiring signed links.
• Birth date (optional) — if you add it, so your partner can be reminded of your birthday.
• Push notification token — issued by Apple, used only to deliver notifications.
• Encryption public key — the public half of a keypair generated on your device. The private half never leaves your device.
• Subscription status — a flag set by our servers after Apple confirms a subscription or trial.

4. Sharing a Check-In

Sharing is opt-in for each check-in, and you choose how much to share. For couples on a current version of the app, shared journal content is end-to-end encrypted on your device before upload — we store only ciphertext and cannot read it (see Section 6).

Changing your tier or unsharing a check-in removes the corresponding data from our servers. Photos and voice notes are stored in private buckets; location and camera (EXIF) metadata is stripped before upload.

5. Partner Content — What Is and Isn't End-to-End Encrypted

We are precise about this rather than claiming blanket “end-to-end encryption.” End-to-end means encrypted on your device with a key we never hold — we cannot read it. Not end-to-end means encrypted in transit and at rest, but readable by our systems (which is what powers notifications and home-screen widgets), and limited to you and your partner by access controls.

Even when content is end-to-end encrypted, we record metadata — for example message counts, check-in streaks, and partnership totals. This is stored in plain text and visible to both partners. We also analyze partnership activity on our servers to send gentle re-engagement nudges (for example, if neither partner has shared in 7 days); you can disable these in the app's settings.

6. Encryption and Security

• In transit: all data is sent over HTTPS/TLS.
• At rest: stored on Supabase with row-level security that limits access to you and your active partner.
• End-to-end: the content marked end-to-end in Section 5 is encrypted on your device (X25519 key exchange with XSalsa20-Poly1305) before upload. We store only the ciphertext and a random nonce.
• Your keys stay with you. Your private key and your authentication tokens are held in your device's secure storage (iOS Keychain) and never leave your device. Because we never hold your private key, we cannot read your end-to-end content — and cannot recover it for you. If you lose your device and its keys, previously shared end-to-end content may become unreadable; encrypted sharing re-establishes itself the next time each of you shares.

We use reasonable administrative, technical, and physical safeguards, but no method of transmission or storage is 100% secure.

7. Mood Data Is Sensitive

Your mood and emotional state can be sensitive. Under the GDPR it may be treated as special-category data, and under California's CPRA it is “sensitive personal information.” We collect it only to provide the journaling and partner features, we do not use it for advertising or to train any machine-learning model, and you can delete it at any time.

8. Information We Collect Automatically

• Pseudonymous analytics (PostHog). Self-hosted at f.beseen.love. Analytics are off by default and only run with your consent; they're disabled in development builds. Events are linked to your account's anonymous UUID (not your name or email). We send event names and categorical metadata only — for example that a check-in was created, the mood category, a tag count, or whether a note was attached. We never send the contents of notes, messages, replies, photos, or audio. You can opt out any time in the app under Usage Analytics.
• Crash reports (Sentry). Stack traces, device type, OS version, and app state at the time of an error — gated by the same consent. Crash reports do not include your journal content, media, or messages.

9. What We Do Not Collect

• GPS or precise location data.
• Your contacts, calendar, or photo library (other than photos you explicitly attach).
• Data for advertising, ad targeting, or cross-app tracking (NSPrivacyTracking is false).
• We do not sell or rent your personal information, and we do not share it with third parties for their own purposes.
• We do not use your check-ins, notes, or messages to train any machine-learning model.

10. How We Use Your Information

11. Push Notifications

Notifications to your partner contain only generic descriptions (“shared how they're feeling,” “sent you a secret message”) plus the sender's display name. Emoji reactions appear in the notification; reply text never does. You can disable partner notifications in BeSeen's settings or in iOS Settings.

12. Third-Party Service Providers

We share data only with the providers needed to operate BeSeen:

• Supabase — database, authentication, file storage, realtime
• Apple — Sign in with Apple, in-app purchases, and app delivery
• Expo — push-notification delivery and over-the-air app updates
• PostHog (self-hosted) — pseudonymous analytics
• Sentry — crash reports
• Resend — service emails (e.g. trial reminders)

We do not use third-party advertising, attribution, or behavioral profiling services.

13. International Data Transfers

BeSeen is operated from the United States, and our infrastructure runs in the United States (AWS, us-east-1). If you are in the EU/EEA or UK, your data is transferred to the United States under the European Commission's Standard Contractual Clauses (and the UK Addendum / IDTA for UK users), which provide an adequate level of protection for international transfers.

14. Data Retention

• Local data — until you delete it or uninstall the app.
• Shared check-ins — until you unshare, dissolve the partnership, or delete your account.
• Invisible-ink messages — auto-deleted within 24 hours.
• Daily prompt responses and mood history — until the partnership is dissolved or your account is deleted.
• Trial-reminder emails — deleted within about two weeks of the trial ending.
• Notification log — 7 days.
• Analytics — per our PostHog retention settings. Crash reports — about 90 days.

15. Your Rights

In-app controls

• Delete individual check-ins (and, if shared, from our servers).
• Change your sharing tier or stop sharing at any time.
• Dissolve a partnership, removing related shared content from our servers.
• Delete your account — permanently removes your profile, partnerships, shared check-ins, messages, and uploaded media from our servers, and wipes your data and keys from your device.

GDPR / UK GDPR (EU/EEA & UK)

You have the right to access, correct, delete, or receive a portable copy of your data; to restrict or object to processing; and to withdraw consent at any time. You may also lodge a complaint with your local data protection authority (the ICO in the UK).

CCPA / CPRA (California)

You have the right to know, delete, and correct your personal information, to limit the use of sensitive personal information, and to non-discrimination for exercising these rights. We do not sell or share your personal information as those terms are defined under the CPRA. To exercise any right, contact us at the email below; we respond within 30 days.

16. Children's Privacy

BeSeen is not directed at children under 13, and we do not knowingly collect their personal information. If you believe a child has provided us information, contact us and we will delete it.

17. Changes to This Policy

We may update this policy from time to time. We will revise the “Last updated” date and, for material changes, notify you in the app. Where the law requires active consent for material changes, we will seek it before they take effect.

18. Contact Us

Questions or requests about this policy or your data: help@beseen.love

MBOA, Inc.
131 Continental Dr, Suite 305
Newark, DE 19713, United States