Privacy Policy

Effective Date: 4 November 2026 · Last Updated: 4 November 2026

This Privacy Policy describes how HALO.AI LLC, a New York limited liability company ("HALO.AI," "we," "us," or "our"), handle information in connection with:

SMILE Agent Studio (including the built-in ioa agent runtime, smile hub autonomous Bot engine, and the "Login with Google" and "Login with Microsoft" desktop OAuth 2.0 integrations);
SMILE Core Engine and SMILE Serve Engine; and
Our websites at https://aihalo.dev and https://www.aihalo.dev (the "Website").

Core Privacy Principle — 100% Local-First Desktop & Self-Hosted Execution: SMILE Agent Studio, SMILE Serve Engine, and SMILE Core Engine run locally on your own computer or within your self-hosted infrastructure. We do not operate a cloud relay server that collects, stores, proxies, or reads your Google or Microsoft OAuth tokens, emails, calendar events, source code, datasets, models, or AI agent transcripts.

1. Google API Services User Data Policy & Limited Use

SMILE Agent Studio includes an optional, user-initiated "Login with Google" integration that allows you to connect your Google Gmail and Google Calendar accounts directly to your local SMILE Agent Studio workspace.

Google Limited Use Disclosure: SMILE Agent Studio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

1.1 Google User Data We Access (OAuth 2.0 Scopes)

When you choose to click Login with Google in SMILE Agent Studio, your system browser opens Google's official OAuth 2.0 consent screen requesting authorization for the following scopes:

Google OAuth Scope	Data Accessed	Purpose in SMILE Agent Studio
`openid`, `email`, `profile`	Google account email address and display name.	Accessed during sign-in to automatically identify your email address and display name and provision your local email and calendar configuration files without manual entry.
`https://www.googleapis.com/auth/gmail.readonly`	Gmail messages, threads, headers, labels, and attachments.	Enables the local Email tool and user-configured local Bot routines to search and read messages in your inbox at your direction.
`https://www.googleapis.com/auth/gmail.compose`	Gmail Drafts folder.	Enables SMILE Agent Studio to create server-side email drafts in your Gmail Drafts folder without sending them.
`https://www.googleapis.com/auth/gmail.send`	Send emails and replies via the Gmail API.	Enables sending or replying to emails when explicitly approved by you. Every outbound email or reply requires explicit human-in-the-loop approval (either via interactive confirmation or via the local Batch Draft Queue).
`https://www.googleapis.com/auth/calendar.events`	Google Calendar events, attendees, and free/busy intervals.	Enables the local Calendar tool and user-configured local Bot routines to list events, check scheduling conflicts, and create, update, delete, or respond to invitations with your explicit approval.

1.2 How Google User Data Is Used

(a) Direct Local Execution Only: All requests to Google APIs (oauth2.googleapis.com, openidconnect.googleapis.com, and www.googleapis.com) are made directly over HTTPS (TLS 1.2+) from the SMILE Agent Studio process running on your local machine to Google's servers.
(b) User-Directed Features Only: Information retrieved from Google APIs is used solely to provide the email and calendar management, scheduling, briefing, and drafting features you invoke or configure within your local SMILE Agent Studio environment.
(c) Human-in-the-Loop Safety Gate: SMILE Agent Studio enforces a strict approval invariant (REQUIRE_APPROVAL) on consequential actions. Autonomous Bot routines cannot send an email, reply to a thread, or modify your calendar without staging the action into your local Batch Draft Queue for your explicit review and approval.
(d) No Advertising, Profiling, or Data Brokerage: We never sell, rent, license, or transfer Google user data to any third party for advertising, marketing, creditworthiness, lending, or data-brokerage purposes.
(e) No AI / ML Model Training by HALO.AI: HALO.AI LLC never collects, accesses, or uses data obtained from Google Workspace APIs (including Gmail and Google Calendar data) to train, fine-tune, or improve generalized, foundational, or proprietary artificial intelligence or machine learning models.

1.3 How Google User Data & Credentials Are Stored and Protected

(a) PKCE Loopback Authentication: SMILE Agent Studio authenticates with Google using OAuth 2.0 Proof Key for Code Exchange (RFC 7636, S256) and an ephemeral loopback listener bound strictly to 127.0.0.1 (RFC 8252).
(b) OS Native Keychain Storage (SecretStore): Long-lived OAuth 2.0 refresh tokens are stored exclusively in your operating system's native hardware- or OS-encrypted credential manager (macOS Keychain, Windows Credential Manager, or Linux Secret Service / libsecret) on your local machine. Short-lived bearer access tokens are kept only in local process memory.
(c) Encrypted Application Client Vault: First-party OAuth client credentials packaged with the ioa runtime are sealed in an AES-256-GCM authenticated envelope and derived in memory via HKDF-SHA256. Users and enterprises may also override built-in credentials at any time with their own OAuth 2.0 Client ID and Client Secret via environment variables or configuration settings.
(d) Local Filesystem Control: Account configuration files (${smile.home}/conf/email.json and ${smile.home}/conf/calendar.json), local session logs (.smile/), and staged draft queues reside solely on your local disk under your operating system user permissions.

Because SMILE Agent Studio runs on your machine, no Google user data is ever transmitted to HALO.AI LLC. Data retrieved from Google APIs leaves your device only in the following user-controlled scenarios:

(a) Back to Google APIs: When you create a draft, send/reply to an email, or create/update a calendar event, SMILE Agent Studio transmits those updates directly back to Google's official APIs.
(b) User-Configured LLM Endpoints: SMILE Agent Studio allows you to choose which AI model processes your prompts—including 100% local, air-gapped models via SMILE Serve or third-party cloud LLM APIs that you configure with your own API keys (such as OpenAI, Anthropic, Google Gemini, Azure OpenAI, or Google Cloud Vertex AI). When you ask an agent to read, summarize, or draft a response to an email or calendar event while connected to a third-party LLM API, the relevant prompt context is sent directly from your computer to your chosen LLM provider under your own API account and subject to that provider's terms and privacy policy.

1.5 Retention, Deletion & Revoking Google Access

You retain full control over all data stored on your machine:

Disconnect in SMILE Agent Studio: You can remove a connected Google account at any time from the SMILE Agent Studio Settings dialog, which deletes the account entry from your local configuration and removes the stored OAuth refresh token from your OS keychain.
Delete Local Files: You can delete any local session transcripts, memory logs, or draft queues at any time by deleting the corresponding files in your local .smile/ or ${smile.home}/conf/ directories.
Revoke via Google Account Settings: You can immediately revoke SMILE Agent Studio's OAuth 2.0 access at any time from your Google Account security settings at https://myaccount.google.com/permissions.

2. Microsoft Account Integration ("Login with Microsoft")

When you voluntarily use Login with Microsoft in SMILE Agent Studio, the application performs a direct PKCE loopback OAuth 2.0 flow with Microsoft Entra ID (login.microsoftonline.com) and Microsoft Graph (graph.microsoft.com) using the scopes offline_access, User.Read, Mail.Read, Mail.ReadWrite, Mail.Send, and Calendars.ReadWrite. The same local-only architecture applies: tokens are stored solely in your OS native keychain, Microsoft Graph API calls occur directly between your device and Microsoft, and no Microsoft user data is ever transmitted to or stored by HALO.AI LLC.

3. SMILE Core Engine, Serve Engine & Agent Studio Software

(a) Zero Telemetry on Your Data & Models: SMILE Core Engine, SMILE Serve Engine, and SMILE Agent Studio do not phones-home or transmit your datasets, features, trained models (.sml, .onnx), inference inputs/outputs, SHAP explanations, notebooks, or source code to HALO.AI LLC.
(b) Offline License Verification: Commercial license keys are verified locally in-process using cryptographic signatures (Ed25519) without requiring an outbound network connection to a license server.

4. Website Information We Collect (aihalo.dev)

When you visit our Website or submit a commercial inquiry, we collect limited information necessary to operate the site and respond to your requests:

(a) Commercial Inquiries, Demo Requests & Order Forms: When you submit the Contact Us, Get a Demo, Request a Pilot, or Order Form modal on our Website, we collect the business contact details you provide—such as your name, work email address, company name, job title, company size, organization type, selected licensing tier, and project notes. We use this information solely to respond to your inquiry, prepare or issue commercial Order Forms and evaluation keys, and administer commercial license agreements.
(b) Website Analytics & Security Logs: Our Website uses Google Analytics to understand aggregate page traffic and Cloudflare Pages to serve static content and protect against abuse. Your browser also stores your light/dark display preference locally in localStorage under the key smile-theme.

5. Data Security

We apply industry-standard cryptographic and operational safeguards, including TLS 1.2/1.3 encryption in transit, OS-native keychain storage for local OAuth tokens, split-key AES-256-GCM / HKDF-SHA256 credential sealing, and strict human-in-the-loop approval controls for agent actions.

6. Your Privacy Rights

Depending on your jurisdiction (including under the GDPR, UK GDPR, and the California Consumer Privacy Act / CPRA), you may have the right to request access to, correction of, deletion of, or portability of personal information that HALO.AI LLC holds about you (such as commercial contact or order records), or to object to certain processing. We do not sell or share personal information for cross-context behavioral advertising. To exercise any privacy right, please contact us at [email protected].

7. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect product updates or legal requirements. When we make changes, we will update the "Last Updated" date at the top of this page. Material changes to how Google API user data is handled will be notified to users and reflected in updated OAuth consent prompts where required.

8. Contact Us

If you have any questions about this Privacy Policy, our Google or Microsoft OAuth integrations, or our data practices, please contact:

HALO.AI LLC
Email: [email protected]