Fondline helps you manage contacts, maintain relationships, and send email sequences from your own Gmail account. This policy explains the information we access, how we use and store it, and your choices, including optional Google Calendar access for meeting preparation and contact meeting history.
Fondline is operated by Fondline LLC, which is the controller of the data described here. Questions about any of it go to help@fondline.com
Your connection choices
Connecting Gmail, Google Contacts, and Google Calendar is optional. You choose each connection independently and can use Fondline without connecting any of them. Signing in with Google does not by itself grant access to your email, contacts, or calendar.
Only features that depend on a connection require that connection: Gmail for sending campaigns and detecting replies; Google Contacts for importing or synchronizing your Google address book; and Google Calendar for calendar-based meeting preparation and contact meeting history. Features that do not depend on those connections remain available.
Choosing one connection does not require choosing another. Fondline will request the permissions for the connection you select and explain what they enable. You may decline access; accepting these terms or this privacy policy does not grant Google permissions.
What Fondline reads from your Gmail
Message headers only — never the contents of your mail. Fondline requests Gmail’s gmail.metadata scope, which returns senders, recipients, subjects, dates and threading identifiers, and which cannot return a message body even if the code asked for one. It also requests gmail.send to send the messages you compose in Fondline, and your email address to know which account was connected.
Headers help Fondline detect replies, bounces and out-of-office responses, keep follow-ups in the right thread, and confirm whether a send completed so it can avoid duplicate messages. Fondline does not retrieve message bodies or attachments from your mailbox. It does store and transmit the outgoing message text you compose in Fondline so that it can send your campaigns.
The Fondline for Gmail Chrome extension
The optional Chrome extension shows the people on the Gmail thread you have open as your Fondline contacts, in Chrome’s side panel. It reads only the names and email addresses shown in that thread’s header lines, from the Gmail page itself. It does not read subjects, message bodies, or attachments, and it does not use your Gmail connection.
The extension keeps those names and addresses in Chrome’s session storage, which is held in memory and cleared when the browser closes, and sends them to fondline.com only to look up matching contacts in your workspace while you are signed in. Looking someone up does not save them; a person is added to your contacts only when you choose to add them.
Google Contacts
Connecting Google Contacts is optional. The connection requests access to your saved Google Contacts and read-only access to automatically saved Other Contacts together. Both can be included in your optional contact import, without connecting Gmail. When you enable import or synchronization, Fondline reads and stores contact records returned by Google, including names, email addresses, phone numbers, addresses, organizations, profile links, photo links, notes, birthdays, other dates, labels, and additional fields on those records. It uses this information to import contacts, match existing contacts, and keep their details up to date.
If you enable synchronization of starred contacts, Fondline can also create and update contacts in Google. Removing a contact from that sync can delete a Google contact Fondline created; a pre-existing contact adopted by the sync is kept, with Fondline’s link and star removed. Sync may remove duplicate Google contacts that Fondline created. Importing alone does not enable these writes.
Google Calendar
Connecting Google Calendar is optional. Fondline asks for separate, read-only permission before accessing your calendars. Updating this policy does not connect your calendar or grant that permission.
You select which calendars to connect. Fondline reads and stores their calendar names and identifiers, event titles, start and end times, time zones, organizers, attendees and their response status, locations, descriptions, meeting links, and event identifiers and status. This information helps you prepare for upcoming meetings and see past and upcoming meetings associated with a contact, by matching attendee email addresses to your Fondline contacts.
Access is read-only: Fondline does not create, change, or delete Google Calendar events. An invitation or RSVP does not confirm that someone attended. Calendar descriptions are separate from Gmail message bodies; the Gmail restriction above does not exclude text that appears in a calendar event description.
What Fondline stores
- Your account details, workspace memberships, and integration settings.
- The contacts you create or import, their source records, notes, and labels.
- The campaigns and message text you write.
- Sending and reply records, including recipients, times, and message and thread identifiers.
- Operational and audit records used to run, secure, and troubleshoot the service.
- Your Google authorization credentials, stored in encrypted form with access restricted to the services that need them to operate your connected features.
Workspaces and tools you authorize
Contacts and other records you place in a shared workspace are available to its members according to their permissions. Choose the destination workspace carefully when importing contacts. Tools and AI agents you authorize can access data and act within the permissions you give them. Information you export or share through those tools is also subject to their providers’ practices.
Fondline also maintains a shared contact-identity directory. For participating workspaces, contact names, email addresses, and social profile links can contribute to matching the same person across workspaces and providing relationship features. This is separate from access to the full contact record within a workspace.
Contacts imported from Google are excluded from that shared directory. A contact that came from your Google Contacts or Other Contacts — and any record it is later merged with — stays inside the workspace you imported it into. It does not contribute to cross-workspace matching, is not used for the profile lookup described below, and is not included in any shared company or relationship directory.
Where contact profile lookup is available, Fondline can use a public profile URL you supply to obtain public professional information through a service provider and fill in contact details. Public profile information may be cached separately and reused for the same profile across Fondline accounts.
What Fondline does not do
- No tracking pixels, and no rewriting of your links.
- No selling your personal data or using Google user data for advertising.
- No use of your data to train machine learning models.
- No staff access to your Google data for routine browsing. Human access is limited to your specific consent, security investigations, or legal requirements.
Google user data
Fondline’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and to the Google Workspace user data and developer policy. These protections also apply to information derived from Google data. Google data is used to provide the features described here; it is not sold to data brokers, used for advertising or credit decisions, or used to train machine learning models. Transfers are limited to providing features you authorize, security needs, legal requirements, or a business transfer with your explicit prior consent, as permitted by Google’s policies. You can revoke Fondline’s access at any time at your Google account permissions.
Deleting your data
Settings → Account deletes your account, the workspaces only you belong to, their campaigns and contacts, the record of what was sent, your sign-in identity, and your stored Google authorization credentials, contact source records, calendars, and saved meetings. Cached identity facts contributed by the deleted records are removed unless independently supported by surviving records. Shared workspaces with other members remain, along with their records; you may need to transfer ownership or move campaigns that use your mailbox before deletion can proceed. Deletion from the active application cannot be undone. Copies may remain in infrastructure backups until those backups expire.
Revoking access in Google stops future authorized access but does not itself delete information already imported into Fondline. Deleting your Fondline account does not unsend email or undo changes already synchronized to Google Contacts. Use Google’s account permissions to revoke access separately. Contact us to request access, correction, or deletion of personal information, including questions about retained copies or records in a shared workspace.
Who else handles it
Data is stored in the United States. We use service providers for cloud hosting, database storage, and transactional email, such as account invitations. These providers process the information needed to perform those functions for Fondline. Public profile lookup also uses a provider of public professional information, as described above. We process data on servers to operate these features, including background sending and contact synchronization.
Changes to this policy
We will notify users of material changes. Before accessing a new category of Google data or using it for a new purpose, we will provide the relevant disclosure and obtain the required consent.
Questions: help@fondline.com