Privacy Policy

How Chief handles your data.

This Privacy Policy explains how Chief Labs LLC collects, uses, discloses, and otherwise processes personal information when you use Chief's websites, apps, integrations, and AI-powered workflow features.

Last updated May 18, 2026Applies to Chief Labs LLCPublic marketing-site policy

1. Scope

Chief Labs LLC ("Chief," "we," "us," or "our") provides AI-powered software and related websites, applications, integrations, and services that help users organize information, build context, generate drafts and recommendations, and automate certain workflows (collectively, the "Services").

This Privacy Policy applies to personal information we collect when you visit our websites, join a waitlist, create or use a Chief account, connect third-party accounts or data sources, communicate with Chief through chat or voice, or use Chief's browser, automation, document, messaging, and workflow features.

2. Information We Collect

Account and profile information

  • Name, email address, username, authentication identifiers, and waitlist or referral information.
  • Phone number and messaging identity (such as SMS/MMS, WhatsApp, RCS, or other messaging channels) when you join the waitlist, opt in to receive messages from Chief, or contact Chief via a messaging channel. Waitlist enrollment collects your verified phone number, email address (verified by one-time code), and optional display name.
  • Waitlist and account notification preferences by channel (email, SMS/MMS, WhatsApp, RCS, or in-app), and consent records for each communication purpose (utility vs. marketing).
  • Account preferences, settings, device identifiers, push tokens, and session identifiers.
  • Support communications and other information you choose to provide.

Connected-service content and workspace data

  • Email content, metadata, labels, recipients, attachments, and drafts from connected email services.
  • Calendar events, attendee information, meeting descriptions, free/busy data, and event updates.
  • Documents, notes, spreadsheets, presentations, file metadata, and imported knowledge-base content.
  • Messaging content and metadata from sources such as SMS/MMS, RCS, iMessage, WhatsApp, Telegram, or other connected channels, including message bodies, attachments, sender and recipient identifiers, timestamps, and delivery status.
  • Contact and identity data you provide or sync, such as names, aliases, email addresses, and phone numbers.
  • Images, files, screenshots, browser snapshots, and work products generated from those materials.

Voice and audio data

  • Microphone audio and voice recordings.
  • Transcriptions, partial transcripts, and synthesized speech requests and outputs.
  • Related timing, diagnostics, and interaction metadata.

Voice features may involve on-device processing, server-side processing, or both, depending on the feature and platform.

Browser and automation data

  • URLs, page titles, page content, screenshots, accessibility snapshots, action traces, and workflow logs.
  • Browser session data needed to maintain authenticated access, which can include cookies and local/session storage state.
  • Login or access-journey metadata and records of actions taken, requested, confirmed, or handed off to you.

Credentials you choose to store

  • Site or service name and credential field names.
  • Metadata such as creation, update, verification, and last-use timestamps.
  • Encrypted credential values for sites or services you intentionally choose to store in Chief.

Chrome browser extension permissions

The Chief Chrome extension is a companion to your Chief account. It does not function independently and sends data exclusively to the Chief server you have authenticated against — never to a third party. Each Chrome permission the extension requests is requested only because it is required for a specific Chief feature, and is used solely for that feature:

  • debugger — Provides Chrome DevTools Protocol access so Chief can capture accessibility trees, take screenshots, and simulate input when executing or recording a browser workflow you have asked it to run.
  • tabs — Manages the tabs Chief opens, focuses, or closes while running automated workflows and recording skill demonstrations on your behalf.
  • activeTab — Reads metadata about the currently active tab so Chief can observe the page you are working on when you explicitly invoke an automation.
  • scripting — Injects content scripts that read DOM structure and detect form fields, which is how Chief understands page layout and identifies credential prompts during teaching mode.
  • cookies — Reads and writes cookies so authenticated browser sessions persist across runs, so Chief can perform actions you have asked it to perform on sites where you are signed in.
  • storage — Stores extension configuration locally in the browser, including the Chief server URL you have configured and the access tokens issued by Chief when you paired the extension.
  • sidePanel — Renders Chief's automation status UI, confirmation prompts, and setup screens in the Chrome side panel.
  • nativeMessaging — Allows the extension to connect to a co-located Chief server over the local OS when you are running Chief on the same machine as your browser, instead of routing through the cloud transport.
  • webNavigation — Observes page navigation events so Chief can track which steps occurred during a skill recording session you initiated.
  • alarms — Maintains a periodic keep-alive ping so Chrome's service worker stays resident while Chief is running an active workflow.
  • downloads — Saves files when an automated workflow you have asked Chief to run produces a download (for example, exporting a report).
  • <all_urls> (host permissions) — Allows the extension to operate on any website you navigate to during an automation. Chief only reads or interacts with a page when you have explicitly asked it to run a workflow on that page; it does not passively monitor the sites you visit.

Data the extension produces (page content read during a workflow, screenshots, accessibility snapshots, cookies for session persistence, form-field metadata for credential capture, and recorded skill traces) is transmitted only to your configured Chief server over an authenticated WebSocket or native messaging channel. The extension does not include analytics, telemetry, or advertising trackers and does not send data to Anthropic, OpenAI, Google, or any other third party.

Usage, device, and diagnostic information

  • IP address, browser type, device type, operating system, app version, and network information.
  • Authentication cookies, refresh cookies, local storage, and session storage used for session continuity and preferences.
  • Feature usage, interaction telemetry, performance metrics, crash reports, debugging information, and security logs.

3. How We Use Information

  • Provide, operate, maintain, and secure the Services.
  • Authenticate users and manage sessions, devices, and access controls.
  • Ingest, organize, analyze, retrieve, and synthesize connected content and user-provided information.
  • Generate answers, drafts, summaries, recommendations, notifications, and other outputs.
  • Support voice, chat, messaging, document, calendar, browser, and automation features.
  • Send Chief communications via email (verification codes, waitlist confirmation, access offers), via SMS/MMS (verification codes, conversational replies to messages you send Chief, and notifications, briefings, or reminders you have asked Chief to deliver), and via WhatsApp or other messaging channels you have connected, according to your channel preferences and consent. Chief does not send unsolicited or marketing messages today; if Chief ever introduces marketing messages, Chief will obtain separate opt-in consent on the relevant channel before sending them.
  • Carry out user-requested actions in connected services or external websites.
  • Personalize the Services and improve product performance and reliability.
  • Troubleshoot problems, respond to support requests, and monitor system health.
  • Detect, prevent, investigate, and address abuse, fraud, security incidents, and policy violations.
  • Comply with law, enforce our terms, and protect rights, safety, and property.
  • Create aggregated or de-identified analytics, reports, and product insights.

4. AI and Model Processing

Chief uses AI and machine-learning systems, including third-party model providers, to operate the Services. Depending on the feature you use, we may send prompts, files, images, audio, browser snapshots, connected-service content, and other inputs to third-party model providers or infrastructure providers in order to understand content, generate outputs, support voice features, perform retrieval, and help execute user-requested workflows.

Chief may use multiple model providers over time, including providers such as OpenAI, Anthropic, and Google, along with hosting, infrastructure, and search providers. Those providers may process your information subject to their contracts with us and their applicable privacy and security commitments.

We do not use your Google Workspace data for advertising. We do not use data obtained through Google Workspace APIs to develop, improve, or train generalized AI or machine-learning models.

Chief'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.

5. How We Disclose Information

Service providers and subprocessors

  • Cloud hosting, database, storage, networking, logging, monitoring, support, security, and fraud-prevention vendors.
  • Model, voice, search, and AI service providers that help us deliver Chief's features.

Connected services and user-directed actions

  • If you ask Chief to draft, send, reply, schedule, edit, message, or automate a workflow, we may disclose the information needed to perform that action.
  • That can include connected email, calendar, document, messaging, and browser-based services or external websites you direct Chief to use.

Legal, safety, and enforcement

  • To comply with applicable law, regulation, legal process, or government request.
  • To enforce our agreements, detect or prevent abuse, and protect the rights, property, or safety of Chief, our users, or others.

Business transfers and your direction

  • In connection with a merger, acquisition, financing, asset sale, bankruptcy, or other corporate transaction.
  • In any other way you direct us to or consent to.

We do not sell personal information, and we do not share personal information for cross-context behavioral advertising.

6. Retention

We retain personal information for as long as reasonably necessary to provide the Services, maintain your account and connected features, comply with legal and reporting obligations, resolve disputes, enforce agreements, and protect against fraud, abuse, and security incidents.

Retention periods vary based on the type of information and the feature involved.

  • Account and access information may be retained while your account remains active and for a reasonable period afterward.
  • Connected-service content and generated work product may be retained until you delete it, disconnect the source, request deletion, or it is no longer needed for the feature that uses it.
  • Chat sessions may remain available until you delete them or request deletion.
  • Logs, telemetry, and backups may persist for a limited period after deletion or disconnection.
  • Some data may need to be retained longer when required by law or for legitimate security and abuse-prevention purposes.

7. Your Choices

  • Access or update certain account and profile information.
  • Connect or disconnect integrations and data sources.
  • Delete chat sessions, stored credentials, channels, or devices through product controls where available.
  • Control certain browser and automation permissions.
  • Manage cookies through your browser settings.
  • Opt out of marketing communications.
  • Tell Chief to stop texting you by replying STOP (or CANCEL, END, QUIT, or UNSUBSCRIBE) to any Chief SMS — Chief will stop sending all SMS to that number. Reply START or UNSTOP to allow Chief to text you again. Reply HELP at any time for assistance and contact information. You can also ask Chief in conversation to stop a specific notification or thread without disabling SMS entirely. Message and data rates may apply.
  • Opt out of WhatsApp messages by replying STOP in any WhatsApp conversation with Chief. Reply START to re-enable. Reply REMOVE to withdraw from the waitlist entirely.
  • Request access, correction, deletion, or export of certain personal information by contacting us using the details below.

Deleting or withholding certain information may limit Chief's ability to provide the Services.

8. SMS and Text Messaging

Chief is your personal AI chief of staff. SMS and MMS are one of the channels you can use to talk to Chief and to receive the updates, briefings, reminders, and account-security messages you have asked Chief to deliver. Chief is request-driven: it does not send unsolicited messages, broadcast promotions, or text you out of the blue. The following terms apply to Chief's SMS/MMS use:

  • Program: Chief personal AI chief of staff messaging from Chief Labs LLC.
  • Opt-in: You opt in to Chief SMS by (a) providing your mobile number when you sign up, join the waitlist, or update your Chief account settings, (b) initiating a text conversation with Chief, (c) asking Chief to send you a specific notification, briefing, reminder, or alert, or (d) replying START or UNSTOP after a prior STOP. Each of those is an explicit request. Chief does not send SMS to numbers that have not opted in. Opt-in records are retained as required by applicable law.
  • Message types: (1) Conversational replies to messages you send Chief; (2) account-security messages such as verification codes and login alerts; and (3) notifications, briefings, reminders, and alerts you have explicitly asked Chief to deliver (for example, 'send me a morning briefing,' 'remind me when X happens,' 'page me if Y'). Chief does not send unsolicited or marketing messages.
  • Message frequency: Determined by what you ask Chief to do. If you don't message Chief and don't have any standing notification requests, Chief won't text you. Active users who chat with Chief and maintain standing requests may receive several messages per day.
  • Carrier charges: Message and data rates may apply. Carriers are not liable for delayed or undelivered messages.
  • HELP: Reply HELP at any time to receive a help response with Chief's contact information and a link to this Privacy Policy. You can also email help@runchief.ai.
  • STOP: Reply STOP (or CANCEL, END, QUIT, UNSUBSCRIBE) at any time to tell Chief to stop sending all SMS/MMS to your number. You will receive one confirmation message and no further SMS/MMS, except as required to confirm your opt-out or to comply with applicable law. Reply START or UNSTOP to opt back in. You can also ask Chief in conversation to stop a specific notification or thread without disabling SMS entirely.
  • Supported carriers: Major U.S. carriers (AT&T, T-Mobile, Verizon, US Cellular, and others). Carrier support and message delivery is not guaranteed.
  • Sharing: Chief does not sell or share mobile phone numbers, opt-in records, or message content with third parties for their own marketing purposes. Mobile information and opt-in data are not shared for cross-context behavioral advertising.

For SMS-related questions, contact Chief at help@runchief.ai or use the address in Section 17.

9. Cookies and Similar Technologies

We use cookies, local storage, session storage, and similar technologies for authentication, session continuity, fraud prevention, saving preferences and product state, measuring performance and feature usage, and improving reliability and user experience.

You can usually control cookies through your browser settings. If you disable certain cookies or storage mechanisms, some parts of the Services may not work properly.

10. Security

We use reasonable administrative, technical, and physical safeguards designed to protect personal information. These measures may include access controls, authentication protections, logging, monitoring, encrypted transport, and encryption for certain especially sensitive data elements, such as credentials you intentionally store for third-party services.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

11. International Transfers

Chief may process and store personal information in the United States and other jurisdictions where we or our service providers operate. If you use the Services from outside the United States, you understand that your information may be transferred to and processed in countries that may not provide the same level of data protection as your home jurisdiction.

12. Children's Privacy

The Services are not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us personal information, contact us using the details in Section 17, and we will take appropriate steps.

13. Additional U.S. State Privacy Disclosures

If you are a resident of a U.S. state that provides privacy rights, including California, you may have the right, subject to applicable exceptions, to know the categories and specific pieces of personal information we have collected about you, know the sources and purposes of that processing, request deletion or correction, request a copy of certain information in a portable format, and opt out of the sale or sharing of personal information.

Chief does not sell personal information and does not share personal information for cross-context behavioral advertising.

To exercise applicable privacy rights, contact us using the details in Section 17 or use any in-product request flow we make available. We may need to verify your identity before completing certain requests. You may also designate an authorized agent where permitted by law. We will not discriminate against you for exercising applicable privacy rights.

14. EEA / UK / Switzerland

If you are located in the European Economic Area, the United Kingdom, or Switzerland, we generally rely on one or more of the following legal bases to process personal information: performance of a contract with you, our legitimate interests in operating, securing, and improving the Services, your consent, compliance with legal obligations, and establishment, exercise, or defense of legal claims.

You may have rights to access, correct, delete, restrict, or object to certain processing, and to data portability, subject to applicable law. You may also have the right to lodge a complaint with your local data protection authority.

15. Third-Party Services

The Services may link to or integrate with third-party websites, applications, products, and services that we do not control. This Privacy Policy does not apply to third-party services. We encourage you to review the privacy policies of any third-party service you connect to or interact with through Chief.

16. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. If we make material changes, we will provide notice as required by applicable law, including by updating the date above and, where appropriate, through the Services.

17. Contact Us

If you have questions, requests, or concerns about this Privacy Policy or our privacy practices, contact:

Chief Labs LLC
11225 SE 6th St Suite 100
Bellevue, WA 98004

If you are an existing user, you may also use any in-product controls or request flows we make available for deletion, disconnection, or other privacy-related actions.