Vidense Privacy Policy

1. Controller and contact

The controller under the General Data Protection Regulation (GDPR) is Apptheism, Fischmarkt 17, 78462 Konstanz, Germany.

Send privacy requests to privacy@vidense.ai. A data protection officer will be named only if legally required; none is currently recorded as appointed.

2. Scope

This Policy applies to vidense.ai, the Vidense web app, native Vidense apps, support communications and related server-side processing. The App Privacy summary supplements but does not replace this Policy.

3. Categories of data

• Account data: name or display name, email address, internal user ID, language and account status.
• Authentication data: password hash at the authentication provider, session and verification information, identifiers for Sign in with Apple or Google, and acceptance records.
• Content: video link, public metadata, uploaded video file, filename, size, duration, preview image, analysis request, result, timestamps and, where offered, transcript.
• Contract and payment data: plan, purchased product, status, term, transaction/provider identifiers, credit ledger entries, invoice and refund status. We generally do not receive full card or bank details.
• Usage and device data: IP address, time, requested URL, browser/app version, operating system, technical errors, security events, product interactions and, if enabled, push token.
• Advertising measurement data, only after consent: Google ad-click information, consent state, purchase value and currency, an opaque conversion transaction ID and technical browser/connection data.
• Communications: optional name, email address, subject and content of support requests, and optional newsletter consent.
• Sharing and moderation data: a versioned rights confirmation with user, analysis, sharing scope and timestamp, plus content reports including the reported URL, category, explanation, good-faith declaration, case reference, contact details where required, and moderation decision.
• Cancellation data: name, contract email address, plan or contract description, type and requested date of cancellation, and an optional reason or the reason given for extraordinary cancellation.

4. Purposes and legal bases

5. Website access and security

When the site is accessed, Vidense and its hosting/security provider Cloudflare process connection data such as IP address, time, destination, headers, device/browser details and security signals. This is used to deliver the service, defend against attacks, enforce regional availability and diagnose errors.

When a free browser analysis is started and when an account is registered, we record the request time, access method, form page and hosting-provider-derived country. An email address is stored only if it is later provided for an account, checkout or an email feature chosen by the user. IP address, browser identifier and browser languages are retained for security and troubleshooting for 30 days, then removed by regular cleanup. Only authorised administrators can access them. IP geolocation does not prove a person's residence.

Only with optional consent do we link entry page, external referral domain, UTM campaign parameters and available ad-click identifiers (gclid, gbraid, wbraid) to your registration. The browser tab holds these details in sessionStorage for up to 24 hours; after server capture, attribution details are retained for up to 90 days until regular cleanup. Withdrawal removes the local attribution and requests deletion of stored account attribution while signed in or on the next sign-in. If you cannot sign in, you can request deletion through our privacy contact. These additional details are not sent to Plausible.

Cloudflare Turnstile may process security signals during registration, login, password recovery and use of the contact or cancellation form to detect automated abuse. Turnstile is loaded only in those security flows.

For up to five free browser analyses, we store a technically necessary random browser identifier in a first-party cookie (up to 365 days). On the server, we compare secret-keyed hashes derived from it and from the IP address and browser identifier to limit resets of the free allowance through new sessions. These hashes are deleted after no more than 365 days and are not used for advertising profiles.

Plausible provides cookieless, aggregate audience and campaign measurement. Its approved event design excludes names, email addresses, account identifiers, video URLs and provider transaction identifiers.

The Google Ads tag is not loaded until you accept advertising measurement. After consent, it can store or read advertising identifiers and send ad-click information, page and connection data, and a confirmed subscription purchase with its value, currency and opaque transaction ID to Google. It is used to attribute and optimise ads, not to provide Vidense functionality. You can withdraw or change the choice through 'Cookie settings' in the footer.

6. Contact form and support

For affiliate applications, we store the contact, channel, audience, reach and proposed partnership information you enter, the form language, receipt time and acknowledgement of the privacy information in our Supabase database. Only authorised administrators can access the application for review and follow-up. No user account or newsletter subscription is created. Applications become due for automatic deletion after 180 days and are no longer displayed in the admin area from that point. We use Cloudflare Turnstile and a secret-keyed IP hash valid for 24 hours to protect the form; the IP address itself is not stored in the application. Scheduled cleanup removes expired applications and hashes.

When you use the contact or cancellation form, we process the contact, message and contract data entered there and technical security data to deliver, confirm and handle the declaration and prevent abuse. Resend transmits the message to support@vidense.ai and, for the cancellation form, sends a receipt to the contract email address provided. You can use support@vidense.ai directly instead.

Requests relating to a contract or pre-contract steps are processed under Article 6(1)(b) GDPR. Other requests and protection of the form rely on Article 6(1)(f) GDPR; our legitimate interests are accessible support and protection against automated abuse.

7. Account and sign-in

Supabase processes the account, email verification, sessions and password hash. With Sign in with Apple, Apple provides an Apple identifier and, depending on the user's choice, a name and either a real or private relay email address. With Sign in with Google, Google provides a Google identifier and the approved basic profile data, in particular name and email address. Vidense cannot access Apple or Google passwords.

We record the accepted Terms version, time and access channel to perform the contract and retain evidence of legal declarations.

8. Video links, uploads and AI analysis

In the web app, processing by Google Gemini is necessary to provide the video analysis requested by the user and is based on performance of a contract or pre-contract steps requested by the user under Article 6(1)(b) GDPR. The transfer is described transparently before the Terms are accepted; no additional consent prompt is required on the web. No video content is transferred for analysis unless the user requests an analysis or has actively configured channel monitoring.

For public video links, we process the URL or video ID and metadata retrieved through official APIs. The link and analysis request are sent to Google's Gemini service, which may retrieve the publicly accessible content directly depending on the source.

Uploads are temporarily stored in Cloudflare R2 and then transferred to Google Gemini for analysis. The selected briefing language and any analysis preferences chosen in Vidense are also sent. Your name, email address and payment data are not included in the analysis request to Google Gemini. Vidense does not use source videos for advertising or model training. We use the AI service as a paid business/API service. Under the paid-service terms, Google may log prompts and responses for a limited period to detect abuse; those security logs are separate from the temporary provider file object deleted by Vidense.

Results may contain personal data visible or audible in the video. Do not upload special-category personal data or third-party recordings unless you have the required legal basis or consent.

9. Purchases, subscriptions and credits

RevenueCat orchestrates the product catalogue, purchases and entitlement status across platforms. Web payments use RevenueCat Billing with Stripe; Apple purchases use StoreKit and Apple. Vidense receives the product, status, term, transaction identifier and mapping to the internal user ID.

Credit lots and immutable credit ledger entries are stored to perform the contract, prevent abuse and maintain a traceable account. A client-side purchase message alone never grants credits.

10. Monitoring, sharing and push notifications

If you monitor a public channel, we store its identifier, limits, status and technical delivery information. Public metadata may be processed through the YouTube Data API and official notification interfaces.

If you activate a public result link, anyone who has the link can access the shared content. Disabling it blocks the link but does not delete copies already made by third parties.

Push notifications are enabled only after operating-system permission. We process a device-specific push token and send messages through Apple Push Notification service. Permission can be withdrawn in system settings.

11. Recipients and processors

We disclose data only where needed to provide and secure the service, process payments, comply with law, or with consent. Where a recipient acts as a processor, the required data-protection terms apply, including the subprocessors incorporated into them.

12. International transfers

Some recipients or subprocessors process data outside the EU/EEA. Where there is no adequacy decision, transfers rely on appropriate safeguards, particularly EU Standard Contractual Clauses and any necessary supplementary measures. EU-US Data Privacy Framework certification is relied on only where it is current and applies to the specific recipient and data flow.

Resend states that it stores customer data, including message content, delivery logs and account records, in the United States. According to Resend, selecting a sending region affects routing and delivery rather than the storage location.

13. Retention and deletion

• Uploaded source files: as soon as possible after completion or final failure; technical maximum of 24 hours for the R2 object and the temporary AI-provider file object addressable by Vidense. Limited provider security logs follow the verified contract and are documented separately.
• Incomplete upload sessions: until the upload window expires, generally no more than 24 hours.
• Analysis results and transcripts: until deleted by the user, account deletion, or an overriding legal/contractual period.
• Account data and push tokens: until account deletion, device deregistration or loss of purpose.
• Public shares: until disabled or the related result is deleted.
• Rights confirmations and content reports, including decisions: while required for sharing operations, legal duties, evidence or legal-defence purposes, followed by deletion or pseudonymisation.
• Billing, tax and accounting records: for applicable statutory retention periods; personal linkage is pseudonymised where possible.
• Security and error logs: only while necessary for protection, diagnosis and evidence; exact provider periods must be documented before publication.
• Free browser-analysis abuse prevention: pseudonymous device, client and network hashes for no more than 365 days; the additional network threshold considers only the last 30 days.
• Contact and support requests: until finally handled and afterwards only for as long as needed for evidence, legal-defence purposes or statutory retention duties.
• Cancellation notices and receipts: for contract handling and afterwards only for as long as needed for evidence, legal-defence purposes or statutory retention duties.

14. Account deletion, subscription cancellation and consent

Account deletion can be started in the app or account settings. We remove the profile, authentication, analyses, sources, push tokens and RevenueCat customer mapping; Sign in with Apple tokens are revoked for Apple accounts. Legally retained financial records remain pseudonymised.

Account deletion does not automatically cancel a subscription billed through an app store. Cancel it separately in the relevant store. Newsletter consent can be withdrawn through the provided control or by email at any time.

15. Your rights

Subject to the legal requirements, you have rights of access, rectification, erasure, restriction, portability and objection. Consent can be withdrawn prospectively at any time. Where processing relies on legitimate interests, you may object for reasons arising from your particular situation; you may always object to direct marketing.

Contact the privacy address above to exercise a right. You may also complain to a data-protection supervisory authority, particularly in your place of residence, place of work or the location of the alleged infringement.

16. Automated processing and security

Vidense automatically generates video analyses. This does not make a solely automated decision with legal or similarly significant effects within Article 22 GDPR.

We use role-based access, transport encryption, separated secrets, server-side purchase verification and purpose-bound deletion workflows. No system is risk-free; security incidents are handled under applicable notification and information duties.

17. Changes

We update this Policy when the product, data flows, recipients or law changes. The current version and date are shown on this page. Material changes will be communicated appropriately.