Privacy Policy

Privacy Policy | Klynt – Sales Intelligence

Privacy Policy

Last updated: April 8, 2026

Klynt’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

1. Introduction

Klynt (hereinafter “we,” “our,” or “Klynt”) is a Sales Intelligence platform operated by Kevin Le Clainche. Klynt automatically analyzes sales calls conducted via Google Meet, generates AI-powered analysis based on the MEDDIC methodology, and syncs results to HubSpot CRM.

This Privacy Policy describes how we collect, use, store, share, and protect the information of our platform users, including specifically data obtained through Google APIs.

By registering for and using Klynt, the user agrees to the practices described in this Policy. If you do not agree with any of these practices, you should not use the platform.

Website: https://goklynt.com
Application: https://app.goklynt.com
Contact: kevin@goklynt.com

2. Data We Collect

2.1 User Account Data

  • Full name
  • Email address
  • Company or organization name
  • Authentication credentials (managed securely via OAuth 2.0)

2.2 Data Obtained from Google Calendar (Google API)

When the user connects their Google Calendar account to Klynt, we access the following information:

  • List of calendar events (title, date, time, duration)
  • Google Meet URL associated with each event
  • Event attendee list (names and email addresses)

This data is used exclusively to identify scheduled sales meetings and automatically send the Klynt recording bot to those meetings, according to the user’s configuration.

2.3 Google Meet Recording Data

When the Klynt bot joins a Google Meet meeting (either automatically via calendar or manually by the user), we collect:

  • Audio and video of the meeting
  • Full transcript of the call with speaker identification (diarization)
  • Meeting metadata (duration, participants, date, and time)

The Klynt bot visibly identifies itself as a meeting participant under the name “Klynt,” ensuring all participants are aware that the meeting is being recorded.

2.4 AI-Generated Data

From the transcriptions, Klynt automatically generates the following using artificial intelligence:

  • Executive call summary
  • MEDDIC analysis (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion)
  • Call Score across 6 dimensions
  • Personalized coaching with improvement suggestions
  • Risk signals and detected objections
  • Deal intelligence (strategy, stakeholders, competitors, evolution)

2.5 HubSpot CRM Data

When the user connects their HubSpot account, Klynt accesses:

  • Active deals (name, amount, stage, close date)
  • Sales pipeline stages
  • Associations between meetings and deals

And automatically creates in HubSpot:

  • Notes with call summary and analysis
  • Follow-up tasks

3. How We Use the Data

We use the collected data exclusively to provide and improve Klynt’s user-facing features that are visible and prominent in the application’s user interface. Specifically:

Data TypePurpose
Google Calendar eventsIdentify sales meetings and automatically schedule the recording bot according to the user’s settings
Google Meet recordingsGenerate speaker-diarized transcriptions for subsequent analysis
TranscriptionsAutomated AI analysis: MEDDIC summary, scoring, coaching, objection and risk detection
HubSpot dataLink calls to deals, automatically sync notes and follow-up tasks
Account dataAuthentication, account management, and communication with the user

We do not use Google data for any purpose other than those described above. Specifically:

  • We do NOT sell user data to third parties
  • We do NOT use Google data for advertising, retargeting, or interest-based advertising
  • We do NOT use Google data to determine creditworthiness or for lending purposes
  • We do NOT transfer Google data to data brokers or information resellers
  • We do NOT use Google data to train generalized or non-personalized AI/ML models

4. Google API Services User Data Policy Compliance

Klynt’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In compliance with Google’s Limited Use requirements, Klynt commits to:

  • Limit the use of data obtained from Google APIs exclusively to providing or improving user-facing features that are visible and prominent in Klynt’s user interface.
  • Not transfer data to third parties except when necessary to provide or improve said features, for security purposes, to comply with applicable law, or as part of a merger or acquisition (with prior user consent).
  • Not allow humans to read user data unless the user has given affirmative consent to view specific messages, files, or other data; it is necessary for security purposes; or it is required by law.
  • Not use or transfer data for serving ads, including retargeting, personalized, or interest-based advertising.
  • Not use data to train generalized or non-personalized AI or machine learning models.

5. Who We Share Data With

To provide the service, Klynt shares data with the following technical sub-processors. All of them act exclusively as data processors under our instructions:

Sub-processorFunctionData SharedLocation
Recall.aiMeeting recording and speaker-diarized transcriptionMeeting audio/video, event metadataEU (eu-central-1)
OpenAIAI-powered transcript analysis (summary, MEDDIC, scoring, coaching)Transcript text only (no audio or video)United States
HubSpotUser’s CRM, note and task synchronizationCall summary, score, follow-up tasksUnited States
Bubble.ioApplication hosting and databaseAll platform dataUnited States

We do not share data with any other company, organization, or individual outside the sub-processors listed above, except in the following cases:

  • User consent: when the user explicitly authorizes us to share their data.
  • Legal obligation: when required by law, regulation, legal process, or applicable governmental request.
  • Protection of rights: when necessary to protect the rights, property, or safety of Klynt, our users, or the public.

6. Data Storage and Security

6.1 Storage Location

Klynt data is stored on Bubble.io servers (United States) and Recall.ai (EU, region eu-central-1). Video recordings are stored temporarily on Recall.ai and are accessible via pre-signed URLs with expiration.

6.2 Security Measures

We implement the following measures to protect user data:

  • Encrypted communications via HTTPS/TLS for all data transmissions
  • OAuth 2.0 authentication for Google and HubSpot connections (no password storage)
  • Access tokens stored securely and renewed periodically
  • Restricted database access via per-company privacy rules (multi-tenant)
  • Pre-signed URLs with expiration for video recording access

6.3 Data Retention

We retain user data for as long as the account is active and the service is in use. Specific retention periods are:

  • Transcriptions and call analyses: retained while the account is active
  • Video recordings: stored temporarily on Recall.ai (maximum 7 days for pre-signed URLs)
  • Google Calendar data: processed in real-time for bot scheduling and not permanently stored
  • Google and HubSpot authentication tokens: stored while the integration is active and revoked upon disconnection

When the retention period expires or the user requests deletion, we will securely delete or anonymize the data.

Users may request deletion of their data at any time by contacting kevin@goklynt.com.

7. User Rights

Users have the following rights over their personal data:

  • Right of access: request a copy of the personal data Klynt has stored.
  • Right of rectification: request the correction of inaccurate or incomplete data.
  • Right of erasure: request the deletion of personal data. This includes the deletion of transcriptions, analyses, scores, and any data derived from recordings.
  • Right of portability: request the export of data in a structured, machine-readable format.
  • Right to object: object to the processing of data for specific purposes.
  • Right to revoke Google permissions: the user may revoke Klynt’s access to their Google account at any time by visiting https://myaccount.google.com/permissions. Revocation will prevent Klynt from accessing new Google Calendar and Google Meet data but will not automatically delete data that has already been processed. To request deletion of previously processed data, the user must contact us.

To exercise any of these rights, users may contact us at kevin@goklynt.com. We will respond to requests within a maximum of 30 days.

8. Legal Basis for Data Processing (GDPR)

In compliance with the General Data Protection Regulation (GDPR) of the European Union, the legal bases for personal data processing are:

Processing ActivityLegal Basis
Account creation and managementPerformance of contract (Art. 6(1)(b) GDPR)
Meeting recording and transcriptionExplicit user consent (Art. 6(1)(a) GDPR)
Google Calendar accessExplicit user consent (Art. 6(1)(a) GDPR)
AI-powered call analysisPerformance of contract (Art. 6(1)(b) GDPR)
HubSpot synchronizationExplicit user consent (Art. 6(1)(a) GDPR)
Service communicationsLegitimate interest (Art. 6(1)(f) GDPR)

The user may withdraw consent at any time without affecting the lawfulness of processing based on consent prior to its withdrawal.

9. International Data Transfers

Some of our sub-processors (OpenAI, HubSpot, Bubble.io) are located in the United States. Personal data transfers to these sub-processors are carried out with appropriate safeguards in accordance with the GDPR, including:

  • Standard Contractual Clauses (SCCs) approved by the European Commission
  • Transfer impact assessments where necessary
  • Supplementary technical measures including encryption and anonymization

Recording and transcription data is processed by Recall.ai in the eu-central-1 region (Frankfurt, Germany), within the European Economic Area.

10. Cookies and Tracking Technologies

Klynt uses only essential cookies required for the platform to function:

  • Session cookies: to maintain the authenticated user session.
  • Preference cookies: to remember user settings within the application.

We do not use advertising cookies, third-party tracking cookies, or any tracking technologies for marketing or advertising purposes.

11. Children’s Privacy

Klynt is a B2B sales intelligence platform and is not directed at individuals under 18 years of age. We do not knowingly collect data from minors. If we become aware that we have collected data from a minor, we will promptly delete it.

12. Changes to This Privacy Policy

We reserve the right to update this Privacy Policy at any time. When we make material changes:

  • We will notify users via email or in-app notification
  • We will update the “Last updated” date at the top of this policy
  • If changes affect the use of Google data, we will request user consent before applying the new practices

Continued use of Klynt after the publication of changes constitutes acceptance of the updated Policy.

13. Contact

For any questions, requests, or complaints related to this Privacy Policy or the processing of your personal data, you may contact us at:

Klynt

Data Controller: Kevin Le Clainche

Email: kevin@goklynt.com

Website: https://goklynt.com

If you believe that the processing of your personal data violates applicable regulations, you have the right to file a complaint with the competent data protection authority in your country of residence.