Your information deserves care.

Current service status

Claim intake is disabled by default. If explicitly enabled after security review, claim details and contact information are stored in Firestore and linked to the authenticated account. Secure customer document uploads remain disabled. Do not submit real sensitive information until the final notice and safeguards have been reviewed.

Information and purposes

Depending on the service requested, information may include contact details, claim facts, insurer correspondence, policy excerpts, support messages and account activity. Information is intended to help organize a claim assessment, respond to customer requests, provide support and protect service security. The final production notice must specify the applicable legal basis, required/optional fields, recipients, service providers, transfers, rights and verified contact details.

Consent and records

Claim intake requires an affirmative consent checkbox. When a claim is successfully accepted, the server records the notice version, purpose and acceptance timestamp alongside the claim and in a separate consent audit record. The current notice version is 2026-10-21-v1. Consent to claim processing is separate from optional marketing communications.

Service providers and AI

Before information is sent to hosting, OCR, AI, messaging or other service providers, Claim Setu Assistant must document the data flow, purpose, access, safeguards and applicable contractual terms. Customer documents must not be used for model training without separately reviewed lawful grounds and appropriate permission.

Access, correction and deletion requests

Signed-in customers can submit access, correction or deletion requests from Account Settings. The service records a request for review; the acknowledgement is not confirmation that the request has been fulfilled. An authorized reviewer must verify the request, assess any applicable legal or operational retention obligations, coordinate action across relevant systems and record the outcome.

Retention and security

A final category-specific retention schedule and automated deletion workflow are not yet implemented. Records are not automatically deleted merely because a request is submitted. Production collection must remain disabled until retention periods, legal-hold handling, secure storage, access controls, deletion fulfilment, audit logging, backups and incident response have been implemented and reviewed.

Your choices and contact

Use Account Settings to submit a privacy request when signed in. Before production launch, Claim Setu Assistant must publish verified privacy and grievance contact details and explain the process for raising concerns. No sensitive document should be sent by ordinary email unless an approved secure process specifically directs you to do so.

This page describes current prototype controls and known limitations. It is not a final statutory privacy policy or legal advice.