Privacy Policy

Overview

This Policy describes how TLJ Apps handles information in the TLJ Meet para Bitrix24 application (also listed as "Google Meet for Bitrix24" on the Bitrix24 marketplace). The Application lets you schedule Google Meet meetings from Bitrix24 deals, leads and smart processes, invite attendees, and automatically receive post-meeting data (duration, attendees, recording and transcript) on the corresponding card.

Google Data We Access

With your explicit authorization via Google OAuth, the Application accesses:

Google Calendar (calendar scope): creating, rescheduling and cancelling events with a Meet link on your calendar, including free/busy lookups to suggest time slots.
Google Meet (meetings.space.created and meetings.space.readonly scopes): reading conference records after the meeting ends — duration, attendees and, when available on your Google Workspace plan, recording and transcript.
Meeting settings (meetings.space.settings scope): when the portal administrator turns the option on, the Application pre-configures automatic recording, transcription and Gemini notes on the meeting it creates, so nobody has to start the recording by hand. If the option is off, nothing is changed.
Email and basic identity (openid and email scopes): only to display which account is connected.

What We Store

Each connected user's Google refresh token, encrypted in transit and stored on Cloudflare infrastructure, used exclusively to operate meetings on your behalf.
Technical meeting records (title, dates, Meet link, source portal and card, and the post-meeting summary) for up to 180 days, to enable rescheduling, cancellation and delivery of data to Bitrix24.
Bitrix24 portal integration tokens, used only to write results back to your CRM.

Post-meeting data (duration, attendees, recording link and transcript text) is written directly to your Bitrix24 and remains under your control. We do not keep a copy of the transcript beyond the temporary technical record.

Limited Use (Google API Services)

The Application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google data is used only to provide the Application's user-facing features, is never sold, is not used for advertising, and is not read by humans except with your consent, for security purposes, or to comply with applicable law.

With Whom We Share, Transfer or Disclose Google User Data

TLJ Apps does NOT sell, rent or trade Google user data. We do not share it with advertisers, data brokers, ad networks or any third party for their own purposes. We do not use Google data to develop, improve or train generalized AI or machine learning models. Google data obtained by the Application is shared, transferred or disclosed solely in the following situations:

With your own Bitrix24 portal (the intended recipient): meeting data — Meet link, duration, attendee list, recording link and transcript text — is written to the CRM card you selected. This transfer is the very purpose of the Application and happens on your instruction. From that point the data is subject to your agreement with Bitrix24 and to your own access controls.
With Google LLC: the Application's calls to the Google Calendar and Google Meet APIs, required to create meetings and read post-meeting data.
With Cloudflare, Inc., as an infrastructure sub-processor: the Application runs on Cloudflare Workers and stores tokens and technical records in Cloudflare Workers KV. Cloudflare processes this data solely to host and store it on our behalf, under contract, and is not permitted to use it for its own purposes.
With Stripe, Inc., only to charge the Application's subscription. Stripe does NOT receive any Google user data — no tokens, no meeting data, no recordings or transcripts.
When required by law: in response to a court order, a valid request from a competent authority or a legal obligation, or to investigate, prevent and address fraud, abuse or security threats — always limited to the minimum necessary.
In a merger, acquisition or asset sale: only if the acquirer assumes the obligations of this Policy in writing; you will be notified in advance and may revoke access before any transfer.

Our staff does not read the content of your meetings, recordings or transcripts, except with your explicit consent (for example, when you open a support request and authorize the review), where required by law, or to investigate a specific security incident.

How We Protect Sensitive Data

We treat Google and Bitrix24 OAuth tokens and meeting data (attendees, recording links and transcript text) as sensitive. We apply the following protection mechanisms:

Encryption in transit: all traffic uses HTTPS with TLS 1.2 or above, both between your browser and the Application and on calls to the Google and Bitrix24 APIs. No endpoint is served over plain HTTP.
Encryption at rest: tokens and technical records live in Cloudflare Workers KV, which encrypts data at rest (AES-256). Application credentials (client secrets, API keys) are held in Cloudflare Secrets, encrypted and never present in source code or logs.
Tokens never reach the browser: the Google refresh token is used server-side only (Cloudflare Worker). It is never sent to the front-end, never placed in URLs and never written to logs.
Access control and per-portal isolation: every Application request is authenticated against the originating Bitrix24 portal, and data is segregated by portal identifier so that one customer cannot reach another's data. Administrative endpoints require a separate secret key.
Least privilege: we request the minimum set of OAuth scopes needed for the features offered and request no restricted scopes. Our team's access to the infrastructure is limited to essential personnel and protected by two-factor authentication.
Minimization and limited retention: we do not store recording video — only the link, which remains in the host's Google Drive. Technical meeting records expire automatically within 180 days. When you disconnect your Google account, the token is deleted immediately.
Notification integrity checks: notifications received from Google Calendar are validated against a secret token before any processing, preventing third parties from injecting forged events.
Incident response: in the event of a security incident affecting Google user data, we will notify affected customers and the competent authorities as required by applicable law, and revoke any compromised credentials.

Revoking Access and Deletion

You may disconnect your Google account at any time from the Application screen in Bitrix24 (the token is deleted immediately) or revoke access at myaccount.google.com/permissions. For complete deletion of your portal's technical records, contact us at the email below and we will comply within 30 days.

Your Rights

You may request access, correction or deletion of the data we hold by contacting contato@tlj.net.br. Data written to your Bitrix24 remains under your control and responsibility.