Google Play Data Safety Summary
Based on com.meeddev.cepnabiz v1.1.0+3 source, permissions, and local data paths.
| Data type | Collected? | Shared? | Purpose | Required? |
|---|---|---|---|---|
| Financial info (income, expenses, budget, assets) | No; not transmitted off-device | No | Local budgeting and analysis | Optional, local |
| Name / greeting preference | No | No | Local personalization | Optional |
| Photo (receipt) | No; on-device OCR | No | Suggest transaction fields | Optional |
| App activity / diagnostics | No | No | No analytics/crash SDK | Not applicable |
| Account, location, advertising ID, payment | No | No | No related feature | Not applicable |
Security and deletion
- The packaged manifest includes dependency-provided INTERNET and ACCESS_NETWORK_STATE permissions; verified app code has no remote path that transmits personal or financial data.
- Camera/gallery permission is needed only when the user starts receipt scanning.
- The in-app “Delete all data” flow clears local Hive boxes.
Child safety and target audience
The target audience and age declaration must match the app's actual content in Play Console. Claims about knowingly collecting data from children, child-directed advertising, or anonymous/random chat may be made only after verifying the real product behavior and applicable Play policies.
Policy and release consistency
This summary must remain consistent with the privacy policy, in-app disclosures, permissions, third-party SDKs, and the current binary release. Revisit the Play Console Data Safety form whenever those facts change.