Privacy Policy

Your confirmed compensation information, forecasts, and planner information are private to your account. Other customers and agents cannot access them through AgentPay.

Automated and service-provider systems handle compensation data during ordinary processing. AgentPay's authorized support personnel do not routinely open customer compensation records or monitor individual pay amounts. Limited authorized access may occur only when reasonably necessary to provide support you request, investigate a processing problem, maintain or secure the service, prevent fraud or abuse, comply with law, or respond to a valid legal process.

AgentPay therefore does not make the absolute promise that no human can ever access a compensation record. Access is limited by role, purpose, and the amount of information reasonably needed.

AgentPay never asks for or uses customer or policyholder information. It works only from your own aggregate compensation totals, your renewal schedule totals, and the planning and marketing values you enter. Team sales tracking records only the lead source, product, premium, policy count, and date, never who the customer is.

• Account and authentication data: name, email address, account identifiers, authentication events, login and recovery records, and account settings.
• Stripe billing identifiers: Stripe customer, checkout, subscription, invoice, payment, and transaction identifiers; subscription status; billing period; assigned price; consent version; and charge status. Stripe processes card details. AgentPay does not receive or store your complete card number or card security code.
• Confirmed compensation information: pay dates, generic compensation categories, aggregate premiums, compensation values, adjustments, deductions, deposits, totals, production information, mapping choices, reconciliation status, and customer corrections or confirmations.
• Forecast and planner information: agency and production inputs, forecast results and scenarios, allocation choices, bills, due dates, planning categories, and other values you choose to enter.
• Renewal graph images: images you explicitly choose for automated extraction are processed temporarily as described below. The raw image is not saved with your account.
• Technical logs: device, browser, IP address, timestamps, request, processing, security, diagnostic, and error records produced by AgentPay and its providers.
• Support communications: the messages and information you provide in service, privacy, billing, security, or legal requests.
• Public-page visit information: on the public home page and landing page only, an advertising pixel from Meta may record that a visit happened: the page address, browser and device information, IP address, and Meta's own cookie identifiers. It is described under "Advertising on public pages" below.

Import only your own authorized aggregate compensation data and information that AgentPay requests for the service. Do not select a workbook containing customer or employee records, policy numbers, addresses, claims, medical or health information, Social Security numbers, dates of birth, full bank or payment-card numbers, passwords, or identity documents.

Review the workbook before selecting it. The approved structured export should contain aggregate compensation data rather than customer- or policy-level information. See the Data Import Guide.

• Create, authenticate, recover, and secure your account.
• Validate structured compensation information locally, present results for review, and persist confirmed generic values.
• Generate preliminary and history-informed forecasts, scenarios, and planner outputs.
• Process subscriptions, document billing authorization, prevent duplicate subscriptions or charges, and control paid access.
• Process confirmed imports, diagnose errors, support customers, protect the service, and prevent fraud or abuse.
• Send account, security, billing, and service email. If you create an account but do not finish setting it up, AgentPay may send an occasional account re-engagement email, which you can opt out of using the link in that email.
• Maintain, test, and improve reliability and accuracy using data limited to what is reasonably needed.
• Comply with law, respond to lawful requests, and establish, exercise, or defend legal claims.

AgentPay uses vendors acting on its behalf to operate the service. Depending on the feature and configured processing path, these providers may receive, store, transmit, or process the limited information needed for their role:

• Supabase provides account authentication, database services, server functions, and related security and technical logs.
• Stripe provides checkout, recurring billing, receipts, payment processing, fraud prevention, and subscription management.
• Vercel provides application and web hosting, request handling, deployment infrastructure, and related technical and security logs.
• Railway hosts AgentPay's dedicated private service for automated renewal graph extraction. Raw renewal graph images are processed in memory and are not stored by that service.
• Meta receives public-page visit information through its advertising pixel on the public home page and landing page only, as described under "Advertising on public pages" below. Meta uses it under its own terms and privacy policy.
• Resend and/or another email provider may deliver account, recovery, transactional, service, support, or account re-engagement email and process the recipient address, message content, and delivery metadata needed to do so.
• Setup call requests sent from the public "Schedule a setup call" page (your name, email address, phone number, office, preferred times, and note) are stored by AgentPay and emailed to AgentPay support to arrange and confirm the call. They are used for nothing else. No account is created and no payment or compensation information is requested.

Providers may also allow exceptional access by their authorized personnel under their security, support, and legal procedures. AgentPay may disclose information to professional advisers, authorities, or transaction participants when reasonably necessary for legal, security, compliance, or corporate-transaction purposes.

AgentPay does not sell personal information. AgentPay does not disclose compensation data to an insurance carrier merely because you use the service.

On its public home page and landing page only, AgentPay may use the Meta pixel. It tells Meta that a visit happened so AgentPay can measure its advertising and show its ads on Facebook and Instagram to people who visited those pages. Under some privacy laws this is considered sharing information for cross-context behavioral advertising.

The pixel is never loaded once you are signed in, and it is not present on any account, forecast, planner, import, or billing page. No account, compensation, forecast, planner, or billing information is ever sent to Meta.

The pixel is not loaded when your browser sends a Global Privacy Control or Do Not Track signal. You can also manage how Meta uses activity from other websites in your Facebook or Instagram ad settings.

Your privacy choices: you can also tell this browser not to share your visits to AgentPay's public pages with Meta. The choice is kept in this browser.

AgentPay uses deterministic structured-data parsing, validation logic, and forecast calculations. The structured workbook is read locally in the browser and is not sent to an external AI service. Automated processing can make mistakes. Customers should review mapped information and can correct or report issues through available service and support channels.

Renewal graph images use a separate process. When you choose an image, it is sent through an authenticated AgentPay endpoint to a dedicated private processing service so the printed values can be read automatically. No external OCR vendor or human reviewer is involved. The raw image is held only in application and worker memory, is not written to Postgres or persistent object storage, and is not saved with your account. Raw image buffers are cleared after success or failure. Processing is bounded by application and hosting request limits. Only structured values that you review and explicitly confirm are saved as Renewal Snapshot data.

AgentPay uses this processing to provide software outputs to the customer. It does not use AgentPay to make decisions about a customer's employment, insurance eligibility, credit, housing, or another legally significant benefit.

Compensation-data access is not part of routine human review. A limited number of authorized personnel may access only the information reasonably needed when:

• you request support or ask AgentPay to investigate a result;
• processing flags a format, mapping, or reconciliation issue that requires secure review;
• AgentPay must maintain the service or investigate suspected fraud, abuse, a security incident, or a threat to service integrity; or
• access is required to comply with law or valid legal process.

AgentPay applies access controls and confidentiality and security measures appropriate to compensation information. Access may be logged or reviewed where the supporting systems make that available.

The structured compensation workbook is read locally in the browser. Workbook bytes, filenames, worksheet names, and local file paths are not persisted by the structured import flow.

Confirmed compensation information, customer corrections and approvals, compensation history, forecast inputs and results, planner information, provenance metadata, support records, and technical information remain according to the retention rules applicable to the account and the service. AgentPay does not promise an unsupported fixed retention period for every retained data type. The period depends on the information, account status, service need, security risk, and legal obligations.

You may delete information using available account controls or request deletion by contacting support. Canceling a subscription does not by itself delete the account or saved information. Deletion from active systems may not immediately remove encrypted backups, security logs, or information AgentPay must retain for fraud prevention, billing, disputes, tax, accounting, legal, or compliance purposes.

Billing and subscription-consent records may be kept as reasonably needed to document authorization, resolve disputes, and meet legal obligations. AgentPay will delete or deidentify information when it is no longer reasonably needed, subject to applicable exceptions.

AgentPay uses reasonable administrative, technical, and organizational safeguards designed for the sensitivity of compensation information, including authenticated accounts, private storage, access controls, and server-side authorization. No method of storage or transmission can be guaranteed completely secure.

Protect your password and account access, use only trusted devices and networks, and contact support promptly if you suspect unauthorized access.

Depending on where you live, you may have rights to request access, correction, deletion, portability, or information about disclosures; to appeal a denied request; and to be free from unlawful discrimination for exercising a right. AgentPay may verify your identity and may retain information when an exception applies.

Send privacy questions or requests to support@agentpayforecast.com. Include the email address associated with your account, but do not attach a compensation workbook or unrelated sensitive information to an ordinary email.

AgentPay is a professional service for adults and is not directed to children under 13. AgentPay does not knowingly collect personal information from children.

AgentPay may update this Policy as its practices or legal obligations change. The last-updated date identifies the current copy. AgentPay will provide additional notice of material changes when required.