Your details, explained.
The current service records applications. Payment collection and insurer issuance are separate, unconfigured steps.
Information collected
The application form collects name, age, gender, email and mobile. The service also records application references, submission time, request status and, if legitimately available later, payment and insurance records. It does not request a password, OTP, card or banking details in the current application flow.
Why information is used
The submitted details are used to create, validate and retrieve your application and generate your application record. They support the request service and any subsequent servicing within the platform's authorized role. Submitting the form does not give permission to collect a premium or activate coverage.
Insurer and service-provider sharing
No insurer is designated as your underwriting partner by the current application flow. If an authorized insurer integration is introduced, the relevant insurer, information to be shared and applicable privacy terms must be disclosed before transfer. Technical service providers may process data to operate hosting and storage; approved operator and processor details must be published before broad rollout.
Storage and access safeguards
Personal details are encrypted in the database. Record and application-document access requires a private capability credential. Its hash is stored in the database, and a reference or mobile number alone is insufficient. These controls reduce risk; no system can promise absolute security.
Your private link and device
The link's private credential is consumed from the URL fragment and retained only in this tab's session storage. Save the link somewhere private before closing the session. Anyone holding it can view your record. Use Remove access from this device when finished on a shared device. A downloaded application PDF contains personal information, but does not contain the private access token.
Retention
Application records persist in the service database; there is no automatic deletion period currently configured. The operator must approve and publish a retention schedule, operational deletion process and any legally required retention before broad deployment. No unsupported retention deadline is promised here.
Your rights and requests
You retain applicable rights under Indian privacy law. A verified process for privacy information, correction, deletion and grievances, together with the responsible entity and contact channel, must be established before a live offering. No unverified mobile-only lookup or deletion request can expose or change your record.
Contact and review
Dedicated privacy and grievance contact details have not been configured for this service. Do not send private links or sensitive personal information through public channels. This operational notice requires review against applicable Indian privacy requirements before live deployment.