Privacy Policy

1. Information We Collect

We collect information you provide directly, information generated when you use our services, and information from service providers that help us operate Orb AI.

• Contact and account information: name, email address, phone number, login information, account identifiers, and communication preferences.
• Order and reservation information: product selection, payment status, shipping or pickup preferences, billing details, transaction identifiers, and customer support history. Payment card details are processed by our payment processor and are not stored by Orb AI in full.
• Dashboard and setup information: household profile details, Bloo setup preferences, memory and personalization settings, hub settings, installed hub information, and other content you choose to provide.
• Device and usage information: IP address, browser type, device type, pages viewed, referring pages, approximate location derived from IP address, timestamps, logs, diagnostics, and interactions with our services.
• Communications: messages you send to Orb AI, support requests, survey responses, and feedback.

2. Bloo, Voice, Face, and Home Data

Bloo is designed for home environments, and we treat personal context, voice, face, and household information as sensitive. Where features involve recognition, memory, personalization, or setup, we use that information to provide the requested Bloo experience and user controls.

Some Bloo features may process information locally on supported devices, while some features may require cloud services, account services, synchronization, or third party infrastructure. The exact behavior may depend on the product version, feature, settings, and availability at the time of use.

You should not provide sensitive information unless it is necessary for the feature you choose to use. Bloo is not intended to be used as a surveillance system, medical device, emergency response device, or substitute for adult supervision.

3. How We Use Information

• To operate, maintain, secure, and improve Orb AI websites, dashboard features, reservation flows, and Bloo-related services.
• To process reservations, payments, order updates, shipping or pickup coordination, customer support, and fraud prevention.
• To personalize Bloo setup, memory, hubs, preferences, and product experiences that you choose to configure.
• To send transactional messages, product updates, safety notices, support responses, legal notices, and marketing communications where permitted.
• To analyze usage, debug issues, improve reliability, test new features, and understand product performance.
• To comply with applicable law, enforce our terms, protect rights and safety, and respond to lawful requests.

4. Cookies and Analytics

Essential cookies and browser storage support account sessions, security, checkout and preferences. Optional Google Analytics and website experiment measurement are off by default, with no automatic consent banner. They run only if you enable analytics through Cookie settings below. Declining does not prevent access to the website or Touch. We honor Global Privacy Control and Do Not Track signals by keeping optional analytics off, even if a previous saved choice allowed it. You can change your browser’s saved choice at any time using Cookie settings.

When allowed, analytics measures public page use, navigation, product engagement and purchase-funnel events. It may process IP/network, browser and device information. Our analytics bootstrap removes URL queries and fragments and excludes form values, account IDs, private conversations, health readings and connected-service contents. Google advertising signals and ad personalization are disabled. We do not sell Touch personal information or share it for cross-context behavioral advertising. Browser controls can also restrict cookies; blocking essential storage may affect sign-in or checkout.

5. How We Share Information

We do not sell your personal information or share it for cross-context behavioral advertising. We may share information with:

• Service providers: hosting, cloud infrastructure, payment processors, analytics providers, email and messaging providers, customer support tools, security providers, and logistics partners.
• Payment and fulfillment partners: providers that process payments, coordinate delivery, support pickup, handle customs or logistics, or verify transactions.
• Legal and safety recipients: authorities, courts, advisors, or other parties when required by law or when necessary to protect rights, security, users, or the public.
• Business transfers: parties involved in a merger, financing, acquisition, reorganization, sale of assets, or similar transaction.

6. Retention

We keep information for as long as reasonably necessary for the purposes described in this Privacy Policy, including to provide services, maintain records, resolve disputes, comply with legal obligations, prevent fraud, and enforce agreements. Retention periods may vary depending on the type of information and context.

7. Security

We use reasonable administrative, technical, and organizational measures designed to protect information. No system is perfectly secure, and we cannot guarantee that information will always remain secure.

8. Your Choices and Rights

Request deletion of your Touch account or shared ORB account without reinstalling the app or signing in on a watch. The Touch section below explains its verification process, retention exceptions, connected-service controls and health-sharing choices. Uninstalling an app is not account deletion.

Depending on where you live, you may have rights to access, correct, delete, or receive a copy of certain personal information, or to object to or restrict certain processing. You may also be able to opt out of marketing emails by using the unsubscribe link in those emails.

California residents may also request information about the categories and specific pieces of personal information collected, their sources, purposes and categories of recipients, subject to the law’s applicability and exceptions. An authorized agent may submit a request with proof of authority; we may verify the consumer’s identity as permitted by law. To make a privacy request or appeal a decision where an appeal right applies, contact us using the information below. We may need to verify ownership proportionately. Where applicable, you may withdraw consent, object to processing, restrict processing, request portability or complain to your privacy regulator. We do not penalize you for exercising mandatory rights. Processing relies, as applicable, on providing requested services, specific consent, legitimate interests in secure and reliable operations, or legal obligations. We aim to respond to verified requests within 30 days and explain any lawful extension or retention exception.

9. Children

Orb AI services are not directed to children under 13 or a higher minimum age required by local law, and we do not knowingly collect personal information from children under 13 without appropriate consent. If you believe a child provided personal information without appropriate consent, contact us so we can review and take appropriate action.

10. International Users

Orb AI is based in the United States. If you use our services from outside the United States, your information may be processed in the United States and other countries where privacy laws may differ from those in your location.

11. Changes to This Policy

We may update this Privacy Policy from time to time. The updated version will be posted on this page with a new effective date. We provide notice of material changes where required. A policy update does not itself grant permission for new optional uses of sensitive information; we obtain the additional consent required by law or platform policy.

12. Contact

Touch: apps, health and connected services

These feature-specific disclosures form part of the ORB Privacy Policy and apply to the Touch website, dashboard, phone and watch apps, ring and connected services. The specific controls and retention periods below apply to the relevant Touch data.

Information collected and why

• Account and device information: name, email, account identifiers, sign-in records, linked-watch and ring references, software versions and preferences support authentication, pairing, account security and synchronization. Apple or Google sign-in provides the identity details you authorize; a private relay email can be used where supported.
• Requests and content: voice audio, transcripts, prompts, replies, conversations, memory, notes, documents, attachments and task receipts support the assistance and features you request.
• Authorized integrations: connection credentials and the messages, contacts, calendar events, files, website content or other records needed for your requests are accessed under the connection permissions you grant. Recipients and the external service receive content you authorize Touch to send.
• Optional sensor and location data: supported health readings, activity, workouts, routes and device location are used for the features and sharing choices described below. A permission does not make an unavailable measurement available.
• Transactions and support: shipping/contact details, ring configuration, order status, payment references, agreement acceptance and support correspondence support fulfillment, billing, remedies and fraud prevention. Stripe processes card details; ORB does not store full payment-card numbers.
• Operational data: IP address, request time, device/app version, error, security and usage/allowance records help operate the service, investigate failures and enforce account limits. Public website analytics is described separately below.

Voice and AI

When you start a voice request, Touch sends audio and transcripts over encrypted connections to ORB and its transcription and AI providers. Recording begins with your screen or supported ring gesture; Touch records a voice request when you activate it. If you explicitly start Notes, it continues recording until you stop it or a device or service interruption ends capture. Temporary watch recordings are removed after processing. AI replies may be inaccurate; review answers and proposed actions.

Account and optional information

Touch stores account identifiers, conversations, personal context, saved drafts, task receipts and preferences to provide your agent across sessions. Location, recorded runs, daily activity and calendar information are used for the features you authorize. Connected services provide data under your approved permissions. Reports include only the conversation text you choose to submit, your account reference and app version. No recording is included in a content report.

Ring health sync between your S3 and phone

When you link a Touch S3 and phone to the same account, available ring readings and recent activity and sleep records sync automatically from the ring through the S3 and ORB to your phone. The ring stays connected to the S3; no separate health-sharing switch or phone Bluetooth pairing is required for this account sync. ORB stores an encrypted, account-restricted latest snapshot, including measurement times, ring/device references, connection state and battery, with a 31-day expiry refreshed by a new snapshot. It can include heart rate, blood oxygen, HRV, stress, temperature, steps, calories, distance and sleep records when actually available. This sync is separate from sending health data to AI or enabling private comparison reports. Account deletion removes account-owned sync records under the deletion process below. Old or missing readings are not evidence of normal health.

Optional AI health guidance

Health permissions alone do not share readings with AI. If you request one-time analysis or explicitly enable Daily guidance in Health, Touch sends current-day readings, measurement times and source names to ORB and OpenAI through your selected Touch or ChatGPT brain. Daily guidance uses available Touch ring and Apple Health readings together, independently of the source you choose to display. While you use Health, it refreshes at most hourly when readings change. It uses your existing AI allowance. If account memory is on, DeepSeek also processes this conversation. The request and reply remain in account conversation history under the retention and deletion controls below. The latest plan and its sharing preference are saved in protected, device-only storage on your iPhone so the plan stays available when you return. Turn off Daily guidance in Health sources to stop future automatic requests and remove the local plan; this does not delete existing conversation history or recall a request already sent. This is separate from Apple Health access and private comparison sharing. You can decline and keep using local Health. AI output can be wrong and is for wellbeing, not diagnosis or treatment.

Optional private health comparison

Apple Health measurements remain on your devices unless you choose a feature that shares them. S3 ring measurements also use the account sync described above. An eligible owner can separately enable private comparison reports in the iPhone app. This shares ring and Apple Watch heart rate, blood oxygen and sleep intervals, measurement times and pseudonymous device references with ORB over an encrypted connection. Reports are encrypted at rest, restricted to the verified owner account and retained for 30 days. They are not used in AI conversations, public analytics or advertising. Stop sharing and delete uploaded report records in Touch → Health. Apple Health read permissions can also be revoked in iPhone settings; denied or missing records cannot be distinguished by Touch. Source records on your devices remain under your control. Comparison shows agreement between consumer devices, not medical accuracy.

Health permissions and restricted uses

Apple HealthKit and Android Health Connect access is optional and limited to supported data types you approve, such as heart rate, blood oxygen, steps/activity, sleep or exercise records. Android Health Connect readings currently support local health views; do not assume an iPhone-only sharing feature exists on Android. You may decline or revoke individual permissions in Apple Health or Health Connect/system settings. On Apple devices, Touch cannot distinguish a denied read permission from the absence of records.

ORB does not sell health data or use it for advertising, marketing, data brokerage, credit or insurance decisions, or training generalized AI models. Authorized processing of health data by service providers is limited to the health feature you explicitly enable and must meet the same use restrictions. Touch does not use iCloud to store HealthKit readings. Local health access, AI health guidance and private comparison sharing are separate choices; accepting terms or granting a system health permission does not enable either sharing feature. Only data actually available from supported hardware is shown. These are consumer wellbeing features, not medical diagnosis, clinical accuracy validation or human-subject research.

Service providers and integrations

ORB uses hosting, database, AI and transcription providers to operate Touch. OpenAI handles Touch AI/transcription and DeepSeek handles background memory processing. If you select another supported brain, that provider processes the requests you send to it under the connection disclosure. Review your selected brain in Settings before sharing sensitive information. Optional Google, Slack and Onairos connections depend on your authorization. The optional WhatsApp, Signal and LINE personal-account connections use unofficial implementations and are identified as such during setup. LINE uses a Chrome-style session, which may replace another LINE Chrome session. Touch stores connection credentials encrypted and decrypts accessible messages to handle your requests. Disconnecting removes the active Touch credentials; revoke the session in the source app as well. Availability and supported operations vary by connection. Touch has no advertising SDK and does not sell your personal information for money.

Documents and attachments

When you select an iCloud Drive folder on your computer, Touch uploads encrypted private copies of its files and metadata to your Touch account. Updates run while the sync page is open with your computer awake and online; your browser may throttle or pause background updates. Your watch uses the last completed copy, which may be older than iCloud. The saved folder permission stays in that browser. Google Drive connects with read-only access to search and retrieve files you authorize; Google Docs and Slides may be exported as PDFs and Sheets as XLSX. File names and metadata are processed by the AI provider to select documents. Attachment bytes are sent to the email provider only for your authorized send. Touch retains encrypted action receipts and temporary attachment snapshots for verification; recipient copies cannot be recalled by disconnecting. Disconnecting iCloud removes its active Touch copies, and account deletion removes account-owned document and temporary records. Provider backups follow their retention policies. Your original source files are unchanged. Touch’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google account/profile data supports sign-in; authorized Gmail messages, metadata, drafts and attachments support email requests; Calendar events support scheduling; read-only Drive files and metadata support document requests. The permissions actually granted determine access. Google data, including derived data, is used only for the user-facing features you authorize; it is not sold, used for advertising, credit decisions or training generalized AI models. Transfers are limited to providing or improving those features with your consent, security, applicable law, or a permitted business transfer with the required consent. Human access is limited to your affirmative permission for specific content, security/abuse investigation, legal requirements, or legally permitted aggregated internal operations. You can disconnect Google in Touch and revoke access in Google Account connections. Revocation stops future access but does not itself delete existing Touch history; use the deletion controls below.

Navigation controls

If you choose to enable Touch navigation controls in watch Accessibility settings, Touch can select the travel mode you explicitly request for your chosen Google Maps destination. This does not require a ring. The same optional service supports your ring navigation gestures. Touch inspects visible app and navigation controls locally to carry out that requested action; this screen content is not stored or sent to ORB. Destination and route information you open is handled by Google Maps. You can decline or turn off this access at any time in watch Settings; without it, select the travel mode yourself in Maps.

Web Agent

If you enable Web Agent, Browserbase hosts a separate cloud browser for Touch. It works while your computer is off. Website logins must be completed in that browser; your existing Gmail connection does not sign it in. Saved browser contexts can contain cookies, login tokens and other website data. Touch requests that browser recordings and logs be disabled. Website content you ask Touch to read is processed by its AI provider. Reading some pages can mark messages read. Website actions require confirmation. Turning Web Agent off stops access but retains saved website sessions; remove a website to request deletion of its saved cloud context. Websites can expire logins or block automated access.

Pulse

Pulse connects you with the person whose invitation you accept and people who accept your invitation. Joining shares your display name with that contact. Messages and display names are encrypted in storage; this is not end-to-end encryption. Touch processes messages for delivery and assistant requests you authorize. Opening a chat marks only the displayed messages read. You can block contacts and turn assistant reading or sending off in Pulse settings. The built-in plugin remains connected. Deleting your Touch data removes your contact relationships and messages involving your account.

Notes

When you start Notes on a supported Touch, recorded audio is sent to ORB and its transcription provider. Touch retains the transcript and a summary with key points and action items in encrypted account storage. Ask Touch to stop taking notes or say “End Notes” to finish. Notes settings control new recordings, assistant access to saved notes and optional email delivery through your connected Gmail account. Email recipients and mail providers receive the delivered transcript and summary. Pending audio stays in private watch storage until accepted for processing; a device interruption can leave gaps.

Sharing, security and international processing

ORB uses OpenAI for AI/transcription and DeepSeek for enabled background memory as described above; your separately selected connected brain may involve another disclosed provider. Browserbase operates the optional cloud browser, and cloud hosting/database, payment, email and delivery providers process the data needed for their service. Authorized message recipients and services you connect process the content you send under their own policies. See OpenAI, DeepSeek, Browserbase, and Stripe for their independent privacy information.

ORB limits service-provider access to the purposes disclosed here and requires protections consistent with this policy and applicable platform requirements. Account records and connection credentials use encrypted storage and access controls; network transmission uses encrypted connections. Pulse is not end-to-end encrypted. No system is completely secure. Authorized personnel may access the minimum information needed for support you request, security, abuse reports, legal obligations or deletion fulfillment. We may disclose legally necessary information to authorities or transfer information in a lawful business transaction subject to the continuing restrictions on Google and health data.

ORB operates in the United States. Providers may process data in the United States and other countries. Where applicable, transfers must use a legally valid safeguard, such as standard contractual clauses or another recognized mechanism. Contact us for information about safeguards relevant to your data; this policy does not claim that ORB is certified under a framework in which it has not enrolled.

Control and retention

Turn off device permissions in the applicable Apple or Android system settings, disconnect integrations and manage memory in the Touch dashboard. Conversations, saved context and account records remain while needed to provide the service unless you delete them or request account deletion. Imported context has its own expiration. Content reports and deletion requests are retained for review and fulfillment. ORB may retain information required for security, legal obligations or dispute resolution as described in this policy. Unlinking or uninstalling the app alone does not delete server-side data.

After identity verification, ORB can erase Touch records from its active database, revoke watch credentials and remove connected-service credentials. A minimal request reference and hashed deletion fence remain to prevent old sessions or delayed workers from recreating erased data. Shared ORB account deletion requires a separate review across other ORB products. Provider-controlled logs and backup copies follow the applicable retention policies; support will explain exceptions and completion status. Deletion does not recall data already transmitted or messages already sent.

Retention by data type

• Conversations, saved notes, memory, account preferences and account-owned documents remain as needed for your ongoing service until removed through supported controls or a verified deletion request.
• Temporary voice recordings on your watch are removed after processing; pending uploads may remain until accepted. Uploaded notes become transcripts/summaries. Do not assume that removing the local recording deletes a saved transcript or conversation.
• S3 ring-health account snapshots expire 31 days after their latest upload. Private health comparison reports expire after 30 days and can be removed earlier using the sharing controls. Imported documents, temporary action attachments and imported context use feature-specific expiry and cleanup; source files and recipient copies are separate.
• Connection credentials remain while the connection is active; disconnecting removes active Touch credentials. Saved Web Agent sessions require removing the website, as described above.
• Order, tax, agreement, fraud/security, support and deletion-verification records may remain for applicable legal, accounting or dispute requirements. A minimal hashed deletion fence prevents delayed work from restoring erased Touch data; it is not retained conversation content.
• Provider-controlled logs, transaction records and backups may remain for their retention cycles or legal duties, with access restricted. We will explain applicable exceptions and completion status when responding to a verified request.

Privacy rights and legal bases

Depending on your location, you may request access, correction, export, deletion, restriction or objection, withdraw consent, and complain to a competent privacy authority. We verify ownership proportionately and do not require you to give up mandatory rights or pay for ordinary requests. Contact alireza@orbai.ai for requests that are not available in the app. Where applicable, processing relies on providing the service you request, your specific consent for optional sensitive-data sharing, legitimate interests in security and reliable operations, or legal obligations. Withdrawing consent stops future consent-based processing; it does not undo processing already lawfully completed. We do not sell Touch personal information or share it for cross-context behavioral advertising.

Deletion and support

Request deletion of your Touch account and associated data, including without access to the watch. The form also offers deletion of your shared ORB account. Third-party source accounts and messages already sent are separate; revoke Touch in the source service as appropriate.

We aim to complete verified deletion requests within 30 days. If a lawful extension or retention exception applies, we will explain the reason and expected completion date. A request receipt is not confirmation of completed deletion. Account deletion does not automatically cancel a subscription billed by Apple, Google or another third party; manage those subscriptions with the billing provider. For privacy or support, contact alireza@orbai.ai. ORB AI INC is based in the United States; processing may occur in the United States and other countries as explained above.

Touch dashboard

Touch members are searchable by name by default. You can turn off name discovery in Pulse Settings. Email and phone discovery require a separate choice, and phone discovery requires SMS verification. Results do not display your email or phone. New chat connections require your acceptance; you can decline or block people.

Touch Chrome Connector

The Touch Chrome Connector is operated by ORB AI INC. It connects websites you select to your Touch Web Agent.

What the extension accesses

The extension reads website addresses from open tabs in your current Chrome profile to build the website picker. It excludes incognito tabs and does not read browser history, saved passwords, passkeys or localStorage. Open-tab paths and queries are not sent to ORB for the picker.

What you choose to share

When you select websites and approve Chrome’s site permissions, the extension reads those websites’ session cookies and sends them over HTTPS directly to ORB. These cookies can grant access to your website accounts. Each transfer uses a short-lived, single-use grant tied to your Touch account and the selected website. Cookie data does not pass through dashboard window messages. Temporary website permissions are removed after transfer.

Use and service providers

ORB uses the imported cookies to create a separate saved cloud-browser session for the selected website. Browserbase hosts this browser and its saved context. ORB encrypts import records in its database and removes cookie payloads from execution commands on completion, failure, cancellation, expiry or worker restart. Browserbase reports encryption at rest for saved contexts. Website actions remain subject to your Touch settings and confirmations. The extension does not sell data or use it for advertising.

Your controls

Stop browser stops further agent access. Disable Web Agent revokes agent access while retaining saved sessions. Remove a website in Web Agent settings deletes its saved cloud context. Removing the extension prevents future imports but does not delete previously saved cloud sessions. You can also revoke the session at the original website. Provider-controlled logs and backups follow provider retention policies; deletion does not recall data already transmitted.

Limited Use

The use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Selected website addresses and session cookies are used only to connect and operate the Web Agent feature you request. They are not sold, used for advertising, credit decisions or generalized AI training. Transfers and human access are limited to operating the authorized feature, specific content you permit for support, security/abuse investigation, legal requirements or other uses expressly permitted by the applicable policy. These restrictions apply to derived data as well.