Why KredSetu may request permissions
Permissions are requested only where operationally necessary for onboarding, verification, support, security, or regulated lending workflows.
| Permission | Purpose | Required or Optional |
|---|---|---|
| Camera | Capture KYC documents, selfies, or verification images | Required only for identity verification steps |
| Storage / Files | Upload documents such as statements, PAN, or supporting proofs | Required when a user chooses document upload |
| Location | Support risk checks, address confirmation, or fraud monitoring where applicable | Optional unless clearly disclosed in product flow |
| Notifications | Share application status, OTP, reminders, and service alerts | Optional but recommended |
What we do not request by default
KredSetu does not request permissions that are not relevant to the service flow. Any future additional permission request should be accompanied by an in-context purpose disclosure.
Consent and control
- Users can deny optional permissions from browser or device settings.
- Permissions should be requested contextually, not pre-emptively without purpose.
- Where denial prevents a critical verification step, the flow should clearly explain the impact.