RESOLVE
Sign inRequest a demo

Privacy Policy

Describes how RESOLVE handles data for every agency on the platform. Last updated August 2026 — added §6’s analytics disclosure.

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. RESOLVE does not currently process payments through the platform itself; if that changes, this policy will be updated to name the processor before it goes live.

7. 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 does not send marketing email based on your account activity.

8. 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.

9. 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.

10. 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.

11. 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.

12. Changes to this policy

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