RESOLVE
Sign inRequest a demo

Privacy Policy

Describes how RESOLVE handles data for every agency on the platform. Last updated September 2026 — added §7’s RESOLVE AI disclosure and §12’s state privacy-rights detail.

1. What RESOLVE is

RESOLVE is a hosted CRM platform for life insurance agencies. RESOLVE operates and secures the platform on behalf of every subscribing agency — you don’t manage any infrastructure yourself, and your data is protected by the same access controls described below regardless of your plan.

2. What data is collected

Your RESOLVE account stores:

  • Account data — name, email, phone, NPN, licensed states, contract level, and role for each agent using the system.
  • Client data — name, date of birth, contact details, and, where entered, Social Security number, bank routing and account number, card number, driver’s license number, and medical condition notes.
  • Business data — leads, pipeline deals, policies, applications, commissions, chargebacks, and activity/dial-tracker history.
  • Imported files — if you upload a CSV or Excel export from another system (your existing book, lead vendor, or dial tracker), RESOLVE reads it in your browser to map and validate its columns, then writes the resulting records into the data above. The uploaded file itself is never sent to or stored on a RESOLVE server — it’s processed locally and discarded once the import completes.

3. How data is protected

Access is enforced with row-level security at the database layer: an agent can read and write only their own records; an agency owner or manager can read the whole agency but write none of it. Social Security numbers, bank routing/account numbers, card numbers, driver’s license numbers, and medical condition details are encrypted at rest. Reading one of these fields back to plaintext requires an authorized call, and every such reveal is logged with who accessed it and when.

4. Who can access data

Access follows role: an agent sees only their own book; an owner or manager sees their agency’s data but cannot edit another agent’s records; RESOLVE platform staff can access accounts only for support purposes, under the same audited-access controls. These rules are enforced by the database, not only hidden in the interface.

5. Authentication & your session

Signing in is handled entirely by RESOLVE’s authentication provider, Supabase Auth — RESOLVE never sees or stores your password in plain text. A session is maintained with a secure, necessary cookie (see the Cookie Policy); RESOLVE does not use any separate session-tracking mechanism.

6. Infrastructure & third parties

RESOLVE is built on Supabase, which hosts the database, authentication, and encrypted-field key management, and Vercel, which hosts and serves the application itself — both under their own security and compliance commitments as RESOLVE’s infrastructure providers. As of August 2026, RESOLVE uses Google Tag Manager on this marketing site and the authenticated platform to measure product and marketing usage — page views, button clicks, and account-lifecycle milestones like signup or first sale (see the event catalog referenced in the Cookie Policy). This is usage analytics, not an advertising or retargeting pixel: RESOLVE does not run any ad network pixel (Meta, Google Ads, or otherwise) today, and does not sell or share this usage data to profile you across other sites. The event data collected is about product usage, not client data — no client PII (name, SSN, health notes, etc.) is ever sent to Google. See the Cookie Policy for the specific cookies this can set and how consent defaults are configured. If your agency enables the optional Discord relay, event metadata (e.g. “a policy was issued, for this premium amount”) can be sent to a Discord channel your agency configures — client PII is never included in these notifications either. If your agency enables Outreach Automations, the recipient’s phone number/email address and the message text are sent to Sendblue (SMS) and RESOLVE’s transactional email provider solely to deliver that message — RESOLVE does not use these vendors for any purpose beyond sending the message your agency configured and requested. Subscription payments are processed by Stripe, our payment processor — RESOLVE never receives or stores your card number, CVC, or bank account details; Stripe handles that directly, and RESOLVE stores only the minimum subscription status (plan, renewal date, active/canceled) needed to grant you access.

7. RESOLVE AI

RESOLVE AI (“Ask your book”) is an optional, account-gated feature that answers questions about your own agency’s data. When you ask it a question, the relevant records already scoped to your normal access (the same row-level security described in §3 — never another agency’s data) are included as context sent to RESOLVE’s AI model provider, Anthropic, solely to generate the answer to that question. RESOLVE AI is read-only: as built today, it cannot create, edit, or delete any record in your account. Questions and answers themselves are not stored by RESOLVE beyond what’s needed to return the response to you; a separate usage log records only which internal tools were used, token counts, and timing, for cost control and rate-limiting — never the question or answer text. RESOLVE AI is off by default and only answers for accounts on plans where it’s enabled. Avoid asking RESOLVE AI to summarize or repeat highly sensitive fields (Social Security numbers, full bank/card numbers) back to you in a question or expect it to withhold information already visible to your own account’s normal access — it answers from data you can already see, not a more restricted view.

8. Email

Account emails — password resets and, where enabled, sign-up confirmation — are sent by Supabase Auth’s built-in email delivery, not a separate marketing email tool. RESOLVE itself does not send marketing email to you based on your account activity. Separately, if your agency enables Outreach Automations, RESOLVE sends messages your agency configures to your own clients on your behalf (see §6) — every such client can ask to stop receiving them, and each automated message includes instructions for how; see §12 for what that means for you as the account holder versus your clients.

9. Data retention and deletion

Client and business records can be deleted directly within RESOLVE by an authorized user at any time. Deleted records are removed from the live system immediately; backup retention follows RESOLVE’s standard backup policy.

10. Data protection during the beta period

RESOLVE is currently in public beta. While RESOLVE takes reasonable measures to protect user data — the row-level security, encryption, and access controls described above — automated backup and disaster-recovery capabilities are still being expanded during this period. We recommend maintaining your own records of critical business information during the beta period.

11. This marketing site

The Contact and Request Demo forms on this site store the name, email, and message you submit for the sole purpose of responding to your inquiry. It is not shared with third parties.

12. Your rights

RESOLVE is the data controller for information stored on the platform. You can request access to, correction of, or deletion of your data by contacting RESOLVE support (see Contact). RESOLVE responds to every request personally rather than through an automated self-service flow today.

If you’re a California resident, the CCPA/CPRA gives you the right to know what personal information is collected about you, to request deletion or correction of it, and to opt out of its “sale” or “sharing” as those terms are defined by that law — RESOLVE does not sell personal information and does not share it for cross-context behavioral advertising (see §6), so there is nothing to opt out of on that front today. You can exercise any of these rights the same way as any other jurisdiction’s: by contacting RESOLVE support. Similar rights may apply under other state privacy laws depending on where you live; RESOLVE honors the same request process regardless of which law applies to you, rather than maintaining a separate process per state.

If you are an insurance agent’s client (not a RESOLVE account holder yourself) and want to know what your agent’s RESOLVE account holds about you, or want a message stopped, start with your agent directly — they control your record. RESOLVE support can also help route the request.

13. Subprocessors

Vendors RESOLVE uses to operate the platform, and what each one can see:

  • Supabase — database, authentication, and encrypted-field key management. Has access to all platform data as the infrastructure host.
  • Vercel — application hosting. Sees request traffic; does not have standing access to the database.
  • Anthropic — RESOLVE AI’s model provider (§7). Receives only the specific records relevant to a question you ask, and only for accounts where RESOLVE AI is enabled.
  • Google (Tag Manager/Analytics) — usage analytics only, as described in §6; no client PII.
  • Sendblue — SMS delivery for Outreach Automations, if your agency enables it (§6). Sees the recipient’s phone number and message text for messages your agency sends.
  • Stripe — payment processing for subscription billing. Sees your payment details directly (RESOLVE never does) and the subscription/billing information needed to process your payment.
  • Transactional email provider — email delivery for Outreach Automations, if your agency enables it and a provider is configured (§6). Same scope as Sendblue, for email instead of SMS.

This list is kept current here rather than in a separate document; check back for the latest version rather than relying on a cached copy.

14. Changes to this policy

This page describes RESOLVE’s current data practices and may be updated as the platform evolves.