Privacy Policy

For the customer data your agency records in Mint, and for call data Mint receives from your connected CRM, your agency is the data controller and Mint acts as a data processor. Mint processes that data only to provide the Service to you and on your documented instructions.

Specifically, when call data flows into Mint from GoHighLevel (GHL), Mint acts as a processor of that GHL-sourced call data on your behalf. You determine why the calls are made and recorded; Mint stores and structures the resulting record for you.

Call-recording consent is the responsibility of your agency as the controller. Where recording or transcription occurs, you are responsible for obtaining any consent that applicable one-party or two-party consent laws require from the parties to the call. Mint does not obtain that consent on your behalf and relies on your instruction that consent has been handled.

Beyond call data received from your connected CRM, Mint itself captures rep-side audio through the Voice Board, its in-app audio feature, using LiveKit. This means Mint records the rep’s side of the audio directly, not only call data sourced from GoHighLevel. The same consent responsibility applies to any audio captured this way.

Mint uses the following sub-processors to operate the Service. Each is bound to protect the data it handles:

• Supabase: database, authentication, and file storage.
• Vercel: application hosting and delivery.
• GoHighLevel: source of connected CRM and call data.
• LiveKit: real-time audio for the Voice Board, which processes rep-side voice audio.
• Stripe: payment processing for usage-based fees.

We will update this list before adding or changing a sub-processor that handles personal data.

We process account information (names, work email, agency and role), the customer records your reps build (financial inventories and related notes), and call activity and metadata from your connected CRM. We use this to train your reps, produce your metrics, and maintain the system of record. We do not sell personal data.

Each agency’s data is isolated from every other agency’s. Access is scoped so that one agency cannot see another agency’s records, and reps see only what their role permits. This isolation is a core security property of the Service.

Records are retained with your agency so they survive rep turnover. The deletion paths described here are capabilities we are building. Once the GoHighLevel integration is live, uninstalling the Mint application from GoHighLevel, or closing your account, will prompt Mint to delete the associated GHL-sourced data, subject to any retention that applicable law requires. You may also request deletion of specific records, and we will honor those requests as this functionality comes online.

Individuals whose data appears in Mint may have rights to access, correct, or delete their personal data. Because your agency is the controller, direct such requests to your agency, and Mint will assist as processor.

Where a request concerns call data received from GoHighLevel, the GHL contact identifier (ghl_contact_id) is treated as pseudonymous personal data and is used to locate and action the corresponding records for a data-subject request.

Mint stores structured records with access control and encryption in transit, and relies on the security posture of its sub-processors. No system is perfectly secure, but tenant isolation and least-privilege access are treated as critical safeguards.

We may update this Policy; material changes will be communicated in the app or by email. We are finalizing this language with counsel ahead of general availability. Privacy questions can be sent to andomccall@gmail.com.