Security and Data Handling

Each Google permission has one job

We request nothing beyond what each feature needs. Here is what each permission allows and where it stops.

Google Calendar

View your calendar list. View and edit events.

What it does: Syncs the calendar you choose, creates and updates meetings from the CRM, generates Google Meet links, and lets Parsa check your existing events so it avoids double-booking.
What we store: A local copy of each event’s title, description, location, start and end times, status, and Meet link.
Where it stops: You choose which calendar to sync.

Google Drive

Only files you choose, or files ParsaLink creates.

What it does: Attaches files you pick in Google’s file picker to CRM records, and copies documents you create in ParsaLink to a Drive folder you select.
What we store: Each file’s name and link.
Where it stops: It cannot see any other files in your Drive.

Gmail

Send only.

What it does: Sends email from your connected Gmail account when you send a message in ParsaLink. Parsa AI prepares drafts for your review before anything is sent, and sends your saved templates only when you ask it to.
Where it stops: It does not list, read, or otherwise access the contents of your inbox.

Your Google data is used to run these features, nothing else

Your Google data is never

Sold
Transferred to advertising platforms, data brokers, or information resellers
Used for advertising, including retargeting or personalized ads
Used to determine creditworthiness or for lending
Used to train generalized AI or ML models

ParsaLink staff only read it when

You give explicit permission for a specific item, for example when you ask for support
It is necessary for security, such as investigating abuse
The law requires it
The data has been aggregated and anonymized for internal operations

ParsaLink’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

Parsa AI and the companies behind it

Parsa AI features you choose to use run on models from Anthropic (Claude), xAI (Grok), and OpenAI (GPT). We don’t use aggregators or intermediary model gateways.

Google data sent to AI providers

Calendar event data, to check availability and schedule meetings
The content of emails Parsa AI composes for you to send through Gmail

Not sent

Drive file content
Your inbox, which ParsaLink cannot read

We use these providers under commercial API terms that prohibit training on our data, and we don’t take part in any program that allows it. Each provider may keep API request data for up to 30 days to monitor for abuse, then deletes it.

You can step back at any point

Four options, from the lightest to the most complete.

Turn off one feature

Switch Calendar, Gmail, or Drive off in ParsaLink Settings. ParsaLink stops using that feature, but the access token stays stored.
Disconnect Google

Disconnecting Google in ParsaLink Settings deletes the token, the connection, and our cached copy of your Calendar events. A calendar event you already converted into a CRM record is your CRM data, so it stays.
Revoke access from Google

In your Google Account permissions page. Google stops honoring the access immediately. ParsaLink marks the connection as disconnected the next time it tries to use it, then deletes the token, the connection, and the cached Calendar events about seven days later.
Delete your account

Google data you imported or synced is deleted when you delete your account, or within 30 days of a request to [email protected].

Questions about your data?

Write to us and a person will answer. Include your account email if the question is about your own data.

[email protected]

Mount Seir Tech LLC
5900 Balcones Drive Ste 16316, Austin, TX 78731

Start Free Privacy Policy Terms

This page summarizes our Privacy Policy (last updated September 2026). If the two ever differ, the Privacy Policy governs.

What ParsaLink can see, and what it can’t.