Store readiness

Store Disclosure Checklist

Transparency notes for users and store review. These disclosures summarize the current intended production behavior for privacy labels, Data safety, permissions, account deletion, AI, and billing.

Important

This page is not legal advice. Store forms and public disclosures must match the exact production app, SDKs, backend configuration, subscriptions, and data retention behavior at submission time.

Public URLs to Enter in Store Consoles

Likely App Store Privacy Data Types

Based on the current VociApp feature set, the following data types may need to be declared when transmitted off-device or linked to an account:

Current public positioning: no third-party ads, no cross-app tracking, no sale of personal data.

Likely Google Play Data Safety Categories

Permissions and Prominent Disclosure

Camera/photo access should remain user-initiated for scan/import flows and be explained immediately before the platform permission prompt where practical. The disclosure should explain that selected images are used to recognize text and create vocabulary cards, and that AI-assisted extraction may send recognized text to backend AI processing.

Account Deletion

VociApp now provides a discoverable in-app deletion path from Account > Delete account for signed-in users. The flow requires final confirmation, deletes the account and account-scoped cloud data, clears local account-scoped data on the current device, and warns that Apple/Google subscriptions must be managed separately. Use account-deletion.html as the external web resource for users who cannot access the app and for Google Play requirements.

AI Submission Notes

AI features are optional study aids with quotas and server-side input limits. Store review notes should explain that AI is used for vocabulary explanations, answer feedback, verb support, context generation, and import enrichment; that harmful AI output can be reported; and that AI output is not authoritative.

Billing Notes

If Plus or Pro AI unlock digital features inside the iOS or Android app, use Apple In-App Purchase and Google Play Billing unless a specific regional entitlement or exception applies. Avoid in-app links or wording that directs users to non-platform payment methods unless that flow is explicitly allowed for the target storefront.

Pre-Submission Checks for the Developer