Collect only what is needed for the selected task

Privacy commitments

• No MCA password, MCA OTP or DSC is requested. Email and mobile OTPs verify only this independent gateway account.
• Example company data and DIN-shaped identifiers that were never issued are used for demonstrations.
• Gateway email and mobile codes expire after ten minutes, allow five attempts per channel and can be used once. Only channel-bound hashes are stored. Gateway sessions expire after twelve hours and only a hash of the browser token is stored in D1.
• Account signup stores the verified email address and mobile number. Production delivery shares the minimum necessary destination and message with the configured email service and SMS provider.
• Profiles store a preferred name, language, optional home State/UT, user persona and accessibility preferences. Company memberships record a role and source so account-scoped tools can enforce access server-side.
• Agent personalisation remains off until the user selects data scopes and grants consent. Consent expires after 180 days and can be revoked from the profile page.
• Authentication, profile and consent changes create purpose-labelled audit events. The event records action metadata, not passwords, raw session tokens or OTP values.
• The DigiLocker exchange is simulated end to end. No connection is made to DigiLocker or API Setu, and no identifier is accepted.
• Assistant history can be cleared from the assistant. Self-service profile export/deletion and automated retention enforcement for audit records are still required before any real public pilot.
• Chat questions are guidance, not statutory submissions, and this prototype never files, approves or takes payment.