VIDENSE
Native app

Vidense App Privacy

App-specific information for iPhone and future native Vidense apps.

Version 2026-09-14.3 · Updated

1. Controller and relationship to the full Policy

The controller is Apptheism, Fischmarkt 17, 78462 Konstanz, Germany. Contact: privacy@vidense.ai.

This App Privacy notice summarises native-app data flows. The full Vidense Privacy Policy supplements it and controls in relation to legal bases, recipients, international transfers, retention and data-subject rights.

2. Data processed in the app

Data typeUse
Name and email addressRegistration, sign-in, account management and support
User IDAccount, analysis, credit and purchase mapping
Photos or videosUser-selected uploads for the requested analysis
Other user contentVideo links, analysis requests, briefings, timestamps and, where offered, transcripts
Purchase historySubscription, top-ups, entitlement verification, restoration and billing
Product interactionFeature delivery, synchronisation, security and troubleshooting
Push token (optional)Analysis-completion notice, only after system permission

3. Uses not intended

  • No third-party advertising tracking and no sale of personal data.
  • No use of location, contacts, health data or advertising ID for product operation.
  • No access to the entire photo library: the app receives only files expressly selected through the system file/photo picker.
  • No direct collection of payment credentials; payment is handled by the store or payment provider.
  • No crash or advertising SDK is included in the currently reviewed build. This is rechecked before every store submission.

4. Sign-in and purchases

Email sign-in uses Supabase. With Sign in with Apple, Apple processes authentication and Vidense receives the Apple identifier and profile data you choose to provide. With Sign in with Google, Google processes authentication and Vidense receives the Google identifier, name and email address of the approved profile.

Purchases use StoreKit/Apple and RevenueCat. Vidense processes product, status, transaction and user identifiers, but not full card or bank data. Purchases are verified on the server before credits are available.

5. Video analysis and deletion

Selected video files are temporarily transferred to Cloudflare R2 and Google Gemini for analysis. The R2 object and provider file object addressable by Vidense are deleted as soon as possible after completion or final failure and no later than the technical 24-hour limit. Limited provider security logs follow the verified contract. Results remain until the user deletes them or the account.

6. Push notifications

Push notifications are optional. With permission, the app registers a push token, which Vidense maps to an internal user ID and addresses through Apple Push Notification service. Permission can be disabled in iOS at any time; obsolete tokens are removed.

7. Delete account and cancel subscription

The app offers complete account deletion in account settings. Content and personal account data are removed; legally retained financial evidence may remain pseudonymised. For Sign in with Apple, Vidense revokes the related authorisation.

An Apple subscription is independent of the Vidense account and must be cancelled in Apple's subscription management. The app explains this before deletion. Account deletion is neither subscription cancellation nor a refund request.

8. App Store privacy disclosures

App Store privacy disclosures must match actual processing. The current draft lists name, email address, photos/videos, other user content, user ID, purchase history and product interaction as linked to identity and not used for tracking. The app, SDKs, backend and store disclosure are rechecked before every submission.

Vidense App Privacy — Vidense