Legal

Privacy Policy

Last updated: 2026-04-29

1. Who we are

This Privacy Policy explains how Indigloo Technologies Inc. collects, uses, discloses, and handles personal information in connection with MeetIndi.

MeetIndi is a front-office AI service that can answer calls, route interactions, support booking, generate call summaries and transcripts, support SMS continuity, and provide dashboard and operational features for businesses using the service.

2. Scope

This Privacy Policy applies to personal information handled through the MeetIndi product, including account sign-up, onboarding, dashboard use, billing, customer support, integrations, and call- and message-related features.

This Privacy Policy does not replace the privacy policies of third-party services that a customer chooses to connect, such as payment, calendar, scheduling, CRM, or similar third-party systems.

3. Personal information we collect

We may collect the following categories of personal information.

A. Information provided by account holders and administrators

This may include:

  • names;
  • business name, display name, and related business profile information;
  • email address, telephone number, address, time zone, and service-area information;
  • login, account, billing, and subscription details;
  • onboarding responses, scripts, FAQs, routing settings, scheduling rules, and other configuration data; and
  • support requests and related communications.

B. Information collected when the service handles a call or message

Depending on how a customer configures MeetIndi, this may include:

  • caller and contact names and phone numbers;
  • call recordings where enabled;
  • transcripts, summaries, tags, call outcomes, notes, and recommended next steps;
  • appointment or callback details;
  • routing and escalation details;
  • SMS continuity or missed-call recovery content and delivery data; and
  • customer-provided knowledge-base or workflow information used during the interaction.

C. Information from connected services

If a customer authorises a connection, we may receive information from third-party services such as:

  • payment and billing providers;
  • calendar and scheduling tools;
  • CRM systems;
  • telephony and messaging providers; and
  • other customer-authorised integrations.

D. Automatically collected technical and usage information

We may collect technical information such as:

  • IP address and device or browser information;
  • product-usage events;
  • log, diagnostic, and performance information;
  • timestamps, identifiers, and audit events; and
  • security, fraud-prevention, and rate-limiting data.

4. How we use personal information

We use personal information to:

  1. provide, operate, secure, and support MeetIndi;
  2. create and manage accounts, subscriptions, onboarding, and billing;
  3. provision phone numbers, route calls, generate transcripts and summaries, support booking, and deliver other service features;
  4. support customer-authorised integrations such as calendar, scheduling, CRM, and payment workflows;
  5. communicate with customers about their account, subscription, operational events, support issues, and product updates;
  6. investigate abuse, fraud, security issues, or misuse of the service;
  7. comply with law, enforce our agreements, and protect rights, safety, and the integrity of the service; and
  8. improve, maintain, monitor, and troubleshoot the service, including through diagnostics, analytics, and de-identified or aggregated analysis; and
  9. send service-related transactional emails, including support and account notices.

MeetIndi does not use Customer Data or caller data to train any AI model.

5. When MeetIndi is used by a business customer

If you are a caller, lead, contact, prospect, or other individual interacting with a business that uses MeetIndi, that business decides how MeetIndi is configured for its operations, including scripts, routing, booking settings, CRM connections, and whether recordings or transcripts are enabled.

In many cases, that business is the first point of contact for questions about how your call or interaction is handled in the context of that business relationship.

6. How we disclose personal information

We may disclose personal information:

  1. to service providers that support hosting, telephony, payments, analytics, messaging, model inference, support, and other operational functions;
  2. to customer-authorised integrations when the customer chooses to connect them;
  3. within a corporate transaction such as a merger, financing, reorganisation, or sale of all or part of our business, subject to applicable confidentiality protections;
  4. to comply with law, legal process, regulator requests, or enforceable requests from competent authorities;
  5. to protect rights, security, property, users, or the integrity of the Services; and
  6. with consent or at the direction of the relevant individual or customer.

MeetIndi uses Resend to send transactional emails such as support messages, account notices, and service communications.

7. Where information is processed

The currently available product documentation indicates a Canada-first posture for core GCP services, including Toronto (northamerica-northeast2) for primary runtime, storage, and database services, and Montréal (northamerica-northeast1) for Gemini Live inference.

We may also use third-party providers or customer-authorised integrations that process information in other locations. For example, Resend is a US-based transactional email provider and may process support, account, or service-notice email data in the United States. Redis queue, cache, rate-limiting, and transient coordination data is hosted on GCP Memorystore in Toronto (northamerica-northeast2).

8. Retention

We retain personal information for as long as reasonably necessary to provide the Services, maintain security and audit records, comply with legal obligations, resolve disputes, and enforce agreements.

Retention periods may vary depending on the type of data, the customer configuration, backup cycles, audit requirements, and applicable law.

We do not promise immediate deletion of all data on request or on termination, and some information may remain in backups, archives, audit logs, or legally required records for a reasonable period.

9. Access, correction, and other requests

Subject to applicable law, individuals may ask to access or correct personal information we hold about them.

Where MeetIndi is used by one of our business customers to handle a call, lead, or booking, the relevant business customer may be the most appropriate first point of contact for the request.

We will review requests in accordance with applicable law, subject to identity verification, legal limits, security requirements, and our need to maintain service, fraud-prevention, audit, or legally required records.

For Canadian personal information, MeetIndi handles privacy requests in a PIPEDA-aligned way, including requests to access personal information, correct inaccurate information, withdraw consent where withdrawal is available, or challenge compliance.

For California and other US state privacy-law requests, rights depend on the law that applies to the individual, the business customer, and the data involved. Where applicable, those rights may include access or portability, correction, deletion, opt-out of sale or sharing, opt-out of targeted advertising, limitation of sensitive personal information, non-discrimination, and appeal of a denied request.

MeetIndi does not sell personal information or share Customer Data, caller data, recordings, or transcripts for cross-context behavioural advertising. If our website advertising or analytics posture changes in a way that creates additional US state privacy choices, we will update this Privacy Policy and the relevant opt-out flow.

Quebec residents: MeetIndi does not currently serve Quebec-resident callers under this product; please contact support@meetindi.com.

10. Security

We use administrative, technical, and physical safeguards designed to protect personal information appropriate to the nature of the information and the service.

The currently available product documentation indicates measures such as role-based access, secret management, signature validation for external webhooks, structured logging, tenant isolation controls, and managed cloud infrastructure.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

11. Children

MeetIndi is intended for business use and is not directed to children.

12. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. If we make a material change, we will post the updated version and may also provide notice through the dashboard, email, or another reasonable method.

13. Contact us

For privacy questions or requests — including PIPEDA access / correction / withdrawal-of-consent requests, CASL opt-out questions, breach concerns, or any other inquiry about how we handle personal information — contact support@meetindi.com.

Changelog

  • 2026-04-22: Locked founder decisions embedded for support-channel contact, Quebec-resident exclusion, no-model-training commitment, Toronto-primary storage wording, and Resend cross-border disclosure.
  • 2026-04-29: Updated Redis processing disclosure after migration to GCP Memorystore in Toronto, and added PIPEDA / CCPA / US state privacy request-rights language.