Deleting your data

How deletion works today.

Deletion is handled by request today, alongside automatic retention and, once Indi Inbox is live, mailbox disconnect. This page says how to ask, what rolls off on its own, what stays, and what deletion cannot reach.

Indi Inbox (coming soon)

Mailbox disconnect and cleanup.

Indi Inbox is coming soon. Once it is on for your brokerage, disconnect the mailbox in MeetIndi Inbox settings. For Gmail, this attempts to stop the Gmail watch and revoke the Google grant, removes the saved credential immediately, and disables syncing for that connection. For Microsoft 365, this attempts to delete remote Graph subscriptions, removes local subscription records, folder cursors, and the saved credential, clears cached access tokens, deactivates mailbox and notification routes, and marks the mailbox disconnected even if Microsoft cannot be reached. It does not revoke Microsoft consent. Mailbox disconnect does not use the record-deletion grace window and does not delete messages in Gmail or Microsoft 365.

  • Scheduled purge jobs remove mailbox content fields and any stored mailbox voice-profile record, targeting cleanup within 24 hours. Locks or failures can delay cleanup; jobs retry remaining work. Voice-profile generation is not offered yet.
  • Open-item metadata and ledger history can remain so items still owed stay visible. Contact display information shared with another connected mailbox can remain for that mailbox.
  • Routine defaults: content 30 days after close and last activity, message metadata 90 days, history about 13 months. Open items, review items, complaint records, and tenant settings affect retention. See the privacy policy for exceptions and records without an automatic age-based purge.
  • Removing access in your Google account stops Gmail access. For Microsoft 365, remove MeetIndi at https://myapps.microsoft.com to remove consent. Disconnect in MeetIndi as well to initiate mailbox-disconnect cleanup.
01 · How to request deletion

By request, not a dashboard button.

There is no self-serve delete screen in the MeetIndi dashboard today. To delete a call, a lead, a transcript, a caller's information, or a full account, the brokerage owner writes to us through the contact page. We review each request and work through it with you. Inbox mailbox disconnect, above, is the one deletion-related action you can start yourself.

  • Owners and brokerages: write to us from the owner address on file
  • Callers and leads: the business you called is usually the first point of contact. You can also write to us, and we may work with that business on the request
  • We verify that the person asking has the authority to ask before acting on a request
  • Rights differ by law. PIPEDA includes access and correction rights and limits how long information is kept, but does not create a general right to erasure. CCPA / CPRA includes a right to delete, with exceptions
02 · Automatic retention

Call data rolls off on a schedule.

Each brokerage has a retention window for call data, 365 days unless it has been changed. A scheduled job clears the stored transcript, summary and recording files for calls past that window and marks expired call records and eligible inactive caller records as deleted. Owners can review the window under compliance settings in the dashboard.

  • The window can be set from 7 to 3,650 days, within what your regulator and contracts allow
  • Marked records are hidden from normal use. This is not a promise that every row is erased from the database at that moment
  • Your own record-keeping duties, such as brokerage trade records, are yours to check before shortening the window
03 · What deletion cannot reach

Backups and outside providers.

A deletion in our database does not reach every copy. We would rather say that here than have you find out later.

  • Database backups: automated daily backups are stored in a Google Cloud US location and roll off after 7 are retained. Backups taken before a database migration can be kept longer. We do not edit individual records inside a backup
  • Telephony and AI providers: providers such as Twilio, Google and, from our next platform release, Anthropic hold data under their own terms. Our process does not automatically remove it there
  • Your CRM and connected services: anything already pushed to your CRM is yours and stays there until you remove it
  • Email already delivered, such as lead notices and digests, stays with the people who received it
04 · What is retained, and why

Some things have to stay.

A small set of records stays through deletion because the law, a dispute, or our own compliance record requires it.

  • CASL consent log entries: append-only, kept as evidence of consent and opt-out
  • Audit records: including the fact that a deletion happened, who asked, and what it covered
  • Billing records: invoice history, kept as long as tax law requires
05 · Closing an account

Handled with you directly.

Closing a full account is not a dashboard action. Write to us and we will work through it with you, including what happens to your numbers, your team's access, your connected services, and your data. Commercial terms are in your Order Form.

  • If you want to keep your phone numbers, port them out before the account closes
  • Export what you need first; see /data-export
  • The limits in section 03 still apply after an account is closed

Also revoke access at Google account permissions or remove Microsoft 365 consent at Microsoft My Apps. For privacy questions or deletion requests, use our contact page.

Need something deleted?

Use our contact page and tell us what you need removed. Include the phone number involved if the request is about a caller. Requests about a full account should come from the owner address on file.

Related: Privacy, Compliance by jurisdiction, CASL, DPA.