Datenschutzerklärung, Store-Eintrag und Screenshot-Plan mit Claude Code schreiben

Inspect this codebase and produce three things.

1. A data inventory as a table: data type (email, name, user ID, payment info, photos, location, usage data, crash data, device identifiers), where it is collected (file or component), where it is stored (database table, third-party service), purpose, whether it is linked to the user identity, and whether it is used for tracking across apps or websites. Include third-party SDKs and APIs (auth provider, analytics, error tracking, payments, push service, AI APIs that receive user content).
2. A privacy policy page at /privacy written from that inventory in plain English: what we collect, why, who receives it, how long we keep it, how users can delete their account in the app (/delete-account) and contact us. Mention that the iOS and Android apps use the same service. No practices we do not have, no boilerplate about cookies we do not set. Mark uncertain statements with TODO.
3. Draft answers for the Apple App Privacy questionnaire (data types, linked to user yes/no, used for tracking yes/no, purposes) and for the Google Play Data safety form (collected or shared, required or optional, encrypted in transit, deletion available), both derived from the same inventory so they cannot contradict each other. Note that the native iOS wrapper integrates the AdMob SDK even when ads are off; if we do not show ads, say that advertising data is not collected, but flag the App Store Connect advertising identifier (IDFA) question for me to answer as the wrapper documentation describes.

Write the store listing for this app based on the features that exist in the codebase today (check routes and components; do not list anything that is behind a feature flag or marked as coming soon).

Apple: app name (max 30 characters), subtitle (max 30), promotional text (max 170), description (up to 4000 characters, first two lines carry the message), keywords field (max 100 characters, comma separated, no spaces after commas, no words already in the name).
Google Play: title (max 30), short description (max 80), full description (up to 4000 characters).
Review notes for both stores: what the app does in two sentences, the demo account (I will fill in the credentials), the native features the app uses (push notifications, biometric login, native share, offline screen) and where to find them, and that users can delete their account under Settings.

Rules: no superlatives we cannot prove, no mention of other platforms or of being a beta, no references to the website version, no competitor names, no AI buzzwords unless the app is an AI product. Use the language the app UI uses.