Privacy Policy

Last updated: October 20, 2026

1. Who we are and what this Policy covers

Prime Intent LLC (“Prime Intent,” “we,” “us,” or “our”) operates InsuranceRevenue.com and its partner services.

This Privacy Policy covers personal information processed in connection with:

• InsuranceRevenue.com and its invitation-request form.
• portal.insurancerevenue.com.
• Related registration, onboarding, and account services provided through our APIs.
• Electronic agreement signing, identity verification, payment onboarding, support, and administration of our publisher relationships.

It applies to visitors, prospective publishers, individual publishers, business owners, signatories, authorized team members, and other business contacts.

Our address is 30 N Gould St, Suite 42491, Sheridan, WY 82801, United States. Contact us at support@insurancerevenue.com.

Where applicable data-protection law uses the term, Prime Intent is the controller of personal information processed for the partner-administration purposes described in this Policy.

Business information and personal information

Our program is B2B, but information identifying an individual remains personal information where applicable law defines it that way. This includes information about sole proprietors and representatives of companies.

Insurance consumers

This Policy primarily concerns partner information. It does not describe the full processing of insurance-consumer information within our lead-distribution business. Consumer-facing privacy notices and applicable law govern those activities; the Publisher Agreement allocates responsibilities between Prime Intent and publishers.

If a consumer contacts us about a complaint or privacy request, we use the information provided to investigate, respond, coordinate with relevant parties, and meet applicable obligations. Contact support@insurancerevenue.com for assistance with a consumer privacy matter.

2. Information we collect and its sources

2.1 Invitation requests

When you request an invitation, we collect:

• First and last name.
• Country.
• Email address and phone number.
• Your selected messaging service and identifier, such as a WhatsApp number, Telegram handle, or Slack Connect email.
• Company name and website, if provided.
• Submission time, IP address, browser user agent, and the legal-document version associated with your acceptance.
• Approximate country derived from your IP address through Cloudflare.

We may compare your selected country with the IP-derived country to identify inconsistencies for review. An invitation request is stored in our systems and sent to authorized staff by email.

2.2 Account creation, authorized users, and support

Staff or an authorized publisher representative may provide your name, email, company, phone number, role, and permissions when creating or inviting you to an account.

We collect account status, onboarding requirements and outcomes, support correspondence, review notes, and records of administrative actions.

When you invite a teammate, we receive that person’s email address and assigned role or permissions. Only provide information you are authorized to share.

Authentication is handled through Supabase Auth, which stores password hashes rather than readable passwords. We also process authentication and account-security records.

2.3 Terms acceptance and privacy acknowledgment

We record acceptance events, which may include the user and partner identifiers, email, acceptance context, date and time, IP address, browser user agent, and document version.

We distinguish acceptance of contractual terms from acknowledgment of this Privacy Policy and from specific consent collected for activities such as biometric verification.

2.4 Publisher details and electronic signatures

The Publisher Agreement requests information such as:

• Whether the publisher is an individual or a company.
• Legal name, company type, and registration jurisdiction where applicable.
• Street address, city, state or region, postal code, and country.
• Email address and phone number.
• Signatory name, title, signature, and signing date.

We use BoldSign, provided by Syncfusion, Inc., for electronic signing. BoldSign processes the document and signing information, including technical and verification records used to document the signing process.

We retain document and template identifiers, signing status, and signing time in our account systems. The completed agreement is available through BoldSign. Copies of the signed agreement and signing audit trail are also sent to our legal mailbox, and a signed copy is emailed to the publisher.

2.5 Identity verification

We may require designated account owners to complete identity verification through Persona Identities, Inc. (“Persona”).

Depending on the verification requested, Persona collects a government-issued photo ID, a live selfie, information appearing on those documents, and technical information needed to conduct verification. Where enabled and lawfully authorized, Persona analyzes facial geometry to compare the images, assess liveness, and detect impersonation or fraud.

Persona processes this information on our behalf. Our account database stores the inquiry reference, verification status, and relevant outcome information, which may include a decline reason. Authorized staff may access identity documents and related verification details in Persona’s dashboard when necessary for review.

We do not routinely download or store ID images, selfies, or biometric templates in our own application database.

Biometric consent, use, and retention are addressed separately in Section 4.

2.6 Payment and tax information

The public invitation-request form does not collect bank account numbers or tax identification numbers.

For bank-transfer onboarding, you enter bank details and applicable tax documentation through Mercury’s recipient-onboarding service. Our account database retains Mercury invitation and recipient identifiers rather than the bank details or tax forms entered through that process.

If you choose PayPal, we collect and store your PayPal email address in the portal and use it to arrange payouts.

We may request additional tax or payment documentation through a designated secure channel where needed. The required tax documentation depends on the payee’s tax status.

We also maintain payment statements, payout amounts, payment status, and related accounting and compliance records.

Cryptocurrency payout details are not currently collected through the partner onboarding process.

2.7 Business diligence and compliance information

Where requested or obtained in a particular review, we may process ownership information, business registration documents, licenses, insurance certificates, references, marketing materials, traffic-source information, and relevant compliance records.

Information may come from you, your authorized representatives, public business records, verification providers, Buyers, or people involved in a complaint or investigation.

Where we conduct business, sanctions, or background checks, we use the information necessary for the particular check and applicable purpose.

2.8 Campaign and account activity

We collect campaign names, sources, media, notes, tracking links and parameters, account activity, and traffic and payout reports.

The partner portal displays aggregate statistics about a publisher’s own traffic. It does not display individual insurance consumers’ names, contact details, or IP addresses.

2.9 Technical information, cookies, and browser storage

We and our infrastructure providers process IP addresses, browser and device information, request timestamps, authentication events, and other technical records needed to deliver and secure the services.

Cloudflare Turnstile evaluates browser and device signals to distinguish legitimate activity from bots and abuse. It may use browser security tokens depending on the configuration.

The portal uses cookies or browser storage for authentication and session functions. It also stores preferences and working information, such as theme, selected date range, and link-builder drafts. Depending on the item, these remain until they expire, are cleared, or are removed through sign-out or browser controls.

We do not currently run advertising pixels or analytics tools on the public partner website or partner portal. Operational and security logs are separate from advertising or audience analytics.

Persona and BoldSign load within the portal when their services are used and may process technical information needed to operate those services.

You can manage browser storage through your browser settings. Blocking necessary storage may prevent sign-in or other requested functionality.

3. How we use information

We use information for the following purposes:

• Assess invitation requests and communicate with applicants.
• Establish accounts, administer permissions, and support authorized users.
• Prepare, execute, retain, and administer publisher agreements.
• Verify identity and business information where required.
• Detect fraud, impersonation, duplicate accounts, and unauthorized access.
• Review traffic sources and compliance with applicable requirements.
• Operate Campaigns, tracking, reporting, statements, and payouts.
• Meet applicable tax, sanctions, legal, and regulatory obligations.
• Investigate complaints, resolve disputes, enforce agreements, and establish, exercise, or defend legal claims.
• Maintain service security, diagnose technical problems, and keep appropriate business records.

Legal bases where EU or UK data-protection law applies

Depending on the purpose and relationship, we rely on:

• Contract: Processing necessary to enter into or perform a contract with you as an individual publisher, or to take requested steps before entering that contract.
• Legitimate interests: Processing necessary to manage relationships with corporate publishers and their representatives, operate and secure our services, prevent fraud, and handle compliance matters and legal claims, where those interests are not overridden by your rights.
• Legal obligation: Processing necessary to satisfy an obligation recognized under the applicable data-protection framework.
• Consent: Processing for which we request your consent, including applicable biometric processing.

A contract with your employer or company does not automatically make contract performance the legal basis for processing your personal information.

Where biometric information is used to uniquely identify a person, we also require an applicable special-category condition. Where that condition is explicit consent, it is requested separately before the relevant processing.

4. Biometric verification

4.1 Notice and consent

Before biometric capture, the verification process must explain the processing and obtain any required consent or written release. Consent covers the stated verification purposes and the parties identified in that notice.

Acknowledging this Privacy Policy or signing the Publisher Agreement does not, by itself, replace required biometric consent.

Contact support@insurancerevenue.com to withdraw consent where processing relies on consent. Withdrawal does not affect the lawfulness of prior processing.

If you do not wish to use biometric verification, contact support@insurancerevenue.com before starting the process to request an alternative. Where we rely on freely given explicit consent, an appropriate alternative must be available. Identity and fraud checks may still be required before approval.

4.2 Use and disclosure

Biometric information is used for the disclosed identity-verification, liveness, and fraud-prevention purposes. We do not sell, lease, trade, or otherwise profit from biometric identifiers or biometric information.

Access and disclosure are limited to the verification process, authorized providers, and other circumstances specifically permitted by applicable law and the relevant consent.

Biometric information is not routinely provided to Buyers or complainants.

5. How we disclose information

5.1 Service providers and infrastructure

We disclose information to providers as necessary for the services they perform. These include:

Providers’ roles depend on the service. Some process information on our instructions; others, such as payment providers, may also process information for their own legal and regulatory purposes under their own notices.

5.2 Publisher administrators and teammates

Authorized owners and users may access account information appropriate to their assigned permissions. Publishers control the users they invite and the permissions available to those users, subject to our administration of the platform.

5.3 Buyers, complaints, and legal matters

We may disclose relevant publisher identity, business information, traffic-source information, sub-publisher details, and compliance records to Buyers, regulators, courts, law enforcement, complainants, or their legal representatives where reasonably necessary and legally permitted to:

• Investigate traffic quality, fraud, or compliance concerns.
• Respond to complaints and disputes.
• Comply with lawful requests and obligations.
• Establish, exercise, or defend legal claims.

We assess the requester, purpose, legal basis, and information reasonably needed. These disclosures do not ordinarily include biometric templates, identity-document images, tax identifiers, or banking details.

The Publisher Agreement describes related contractual rights and responsibilities. It does not authorize disclosures prohibited by applicable law.

5.4 Advisers, affiliates, and business transactions

We may disclose relevant information to corporate affiliates, legal advisers, auditors, insurers, and other professional advisers for the purposes described in this Policy.

Information may also be disclosed in connection with a proposed or completed financing, merger, acquisition, reorganization, or sale of a business or assets, subject to applicable confidentiality and data-protection requirements.

5.5 Advertising and sale or sharing of partner information

We do not sell partner personal information or share it for cross-context behavioral advertising, as those terms are defined by the California Consumer Privacy Act. We do not use the partner website or portal for targeted advertising.

This statement concerns information covered by this Policy. It does not describe the separate insurance-consumer lead-distribution activity.

6. International processing

Prime Intent is based in the United States. Information may be processed in the United States and in other countries where our providers and authorized personnel operate.

Different countries may provide different legal protections.

For a restricted international transfer subject to EU, UK, or other applicable data-protection requirements, we require an applicable transfer mechanism. Depending on the transfer, this may be a recognized adequacy arrangement, appropriate contractual safeguards such as EU Standard Contractual Clauses and relevant UK transfer documentation, or a narrowly applicable legal exception.

Signing a B2B contract does not, by itself, authorize all international transfers. Routine transfers are not justified solely by a general assertion of contractual necessity.

Contact support@insurancerevenue.com for information about the safeguards applicable to your information and to request a copy or description, subject to appropriate protection of confidential information.

7. Retention

We retain personal information for as long as reasonably necessary for the disclosed purposes, subject to applicable retention and deletion requirements.

7.1 Invitation requests

Records in our invitation-request database are scheduled for deletion 24 months after submission, regardless of whether the request was archived. Staff may delete them earlier.

If an invitation request leads to a partner account, information incorporated into that account is subject to the account-retention criteria below.

Staff-email copies, correspondence, and other separately maintained records are not necessarily removed by the invitation-database deletion job. They are subject to the relevant business-record retention criteria and applicable deletion requests.

7.2 Pending, rejected, inactive, and closed accounts

We retain information as necessary to complete or document a review, administer an account, prevent reasonably identified fraud or duplicate applications, handle complaints, and meet legal obligations.

Retention depends on the account’s status, the information involved, outstanding obligations, and whether particular records remain necessary for a documented legal or security purpose. Indefinite retention is not justified merely because an automatic deletion function is unavailable.

7.3 Agreements, payments, and compliance records

Agreements, signature evidence, payment records, tax documentation, and relevant compliance records may need to be retained during the relationship and afterward.

The applicable period depends on the record, legal requirements, relevant claim periods, unresolved disputes, and the need to establish, exercise, or defend legal claims.

A contractual duty requiring a publisher to retain specified records does not automatically require Prime Intent to retain all partner information for that same period.

7.4 Technical records and browser storage

Security and operational records are retained for periods appropriate to their purposes, including investigation of incidents and protection against abuse.

Browser storage remains according to its technical expiration, sign-out behavior, and your browser controls.

7.5 Provider records, backups, and legal holds

Records held on our behalf are subject to applicable provider arrangements and retention instructions. Providers acting independently may retain information to meet their own lawful obligations.

Where information is deleted from active systems, restricted backup copies may remain until the applicable backup cycle expires. They are not used for ordinary business purposes.

A legal hold applies to relevant records where preservation is necessary and lawful. It does not justify retaining unrelated information or override a biometric destruction rule unless that rule permits the exception.

8. Security

We use safeguards designed to protect information, including encrypted connections, access controls, authentication protections, and restricted access to provider systems.

No system or internet transmission is completely secure. Keep your credentials confidential and promptly report suspected unauthorized access to support@insurancerevenue.com.

Do not send passwords, identity documents, bank account numbers, or tax identifiers through ordinary support email or messaging channels. Ask us for the designated secure submission method.

9. Your rights and choices

Depending on the applicable law and our processing, you may have rights to:

• Confirm whether we process your information and request access or a copy.
• Correct inaccurate information.
• Request deletion.
• Receive qualifying information in a portable format.
• Object to or restrict certain processing.
• Withdraw consent where we rely on consent.
• Opt out of covered sales, advertising-related sharing, targeted advertising, or certain profiling where applicable.
• Limit certain uses of sensitive personal information.
• Appeal a decision about a privacy request where applicable.
• Complain to a competent data-protection authority.

These rights are subject to applicable conditions and exceptions. We do not unlawfully discriminate or retaliate against you for exercising them.

9.1 Making a request

Email support@insurancerevenue.com. You may use “Publisher Privacy Request” as the subject, but no particular wording is required.

For ordinary account corrections, you may also contact support@insurancerevenue.com.

We verify identity where appropriate to the request and risk, using information reasonably necessary for that purpose. We do not require identity verification for opt-out requests where applicable law prohibits it. Authorized agents may submit requests subject to applicable authorization requirements.

We respond within the period required by applicable law and explain any permitted extension.

9.2 Deletion exceptions

We assess deletion requests individually. We may retain particular information where necessary and legally permitted to meet legal obligations, protect security, prevent fraud, or establish, exercise, or defend legal claims.

Where an exception applies, we retain only the relevant information needed for that purpose and explain the decision unless prohibited by law. There is no blanket rule that all partner information must remain for five years.

9.3 Consent and communications

You may withdraw applicable consent or ask us to stop using a particular communication channel by contacting us. SMS recipients may reply STOP.

Withdrawal does not affect processing lawfully completed beforehand. Necessary account, security, and legal notices may continue through an appropriate channel.

9.4 Verification and review decisions

Verification providers use automated checks to produce results or risk indicators. Staff review completed onboarding and decide whether to activate an account.

You may contact support@insurancerevenue.com to raise an apparent verification error or request review. We may limit the explanation of security methods or fraud indicators where legally permitted, without restricting rights that applicable law requires us to provide.

9.5 Appeals and regulatory complaints

If we deny a request, you may ask us to reconsider by emailing support@insurancerevenue.com and identifying the original request. Where a statutory appeal right applies, we handle the appeal under that law and provide the required outcome and escalation information.

Where EU or UK data-protection law applies, you may complain to the relevant supervisory authority, including the UK Information Commissioner’s Office where appropriate.

10. Children

The partner services are intended for adults aged 18 and older. We do not knowingly collect partner information from children under 18.

Contact support@insurancerevenue.com if you believe a child has provided information through these services so we can investigate and take appropriate action.

11. Changes to this Policy

We may update this Policy and change the date above.

For material changes, we provide appropriate notice to affected individuals, which may include email, a portal notice, or a notice at the relevant collection point.

Where applicable law requires new consent or another step before a changed use, we complete that step before the changed processing begins. Continued use does not substitute for consent where consent is legally required.

12. Contact

Privacy and legal requests: support@insurancerevenue.com
Account support: support@insurancerevenue.com

Prime Intent LLC
Attn: Legal / Privacy
30 N Gould St, Suite 42491
Sheridan, WY 82801
United States