We've built Chief with trust and safety in mind.

Chief is the command layer for people who run things.

If you are a founder or executive at a small, high-growth company, you already know the cost of being the one who holds everything together. Context lives in your head. Priorities shift before the last decision is even documented. The work is real, the stakes are high, and the operational drag is constant.

Chief is not a task manager. It is not a generic knowledge tool. It is an AI chief of staff - built to make sense of the chaotic, messy, unstructured work that defines high-growth leadership. Chief does this through a flexible schema and object model, so context is never lost and nothing falls through the cracks.

Chief is designed to scale you - the human operator - so you can feel superhuman.

State what you want to achieve. Chief figures out how to get there - organizing context, coordinating agents, and surfacing what needs your attention before you have to ask. You stay oriented, confident, and early to every situation, without becoming the human coordination hub for everyone around you.

Because the best leaders do not manage information. They make decisions. Chief makes sure you always have what you need to make the right one.

Our goal is to give you, the user, as much control as possible. Here's how we do that:

Your content is never used to train LLMs: We use OpenAI's API and other LLM providers to process content, none of which use your data to train their models. This applies to all content you upload or connect to Chief, including files from Google Drive, Chrome Extension captures, and direct uploads. We are not using your data to train our own models, either. Your data is used solely to provide and improve the functionality of our Service for you.

Chat responses are based on your content: If you're using our product on files you've uploaded, our use of AI helps to query your database of knowledge and give human readable responses. You can think of the AI as a parser or formatter of content as well as an accessor of information. In this case, that's any information you've made accessible through our product.

You have the power to delete files: With regard to any content you upload to your account, in our product, you can delete that content, file by file, or in bulk, within your dashboard. If you want to know more, email us at privacy@chief.bot.

Our Chrome extension only processes a URL when it's open, which we call “Enabled.” When it's closed, which we call “Disabled,” Chief doesn't process the data.

We are building additional features into our product to give you even more fine-grained control over what content Chief runs on. Stay tuned!

Alternately, you may just want to free up some screen real estate while you keep Chief running:

You can easily change the size of Chief by clicking the “Expand” and “Hide” arrows, and by changing the width of Chief on your screen.

Chief connects with external services to help you access and analyze your data where it lives. When you connect these integrations, we access only the data you explicitly authorize.

Google Drive Integration

When you connect your Google Drive account to Chief:

What Google Drive data we access:

• Files and folders you select for use with Chief.
• File names, types, and metadata necessary to display and process your content.
• Content within the files you choose to analyze.

How we use your Google Drive data:

• To allow you to query and analyze documents stored in your Google Drive.
• To generate insights and responses based on the files you've selected.
• To enable you to organize and label your Google Drive content within Chief.

Live Call Recording

When you use Chief's Live Call Recording feature:

What audio and call data we collect:

• Live audio captured from calls and meetings you choose to record using Chief.
• Transcripts generated from that audio.
• Call metadata including date, duration, speaker identification (if available), and call context.
• Any notes, summaries, or insights generated by Chief based on the recording.

How we use your audio and call data:

• To transcribe live audio into text format in real time.
• To generate summaries, action items, and insights from recorded calls.
• To enable you to search and query your recorded call history.
• To improve Chief's transcription and analysis features (only with your explicit consent).

Important protections for call recording data:

• Recording only occurs when you explicitly initiate it through Chief.
• You are responsible for obtaining consent from all call participants before recording.
• Raw audio files are deleted after transcription is complete.
• Transcripts are retained as long as your account is active, unless you delete them.
• All audio and transcript data is encrypted in transit and at rest.
• You can delete any recording and associated transcript at any time from your Chief dashboard.
• Audio data is transmitted to Deepgram (our transcription provider) for processing, subject to Deepgram's privacy policy.

Important protections for all integrations:

• We only access data when you explicitly connect the integration to Chief.
• Your data is never used to train AI models (ours or third-party LLMs).
• We never access your data without your explicit permission.
• You can disconnect any integration at any time, and we will immediately stop accessing new data.
• All data from integrations is encrypted in transit and at rest.
• Integration data is subject to the same security standards as directly uploaded content.

As a part of helping you distill signal from noise, we ask you to register so we can craft unique experiences just for you. When you register, we ask for your:

• Email address.
• First Name.
• Last Name.

This is known as “personally identifiable information” or “PII.” We store this data in an encrypted (not plain text) state that supports GDPR protocols.

Our Service is meant for people over the age of 13. We do not knowingly collect personally identifiable information from anyone under the age of 13.

When you use Chief integrations:

When the Chief Chrome Extension is “Enabled,” we collect:

• Web page usage data: We look at the web page you are on so we can allow you to run Chief on that content.
• IP address, browser information and tracking technologies such as cookies, beacons, tags, and scripts: We use these techniques to create the most personalized, relevant experience for you.

When you connect Google Drive to Chief, we access:

• Files and folders you explicitly select or authorize.
• File names, types, and metadata necessary to display your content.
• Content within the files you choose to analyze with Chief.

And that's it! Nothing else.

We use the latest, most advanced data encryption and security practices we can find to keep this personal data safe. Our approach is certified under major privacy and security standards such as ISO, SOC, and CCPA.

Important: If you use Sign in with Google to create a Chief account, Google only shares the following information with us:

• Your name.
• Your email address.
• Your profile picture.

This data is associated with your Google account and it's only shared after you give permission through Google OAuth Consent Screen.

It's important you know that we do not gain access to your Google Account password or anything beyond the data listed above. Furthermore, all of our databases are end-to-end encrypted.

Your name, email, and profile picture are stored in our database to help us provide a better Service for you by personalizing our product. Our vendors and Service providers, which are SOC2 compliant, also have access to the data so we can catch bugs and build a better product for you.

Chief is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

To request account deletion, follow the steps on our account deletion page or email privacy@chief.bot.

We will never sell your data to third parties.

We rely on some vendor APIs to power parts of the Chief Service, including Google Cloud Computing Service, OpenAI.com, and other providers. We carefully vet vendors to ensure their privacy policies also honor our approach to user privacy. Here is a diagram showing how we use these vendors:

Everything You Need to Know

This Privacy Policy describes our policies and procedures on the collection, use and disclosure of your information when you use the Service and tells you about your privacy rights and how the law protects you.

We use your personal data to provide and improve the Service. By using the Service, you agree to the collection and use of information in accordance with this Privacy Policy.

Interpretation and Definitions

Interpretation

The words of which the initial letter is capitalized have meanings defined under the following conditions. The following definitions have the same meaning regardless of whether they appear in singular or plural.

Definitions

For the purposes of this Privacy Policy:

• Account means a unique account created for you to access our Service or parts of our Service.
• Company (referred to as either "the Company", "We", "Us" or "Our" in this Agreement) refers to Signal from Noise, Inc, 2443 Fillmore St #380-5463, San Francisco, CA 94115.
• Cookies are small files that are placed on Your computer, mobile device or any other device by a website, containing the details of Your browsing history on that website among its many uses.
• Country refers to: California, United States.
• Device means any device that can access the Service such as a computer, a web browser, a Slack interface, a cellphone or a digital tablet.
• Personal Data is any information that relates to an identified or identifiable individual.
• Service refers to the Website.
• Service Provider means any natural or legal person who processes the data on behalf of the Company. It refers to third-party companies or individuals employed by the Company to facilitate the Service, to provide the Service on behalf of the Company, to perform Services related to the Service or to assist the Company in analyzing how the Service is used.
• Usage Data refers to data collected automatically, either generated by the use of the Service or from the Service infrastructure itself (for example, the duration of a page visit).
• Website refers to Chief.bot, accessible from https://chief.bot and all associated subdomains.
• You means the individual accessing or using the Service, or the company, or other legal entity on behalf of which such individual is accessing or using the Service, as applicable.

Collecting and Using Your Personal Data Types of Data Collected

Types of Data Collected

Personal Data

While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you. Personally identifiable information may include, but is not limited to:

• Email address
• First name and last name
• Usage Data

Usage Data

Usage Data is collected automatically when using the Service. Usage Data may include information such as your Device's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, unique device identifiers and other diagnostic data.

When you access the Service by or through a mobile device, we may collect certain information automatically, including, but not limited to, the type of mobile device you use, your mobile device unique ID, the IP address of your mobile device, your mobile operating system, the type of mobile Internet browser you use, unique device identifiers and other diagnostic data.

Tracking Technologies and Cookies

We use Cookies and similar technologies (beacons, tags, scripts) to track activity and improve the Service.

• Browser Cookies: You can refuse cookies in your browser settings, though parts of the Service may not work.
• Flash Cookies: Used by some features and managed differently from browser cookies.
• Web Beacons: Used for analytics and system integrity checks.

We use Session and Persistent Cookies, including:

• Necessary / Essential Cookies - Type: Session Cookies. Administered by: Us. Purpose: These Cookies are essential to provide you with Services available through the Website and to enable you to use some of its features. They help to authenticate users and prevent fraudulent use of user accounts.
• Cookies Policy / Notice Acceptance Cookies - Type: Persistent Cookies. Administered by: Us. Purpose: Records whether users accepted the use of cookies on the Website.
• Functionality Cookies - remembers Type: Persistent Cookies. Administered by: Us. Purpose: Remembers choices you make, such as login details or language preference.

Use of Your Personal Data

The Company may use Personal Data for the following purposes:

• Provide and maintain the Service.
• Manage your account and registration.
• Perform contracts and fulfill purchased services.
• Contact you regarding updates, notices, and support.
• Provide offers and service-related communications.
• Manage your requests.
• Support business-transfer scenarios.
• Analyze and improve product, service, and user experience.
• Create anonymized and generalized case studies/training materials.

We may share your personal information in the following situations:

When We May Share Personal Information

• With service providers.
• During business transfers.
• With affiliates under this Privacy Policy.
• With business partners for products/services/promotions.
• With other users where you share in public areas.
• With your consent for other purposes.

Retention and Transfer

Retention of Your Personal Data

We retain Personal Data only as long as needed for the purposes in this policy and to meet legal obligations, resolve disputes, and enforce agreements.

Transfer of Your Personal Data

Your data may be processed and stored in locations outside your jurisdiction. We apply safeguards to protect your data during transfers.

Disclosure of Personal Data

• Business transactions (e.g., merger, acquisition, asset sale).
• Law enforcement requests where legally required.
• Other legal requirements, including preventing wrongdoing and protecting rights and safety.

Security of Personal Data

We use commercially acceptable means to protect your data, but no internet transmission or storage method is 100% secure.

Children's Privacy

Our Service does not address anyone under 13. If you believe a child has provided personal data, contact us at privacy@chief.bot.

Links to Other Websites and APIs

Our Service may link to third-party websites and APIs. We are not responsible for their content or privacy practices.

Changes to this Privacy Policy

We may update this policy and notify you via this page and, where appropriate, via email or a prominent notice before changes take effect.

Contact Us

• By email: privacy@chief.bot

Chief interfaces with the following APIs

This list may not be comprehensive as we are iterating and building quickly.

Large Language Models (LLMs)

Chief may call Large Language Models (LLMs) from various vendors in the course of offering its Service. These vendors are subject to change without prior notice and currently include:

• OpenAI: You can find its privacy policy here.
• Anthropic: You can find its privacy policy here.
• Google Gemini: You can find its privacy policy here.
• Groq: You can find its privacy policy here.
• GMI Cloud: You can find its privacy policy here.

For any other API integration (if required), include:

• Resend (email): You can find its privacy policy here.
• Grafana Labs (metrics): You can find its privacy policy here.

Where possible, Chief uses the enterprise API from each of these LLMs such that:

• LLMs store and process the data Chief submits through their respective APIs in order to provide Chief with its API services.
• LLMs do not use the data Chief submits through the API to train generative custom models for other API customers.

Audio Transcription and Processing (Deepgram)

Chief uses Deepgram, Inc. ("Deepgram") as a subprocessor to transcribe live audio captured during calls and meetings. Deepgram's privacy policy is available at https://deepgram.com/privacy.

When you use Chief's Live Call Recording feature:

• Your live audio is captured locally on your device and transmitted to Deepgram's servers for real-time transcription.
• Deepgram processes the audio and returns a text transcript to Chief.
• Deepgram's privacy policy governs its processing of audio data. You should review Deepgram's privacy policy before using Chief's Recording features.
• Neither Chief nor Deepgram stores raw audio files indefinitely. Raw audio is deleted after transcription is complete; transcripts remain in your Chief account until you delete them.

Storage

Chief may store data in secure cloud platforms that include:

• Google Cloud Platform (GCP): Using AlloyDB for the database, ClickHouse for the search service, and GCS for asset storage. You can find its privacy policy here.
• Temporal: You can find its privacy policy here.