Data Policy

This policy explains the product’s intended data principles separately from the limited information collected by the public website. Capabilities still being designed are described as strategy, not completed guarantees.

Identity, verification and data-sharing workflows are intended to begin with clear user action and an authorized purpose. Consent language and revocation behavior must be validated for each production integration.

Tripeaz intends to request only the information needed for a defined workflow and to avoid copying sensitive source documents where a verified result or user-controlled transfer can serve the purpose.

DigiLocker and API Setu access and integration approval provide a foundation for authorized workflows. This does not mean every desired API is available, live in the product or endorsed by the government.

Production controls are intended to include role-based access, least-privilege service access, secure transport, controlled operational access and avoiding sensitive data in logs. These controls require technical verification before stronger claims are made.

For relevant regulated or sensitive workloads, the infrastructure strategy is to evaluate appropriate India-hosted processing and storage. This page does not claim that all current or future data is stored only in India.

Where integrations permit, the product intends to let users initiate identity flows, understand the purpose and control the information shared. Detailed retention and deletion behavior will depend on the approved production workflow.

The final data policy must be aligned with the deployed architecture, providers, incident process, retention schedule, grievance contact and applicable Indian law before public launch.