Privacy Policy

1.1 What Google user data we access

Lynkk accesses Google user data only after you connect your Google account, and only through the OAuth scopes you grant. Google Calendar and sign-in are requested when you connect Google. Gmail and Google Docs and Sheets are separate and optional: we ask for their scopes only when you turn them on on the Integrations page, and Google shows you those permissions before you agree. Lynkk does not read or search your email, and does not search your Google Drive or read files you have not linked to or that it did not create. The scopes, and the exact data each one gives us, are:

• Google Calendar, read (https://www.googleapis.com/auth/calendar.readonly): your calendar list, and your calendar events, including each event's title, description, start and end time, time zone, location, conferencing (Google Meet) link, recurrence, organizer, attendee names and email addresses, and response status.
• Google Calendar, write (https://www.googleapis.com/auth/calendar.events): the ability to create or update calendar events. We use it only for the specific events you ask us to create or change, with the title, time, guests, and Meet link you confirm.
• Sign-in and basic profile (openid, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/userinfo.profile): your Google account identifier, email address, name, and profile picture.
• Gmail, send (https://www.googleapis.com/auth/gmail.send), only if you turn on Gmail: sending an email that you have reviewed in full and confirmed, from your own Gmail address. This scope cannot read your mail, and we do not request any scope that can: Lynkk never reads, searches, deletes, archives, labels, or moves your email, saves drafts, changes your Gmail settings, or downloads attachments. When you ask for an email to finish yourself, Lynkk opens Gmail's compose window prefilled with the text, which needs no Google permission at all.
• Google Drive, files created by Lynkk (https://www.googleapis.com/auth/drive.file), only if you turn on Google Docs and Sheets: creating a new Google Doc or Sheet you have confirmed, and reading or listing the files Lynkk itself created. This scope cannot see your other files. We do not delete, move, or share your files, or change who can access them.
• Google Docs (https://www.googleapis.com/auth/documents), only if you turn on Google Docs and Sheets: reading the text of a Google Doc whose link you give Ask Lynkk, and adding text to, or replacing text in, a document you asked us to edit, after you confirm the change.
• Google Sheets (https://www.googleapis.com/auth/spreadsheets), only if you turn on Google Docs and Sheets: reading the cells of a spreadsheet whose link you give Ask Lynkk, and creating a spreadsheet, adding rows, or updating cells after you confirm the change.

Docs and Sheets are read live, not copied. We fetch a document's or spreadsheet's content from Google at the moment you ask a question about it, use it to answer that question, and then discard it. We do not store, copy, index, or build a searchable archive of your files. What we do keep is described in Section 1.6.

We also store the OAuth access and refresh tokens Google issues for your connection, so the features you enabled keep working without asking you to sign in again.

We do not request or access Google Tasks, Google Chat, Google Contacts, or Google Photos data, and we do not access any Google data outside the scopes listed above.

1.2 How we use Google user data

We use Google user data only to provide and improve the user-facing features you turned on:

• Showing your schedule: displaying your upcoming and past meetings inside Lynkk so you can see your day.
• Sending the notetaker bot: using an event's conferencing link and start time to join the calls you selected, at the right moment.
• Matching and labelling notes: linking a recording to the meeting it came from, and using the event title and attendee list to name and attribute the resulting note.
• Meeting preparation: producing a brief for an upcoming meeting from the event's title, description, time, and guest list, together with your related past notes.
• Answering your questions: responding when you ask Lynkk about your own schedule or meetings in chat or by voice.
• Creating events you ask for: scheduling or updating a calendar event when you request it. We show you the exact event before it is created and act only after you confirm.
• Answering questions from Docs and Sheets you link to: when you paste the link of a Google Doc or Sheet and ask Ask Lynkk something like “summarise this plan”, it reads that file and answers with a link back to it. It does not search your Drive and does not read your email.
• Sending email you ask for: for example, emailing the action items from a meeting to the people who were in it. We show you the full email (recipients, subject, and body) before anything is sent, and send it only after you confirm. If you would rather finish it yourself, we open Gmail's compose window with the text prefilled and you press Send there; nothing is sent or saved by Lynkk.
• Creating and editing Docs and Sheets you ask for: for example, turning a meeting note into a Google Doc, or adding action items as rows in a tracker sheet. We show you what will be written, and to which file, before the change is made, and act only after you confirm.
• Identifying your account: using sign-in and profile data to link your Google account to your Lynkk account and to show which account is connected.

We never write to your Google account (sending email, creating or changing events, documents, or spreadsheets) without your confirmation of that specific change. In a voice conversation with Lynkk, we read the change back to you and act only after you say yes.

Gmail, Docs and Sheets are used only in your own private conversations with Ask Lynkk: in the web and mobile apps, the desktop app, the voice assistant, and direct messages with the Lynkk Slack app (or Slack replies that only you can see). They are never used to answer in a shared Slack channel, and our meeting bot never reads your files aloud in a meeting.

We do not use Google user data, raw or derived, for advertising or ad targeting, for credit, lending, insurance, employment, or eligibility decisions, for building profiles to sell, or for any purpose unrelated to the features above.

1.3 Who we share, transfer, or disclose Google user data to

We do not sell Google user data, and we do not transfer it to data brokers, advertising networks, or information resellers. We share it only in these situations:

• With you, and with anyone you explicitly share a note or meeting with from inside the Service.
• With the people you choose to email: when you confirm an email, it is sent from your Gmail to the recipients shown on the confirmation.
• With Slack, when you ask there: if you ask the Lynkk Slack app a question in a direct message, the answer, which may draw on your email or files, is posted back to you in that direct message.
• With service providers who process it on our behalf, under contract, only to deliver the features described above, and only to the extent each one needs. These are: our cloud infrastructure provider (hosting, database, and file storage); MeetingBaas (the notetaker bot, which receives the meeting link and join time so it can join the call you selected); Anthropic (the AI model that writes your meeting brief, summary, and chat answers, which receives the event details, and the email and file content, needed for that specific request); and Cohere (embeddings for search over your own notes, where a note may contain calendar-derived text such as a meeting title or attendee name. Cohere never receives your Gmail or Google Drive content).
• When the law requires it, or where disclosure is necessary to investigate fraud or abuse, enforce our Terms, or protect the rights, property, or safety of our users or the public.
• In a business transfer, such as a merger, acquisition, or sale of assets, in which case the successor remains bound by this Policy for Google user data, and we will notify you before your data becomes subject to a different policy.

No Lynkk employee or contractor reads your Google user data, except with your explicit consent (for example when you ask for support and authorize it), where it is necessary for security purposes such as investigating abuse, where the law requires it, or where the data has been aggregated and anonymized so it no longer identifies you.

1.4 AI and machine learning: Limited Use compliance

The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

Lynkk does not use Google user data, whether raw, aggregated, anonymized, or derived, to develop, improve, or train generalized or foundational artificial intelligence or machine learning models, our own or anyone else's. We do not transfer Google user data to any third party that would use it for that purpose.

The AI providers that can receive Google user data are Anthropic (Claude models, used to generate meeting briefs, summaries, action items, and chat and voice answers, including answers drawn from your email and files, and the drafts of emails, documents, and spreadsheet rows you ask for) and Cohere (embeddings, used only to power search over your own notes). We call both directly over their paid, commercial APIs from our own infrastructure. Their API terms prohibit training on customer data, and we do not opt in to any model-improvement or data-sharing program. Data is sent only to answer the specific request you triggered, and the output is returned to you.

We do not route Google user data through AI aggregators, gateways, or model hubs, and we do not send it to consumer AI chat products. We do not operate self-hosted or offline models on Google user data. If we ever add an AI provider or route that can receive Google user data, we will update this section before doing so, and the Limited Use requirements above will continue to apply.

Our speech-to-text providers (Deepgram and AssemblyAI) process the audio you record. They do not receive Google user data.

1.5 How we protect Google user data

Google user data is protected by the following measures, which are specific to sensitive data and go beyond our general security practices:

• Encryption in transit: all traffic between your devices, our servers, Google's APIs, and our service providers travels over TLS 1.2 or higher.
• Encryption at rest: our databases and file storage are encrypted at rest.
• Additional encryption of credentials: your Google OAuth access and refresh tokens are separately encrypted with AES-256-GCM before being stored, using keys held outside the database, so a copy of the database alone does not yield usable credentials. Keys can be rotated without re-authorizing your account.
• Access control: every query for Google user data is scoped to the account that owns it. Internal access to production systems is restricted to the small number of personnel who need it, is individually authenticated, and is logged.
• Least privilege at the source: we request the narrowest Google scopes that support the features we offer, ask for Gmail and Docs and Sheets only when you turn them on, and store only the calendar fields our features use. Gmail access is send-only (we hold no scope that can read mail), Drive access reaches only files Lynkk creates or you link to, and we store no Gmail or Google Drive content.
• Your data only: Gmail, Docs and Sheets are always reached with your own authorization. Nobody else in your Lynkk workspace, including its admins, can send from your Gmail or read your files through Lynkk.
• Safeguards on writing: every email, document, and spreadsheet change needs your confirmation, is recorded in an audit log, and email sending is limited to 50 messages per day per account. Ask Lynkk is set up to treat instructions that appear inside an email or file as content, not as commands, and even then it cannot write anything without your confirmation.
• Secret handling: API keys and encryption keys are held in the runtime secret store, never in source control, and are not exposed to client applications.
• Incident response: we monitor for unauthorized access, investigate suspected incidents, and will notify affected users and regulators where the law requires it.

1.6 How long we keep Google user data, and how to delete it

While your connection is active. We keep a mirror of the calendar events relevant to the features you enabled, plus your encrypted OAuth tokens, only for as long as your Google account stays connected. Calendar events that pass out of the window we sync are removed on the next sync.

Gmail and Google Drive. We keep no copy of your email (which we cannot read) or your files. Two things are kept in your account: the answers Ask Lynkk gave you, in your chat history, until you delete the conversation; and a record of each change we made for you (for an email: the recipients, subject, time, and a link to it; for a document or spreadsheet: its title or file id, time, and a link), which does not include the email body or the text written. That record stays until you delete your account.

Turning Gmail or Docs and Sheets off. Switching Gmail or Google Docs and Sheets off on the Integrations page stops Lynkk using it immediately. Google keeps a single grant for your connection, so to end our access at Google itself, disconnect Google as described below.

When you disconnect Google. Disconnecting Google in your Lynkk settings revokes our OAuth tokens with Google (ending our access at Google itself, not only on our side), deletes the stored tokens immediately, deletes the calendar events we mirrored from your account, and stops all syncing and all Gmail and Drive access. You can also revoke our access at any time from your Google account permissions page, which has the same effect on our ability to reach your data.

Notes from meetings you recorded. If you recorded a meeting, its note and transcript are your own content and stay in your account until you delete them, even after you disconnect Google. Any calendar-derived detail inside such a note (for example the meeting title or an attendee name) is removed when you delete the note.

When you delete your account. Deleting your Lynkk account deletes the associated Google user data, including tokens, mirrored calendar events, notes, chat history, and records of changes we made for you, within 30 days, except where we must retain specific records to meet a legal or accounting obligation. Backups are overwritten on a rolling cycle and are purged within 90 days.

Requesting deletion. To request deletion of your Google user data at any time, email us at admin@lynkk.ai and we will action it within 30 days.

1.7 Google API Services User Data Policy

Lynkk'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.

2.1 What Slack data we access

• Workspace and account identifiers: the Slack workspace id and name, your Slack user id, display name, and timezone. The timezone is what lets the bot understand "last Tuesday".
• Messages addressed to the app: direct messages you send the bot, messages that mention it, and text you type after a slash command. We are not subscribed to your channel history and we do not receive messages that are not addressed to the app.
• A workspace access token, issued by Slack when the app is installed, which is what lets the bot post replies.

2.2 How we use it

Only to run the feature: to work out which Lynkk account is asking, to answer the question from that person's own notes (and, in a direct message, from a Google Doc or Sheet they link to, if they turned that on, as described in Section 1), and to post the answer back. Each person links their own account, so the bot never answers one person from another person's notes. We do not use Slack data for advertising or profiling, and we do not sell it.

2.3 Who we share it with

The question you ask is sent to Anthropic, our AI provider, together with the relevant passages of your own notes, in order to generate the answer. Search may involve Cohere, as described in the sub-processor section. No other recipient gets Slack data, and no processor is permitted to use it to train or improve their own generalized AI or machine learning models.

2.4 How we protect it

The workspace access token is encrypted at rest with AES-256-GCM and is never written to logs or shown in the product. Every request we receive from Slack is verified against Slack's request signature, with a short replay window, so we act only on traffic Slack actually sent. All traffic is over TLS.

2.5 How long we keep it, and how to delete it

We store the question you asked and the answer we gave in your own Ask Lynkk history, the same as if you had asked in the app, so you can find the conversation later. We keep no other Slack message content. The link between your Slack account and your Lynkkaccount is kept until you remove it.

You can unlink your Slack account at any time from Integrations in your dashboard, which stops the bot answering for you. Removing the app from your Slack workspace immediately revokes and deletes the stored access token. Deleting your Lynkk account removes the link and the stored conversations on the schedule in the retention section below. To ask us to do any of this for you, email admin@lynkk.ai.

2.6 Accuracy

Answers in chat apps are generated by AI from your notes and can be wrong or incomplete. Each answer cites the notes it drew on so you can check it. Do not rely on an answer for anything consequential without reading the source.