AI Video Signal
Editorial

Privacy Policy

Effective date: September 19, 2026. AI Video Signal is primarily a static editorial website and does not require readers to create an account.

Controller and contact

Data controller: AI Video Signal. For direct digital-product sales, the legal operator/seller identity, postal address, tax identifier, commercial email and telephone are published on the Seller & Legal Information page. General privacy enquiries may also be sent through the contact page.

What data we process, why, and the legal basis

  • Editorial site and security: Cloudflare processes ordinary network/request data needed to deliver and protect the site. The purpose is site delivery, availability and abuse prevention. The legal basis is our legitimate interest in operating a secure, reliable website and, where applicable, performance of a requested service.
  • First-party affiliate-click measurement: when you intentionally follow an outbound Direct provider link, the site may send an aggregate event containing page path, merchant, CTA placement, page zone, commercial-intent label, affiliate click reference, destination host, link text and campaign parameters already present in the URL. Our custom dataset is designed not to write IP addresses, user-agent strings, email addresses, account identifiers, cookies or device fingerprints. The purpose is aggregate editorial/commercial performance measurement. The legal basis is our legitimate interest in measuring outbound referral performance without building reader profiles.
  • First-party conversion-funnel measurement: the site may also record aggregate events when a reader opens the AI Video Stack & Cost Audit page, follows an internal link to that service, chooses the Stripe checkout button, chooses the audit contact option or, after server-side Stripe verification, reaches a successfully verified paid-audit state. These events can include page path, CTA placement, page zone, a non-personal target label, destination host, link text and campaign parameters already present in the URL. The verified-payment funnel event does not include the Checkout Session ID. This custom measurement uses the same privacy-minimizing design: no reader cookies, account identifiers, email addresses, device fingerprints, IP fields or user-agent fields are written to the event dataset. The purpose is to measure the service funnel in aggregate and improve page usefulness and conversion flow. The legal basis is our legitimate interest in measuring and improving our own service journey without building reader profiles.
  • Digital-product checkout and fulfilment: Stripe may collect email, billing details, payment-method data and transaction identifiers. AI Video Signal receives only the transaction/order data needed to verify payment, record contractual consent, fulfil the download, support the customer, detect fraud and handle refunds/disputes. The legal bases are performance of the purchase contract, steps requested before entering the contract, compliance with accounting/tax/consumer-law obligations, and legitimate interests in fraud/dispute prevention.
  • Checkout abuse prevention: the checkout endpoint can derive a short-lived pseudonymous HMAC token from the Cloudflare-provided client network address. The raw address is not written to the commerce rate-limit table. The token is used only to count checkout attempts within a short anti-abuse window. The legal basis is our legitimate interest in preventing automated abuse, payment fraud and unnecessary Stripe API traffic.
  • Audit-service checkout, intake and customer support: for the AI Video Stack & Cost Audit, Stripe Checkout collects the purchaser name and can collect an optional business name in addition to the checkout email and payment-related information. If you purchase or enquire about the Audit, you may also provide company or project name, team size, tool and plan names, approximate software spend, workflow information, bottlenecks, goals and other details you choose to include. We use this information to assess scope, perform the service, deliver the written audit, answer questions and handle complaints. We ask clients not to send passwords, full payment-card details or unnecessary sensitive customer data. The legal basis is performance of the service contract, steps requested before entering the contract where relevant, and our legitimate interest in responding to genuine enquiries.

Payment data and order records

Payment is processed through Stripe Checkout. AI Video Signal does not receive your full payment-card number from Stripe. We may retain Checkout Session ID, PaymentIntent/charge identifiers, customer email, amount/currency, consent and pre-contract information versions/timestamps, fulfilment or service status, refund/dispute state and related order-support records where needed for a direct purchase. For the AI Video Stack & Cost Audit, the verified post-payment page can also generate a downloadable service order confirmation for the purchaser containing the service, payment reference, amount, seller details, scope and contractual links. Stripe can append the completed Checkout Session ID to the first-party post-payment URL. The browser sends that identifier to a first-party verification endpoint solely to confirm that the session matches the expected live Payment Link, amount/currency and price and that the payment is not refunded or disputed. The Checkout Session ID is not added to the aggregate service-funnel event payload; after a successful browser-side verification, the page removes the session identifier from the visible URL without reloading where the browser supports History API replacement. Digital-product records can be stored in Cloudflare D1 and updated from verified Stripe webhook events; download authorization is re-checked before a protected file is released.

Recipients and service providers

Data may be processed by service providers strictly as needed for the functions described above, principally Cloudflare for hosting, security, Worker/D1 infrastructure and aggregate event storage, and Stripe for checkout, payment processing, tax features, fraud controls, receipts, refunds and disputes. If you choose an affiliate/provider link, the relevant merchant or affiliate network receives the referral request under its own terms and privacy notice.

International processing

Cloudflare, Stripe and external merchants/networks may process data in more than one country. Where personal data are transferred outside the European Economic Area, the applicable provider is responsible for using a lawful transfer mechanism and safeguards required for its processing. Their current privacy documentation should be consulted for the exact locations and transfer framework that apply to your transaction or visit.

Retention

  • Order, tax and accounting records: retained for the period required by applicable accounting, tax, consumer-protection and limitation rules, then deleted or anonymised where appropriate.
  • Fraud, refund and dispute records: retained while reasonably needed to administer the payment, chargeback/refund process and related legal claims.
  • Audit intake and service-delivery records: retained while reasonably needed to perform the agreed audit, provide support, document delivery and handle legitimate accounting, dispute or legal requirements, then deleted or anonymised where appropriate.
  • Checkout rate-limit buckets: used only for the active anti-abuse window. The Worker ignores expired buckets and purges old rows opportunistically; these pseudonymous tokens are not used for marketing or reader profiling.
  • Aggregate click and service-funnel measurement: retained only while reasonably useful for measuring editorial/referral and service-funnel performance and reviewed periodically; the custom dataset is designed without direct reader identifiers.
  • Support correspondence: retained while needed to resolve the request and for any related contractual/legal recordkeeping.

Your GDPR rights

Where the GDPR applies, you may request access to your personal data, rectification, erasure, restriction of processing, objection to processing based on legitimate interests, and data portability where the legal conditions are met. Where processing is based on consent, you may withdraw that consent for future processing without affecting prior lawfulness.

To exercise a right, use the contact details on Seller & Legal Information or the contact page. We may need enough information to verify that a request relates to you before disclosing order data.

You also have the right to lodge a complaint with a competent supervisory authority. In Spain, this is the Agencia Española de Protección de Datos (AEPD).

Automated decisions and profiling

AI Video Signal does not use the first-party aggregate click and service-funnel dataset to make decisions producing legal or similarly significant effects about individual readers. Stripe may apply its own automated fraud/risk systems under Stripe's privacy terms.

Direct provider links and referral tracking

Some articles contain Direct provider links. When you click one, the URL may route through an affiliate network or provider tracking domain so the referral can be attributed to AI Video Signal. For example, some FlexClip links can route through Awin. Those third parties may process referral identifiers and may use cookies or similar technologies under their own privacy policies.

AI Video Signal does not currently load an Awin tracking script on page load. Referral routing occurs only when a reader chooses to follow an applicable outbound link.

Cookies, additional analytics and advertising

The current first-party affiliate-click and service-funnel measurement described above is designed without reader cookies or direct identifiers. If AI Video Signal later enables additional analytics, advertising pixels, embedded tracking scripts or other technologies that materially change the information collected directly on the site, this policy and any legally required consent controls must be reviewed before activation.

Changes to this notice

We may update this notice when the site's data flows, providers or legal obligations change. The effective date at the top identifies the current version.