Legal
Privacy Policy
Last updated 2026-10-18
This policy describes how Natively (“Natively,” “we,” “us”) collects, uses, stores, and shares information when you use getnatively.ai, the Natively client portal (app.getnatively.ai), and Tully, our desktop call coach, including information accessed through third-party accounts you connect, such as Google.
Information we collect
We collect information in three ways:
- Account and contact information you provide directly: name, work email, company, and any information submitted through a form on this site.
- Usage data: page views, referrers, device type, and, on select marketing pages, deeper behavioral analytics and session recording, see “Analytics and session recording” below.
- Data from connected third-party accounts you explicitly authorize, see “Google user data” below.
Analytics and session recording
On some of our marketing pages, we use a third-party analytics provider, acting as our data processor and hosted in the United States, to understand how visitors use the site.
- What we collect. Page views, referrers, and device type, plus behavioral events: scroll depth, which sections of a page you view, clicks, and how long you spend on a page. If you interact with a form, we also record which field you focused, which fields you completed, and which field you were on last before leaving.
- Session recording. We record a replay of the page as you saw it, including mouse movement, scrolling, and clicks. Anything you type into a form field is masked and is never recorded. The page’s own text, which is our marketing copy, is not masked.
- No cookies. This analytics tooling does not use cookies. Instead, an identifier is stored in your browser’s local storage.
- Approximate location. We derive an approximate location (country and region) and network operator from your connection, server-side, to help distinguish real visitors from automated traffic.
- Form submissions. If you submit our access-request form, that submission is linked to your analytics session using a salted one-way hash of your email address, so your email address itself is never sent to the analytics provider. The form’s actual contents (name, email, brand, and your answers) go to our email and CRM provider, not to the analytics provider.
On getnatively.ai we also use a third-party website visitor tool, which matches visits to the companies they come from. It works at the company level and does not identify you as an individual.
Your choice. None of these analytics tools load until you accept them in the cookie banner. You can change your answer at any time with the Cookie settings link in the page footer. If your browser sends a Global Privacy Control signal, we treat it as a rejection and do not ask.
Google user data
If you connect a Google account to the Natively client portal, we request read-only access to two Google APIs, solely to power the analytics features you’ve asked for:
- Google Search Console API (
webmasters.readonlyscope): organic search performance: clicks, impressions, click-through rate, and average position, broken down by query, page, country, and date, for the property you select. - Google Analytics Data API (
analytics.readonlyscope): sessions, conversions, engagement, and traffic-source data for the property you select.
How we use it. This data is used exclusively to render analytics dashboards inside your Natively client portal and, where you’ve enabled it, to inform the SEO and content use case’s opportunity scoring (e.g. identifying search queries where you rank on page two). We do not use Google user data for advertising, and we do not sell it.
How we store it. Search Console and Analytics data are stored in a Postgres database isolated to your organization’s own schema, never a shared table across customers. Your OAuth refresh token is encrypted at rest (AES-256-GCM) and used only to request short-lived access tokens for the scopes above.
How we share it. We do not share Google user data with any third party, except: (a) our infrastructure providers (cloud hosting and database) strictly as data processors to operate the service, under standard processing terms, and (b) if required by law.
Human access. Natively staff do not access your Google-sourced data except as needed to provide customer support you’ve requested, or to debug a reported issue.
Retention and revocation. You may disconnect your Google account at any time from Settings → Integrations. Disconnecting revokes our access token immediately and deletes the stored refresh token; previously synced Search Console / Analytics rows remain in your workspace (so historical charts don’t break) until you request deletion.
Tully and Google Calendar. If you connect Google Calendar to Tully, our desktop call coach, we request read-only access to your calendars (calendar.readonly scope) and your Google account’s email address (openid and email scopes). Tully reads the calendars you have selected in Google Calendar: each calendar’s name and color, and for each event its title, start and end time, guest names and email addresses, and video meeting link.
We use this data only to show your upcoming meetings in the Tully app and in your computer’s menu bar, to start a coached call from a meeting, and to name a call after the meeting it belongs to. Tully never creates, edits, or deletes calendar events. We do not use Google Calendar data for advertising, we do not sell it, and we do not use it to train AI models.
Tully reads events from Google when the app asks for them and does not store them on our servers. The one exception is a meeting’s title, which becomes the title of the call you coached and is saved with that call in your account. Your refresh token is encrypted at rest (AES-256-GCM). You can disconnect at any time from Settings → Calendar in Tully, which revokes our access with Google and deletes the stored token, or remove Tully from your Google Account’s third-party access page. The sharing, human access, and compliance terms in this section apply to Google Calendar data as well.
Compliance. Natively’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Tully call data
What Tully handles during and after a call, and where it is kept:
- Call audio: Tully captures your microphone and the sound of the other people on the call. If you keep recordings (on by default), the audio is saved only on your computer and deleted after the period you choose in Tully’s settings (30 days by default). Recordings are never uploaded to our servers.
- Transcription: on the Free plan, Tully transcribes the call on your computer. Paid plans use cloud transcription by default, and you can keep the audio on your computer in Tully’s settings. On Windows transcription is always in the cloud. With cloud transcription, the call audio streams through our servers to our speech-to-text provider as the call happens. We do not store that audio.
- Transcripts: the full transcript is saved on your computer and deleted with the call’s recording after the same period (30 days by default). During a call, transcript lines also go to our servers so Tully can write live suggestions; we delete them about an hour after the call ends.
- Summaries and coaching: after a call, Tully sends the transcript to our servers to write the call’s summary, coaching, and checklist results. Before the transcript reaches the AI model, we remove card numbers, Social Security numbers, and dates of birth. We keep the result with the call in your account: the call’s title, the app it ran in, its time and length, the summary, next steps, objections, coaching, and checklist results. These can quote short lines from the call. We do not keep the full transcript.
- Teams: if you join a team, the team owner can see the calls you make in the team’s space with their summaries, coaching, and checklist results. Team owners do not see transcripts or audio.
- Shared calls: when you share a call, we store what you chose to share, which can include the full transcript, and the email addresses you invited, until you stop sharing.
- Speakers: to label who said what, Tully tells voices apart within a single call. It does not create, store, or reuse voiceprints or any other biometric identifier, and it does not try to recognize anyone across calls.
Tully uses an AI model provider for live suggestions, summaries, and coaching, and a speech-to-text provider for cloud transcription. We do not let these providers use your calls to train their models. We do not sell call data or use it for advertising. To delete your calls from our servers, contact us (see below); recordings and transcripts on your computer are yours to delete in Tully.
Tully app diagnostics
Tully, our desktop call coach, sends us diagnostic information so we can fix bugs and confirm that updates reach you:
- Crash reports: when Tully crashes or hits an error, it sends the error details, the crash report your computer writes, and recent lines from the app’s log.
- App info: each time Tully opens, it sends the app version, your operating system and its version, your computer’s chip type and model identifier (for example “Mac14,2”), and a random ID that Tully creates when it is installed.
These reports are linked to your Tully account so we can follow up on a problem. They are built to leave out your call audio, transcripts and summaries, and they never include your computer’s name or serial number. Before a report is sent, Tully removes your computer’s user name from file paths and removes email addresses. We use this information only to run, fix and improve Tully. We do not sell it or use it for advertising.
You can turn this off at any time in Tully under Settings → Help → “Send crash reports and app info”. When it is off, Tully sends neither.
Data from AI providers
Natively uses large-language-model providers to draft content and score opportunities. Prompts sent to these providers may include data from your connected accounts (e.g. a search query and its ranking) strictly to generate the specific output you requested. We do not permit these providers to use your data to train their models, per our agreements with them.
Your choices
- Disconnect any connected account at any time from Settings → Integrations.
- Turn off Tully’s crash reports and app info at any time in Tully under Settings → Help.
- Request a copy or deletion of your data by contacting us (see below).
- Every automated action Natively takes on your behalf routes through a human-review queue before it executes. Nothing publishes or sends without your approval.
Contact
Questions about this policy or your data: [email protected]. A list of our service providers is available on request at the same address.
Changes to this policy
We’ll update the “Last updated” date above when this policy changes, and post material changes here before they take effect.