Data handling for a B2B insurance-technology platform.

Our role

Beneficiary Continuity Guard provides technology exclusively to licensed insurance companies and licensed insurance broker organizations, including authorized personnel acting on their behalf. An organization determines the business purpose, authorized users, and permitted records in its workspace. Depending on the written agreement and applicable law, the organization may direct our processing of workspace data while we separately determine how we process account, security, inquiry, and billing-administration data.

Technology platform only — we do not recommend or sell insurance. Beneficiary Continuity Guard provides digital delivery systems and workflow technology exclusively for licensed insurance companies and licensed insurance broker organizations, including authorized personnel acting on their behalf. This platform is not offered to John Q. Public. In connection with this platform, the technology company does not offer, recommend, quote, sell, solicit, negotiate, place, underwrite, bind, issue, service, cancel, adjust, or settle insurance, and does not collect, receive, control, hold, transmit, or retain insurance premiums. Insurance products, professional judgments, and decisions remain solely with the appropriately licensed insurance organization. Any permitted insurance payment is handled by that organization or its authorized payment processor—not by the technology company. Amounts invoiced by the technology company are solely for technology products and services and are not insurance premiums or insurance transaction fees.

Insurance Technology Platform — We Do Not Sell Insurance →

Organization identity and access review

Account identity is supplied through Manus OAuth: an opaque account identifier, name, and email address. We do not receive an OAuth password. Signing in does not open the workspace. A non-owner user must submit an organization name and type, professional capacity, organization-issued email, jurisdiction, license or organization identifier, and intended workflow. The owner reviews and approves or denies access. We store the request, review status, review note, reviewer, and review time.

Public software inquiries

The public inquiry form collects a representative’s name, organization-issued email, organization, professional capacity, jurisdiction, identifier, operational workflow, current business systems, implementation timing, and software-demonstration intent. It does not ask for a consumer insurance application, personal policy details, medical history, family circumstances, claim information, or coverage needs.

Organization workspace records

The platform can store organization-managed policy reference data, people and relationship records, designation tiers and allocations, attestations, rule-based findings, implementation settings, organization branding, workflow communications, and operational activity evidence. The organization is responsible for deciding whether it is authorized to provide and use those records and for limiting access to appropriate personnel.

The application does not request Social Security numbers, government identity documents, medical records, bank account credentials, or card numbers. Organization users should not place those items in free-text fields or the public assistant.

Audit evidence and retention

Consequential workspace actions append to a hash-linked audit record. The active application has no procedure that edits or deletes an existing audit entry. This supports later verification but also means the record may outlive the policy, person, or workflow object it describes. Organization agreements should define lawful retention, access, export, correction by appended entry, and end-of-service handling before production data is introduced.

Other records are kept for the period needed to operate and secure the service, administer the organization relationship, meet written retention requirements, preserve transaction and dispute records, and comply with law. A production agreement may set a more specific schedule.

Private B2B software billing

Staff may prepare local technology-service invoice drafts containing an organization billing contact, software scope, amount, due period, and draft status. Provider issuance is currently inactive, so a new draft creates no Stripe customer, hosted invoice, email, or payment request. If an invoice workflow is later authorized in writing, Stripe is the configured technology-payment processor and provider identifiers, links, status, and timestamps may be retained for reconciliation. We do not store card or bank-account numbers. Billing outcomes cannot change any policy, coverage, claim, beneficiary, quote, payout, or settlement record.

Invoices are for technology products and services only and do not include insurance premium, policy fees, claim funds, or settlement funds.

AI assistant

Public assistant messages are sent to a language-model service to produce a response. The assistant is configured to discuss the software, workflow, implementation, integration, reporting, training, and support—not an individual insurance situation. It has no direct access to organization workspace records. Do not submit confidential records, credentials, policyholder data, or personal insurance facts in chat.

AI-assisted software output is informational and must be reviewed by authorized personnel. It does not make or recommend an insurance decision.

Service providers and transfers

The service relies on providers for cloud hosting and database infrastructure, OAuth identity, transactional email, software invoicing and payment, language-model responses, monitoring and analytics, and file storage. Information is shared only as needed for those functions and under the provider’s applicable terms. Production customers should require a current subprocessor list, location and transfer review, and contractual safeguards appropriate to their jurisdiction before deployment.

Historical consumer-era records

The public consumer experience was retired during the August 2026 B2B repositioning. Historical account, lead, contribution, policy, family, designation, audit, email-delivery, and payment-reconciliation records were preserved rather than relabeled, overwritten, or deleted. They are not evidence of a current consumer offering and are not used as organization-qualified B2B pipeline.

Security and assurance limitations

Access controls, server-side authorization, database separation, signed webhooks, and hash-linked records reduce risk; they do not make any system risk-free. The service does not currently represent that it holds SOC 2 attestation, HIPAA coverage, a formal third-party penetration-test report, or a carrier security approval. An organization requiring those assurances should include them in due diligence and written implementation conditions.

Requests and questions

Organization users should direct access, correction, export, retention, and deletion requests through their organization’s authorized contact and the applicable agreement. Public questions about this policy may be submitted through the software inquiry page without including confidential or personal insurance data.

See Insurance Technology Platform — We Do Not Sell Insurance → for the permanent technology, insurance-payment, data, and question-routing boundary.