1. Information we collect
Depending on how the service is used, InsureAhead may collect account information such as name, email address, role, and authentication data; agent-profile information such as licensing categories, states, registrations, training, firm information, and carrier appointments; and client case information entered by an authorized user.
Client case information may include contact details, date of birth, marital/household information, dependents, income, housing, debts, savings, retirement accounts, existing insurance or annuity information, goals, budget, beneficiary information, policy concerns, tax-related status questions, and limited underwriting pre-screen information such as height, weight, nicotine use, broad medical-condition summaries, medications, recent hospitalizations/surgeries, hazardous activities, driving history, and travel history.
The current intake is designed not to collect a full Social Security number, bank-account number, routing number, card number, or full check-account information. InsureAhead may record whether an SSN/TIN is available for later carrier or tax-reporting needs without storing the actual number in the intake.
2. How information is used
Information is used to provide account access, organize client cases, calculate needs, identify missing information, explain insurance concepts, evaluate broad product and service fit, apply agent-eligibility gates, compare premium/benefit scenarios, support quote/application workflows, save user progress, protect the service, troubleshoot issues, and improve product functionality.
3. Automated and AI-assisted features
InsureAhead may use automated rules or AI-assisted features to summarize information, explain concepts, identify missing data, or support workflows. Important licensing, tax, compliance, product, and carrier rules should be tied to verified sources or deterministic rules rather than guessed. Sensitive client information should not be sent to an AI provider unless the feature, provider terms, security controls, and user disclosures have been specifically approved for that use.
4. How information is stored and protected
The current application uses authenticated access and database row-level security so users can access only records permitted by the application's authorization rules. Additional technical and administrative safeguards should be added as the product moves toward production, including least-privilege access, audit logging, secure secret management, encryption practices, incident-response procedures, backups, and stronger controls for any future high-risk identity data.
No security measure can guarantee absolute security. Users are also responsible for keeping account credentials secure and for avoiding sensitive information in fields that are not intended to store it.
5. Service providers and third parties
InsureAhead may use vendors for hosting, authentication, databases, email, analytics, customer support, error monitoring, quoting, insurance-carrier connectivity, illustration systems, e-applications, or other operational services. Those providers should receive only the information reasonably necessary for their role and should be subject to appropriate contractual and security requirements before production use.
When a user chooses to request a carrier quote, start an application, or use another integrated service, information may be sent to the selected carrier or authorized technology provider as necessary to perform that request.
6. We do not sell personal information
InsureAhead is not designed to sell client or agent personal information to advertisers. If the business model or data practices ever change in a way that creates additional legal notice or opt-out obligations, this policy and the product controls should be updated before that change takes effect.
7. Cookies and similar technologies
InsureAhead currently relies on strictly necessary authentication/session technologies and may use local or browser storage needed to operate the service. See the Cookie Policy for more detail. Non-essential analytics, advertising, or behavioral-tracking cookies should not be enabled without updating disclosures and consent controls where required.
8. Retention
Information should be retained only as long as reasonably necessary to provide the service, satisfy legitimate business and compliance needs, resolve disputes, maintain records, and meet legal obligations. Before production launch, InsureAhead should adopt specific retention and deletion schedules for account data, client cases, quotes, application records, logs, and backups.
9. Access, correction, deletion, and privacy requests
Users should be able to review and correct information within the service where functionality permits. The final production policy should identify the legal entity operating InsureAhead, the privacy-contact method, and the process for exercising any rights available under applicable state or federal privacy laws.
10. Children
InsureAhead accounts are intended for adult users. A client case may contain limited information about a dependent or minor when relevant to insurance planning, such as name, relationship, age, or beneficiary status. The service is not intended for children to create or independently manage accounts.
11. Changes to this policy
This Privacy Policy may be updated as features, integrations, data practices, or legal requirements change. The revised policy should show an updated effective date, and material changes should be communicated as required.