LeadArivo Privacy Policy

Who is responsible

LeadArivo is operated by TEAL Infotech, the trade name of a proprietorship owned by Varinder Pal Singh (GSTIN 03BQPPS8444C1ZM), of 262A, Patiala Road, Swastik Vihar, Zirakpur, SAS Nagar, Punjab, 140603, India. This Policy applies to the LeadArivo public website, Early Access and LeadArivo List registration, contact and trial enquiries, and personal data we handle as operator of LeadArivo.

For privacy and personal-data requests, contact privacy@leadarivo.com. For other legal or security enquiries, use info@leadarivo.com.

Controller and processor

For our own website, sales, marketing conversations, accounts and billing, TEAL Infotech decides why that information is processed (the business / controller role under many privacy laws).

For lead, contact and conversation data that LeadArivo customers submit so they can handle their own enquiries (“Customer Data”), the customer generally decides why that data is collected. We process that Customer Data to provide LeadArivo on the customer’s instructions, as further described in the Data Processing Addendum.

This Policy does not claim that TEAL Infotech is “GDPR certified” or that a single role applies in every country.

Who this Policy covers

• Website visitors
• People who join Early Access or the LeadArivo List
• People who send a contact, trial or footer enquiry
• Trial users and paying customers
• Authorized Users of a customer account
• Individuals whose data a customer stores in LeadArivo (end customers / leads) — that Customer Data is primarily the customer’s responsibility

Personal data we handle

On the public website and enquiry forms we may collect:

• Identity and contact details you submit: name and work email; optional phone on Early Access; and, on the main Contact form, company, industry and topic. Public LeadArivo contact does not publish a telephone number.
• Message content you choose to send.
• Technical data such as IP address, browser type, approximate time and security tokens used to prevent spam (including a short-lived form challenge held in page memory).
• Support tickets you open at app.leadarivo.com/tickets, subject to that application’s own screens.

If you become a trial or paying customer, account, authentication and billing details needed to operate the subscription may also be processed. Production payment-card data, if collected, would be handled by a payment provider — none is named here because a production payment processor is not verified on this website.

Google Analytics and Microsoft Clarity are optional website measurement services, disabled by default. A service may operate only when explicitly configured and enabled and you allow Analytics in Cookie settings on an eligible public page. These services can receive browser and network information, page visits and interaction signals; Clarity provides session insights. This website uses first-party consent controls. Google Tag Manager, CookieYes and arbitrary legacy CMS snippets do not run. The Cookie Policy explains categories, choices and inventory limitations.

Please do not include passwords, full payment-card numbers, bank details or unnecessary health information in website messages.

Purposes and legal bases

We use this information to respond to enquiries, operate Early Access and the LeadArivo List, provide trials and the service, send transactional verification messages, secure the website, meet accounting and legal duties, and communicate about your request. Where privacy law requires a “legal basis,” we rely on steps needed to answer your request or perform a contract, legitimate interests in operating a secure business website, consent where we ask for it, and legal obligation.

Early Access and the LeadArivo List use double opt-in: we send a verification email and only treat the address as an active subscriber after you confirm. You can unsubscribe from product updates at any time. Unsubscribing from updates does not automatically remove Early Access registration. Contact form submissions are captured directly in LeadArivo when you submit them; no separate email confirmation is required.

Website chat

Website chat is provided through our native LeadArivo widget at app.leadarivo.com and loads when you open it. We process the messages and contact details you choose to share, conversation history and technical session data to respond to your enquiry and support follow-up. When AI-assisted replies are enabled, message content, relevant conversation history and business context may be processed by the configured AI provider. AI replies can be inaccurate; contact our team to confirm important information. The chat uses browser session storage to resume a conversation in the same tab. Conversation retention and deletion follow the ‘Retention, security and rights’ section below; closing chat does not delete messages.

Customer Data in LeadArivo

Customers may store lead names, contact details, conversation content, sources, Assignee, follow-up and outcome information. Customers must have lawful rights to that data. Clinics & Healthcare is an approved Industry configuration; that does not make LeadArivo a medical-record system, HIPAA-compliant product or health-data certified service. Customers must not use LeadArivo as an electronic health record and should not store unnecessary health information.

Customers may connect messaging, advertising, email, calendar or other platforms under their own arrangements. These platforms may receive data needed for the enabled workflow and have their own terms; they are not automatically LeadArivo subprocessors. AI-enabled features may send message content, relevant lead/contact context, conversation history and business knowledge to the configured provider when enabled. Provider identity, retention, training and location settings must be confirmed for the account. See the AI Terms and Subprocessors.

Google and YouTube account and comment data

LeadArivo uses YouTube API Services when you connect a YouTube channel. Google authorization lets us identify the connected Google account by its email address, identify the channel you authorize, and access channel comment threads and replies. We receive channel IDs and titles; comment and parent IDs; comment text; commenter display names and channel IDs when provided; video IDs and links; publication times; and whether a thread permits replies. Google also supplies access tokens and, when granted, refresh tokens so the connection can work without asking you to sign in for each synchronization. We do not receive your Google password.

We use this information to synchronize comments, identify enquiries, show their public context in the authorized workspace, keep comments up to date, and send replies that an authorized person reviews and approves. A reply is sent to Google/YouTube only when that person chooses to send it; it can then become publicly visible on YouTube under the connected channel, subject to YouTube permissions and moderation. YouTube private messaging, video uploads and deletion of comments on YouTube are not features of this integration.

If AI assistance is enabled and configured, YouTube comment text and relevant conversation, lead/contact and Business Knowledge context can be sent to the configured AI service to generate a summary, suggested next step or reply draft. Human approval of a public reply does not prevent this earlier AI processing. AI outputs may be inaccurate and are not statements from YouTube. A draft is not automatically posted to YouTube.

This section concerns the YouTube channel connection. Other Google services, such as a mailbox or calendar, require their own separately authorized functionality and permissions; connecting YouTube does not itself authorize those services.

Who receives Google and YouTube user data

• TEAL Infotech, as the operator of LeadArivo, processes the authorized data to provide the connection and the workspace features described above. Access by our personnel requires your specific agreement or a purpose permitted by Google’s user data policy, such as a necessary security investigation or a legal obligation, together with the DPA’s confidentiality requirements.
• Authorized users of your LeadArivo workspace can receive the integration information and comment/conversation content that their access permits them to view. A comment is public on YouTube, but its presence in a workspace does not give users access to another customer’s workspace.
• Google/YouTube receives authorization and API requests, identifiers needed to read or refresh comments, tokens for authorization or revocation, and the reply text and parent-comment ID when you send an approved reply. Public replies are also visible to people who can view the relevant YouTube thread. Google processes data under its own policies.
• Our infrastructure service providers may process stored account, token and comment data to operate the application, database and backups. Ask us for the current verified provider names, processing countries and applicable arrangements through the Subprocessors and recipients disclosure.
• When enabled, the AI service provider configured for the workspace receives the comment and related context described above. The actual provider, model, processing location and retention/training settings must be confirmed before enabling that processing. No provider-wide promise of zero retention or no model training is made by this Policy.

These disclosures distinguish data processing by our suppliers from the Google/YouTube platform that you connect. Optional website Analytics permission does not authorize sharing YouTube account or comment content with website analytics or advertising services. This integration does not send that content to the website measurement loaders. See Subprocessors and recipients and the AI Terms for the applicable roles and verification limits.

TEAL Infotech operates from India. Processing by a service provider or Google may involve another country; the actual infrastructure and AI countries and transfer arrangements require confirmation for the enabled service. This Policy does not assert an unverified hosting region, transfer mechanism or certification.

Google data storage, disconnection and deletion

The application stores integration details and comment/conversation records in its database. Integration credentials use application-level encryption. Access to records is scoped to the workspace. HTTPS protects supported service connections in transit. This is not a claim that every database field, disk, backup or external-provider copy has independently verified encryption or deletion controls.

Scheduled comment synchronization refreshes stored YouTube comment text and context, removes copies of comments that are no longer available, and removes stored API comment content that has not been refreshed for 30 days. Other records you independently supply to LeadArivo follow the applicable Customer Data arrangements; a generic retention exception does not extend the requirements for YouTube API data.

You can disconnect YouTube in Lead Source Setup, or revoke LeadArivo access through Google account permissions. Disconnecting stops future synchronization, attempts Google token revocation and clears the local connection credentials and associated API comment content. Detected authorization loss also stops the connection and requires reconnection. Removing data stored by LeadArivo does not delete a comment or a published reply from YouTube; use YouTube’s own controls for data held there.

Request access, correction or deletion through privacy@leadarivo.com, the Contact page, or the Support Center. Identify the workspace and connected channel without sending credentials. We verify the requester’s authority. Requests covering Google/YouTube data must be handled under the applicable Google/YouTube deletion requirements, including the seven-calendar-day deadline for a user-requested deletion. The review must cover relevant active records, retained copies and service providers; disconnecting is not confirmation that every copy or AI-derived record has been erased. See Data Deletion.

Our use of Google user data is subject to the Google API Services User Data Policy, including its applicable Limited Use requirements, and the YouTube API Services Developer Policies. Read the Google Privacy Policy and YouTube Terms of Service for Google’s own handling and your use of YouTube.

Service providers and transfers

The Subprocessors and recipients page separates conditional website recipients, Customer Data subprocessors, customer-connected platforms and TEAL Infotech as operator. Google Analytics and Microsoft Clarity receive website measurement data only when enabled and permitted. Consent choices are managed by this website using first-party storage. Cloudflare Turnstile may process technical data for bot protection when enabled; external video players may receive technical and playback data when Functional is permitted.

TEAL Infotech is established in India. If a provider processes data in another country, that is identified on the Subprocessors page when verified. This website does not attach Standard Contractual Clauses as a published mechanism.

Retention, security and rights

Website enquiry, account and Customer Data retention depends on the purpose, applicable legal requirements and the agreed service arrangements. A complete fixed retention schedule has not been verified for publication. Request enquiry deletion, account-data access or correction at privacy@leadarivo.com. We verify authority and distinguish our own records from data controlled by a customer.

Return or deletion of eligible Customer Data requires an agreed scope and confirmation of completed steps. Database removal does not by itself erase attachments, exports, backups or external-provider copies, revoke platform access or cancel billing. Specific records may need to be retained for applicable law or a justified legal hold with restricted use. Backup expiry and provider deletion depend on their verified capabilities and arrangements. We do not promise immediate or complete erasure of all copies. See the DPA.

Security measures we can describe publicly are on the Security page. No method of transmission is perfectly secure.

Depending on applicable law, you may request access, correction, deletion, restriction or a copy of personal data we hold as operator, or object to certain processing. Customers should be asked first for data they control in LeadArivo. We will not discriminate against you for making a valid request.

For practical instructions on requesting deletion of personal data or account-related data, including information received through connected Meta services, see Data Deletion.

LeadArivo is not directed at children. Do not submit information about minors.

Changes and contact

We will post changes on this page with a new “Last updated” date. Contact privacy@leadarivo.com for privacy requests. Public LeadArivo contact does not use telephone.