Privacy Policy — LPH Meet

Version 2.0 — May 2026

Leads Per Hour LTDA ("LPH") operates an artificial intelligence platform for B2B sales. This Privacy Policy applies to LPH Meet (Broadcast/Coach): a live AI assistant for video conferences that provides pre-call briefings, real-time sentiment and objection detection, battle cards, suggested next steps, and post-call CRM updates and scorecards.

By accessing or using LPH Meet (Broadcast/Coach), you represent that you have read, understood, and accepted this Policy. If you do not agree, do not use the Services. This Policy is designed to comply with the Brazilian General Data Protection Law (LGPD), the European General Data Protection Regulation (GDPR), and the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA).

1. Who We Are and Our Roles in Data Processing

1.1 When LPH Acts as Processor

In most situations, LPH acts as data processor, processing personal data in accordance with the Customer's instructions, who is the controller. In these cases, the obligations of transparency and obtaining consent from data subjects belong to the Customer.

1.2 When LPH Acts as Controller

LPH acts as controller when it autonomously defines the purposes and means of processing — for example, when processing data of LPH's own Customers and platform users for managing the commercial relationship, when developing AI models with genuinely anonymized data, or when complying with LPH's own legal obligations.

2. What Data We Collect

2.1 Customer and Platform User Data

To enable the provision of the Services and the management of the commercial relationship, LPH collects the following data from the Customer's representatives and Authorized Users:

  • Identification data: full name, role, company, tax ID;
  • Contact data: business email, phone, WhatsApp;
  • Access data: login credentials, access logs, IP address, device used;
  • Platform usage data: features accessed, configurations, history of support interactions;
  • Financial data: billing information, tax ID for invoice issuance (we do not store credit card data).

2.2 Automatically Collected Data

When accessing the platform, LPH automatically collects:

  • IP address, device and browser type, operating system;
  • Pages accessed, session duration, and navigation flow;
  • Cookie data and similar technologies, as described in Section 10.

2.3 Product-Specific Data

LPH Meet (Broadcast/Coach) processes additional categories of data specific to its function, including data accessed through Google Workspace APIs. See the product-specific section below for the complete description and the Google Limited Use disclosure.

Google Calendar Integration (user-initiated). When an Authorized User connects their Google account via the Integrations feature of the platform, LPH collects and stores: (i) an OAuth access token and refresh token issued by Google, which authorize LPH to read the user's calendar data on their behalf; and (ii) the e-mail address of the connected Google account, extracted from the OpenID Connect identity token at the time of authorization. LPH reads calendar events solely to identify upcoming commitments of the Authorized User and cross-reference them with calls registered in the platform. Raw calendar event data is fetched on demand and is not persistently stored by LPH beyond what is necessary to display results in the user interface.

3. Why We Use the Data — Purposes

3.1 Provision of Contracted Services

The primary use of data is the operation of the Services contracted by the Customer. Without this data, it is not possible to deliver the Services.

3.2 Management of the Commercial Relationship

Customer and platform user data is used for: invoice issuance and billing; communications about contracted Services; technical support; and renewals or contract changes.

3.3 Service Improvement and AI Development

LPH uses anonymized and aggregated data for identifying errors and improvements in the platform and developing AI models. Identifiable personal data obtained from Google Workspace APIs is never used to train, develop, or improve generalized or non-personalized AI/ML models. See the Google Limited Use disclosure below.

3.4 Compliance with Legal Obligations

LPH may process personal data to comply with legal, regulatory, judicial, or administrative obligations, disclosing only the minimum necessary.

3.5 Security and Fraud Prevention

Platform access and usage data are used for security monitoring, detecting improper use, fraud prevention, and protection of system integrity.

4. Legal Bases for Processing

LPH processes personal data only when a valid legal basis exists under the LGPD (arts. 7 and 11), the GDPR (art. 6 and art. 9), and applicable U.S. state privacy laws including the CCPA/CPRA.

Purpose
Provision of contracted Services
LGPD Basis
Performance of contract (art. 7, V)
GDPR Basis
Performance of contract (art. 6(1)(b))
Purpose
Customer relationship management
LGPD Basis
Performance of contract (art. 7, V)
GDPR Basis
Performance of contract (art. 6(1)(b))
Purpose
Platform / AI model improvement
LGPD Basis
Legitimate interest or anonymized data
GDPR Basis
Legitimate interest or anonymized data
Purpose
Compliance with legal obligation
LGPD Basis
Legal obligation (art. 7, II)
GDPR Basis
Legal obligation (art. 6(1)(c))
Purpose
Security and fraud prevention
LGPD Basis
Legitimate interest (art. 7, IX)
GDPR Basis
Legitimate interest (art. 6(1)(f))
Purpose
Google Calendar integration (user-initiated)
LGPD Basis
Consent (art. 7, I)
GDPR Basis
Consent (art. 6(1)(a))

Additional legal bases specific to LPH Meet (Broadcast/Coach) are described in the product-specific section below.

5. Sharing and International Data Transfer

5.1 Categories of Recipients

LPH may share personal data with the following recipients:

  • Service providers and sub-processors: cloud infrastructure providers (including Google Cloud Platform), video conferencing platforms, CRM and analytics tools — contractually obligated to maintain equivalent protection standards;
  • Customers: in the course of providing the Services, LPH shares generated outputs with the contracting Customer;
  • Competent authorities: when required by law, judicial decision, or administrative authority request, only to the extent strictly necessary;
  • Acquirers in corporate transactions: in the event of a merger, acquisition, or sale of LPH's assets, with notice to users.

5.2 International Transfer

LPH uses cloud infrastructure that may be located outside Brazilian territory. International transfers are made under:

  • European Union / EEA: Standard Contractual Clauses (SCCs) approved by the European Commission, under art. 46 of the GDPR;
  • Brazil: for data sent to countries with an adequate level of protection recognized by the ANPD, the transfer occurs without additional requirements;
  • Other countries: SCCs approved by ANPD Resolution No. 19/2024.

5.3 No Sale of Data — CCPA/CPRA Statement

LPH does not sell, rent, share, or assign personal data to third parties for marketing or advertising purposes independent of the Services contracted by the Customer. For purposes of the California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA), LPH does not "sell" or "share" personal information as those terms are defined under California law.

6. Data Retention and Deletion

LPH retains personal data only for the time necessary to fulfill the purposes that motivated its collection:

Data Category
Customer and platform user data
Retention Period
During contract term + 5 years
Basis
Civil claims statute of limitations.
Data Category
Google Workspace API data
Retention Period
Only as long as needed for the user-facing feature
Basis
Per Google Limited Use requirements.
Data Category
Access and security logs
Retention Period
6 months or specific legal term
Basis
Art. 15, Brazilian Internet Civil Framework.
Data Category
Tax and financial data
Retention Period
5 years after invoice issuance
Basis
Tax and accounting obligations.
Data Category
Consent records
Retention Period
5 years after revocation or end of relationship
Basis
Required for evidence of legal compliance.
Data Category
Google Calendar OAuth tokens and connected account e-mail
Retention Period
Until the user disconnects the integration or terminates the account, whichever comes first. Upon disconnection, tokens are revoked with Google and deleted from LPH’s database immediately.
Basis
User consent / contract termination

Additional product-specific retention periods are described in the product-specific section below. After the applicable retention period ends, data is securely deleted or irreversibly anonymized.

7. Information Security

7.1 Technical and Organizational Measures

LPH adopts technical and organizational measures consistent with market standards to protect personal data. Data is encrypted in transit (TLS 1.2+) and at rest (AES-256).

7.2 Incident Notification

In the event of a Data Breach that may pose risk or harm to data subjects, LPH will notify the Customer within no more than 72 (seventy-two) hours after becoming aware of the incident, with the information necessary to comply with communication obligations to the ANPD (LGPD art. 48) and to affected data subjects under the GDPR (art. 33).

8. Data Subject Rights

Under the LGPD (arts. 17 to 22), the GDPR (arts. 15 to 22), and the CCPA/CPRA, you have the following rights:

Right
Confirmation and Access
Description
Obtain confirmation of the existence of processing and access to the personal data held by LPH.
Right
Rectification
Description
Request correction of incomplete, inaccurate, or outdated data.
Right
Deletion
Description
Request deletion of data when unnecessary, processed unlawfully, or when consent is withdrawn.
Right
Portability
Description
Receive the personal data provided in a structured, commonly used format.
Right
Restriction of Processing
Description
Request suspension of processing while there is a dispute about its lawfulness or necessity.
Right
Objection
Description
Object to processing carried out on the basis of legitimate interest.
Right
Withdrawal of Consent
Description
Withdraw consent at any time, without prejudice to processing carried out before withdrawal.
Right
Review of Automated Decision
Description
Request human review of decisions made solely by automated means.
Right
Right to Know (CCPA)
Description
Request disclosure of categories of personal information collected, sources, purposes, and recipients.
Right
Right to Opt-Out (CCPA)
Description
Opt out of the sale or sharing of personal information (note: LPH does not sell or share).
Right
Non-Discrimination
Description
Not be discriminated against for exercising any privacy right.
Right
Petition to Authority
Description
File a complaint with the ANPD (Brazil), the relevant supervisory authority (EU), or the California Privacy Protection Agency.

8.1 How to Exercise Your Rights

You may exercise your rights at any time by contacting privacy@leadsperhour.com. LPH will respond within no more than 15 (fifteen) days (LGPD) or 30 days (GDPR/CCPA).

8.2 Revoking Google Account Authorization

You may revoke LPH's access to your Google account in two ways: (i) directly within the platform, by navigating to Integrations and clicking Disconnect next to Google Calendar — this immediately revokes the token with Google and deletes all stored credential data from LPH's database; or (ii) by visiting your Google Account permissions page. Revocation by either method immediately stops LPH from accessing your Google Calendar data. Revocation does not affect lawful processing performed prior to revocation.

9. Minors

LPH's Services are intended exclusively for individuals over 18 years of age or for companies represented by their legal representatives. LPH does not knowingly collect personal data from minors under 18. If LPH becomes aware that data from minors has been inadvertently collected, it will take steps to delete it promptly.

10. Cookies and Tracking Technologies

LPH uses essential, analytical, and performance cookies on the platform. LPH does not use third-party cookies for targeted advertising. Users can manage cookie preferences in their browser settings.

11. Changes to This Policy

LPH may update this Policy from time to time. Material changes will be communicated to the Customer with at least 15 (fifteen) days' prior notice via the registered email.

12. Contact and Data Protection Officer

To exercise rights, clarify questions, file complaints, or report incidents related to personal data, you may contact LPH's Data Protection Officer (DPO):

Item
Controller
Information
Leads Per Hour LTDA
Item
CNPJ
Information
57.835.053/0001-40
Item
Address
Information
Rua Nereu Ramos, 165, Sala 201, Andar 2, Centro, Blumenau, SC, CEP 89010-019, Brazil
Item
Privacy Email
Information
privacy@leadsperhour.com
Item
Response Time
Information
Up to 15 business days (LGPD) / 30 days (GDPR & CCPA)

13. LPH Meet — Specific Data Practices

13.1 Data Processed

When LPH Meet is active during a session, it processes the following categories of data, in addition to those described in Section 2:

  • Biometric data: facial images and facial geometry points captured during the video call to infer engagement and attention metrics;
  • Audio transcripts and inferred engagement / sentiment metrics;
  • Session metadata: date, time, duration, participant identifiers;
  • CRM and lead context fetched to compose the pre-call briefing.

Raw biometric data (video frames and facial templates) are processed in real time and are not retained by LPH after the session ends, except for specific configurations contracted with an adequate legal basis. Analytical outputs (metrics and indicators) may be retained as configured by the Customer, up to 2 years.

13.2 Legal Basis — Specific Consent

Because LPH Meet processes biometric data (LGPD art. 5, II; GDPR art. 9), processing requires specific, prominent, free, informed, and unambiguous consent from each participant before each session in which the assistant is active. Legitimate interest is not available as a legal basis for this processing.

The consent must:

  • Be obtained before the start of each session in which analysis is active;
  • Be documented in a way that allows subsequent verification;
  • Clearly describe that the video conference will be analyzed by an AI system that processes facial expressions for the purpose of supporting the negotiation;
  • Be distinct from any other consents (e.g., meeting recording);
  • Provide an easy-revocation mechanism, the exercise of which immediately ends the analysis.

The Customer is solely responsible for implementing and documenting this consent flow.

13.3 Purpose Limitations

LPH Meet outputs may only be used for:

  • supporting the sales rep during real-time negotiation;
  • analyzing the meeting performance by the sales rep themselves.

It is prohibited to use the outputs for:

  • biometric identification of participants;
  • employment decisions about Authorized Users;
  • permanent behavioral profiles without specific consent;
  • training of sales reps in LPH Roleplay, without separate consent from data subjects for that new purpose.

13.4 Google Calendar Integration

The Integrations feature allows Authorized Users to voluntarily connect their Google Calendar account to the platform. The following practices apply specifically to this integration:

Authorization: The connection is established via Google's OAuth 2.0 authorization flow. The user grants access explicitly through Google's consent screen. The requested scopes are calendar.readonly (read access to all calendars and events), openid, and email (to identify the connected account).

Data stored: LPH stores the OAuth access token, refresh token, token expiry metadata, and the e-mail address of the connected Google account. No calendar event content is persistently stored.

Data use: Stored tokens are used exclusively to retrieve the Authorized User's upcoming calendar events on their behalf, for the purpose of identifying meetings to cross-reference with calls registered in the platform. This data is not shared with other users, used for advertising, or used to train AI/ML models.

User control: The Authorized User may disconnect the integration at any time from the Integrations screen. Upon disconnection, LPH immediately revokes the OAuth token with Google and permanently deletes the stored credentials from its database. The user may reconnect at any time by re-authorizing through the same flow.

Token refresh: LPH may automatically refresh the access token using the stored refresh token, without requiring re-authorization, to maintain uninterrupted service. The user can prevent this at any time by disconnecting the integration.

Google API Services — Limited Use Disclosure

LPH Meet requests authorization to access the following Google Workspace API scopes. Each scope is requested in a distinct authorization flow, as described below:

API
Google Calendar API
Scope
calendar.readonly
Purpose
Read the Authorized User's calendars and events to identify upcoming meetings and cross-reference them with calls registered in the platform. Access is read-only; LPH does not create, modify, or delete any calendar data.

LPH Meet's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.

Specifically, LPH Meet affirms that:

  • The use of information received from Google APIs is limited to providing or improving user-facing features that are prominent in the requesting application's user interface.
  • Data obtained from Google APIs is not transferred to others except as necessary to provide or improve user-facing features, comply with applicable law, or as part of a merger, acquisition, or sale of assets (with notice to users).
  • Data obtained from Google APIs is not used or transferred for serving advertisements, including retargeted, personalized, or interest-based advertising.
  • Humans do not read the data unless: (a) we have the user's affirmative agreement for specific messages, (b) it is necessary for security purposes such as investigating abuse, (c) it is needed to comply with applicable law, or (d) the data has been aggregated and anonymized for internal operations.
  • Data obtained from Google APIs is not used to train or improve generalized / non-personalized AI or machine learning models.

14. Jurisdictional Notices

European Union — EU AI Act art. 5(1)(f): may prohibit AI systems that infer emotions of natural persons in the workplace context. Customers using LPH Meet in sessions with EU participants are responsible for verifying applicability before enabling the product.
United States — Illinois BIPA / Texas CUBI / Washington MHMDA: require prior written consent for the collection of biometric data, with fines of USD 1,000 to USD 5,000 per violation under BIPA. The Customer assumes responsibility for compliance in sessions with U.S. participants.

14.1 Scientific Limitations

The Customer acknowledges that the relationship between facial expression and internal emotional state is the subject of scientific debate and that the generated indicators are probabilistic estimates. Outputs must be treated as inputs to support human decision-making, never as objective determinations of the participant's emotional state.

Blumenau, May 2026.

Leads Per Hour LTDA

leadsperhour.com · lphmeet.com

Privacy Channel

Questions about your data, requests for access, correction, deletion, portability, or to exercise any right under the LGPD, GDPR, or CCPA/CPRA. Email privacy@leadsperhour.com. We respond within 15 business days (LGPD) or 30 days (GDPR/CCPA).