Privacy Policy

This Privacy Policy explains how Funnel One ("Funnel One", "we", "us") collects, uses, stores, shares, and protects information when you use our website and the Funnel One application (together, the "Services"). It also describes the choices and rights you have regarding your information.

Funnel One is a GTM platform that puts marketing, sales and RevOps on one funnel, under one set of rules. Our customers are business-to-business revenue teams; the Services are not directed to consumers or to children under 16.

1. Information we collect

We collect the following categories of information:

Account & contact data you provide — name, work email, company, role, and authentication credentials for users of the app.
Customer prospecting data our customers load or that we surface about companies and business contacts (company name, business email, public firmographic and technographic data).
Google user data where a user connects a Google account (see Section 2).
Slack and Zoom data where your organization connects Slack or Zoom (see Sections 1.1 and 1.2).
Usage & device data — log data, IP address, browser type, and product-usage events, used to operate and secure the Services.
Cookies — the marketing site uses only minimal, essential cookies and the application uses a strictly necessary session cookie for authentication.

1.1 Slack data

If your organization connects Slack, Funnel One receives:

the workspace ID and name, and an encrypted bot token;
the Slack user ID of each person who links their Slack account to Funnel One;
messages a person sends to Funnel One, in a direct message or in a thread where they mention it, the earlier messages in that thread it needs to answer, and files shared with it;
the member list of a channel Funnel One answers in, held briefly to decide what it may say there;
event IDs, held to ignore duplicate deliveries.

Funnel One does not read channels it is not in or messages not addressed to it. It requests no Slack user tokens. We use this data to answer and act for the person who asked, under that person's Funnel One permissions, and to send the Slack notifications each person chooses. Message content goes to our AI model provider to generate the answer, under the terms in Section 4. Slack conversations are never sampled or used to improve AI teammates. We do not use Slack data for advertising. We do not sell it. And we do not use it to train generalized AI models. Where it is stored: in the United States.

1.2 Zoom data

If your organization connects Zoom, Funnel One receives:

your Zoom account ID and encrypted access credentials;
the users in your Zoom account (Zoom user ID, email address and license type), so Funnel One can match each rep to a Zoom host;
the ID and join link of each meeting Funnel One creates.

Funnel One does not receive recordings, transcripts, meeting chat, or any meeting it did not create. We use this data to create, move and cancel meetings booked through Funnel One. The join link appears in the calendar invite and in the confirmation and reminder emails. Zoom user data is never used for advertising or to build marketing profiles. We do not sell it, and we do not use it to train AI models. Where it is stored: in the United States.

If your organization connects Zoom using its own Zoom app credentials, we store those credentials encrypted and delete them, along with every Zoom identifier we hold, when you disconnect.

2. Google user data

Funnel One integrates with Google Calendar so that reps can offer meeting times they are actually free for, and so that a booked meeting lands on the calendar they already use. The integration is optional. It is only active if you choose to connect a Google account.

Funnel One requests Google Calendar access and your basic account identity (your Google account ID and email address), and nothing more. It does not request access to your Gmail mailbox, your contacts, your files, or any other Google service.

2.1 Google Calendar

With your permission, Funnel One requests exactly two Google Calendar scopes:

Your free/busy availability (calendar.freebusy). This tells Funnel One whether a block of time is busy, not what fills it. The scope returns busy time ranges and nothing else: no event titles, no attendees, no descriptions, no locations. We use it to offer a prospect only the times you are free.
Events on calendars you own (calendar.events.owned). Google describes this scope as letting an app see, create, change and delete events on calendars you own. Funnel One uses it for bookings only. When a prospect books a meeting, Funnel One creates that event on your calendar and invites the prospect. Funnel One keeps the ID of each event it creates, and only reads, changes or deletes those events: to update or cancel a booking, and to notice when you move or cancel one yourself. It does not list or read your other calendar events.

Connecting also tells us which Google account you connected (openid, email, userinfo.email), so the app can show you the connected address and route each booking to the right person.

What we store: OAuth tokens (encrypted), the connected Google account address, and a reference to each calendar event Funnel One creates, so that booking can be updated or cancelled. We do not copy your calendar into Funnel One.

2.2 What we do not do

We do not use your Google Calendar data for advertising. We do not sell it. We do not use it to determine credit-worthiness. And we do not use it to train generalized artificial-intelligence or machine-learning models. All Google user data is handled under the Limited Use terms below.

2.3 Google API Services Limited Use disclosure

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

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

In particular:

We only use access to Google user data to provide or improve user-facing features that are prominent in the Funnel One application.
We do not transfer Google user data to anyone except as necessary to provide or improve the features described above, to comply with applicable law, for security purposes, or as part of a merger, acquisition or sale of assets with notice to users. We never transfer or sell Google user data to advertising platforms, data brokers or information resellers. Section 4 describes which kinds of service providers receive it.
We do not use Google user data for serving advertisements.
We do not use Google user data to determine credit-worthiness or for lending purposes.
We do not allow humans to read Google user data unless (a) we have your affirmative consent for specific calendar data, (b) it is necessary for security purposes such as investigating abuse, (c) it is required to comply with applicable law, or (d) the data is aggregated and anonymized and used to operate or improve the Services.
We do not use Google user data to develop, improve, or train generalized or non-personalized AI and/or ML models.

3. How we use information

To provide, operate, secure, and support the Services.
To detect buying signals, enrich and score companies, and orchestrate outbound.
To send the email you configure in the Services, and to honor unsubscribe requests.
To communicate with you about your account, support, and service changes.
To comply with legal obligations and enforce our agreements.

3.1 How we improve our AI teammates

We might sample conversations handled by your AI teammates, including calls, emails and chats, to improve how they work for every workspace. Staff who review these conversations have restricted access, and names and contact details are hidden by default.

Conversations in Slack are the exception. They are never sampled or used to improve AI teammates (see Section 1.1).

We do not sell personal information. We share information only with sub-processors that help us run the Services (hosting, database, email delivery, AI processing), under contracts that require appropriate safeguards. We may also disclose information to comply with law, protect our rights, or in connection with a corporate transaction, with notice where required.

Our service providers. We use service providers for:

hosting and databases;
file storage and backups;
email delivery, both account email and the email you send through the Services;
AI processing (see "AI providers" below);
AI voice calls (speech-to-text, text-to-speech and telephony);
business contact and company data used to enrich records;
AI teammate mailboxes, where your organization creates them;
web browsing for AI research;
website visitor identification, where you switch it on;
error monitoring.

Customers can request our current list of sub-processors through our Trust Center. To ask for it, email privacy@funnelone.ai.

Which service providers receive Google user data. Our hosting and database providers store it: the OAuth tokens, the connected account address, and a reference to each event Funnel One creates. Beyond them, only scheduling details are shared (a rep's open times, and the time and status of a meeting Funnel One booked), and only to run the feature they belong to. Our email delivery provider sends the confirmation and reminder emails, which carry the meeting time and video link. When an AI voice call offers and books a meeting, the scheduling details described under "AI providers" below pass through our voice providers. Funnel One does not read your other calendar events, so no service provider receives them. If your organization connects Slack, the rep who owns a meeting gets a message in your own Slack workspace with its time and video link, and the connected address may be used to find that rep there.

AI providers. Funnel One uses three third-party AI providers, each directly under paid commercial terms. We do not send data through AI gateways or aggregators. Our voice service also runs a small speech-detection model on our own servers. It only tells when a person has stopped speaking.

Our AI model provider, used directly through its commercial API, generates sales content and analysis in the Services, writes answers in Slack where your organization connects it, and writes what the AI caller says on an AI voice call. When an AI voice call offers and books a meeting, it receives only a rep's available time slots, calculated from that rep's Google Calendar free/busy information, and the booked meeting's time. It receives no event titles, event descriptions or attendee lists. Our AI model provider does not use data sent through its commercial API to train its models. It deletes API inputs and outputs within 30 days of receiving or generating them, except where content is flagged under its usage policy, which it may keep for up to 2 years, or where the law requires it to keep data longer.
Our speech-to-text provider transcribes the other person's speech on an AI voice call, as the call happens. We have opted out of model training with our speech-to-text provider, so it does not use the audio we send it to train its models.
Our text-to-speech provider turns the AI caller's words into speech, as the call happens, including any meeting times it offers. We have opted out of model training with our text-to-speech provider, so it does not use the data we send it to train its models.

5. Data retention

We retain information for as long as needed to provide the Services and for legitimate business or legal purposes. Google user data is kept only while you need the connection. Disconnecting the integration erases the stored OAuth tokens, so Funnel One can no longer reach your calendar. Removing the connection, or deleting your Funnel One account, deletes the connection record itself, including the connected account address. Deleted data may persist for short backup rotation windows.

If a workspace removes the Funnel One Slack app, we delete its Slack tokens and Slack account links. Conversations that started in Slack stay in your Funnel One account as normal threads. They are your data, and we delete them on request.

If your organization removes the Funnel One Zoom app, or disconnects Zoom in Funnel One, we delete the Zoom tokens, every Zoom account and user identifier we hold, and the mapping of Zoom users to hosts. Meeting links already on bookings are kept, so scheduled meetings still work. Funnel One creates no new Zoom links.

If your organization connected Zoom using its own Zoom app credentials, disconnecting Zoom in Funnel One deletes those credentials, every Zoom account and user identifier we hold, and the mapping of Zoom users to hosts. Meeting links already on bookings are kept here too.

6. Data deletion & revoking access

Revoke Google access at any time from your Google Account security settings (Third-party access), which ends Funnel One's access at Google. You can also disconnect the integration inside Funnel One, which erases the Google tokens we stored for that connection.
Remove the Slack app from your Slack workspace's app management, or disconnect Slack on the Integrations page in Funnel One. Either one deletes the Slack tokens and account links (Section 5).
Remove the Zoom app from the Zoom App Marketplace, or disconnect Zoom on the Integrations page in Funnel One. Either one deletes the Zoom tokens, the Zoom account and user identifiers, and the user mapping (Section 5). If your organization connected Zoom using its own Zoom app credentials, disconnect Zoom on the Integrations page in Funnel One, which deletes those credentials, the Zoom account and user identifiers, and the user mapping (Section 5). You can also deactivate your own Zoom app in Zoom, which ends Funnel One's access at Zoom.
Delete your data by emailing privacy@funnelone.ai. We will delete your personal data and any associated Google user data within 30 days, except where retention is required by law.

7. Security

We protect information with encryption in transit and at rest, tenant isolation with row-level access controls, least-privilege access, and monitoring. No method of transmission or storage is perfectly secure, but we work to protect your information and to notify you of incidents where required. Report concerns to security@funnelone.ai.

8. Cookies

The marketing site runs with minimal, essential cookies. The application uses a strictly necessary session cookie for authentication. We do not use advertising or cross-site tracking cookies.

If you are in the European Economic Area or the United Kingdom, you have the right to access, correct, delete, restrict, or object to processing of your personal data, and the right to data portability. Where we rely on consent, you may withdraw it at any time. Our lawful bases include performance of a contract, legitimate interests in operating a B2B service, and consent where required. You may lodge a complaint with your supervisory authority. To exercise your rights, contact privacy@funnelone.ai.

10. Your rights (CCPA / California)

California residents have the right to know what personal information we collect, to request deletion, to correct inaccurate information, and to opt out of "sale" or "sharing" of personal information. Funnel One does not sell personal information and does not share it for cross-context behavioral advertising. We will not discriminate against you for exercising these rights. To make a request, contact privacy@funnelone.ai.

11. International transfers

We may process information in the United States and other countries. Where required, we use appropriate safeguards such as Standard Contractual Clauses for cross-border transfers.

12. Changes to this policy

We may update this Policy from time to time. Material changes will be reflected by an updated "Last updated" date and, where appropriate, additional notice.

13. Contact us

Questions about this Policy or your data? Email privacy@funnelone.ai, or write to the data controller:

Funnel One
1111B S Governors Ave # 26638
Dover, DE 19904

For product support, email support@funnelone.ai. We answer Monday through Friday, 9:00 to 17:00 US Eastern Time. Report a security concern to security@funnelone.ai.