What the connection does

Feron uses relevant email to help you manage customer accounts and follow-ups. Connecting Gmail lets Feron:

Search your mailbox for the messages and threads relevant to an account you are working on.
Read those messages to prepare summaries and follow-ups.
Create email drafts in Gmail for you to review and edit.
Send a follow-up you have configured through an automated routine (see Drafts and sending).

Each Gmail connection belongs to the person who connected it. Other workspace members cannot use that connection.

Permissions requested

Google asks you to approve these permissions when you connect. The technical name of each permission is listed below its description.

Sign-in identitySign-in scope

openid

Confirms which Google Account you are connecting.

Your Google email addressSign-in scope

email

Shows which Gmail account is connected. Feron stores this address as the connection label.

Read and search your Gmail messagesRestricted scope

https://www.googleapis.com/auth/gmail.readonly

Lets Feron find and read relevant emails for summaries and follow-ups. This includes message headers, bodies, and snippets. Attachments are not downloaded.

Create drafts and send email as youRestricted scope

https://www.googleapis.com/auth/gmail.compose

Lets the assistant create drafts for you to review in Gmail. Automated follow-up routines use the same permission to send messages according to your settings.

Feron does not request the Gmail profile scope, and it does not request permission to permanently delete messages or modify Gmail settings.

Email data accessed

For a request or a routine you configure, Feron can read:

Headers: From, To, Subject, and the date.
The message body (plain-text, or text extracted from HTML), up to roughly the first 20,000 characters of a long message.
The Gmail snippet, thread identifier, and whether the message is unread.

For search and listing, Feron requests message metadata only (the headers above) until you ask it to read a specific message in full. Feron does not download or open attachments.

Data processing and storage

Feron fetches relevant messages when processing a request or routine. It does not keep a copy of your mailbox or store fetched message bodies as separate records. Email content may remain in saved conversations and drafts, as described below.

Stored by Feron:

Your OAuth access and refresh tokens, encrypted at the application layer (AES-256-GCM) before storage, so the connection persists between sessions.
The email address of the connected Google Account, stored as a human-readable label so you can see which mailbox is connected.
The set of scopes you granted, and connection timestamps.
Your conversations with the assistant. Because the assistant can retrieve email while you work, a saved conversation may contain email content you pulled into it, kept until the conversation or your account is deleted.
For automated follow-up routines: the generated draft (recipient, subject, body) and a short explanation of the draft. Routines record whether prior correspondence was available, but do not store the fetched correspondence itself.
For a routine follow-up that is sent: the sent subject and body and the Gmail message and thread identifiers, retained until deleted.

AI processing

Feron sends relevant Gmail content to its AI service provider to prepare answers, summaries, and drafts. The Privacy Policy identifies the provider and describes this processing.

Feron and its service providers do not use data from Google Workspace APIs, including Gmail, to develop, improve, or train generalized or non-personalized AI or machine-learning models. Feron does not sell your Gmail data or use it for advertising. See the service provider disclosures for details about data sharing.

Staff access

Feron processes email automatically. Access to systems holding connection tokens is restricted to authorized personnel, and staff do not routinely read Gmail content.

For support, a person may read specific Gmail content only after you affirmatively agree to that access. Human access without that agreement is limited to what is necessary to investigate a security issue or abuse, or comply with law.

Drafts and automated sending

The gmail.compose permission allows both drafting and sending. Feron uses it in two ways:

Assistant: when you ask for a follow-up, it creates drafts in your Gmail. It does not send them. You review, edit, and send from Gmail yourself.
Automated routines: Feron also offers follow-up routines. When you set one up, Feron can send the message you configured on your behalf, using the same gmail.compose permission. You control whether a routine exists and what it sends.

A routine can send without a separate review before each message. Check its settings before enabling it.

Disconnect Gmail in Feron

Open Feron and go to Connections.
Open your Gmail connection and choose Disconnect.
Feron deletes its stored access and refresh tokens for that connection and asks Google to revoke the grant.

Revoke access in Google

You can also revoke Feron directly from Google, independent of Feron:

Go to myaccount.google.com/permissions.
Select Feron in the list of third-party apps.
Choose Remove access.

After disconnecting

Once you disconnect in Feron or revoke access at Google, Feron can no longer read your Gmail, create drafts, or send routine follow-ups. Any feature that depends on Gmail will prompt you to reconnect. To also have Feron delete stored data associated with your account, see Data Deletion.

Gmail Connector