Privacy Policy

Last updated: August 24, 2026

Bloom Street LLC ("Bloom Street," "we," "us," or "our") operates Osera, a personal AI application and related services, including the iPhone app, desktop daemon, backend services, admin systems, and website at osera.io. This Privacy Policy explains what information we collect, how we use it, where it may be processed, and the choices you have.

Osera is designed to be personal. That means it can process sensitive context, including messages, health signals, location, calendar events, reminders, photos metadata, contacts, files, voice notes, music context, and data from connected accounts when you choose to grant access.

1. AI and Safety Disclosure

Osera is powered by artificial intelligence. You are not talking to a human, therapist, doctor, lawyer, financial advisor, emergency service, or crisis counselor. AI responses can be inaccurate, incomplete, inappropriate, or unexpectedly personal because they are generated from your conversation and context.

When enabled connected services let Osera take actions, Osera can misunderstand intent or context and take unintended actions that are wrong, duplicate, incomplete, delayed, or irreversible. Actions may come from direct requests, standing permissions, heartbeats, automations, and background goals, depending on the features you enable.

Connected content, including messages, documents, websites, and tool results, can contain hidden, malicious, misleading, or hostile instructions. Those instructions may try to manipulate Osera's actions. Safety, permission, and confirmation controls reduce but cannot eliminate these risks. Scope or revoke access you no longer need, monitor important activity, and report unexpected behavior to us.

Do not use Osera for emergencies. If you may harm yourself or someone else, call or text 988 in the United States, contact local emergency services, or reach a trusted person immediately. Osera may show crisis resources when our systems detect self-harm or crisis language, but those systems are not guaranteed to detect every emergency.

2. Information We Collect

2.1 Account and Authentication

• Email address, optional name, authentication identifiers, verification codes, and Sign in with Apple identifiers.
• Subscription tier, billing status, referral or campaign attribution, invite codes, and related account metadata.

2.2 Messages, Memory, and Personalization

• Messages you send, AI responses, reactions, cards, shared-space messages, polls, notebook/capture content, journal entries, to-dos and task lists, and related metadata.
• Derived memory, relationship context, entities, life threads, episodic summaries, goals, preferences, communication style, and proactive-notice state.
• Tool results used to answer you, such as calendar reads, reminder reads, web results, file contents, email snippets, weather, place results, or connected-service results.
• Action requests, tool calls, execution traces, approvals, denials, corrections, error reports, automations, heartbeat activity, background goals, learned patterns, and successful, unsuccessful, failed, partial, reversed, and corrected outcomes.

2.3 Files, Images, Camera, and Photos

• Files, images, screenshots, documents, profile photos, and shared-space attachments that you upload or share with Osera.
• Camera captures when you choose to take a photo inside the app.
• If photo context is enabled, Osera scans non-hidden Photos library metadata on device and may send photo dates, media type, favorite/edit status, subtypes, durations, GPS coordinates from photo metadata, Vision scene labels, face counts, and summary statistics. Actual library images and facial identities are not uploaded by the photo-context scan.
• When you explicitly upload or attach a photo, that uploaded image itself is sent to our storage and may be processed as part of the conversation or feature you used.
• When you share or describe meals, food photos or text descriptions may be analyzed into structured nutrition data such as detected food items, estimated calories, and macronutrients, which may be stored to power food and wellness features.

2.4 Apple Health and Fitness Data

If you enable Apple Health sync and grant HealthKit access, Osera reads workouts, sleep, sleep stages when available, steps, active energy, exercise minutes, distance, flights climbed, resting heart rate, heart-rate variability, cardio fitness, and body weight.

When sync is enabled, Osera sends three layers to our backend:

• Derived categorical states such as recovery, strain, readiness, routine stability, workout recency, and routine-disruption flags.
• A daily numeric snapshot that may include sleep start/end, sleep duration, sleep stage minutes, resting heart rate, HRV, steps, active energy, exercise minutes, and latest same-day workout type/start/duration.
• A daily body-weight value when a smart scale or another app writes weight to Apple Health.

You can also log your weight manually in the app or by telling Osera your weight in chat. Those entries are direct user input: they are stored on our backend as part of your conversation and health history whether or not Apple Health sync is on, and they power your weight trends, briefings, and check-ins.

We use this data for morning cards, briefings, chat answers, pattern recognition, and proactive check-ins. HealthKit data is not sold, used for advertising, used for marketing data mining, or shared with data brokers. Relevant health context may be sent to AI providers when needed to answer you or generate a proactive message.

2.5 Location, Weather, and Places

• With location permission, Osera may collect latitude, longitude, accuracy, timestamp, timezone, city, country, and permission level.
• With When In Use access, Osera refreshes location while the app is active or when a user action needs fresh context.
• With Always access, Osera may use Apple significant-location-change and visit monitoring. These are OS-driven arrival/departure signals, not continuous GPS polling.
• Osera derives place profiles, home/work/routine clusters, movement state, likely destinations, trip state, and location-aware proactive reasons.
• WeatherKit data may be fetched from your current location and stored as the latest weather context in Apple-data sync rows.

2.6 Calendar, Reminders, Contacts, and Connected Accounts

• Calendar sync reads upcoming events, including title, start/end time, all-day status, and location. Current iOS code reads roughly the next 90 days.
• Reminder sync reads incomplete reminders, including title, due date, and priority, and may create or complete reminders when you ask.
• Contact access may read names, phone numbers, email addresses, and birthdays for contact discovery and relationship context. Osera may match synced contacts against existing Osera users and create contact-match suggestions.
• Osera may create calendar events, reminders, contacts, playlists, or other records only when a feature or command asks the device to perform that action and the relevant permission is granted.
• If you connect Google, Microsoft, email, JMAP, Composio, or other integrations, Osera stores connection metadata and the tokens or credentials needed to act on your behalf. Disconnecting or removing an integration stops Osera from making new requests through that connection; it does not automatically delete information already collected or created.
• If you add ICS calendar feed URLs, we store the URL, fetch and parse events, and refresh the feed periodically.

2.7 Voice, Audio, Speech, and Music

• Voice notes you record are uploaded and stored so they can be delivered and played in the app.
• Osera may generate assistant audio or TTS voice notes and store playback references.
• Speech recognition is used for local and streaming transcription experiments or voice features when enabled.
• Apple Music access may read library and recently played context to build a music taste profile. ShazamKit-style recognition may identify songs and store recognition results. Raw music-recognition audio is not stored as a music profile.

2.8 Desktop Daemon and Local Workers

If you use the Mac desktop daemon, Osera may process daemon status, worker installation and health, local command results, machine connection state, logs, and local integration outputs. Some desktop flows can access local tools or Apple services on your Mac only after local OS permission or user setup. The desktop app is intended as a setup and worker dashboard, not the primary chat surface.

2.9 Device, Usage, Analytics, and Diagnostics

• Device identifiers, app version, OS version, push tokens, notification state, connection events, sessions, errors, latency, token counts, model/provider usage, cost estimates, and feature interactions.
• Website page views, referrers, UTM parameters, approximate country from IP geolocation, waitlist submissions, SMS waitlist opt-in status, and cookie-consented advertising measurement where applicable.
• Feedback messages, screenshots, recordings, and diagnostic context you submit.

2.10 Browser Control When Enabled

Browser control remains under development. These disclosures describe processing that applies only when the feature is enabled and used; they are not a statement that it is currently available or cleared for launch.

When browser control is enabled and you choose to use it, Osera may process authenticated browser session state, including cookies, origins, and local or session storage; URLs and visible page content; DOM and accessibility-derived data; live or replay frames; takeover input events; and browser activity receipts and audit records.

Page content, URLs, DOM and accessibility-derived data, and tool results may be processed by Osera and by model providers when included in model requests. Browser infrastructure and integration providers process the data needed to operate their distinct parts of the feature.

Authenticated browser custody state is encrypted before storage.

Live browser frames may be conditionally masked during credential injection, when URL safety is blocked or not yet confirmed, or when page focus is unknown or on a sensitive field, but those safeguards may not identify every sensitive item.

Replay capture may be suppressed or cross-origin content occluded around sensitive or password contexts, but replay frames can still contain visible page content.

Disconnecting browser access stops future restoration through that connection and removes or revokes Osera-held connection credentials where supported. It does not close, delete, or necessarily sign you out of the underlying external account.

Browser receipts, connection metadata, custody records, and replay frames may have different retention and pruning rules. Some records are pruned only as new runs occur, and current account deletion does not yet prove complete deletion of every account-specific browser record.

3. Apple Permission Strings and App Permissions

The current iOS app declares permission use for Health sharing and updating, location When In Use and Always, photo library read/write and add-only save, camera, microphone, speech recognition, calendars, reminders, contacts, Apple Music, notifications, WeatherKit, Sign in with Apple, associated domains, Live Activities, and communication notifications.

Revoke an OS permission: You can revoke a device permission through iOS Settings or macOS System Settings. This stops new collection or device access for that permission, but it does not automatically remove information already incorporated into messages, files, summaries, memories, derived profiles, action records, logs, backups, or generalized learnings.

4. How Data Reaches AI Providers

Third-party AI providers receive context to perform requested services, including to generate responses, route tools, summarize context, create proactive messages, process files, or power voice features. That context can include your message, previous conversation context, memory, files, image attachments, tool results, calendar/reminder context, location/weather/place context, photo-derived context, health and nutrition context, and connected-service results.

Current provider families in code include Anthropic, Google Gemini, MiniMax, DeepSeek, xAI/Grok, OpenAI, Groq, Moonshot/Kimi, Mistral, Together, DeepInfra, Fireworks, and OpenRouter. OpenRouter may receive requests on primary or fallback routes and may route them to downstream model providers. Third-party AI providers may be developed or operated in different countries, and data may be processed in the United States, the European Union, or other jurisdictions. Provider routing can change for reliability, quality, cost, or latency, including through OpenRouter and its downstream providers.

We do not intentionally send your account password, payment card number, OAuth tokens, API keys, or integration credentials to AI providers as prompt context. We do not currently guarantee redaction of personal information you include in messages, files, or tool results before they are sent to AI providers.

Bloom Street's own improvement uses are distinct from third-party AI-provider processing. Provider terms and contractual controls are not identical. We honor provider-specific no-training or restricted-use commitments where they apply. A provider route that conflicts with a binding source restriction is not authorized by this policy.

5. How We Use Information

• Operate Osera, authenticate users, sync devices, generate AI responses, execute requested actions, and maintain memory and personalization.
• Deliver proactive check-ins, notifications, cards, briefings, meeting prep, relationship context, location-aware suggestions, health-aware moments, and other contextual features.
• Provide connected-service functionality such as calendar, reminders, contacts, email, files, music, weather, desktop daemon control, and local workers.
• Process billing, enforce usage limits, prevent abuse, debug errors, improve reliability, and monitor system health.
• Communicate with you about authentication, support, feedback, important service changes, and policy changes.

We may investigate suspected violations of the Acceptable Use Policy, preserve relevant records, including records subject to a valid legal hold, restrict capabilities, and suspend or terminate access.

5.1 Service Operation and Consumption Tracking

We measure service use, including message counts, voice minutes, attachment volume, tool invocations, action traces, outcomes, and model/provider token consumption, to operate the service, enforce plan limits, prevent abuse, improve reliability, and give you visibility into use where available.

6. Personalization and Product Improvement

Private content includes message and file contents, model outputs, memories, summaries, embeddings, tool arguments and results, connected-account contents, and sensitive facts or inferences derived from those sources. Osera processes private content to provide and personalize the service for you, including memory, responses, proactive features, and actions you authorize.

Bloom Street does not use private content or account-linked data to train or fine-tune general-purpose or foundation language models.

We use action-performance information such as the feature or tool used, timestamps, latency, completion state, error category, approval state, and structured reactions or correction states to operate Osera and improve reliability and safety. Account-linked operational telemetry may be used for internal product, adoption, reliability, and safety analysis. Only genuinely aggregated or deidentified telemetry may contribute to cross-user model development or generalized analysis. Free-text or otherwise content-bearing feedback remains private content.

Authorized personnel and processors may review limited, sampled private interactions for quality and safety evaluation, support, security, abuse prevention, legal compliance, or investigation of a specific reliability or safety problem, except where source-specific restrictions provide otherwise. Access is limited to what is reasonably needed for those purposes. This review is not foundation-model training.

Osera may create reusable workflows from generalized action patterns and outcomes. Reusable workflows made available across users must not contain private content, identifiers, or sensitive facts inferred from them and must be human reviewed before publication. Automatically generated action traces cannot directly become shared workflows; publication requires human review.

Passwords, OAuth tokens, API keys, integration credentials, payment credentials, session cookies, and comparable authentication or payment secrets are excluded from model development and cross-user learning. Google Workspace API data and HealthKit-originated data are not used by Bloom Street to train or fine-tune general-purpose or foundation language models or for cross-user model development. Review and personnel access involving Google Workspace API data remain subject to Google’s policies and Limited Use requirements. Google Workspace API data may not appear in a published shared workflow as private content.

Osera’s use and transfer of information received from Google Workspace APIs complies with the Google Workspace API User Data and Developer Policy, including its Limited Use requirements. Google Workspace API data is not used to create, train, or improve a model beyond that specific user’s personalized model for the appropriate user-facing use case, and no other prohibited use is authorized.

These restrictions apply in addition to the HealthKit commitments above: HealthKit data is not sold, used for advertising, used for marketing data mining, or shared with data brokers.

7. How We Share Information

We do not sell personal information. We share information only when reasonably necessary and proportionate to run Osera, act at your direction, comply with law, protect rights, safety, security, or service integrity, or enforce our policies as specifically described below.

• AI providers: receive prompts, context, files, images, tool results, and other relevant data needed to generate or process output.
• Backend and infrastructure providers: host databases, workers, object storage, authentication, email delivery, DNS, content delivery, observability, and deployments.
• Integration providers: process account connections, OAuth flows, connected-service calls, email/calendar/productivity actions, and local worker commands.
• Payment processors: process subscription payments. We receive subscription identifiers and status, not full card numbers.
• Website and SMS providers: process waitlist, support, analytics, consent, and SMS delivery. SMS opt-in data is not shared with third parties for marketing or promotional use.
• Legal and safety recipients: We may disclose information only as permitted by this Privacy Policy and applicable law for enforcement, fraud prevention, security, imminent harm, or abuse.

For those narrow purposes, and only in response to a valid request or documented investigation, we may make reasonably necessary and proportionate disclosures to service providers, affected platforms, rights holders, and lawful authorities, subject to this Privacy Policy and applicable law.

8. Retention and Deletion

Disconnect or remove an integration: Disconnecting or removing an integration revokes or removes the credentials for that connection and stops new requests through it. It does not automatically remove information already incorporated into messages, files, summaries, memories, derived profiles, action records, logs, backups, or generalized learnings.

Account deletion: You can request deletion in the app where available or by contacting privacy@osera.io. Account deletion initiates an account-wide, multi-phase deletion process that targets account-linked records, credentials, memory, file objects, and workspace backups, including account-linked authentication accounts, sessions, and verification records.

Deletion timing and limits: Deletion can take time across systems and backups. Account deletion does not reverse completed external Actions, such as sent communications, purchases, bookings, commitments, modifications, or deletions. Account deletion also does not require a Connected Service or other external service to delete records it controls independently under its own relationship with you; you may need to request deletion directly from that service. Some legally required, security, transaction, aggregate, deidentified, or non-attributable generalized records may remain where permitted. Some learned-skill records may remain after account deletion. We may replace a direct creator field, but other internal ownership or scope identifiers can remain on a retained record. Those records can include generalized or user-authored workflow content, and we do not promise that every retained workflow can be individually attributed to or removed for one account. Non-attributable, source-compliant workflows, aggregate metrics, and product changes may not be reversible or attributable to one account. Some records may be anonymized instead of deleted where other users depend on shared context.

Investigation and enforcement records: We retain investigation, enforcement, security, legal, and dispute records only for as long as reasonably necessary for those purposes, subject to longer retention required by law.

Records subject to a valid legal hold are retained only for the duration necessary to comply with that hold or applicable law.

9. Security

• Data in transit is encrypted with TLS.
• Device authentication tokens are stored in the iOS Keychain where applicable.
• API keys and provider credentials are kept server-side, not shipped in the app.
• We use access controls, guarded operational scripts, and deployment separation for development and production systems.

Osera does not currently provide end-to-end encryption for conversations, and we cannot guarantee that any internet-connected service or third-party provider is perfectly secure. Our safety, permission, and confirmation controls reduce but cannot eliminate the risk of wrong, duplicate, incomplete, delayed, unintended, or irreversible actions, including actions influenced by hostile instructions in connected content.

10. Legal Bases for EEA/UK Users

Our legal bases for investigation and enforcement are performance of our contract, compliance with legal obligations, consent where applicable, and our legitimate interests in security, fraud prevention, abuse prevention, and enforcing our terms where those interests are not overridden by your rights.

• Contract: account operation, messages, AI responses, sync, billing, and requested features.
• Consent: HealthKit, location, photo library, camera, microphone, speech recognition, contacts, calendar, reminders, Apple Music, notifications, integrations, cookies, and similar permissioned features.
• Legitimate interests: security, fraud prevention, debugging, reliability, product analytics, and service improvement.
• Legal obligation: tax, accounting, compliance, and lawful requests.

11. Your Choices and Rights

• Revoke an OS permission: stop new collection or device access for that permission in iOS Settings or macOS System Settings. This is not account deletion.
• Turn off in-app toggles for features such as health sync, photo context, and location where available.
• Disconnect or remove an integration: revoke or remove its credentials and stop new requests through that connection. This is not account deletion.
• Delete your account: initiate the account-wide multi-phase deletion process described above.
• Reply STOP to opt out of waitlist SMS messages, or HELP for help. Message and data rates may apply.
• Contact privacy@osera.io to request access, correction, deletion, export, restriction, objection, or consent withdrawal. We aim to respond within 30 days.

California users have the right to know, delete, correct, and opt out of sale/share as provided by applicable law. We do not sell personal information.

12. Cookies and Website Tracking

The Osera app does not use advertising SDKs. The website may use server-side analytics without cookies for page views, referrers, UTM parameters, and approximate country. With consent, advertising measurement tools may set cookies or pixels to measure campaign effectiveness. You can reject or clear cookies through browser controls and the consent banner where available.

13. Children

Osera is not intended for users under 18 or the age of majority in their jurisdiction. We do not knowingly collect personal information from minors. If you believe a minor has provided personal information, contact privacy@osera.io.

14. Changes to This Policy

We may update this policy as Osera changes. When changes are material, we will update the date above and use reasonable notice such as email, in-app notice, or website notice.

15. Contact

Bloom Street LLC
Email: privacy@osera.io

Effective as of August 24, 2026.