Skip to main content
Ransom Life
Join the Team

Privacy Policy

Last updated: August 11, 2026

Ransom Life Enterprises (“Ransom Life,” “we,” “us”) is an independent, licensed life insurance agency. This policy explains what personal information we collect, how we use it, and the choices you have. It covers this website (ransomlife.enterprises), our agent portal, and our scheduling application. That application is the appointment and interview booking tool our team uses, and it can connect to Google Calendar.

Information we collect

  • Contact form. When you submit the form on our Contact page, we collect your name, email address, phone number, your message, and which audience you identify with. As evidence of your consent to be contacted, we also record the consent statement you agreed to, the page you submitted from, your IP address, your browser’s user-agent string, and the submission time.
  • Agent accounts. If you register for our agent portal, we collect your name, email address, phone number, username, and password (stored only in hashed form), along with the CRM connection credentials you provide so the portal can operate on your behalf.
  • Lead purchases. Payments are processed by Stripe. Card details are entered in Stripe-hosted payment fields and go directly to Stripe. They never touch our servers. We keep order records (package, amount, status), and Stripe emails receipts to the address on the order. If you start a recurring weekly lead plan, your payment method is saved with Stripe for those charges.

How we use information

  • To respond to your inquiries and provide the services you request.
  • To operate agent accounts, lead programs, and lead delivery.
  • To process payments and maintain purchase records.
  • To schedule and manage appointments and interviews, including calendar invitations.
  • To contact you consistent with the consent you gave us. Consent is never a condition of purchase, and you can opt out at any time.
  • To meet legal, regulatory, and record-keeping obligations.

Google user data (our scheduling application)

Members of our team can connect their own Google account to our scheduling application, and administrators can connect shared team calendars the same way, so that scheduled appointments and interviews appear on the right Google Calendar. When an account is connected, we request access to Google Calendar and to the email address of the connected Google account. Here is exactly how that data is accessed, used, stored, and shared:

  • Access and use. We use Calendar access only to create calendar events for scheduled appointments and interviews, and to remove and replace those same events when a booking is rescheduled. We do not read, browse, or import your existing calendar events, calendars, contacts, or any other Google data. The connected account’s email address is used only to show which Google account is linked.
  • Storage. The authorization tokens Google issues are stored in our application database and are used solely for direct, server-to-server communication with Google’s APIs.
  • Sharing. We do not share, transfer, or sell Google user data to any third party, and we do not use it for advertising of any kind.
  • Retention and revocation. Disconnecting Google Calendar in portal or admin settings deletes the stored tokens from our systems, and tokens are deleted when the associated account is removed. You can also revoke the application’s access at any time from your Google Account security settings.

Ransom Life Enterprises’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How we protect information

We use technical and organizational safeguards to protect personal information (including Google user data and payment information) against unauthorized access, disclosure, and misuse:

  • Encryption in transit. This website, our portal, and our scheduling application are served over HTTPS, and every exchange with Google, Stripe, and our other service providers happens over encrypted TLS connections.
  • Google Calendar authorization. Calendar connections use Google’s OAuth authorization. We never receive, handle, or store anyone’s Google password. The only credential we hold is the authorization token Google issues for the specific access described above.
  • Server-side token handling. Google authorization tokens are held server-side in our application database and used only for direct, server-to-server calls to Google’s APIs. They are never sent to a browser, embedded in a page, or exposed to client-side code, and they are deleted when the connection is disconnected or the account is removed.
  • Access controls. Administrative functions are restricted by role-based permissions, the agent portal requires authenticated sign-in, and each team member’s calendar connection is scoped to their own account. Portal passwords are stored only in hashed form.
  • Data minimization. Calendar events for client appointments deliberately contain the minimum needed (a first name, last initial, and the appointment time) and never include coverage information or other client records in the event title or description. The client’s own email address is added as an attendee so they receive their appointment invite. Interview-scheduling events for job candidates are internal to our team’s calendars (candidates are not added as attendees) and include the application details our recruiting team needs to conduct the interview.
  • Payment isolation. Card details are entered in Stripe-hosted fields and go directly to Stripe over encrypted connections. They never pass through or rest on our servers.

Cookies and tracking

  • Ad measurement. This site uses the Meta Pixel to measure our advertising. It runs when you click key buttons or submit the contact form, and it sets Meta’s standard cookies (such as _fbp and _fbc). You can manage this in your browser settings and in your Meta ad preferences.
  • Campaign identifiers. If you arrive from an ad, we pass standard ad-click identifiers (such as utm parameters, fbclid, or gclid) along when you continue to our portal or signup pages, so we can attribute the visit to the campaign that brought you.
  • Portal sign-in. The agent portal sets an authentication cookie to keep you signed in.

How we share information

We do not sell personal information. We share it only with service providers who process it on our behalf (Google for calendar scheduling, Stripe for payments, and Meta for ad measurement) and where required to comply with law, enforce our agreements, or protect our rights. Licensed agents working with Ransom Life receive the information needed to serve the people who asked to be contacted.

Data retention

We keep personal information for as long as it is needed for the purposes described above, including maintaining consent and transaction records for legal and compliance reasons, and then delete or de-identify it.

Your choices

You can opt out of calls, texts, or emails at any time: reply STOP to a text, use the unsubscribe link in an email, or tell the person who contacts you. To request access to, correction of, or deletion of your personal information, reach us through our Contact page.

Children

Our services are for adults. This site is not directed to anyone under 18, and we do not knowingly collect personal information from children.

Changes to this policy

If we change this policy, we will post the updated version on this page with a new “Last updated” date. Material changes will be highlighted here before they take effect.

Contact us

Questions about this policy or your information? Reach us through our Contact page and we’ll get back to you.