LegalPrivacy Policy
This policy explains what personal data VODPilot processes, on which legal basis, how long it is kept, which third parties receive it, and which rights you have under the GDPR.
Last updated: November 20, 2026
1. Controller
The controller for VODPilot’s own processing described in this policy, including its optional viewer chat-game service, is Michael Ketzer, Rotkehlchenweg 51, 40789 Monheim am Rhein, Germany. VODPilot is operated by Michael Ketzer. Processing on behalf of business customers is distinguished in section 16. You can reach us at
support@vodpilot.com.
2. Data protection officer
A separate data protection officer has not currently been designated.
3. Categories and sources of personal data
- Account data such as email address, account identifiers, session information, sign-in verification data, and the version and time of Terms acceptance.
- Workspace and service data such as member roles, channel connections, stream session records, VOD metadata, review status, and storage usage.
- Optional viewer game data such as Twitch user ID, participation status, game-notice version and acknowledgement time, balance, collection items, game history, cooldowns, daily usage and necessary activity timestamps. Stake-game history also includes the stake, multiplier and outcome. Pending game replies briefly contain the current Twitch chat name; the game does not store raw chat transcripts or a username history.
- Twitch API data such as connected channel IDs, logins, display names, avatar URLs, stream and channel status, titles, categories, tags, VOD metadata, muted-segment information, stream keys for replay playout, chat command/message data, EventSub delivery records, token metadata, scopes, expiry information, and connection audit logs.
- Uploaded and processed content data such as media files, thumbnails, object-storage keys, file names, metadata, categories, titles, timestamps, review notes, processing status, and related technical identifiers.
- Payment and subscription data such as Paddle customer IDs, invoices, subscription status, transaction references, and billing period records.
- Cancellation, withdrawal, report, rights-complaint, and legal-request data submitted through VODPilot forms or support channels.
- Communication data when you contact support.
- Security, audit, and abuse-prevention data such as IP-derived request information, logs, device and browser information, authentication events, upload events, moderation decisions, abuse reports, enforcement records, and evidence needed to investigate suspected misuse.
- AI-assisted metadata cleanup inputs and outputs, such as stream titles sent to Google Gemini when title cleaning is configured.
- Referral program data, including keyed hashes of billing identities of every paying customer, as described in section 6c.
- Affiliate commission data, as described in section 6d.
- We collect personal data directly from you, from connected services such as Twitch, and from payment-related events sent by Paddle.
4. Purposes and legal bases
- Account creation, authentication, connected-channel management, subscription handling, and service delivery are processed under Art. 6(1)(b) GDPR.
- Recording which Terms version you accepted and when is processed under Art. 6(1)(b) GDPR to administer the contractual relationship and under Art. 6(1)(f) GDPR based on our legitimate interest in documenting the applicable agreement.
- The optional viewer chat-game service is processed under Art. 6(1)(f) GDPR. Our legitimate interest is providing a reliable, voluntary, non-monetary game, maintaining points and collections, enforcing cooldowns and daily limits, and preventing duplicate or delayed actions. Notice version and acknowledgement time document which game notice was shown when a viewer explicitly joined. Joining is a participation control, not GDPR consent. You may object on grounds relating to your particular situation by contacting support@vodpilot.com.
- Tax, accounting, invoicing, and mandatory record-keeping are processed under Art. 6(1)(c) GDPR.
- Cancellation handling, withdrawal handling, and legally required consumer communications are processed under Art. 6(1)(b) and Art. 6(1)(c) GDPR.
- IT security, fraud prevention, abuse prevention, content-safety enforcement, illegal-content investigation, evidence preservation, service stability, and support handling are processed under Art. 6(1)(f) GDPR based on our legitimate interest in operating VODPilot securely and reliably and protecting users, third parties, rights holders, connected providers, and the public.
- The legal bases for the referral program are set out in section 6c.
- Calculating and paying commissions to partners for workspaces they introduced is processed under Art. 6(1)(f) GDPR, and recording commission payments under Art. 6(1)(c) GDPR (section 6d).
- Where processing or disclosure is necessary to comply with legal obligations, lawful requests, court orders, regulator requests, or legally required reports, the legal basis is Art. 6(1)(c) GDPR.
- Where processing is necessary to establish, exercise, or defend legal claims, the legal basis is Art. 6(1)(f) GDPR. If special categories of data or data relating to alleged offences are involved, we process that data only where necessary and permitted by applicable law.
- If we request consent for a specific processing activity, the legal basis is Art. 6(1)(a) GDPR. Consent can be withdrawn at any time for the future.
5. Recipients and processors
- Vercel: retained compatibility hosting and custom-domain integration.
- OVHcloud: production web hosting, workers, schedules, and our self-managed PostgreSQL database. The PostgreSQL database is hosted in Germany.
- Paddle: payments, subscriptions, invoicing, and refund handling.
- Letterpier: transactional email delivery such as sign-in codes.
- Twitch: OAuth account connection, Twitch API calls, EventSub webhooks, channel identity data, stream state, replay-channel actions, and public preview images loaded from static-cdn.jtvnw.net.
- Cloudflare R2: object storage for media-related files.
- Pusher: realtime operational events used for playout and worker coordination.
- Google Gemini: optional AI-assisted title cleanup for stream metadata when configured.
- Competent authorities, law enforcement, courts, regulators, child-protection organizations, abuse-reporting hotlines, legal advisers, rights holders, and affected platform providers where necessary and permitted for illegal-content reports, safety escalations, rights complaints, legal claims, or compliance with law.
6. Twitch connections and API data
- Twitch sign-in may use the user:read:email permission so VODPilot can authenticate your account and keep the account email current.
- When you connect a main channel for tracking, VODPilot stores channel identity data and creates EventSub subscriptions for stream.online, stream.offline, and channel.update events. The main channel connection is used to detect live/offline state and channel metadata; replay automation is not performed on the main channel.
- When you connect a replay channel, VODPilot requests the permissions needed for replay playout and automation: channel:manage:broadcast, channel:read:stream_key, user:read:chat, user:write:chat, channel:bot, user:bot, and moderator:manage:chat_messages. If you enable optional raid, ad-break, or replay-vote features, VODPilot may also request channel:manage:raids, channel:edit:commercial, channel:manage:polls, or moderator:manage:announcements.
- VODPilot may use the replay-channel permissions to fetch the stream key for playout, update replay title/category/tags, send, announce, and pin chat messages, read chat events needed for commands, start commercials when enabled, create Twitch polls when replay voting is enabled, and raid the main channel when the optional raid feature is enabled.
- Connected Twitch tokens, scopes, expiry data, validation timestamps, EventSub subscription records, and related audit logs are stored so VODPilot can operate the connection, validate it at least hourly where required by Twitch, detect revoked tokens, and ask you to reconnect when needed.
- Disconnecting a Twitch channel removes local access/refresh tokens and related EventSub subscriptions from active use. Some audit logs, backups, security records, or legal-report evidence may be preserved for the limited retention purposes described in this policy.
- The public VODPilot homepage embeds public Twitch preview images for showcased channels from static-cdn.jtvnw.net. When those images load, your browser may contact Twitch's CDN directly.
6a. Optional VODPilot viewer games
- VODPilot offers the optional game service directly to viewers and determines its game-data purposes, data scope, retention rules and privacy controls. Channel operators configure game rules, point names and game messages within those service limits. A streamer’s name or private contact address is not used as the game-service privacy contact.
- Normal chat alone does not create a game account. Read the game rules and central privacy notice on the channel’s VODPilot game page before joining with !play. Existing participants under the previous channel-specific notice must use !play again before earning more points or playing games under the VODPilot service notice.
- Twitch supplies the user ID and chat events used for game commands and eligible point earning. Game replies and balances that viewers request with !points are public in Twitch chat, including to channel operators and moderators. Twitch’s own processing and a channel operator’s independent chat use or moderation remain separate from VODPilot’s stored game account.
- OVHcloud provides production application hosting, and we operate the game database on OVHcloud servers in Germany. Vercel remains available for compatibility hosting and custom-domain integration. Twitch carries the public chat and authenticates private viewer-data access. The international-transfer information in section 7 also applies to these providers. Contact VODPilot for further information about the applicable provider and transfer arrangements.
- Use !play leave to stop participating; this does not immediately delete the stored game account. To delete your game account, send !forgetme, then confirm with !yes from the same viewer account in the same channel within 2 minutes. After that, the request expires; start again with !forgetme. You can also confirm with !forgetme confirm. The channel’s private viewer area also provides access, export, leave and deletion after a separate Twitch sign-in, without a VODPilot subscription or customer account.
- VODPilot handles game-data access, correction, deletion, restriction, portability where applicable, objection and broader game support requests centrally at support@vodpilot.com. Self-service controls cover the selected channel’s game account; contact us for game data in other channels or related support records. VODPilot game deletion does not remove independent Twitch chat records.
6b. Website measurement
- We count visits and start/sign-in clicks on selected public pages to understand which guides and sources are useful. The analytics records contain daily totals by an approved page path and a fixed source category, such as Google, YouTube, or Twitch. They do not store IP addresses, browser fingerprints, full referring URLs, arbitrary campaign text, email addresses, or persistent visitor identifiers. These are event counts, not counts of unique people. Normal security and hosting logs remain separate.
- Website measurement respects browser Do Not Track and Global Privacy Control signals. Anonymous counters use no analytics cookies, localStorage, or sessionStorage. A random identifier for each event prevents duplicate delivery and is removed after 24 hours; it does not identify a visitor across page loads.
- These counts are not linked to your account or workspace, and we do not record which page or source led you to sign up. Separately, to understand how new workspaces progress, we note when a workspace first starts a checkout (with a one-way hash of the payment provider's transaction ID) and when its first public replay is observed, and combine these with existing connection, import and invoice records in aggregate internal reports. These milestones are deleted with the workspace; other operational records follow the service retention periods described in this policy. The public viewer counter publishes aggregate concurrent audiences and does not identify visitors.
6c. Referral program
- Workspace owners who pay for VODPilot can share a personal referral link with creators they know. An invited creator who applies the link to their own workspace before their first payment gets a referral welcome; the inviting creator gets a referral discount while the invited creator keeps paying. The conditions are in the Referral Program Terms.
- Referral links: the link code and the inviting workspace; when the link was created and when it stopped working (reset by the inviting creator or disabled by VODPilot); whether the inviting creator chose to show their channel name on the invite page and, if so, the Twitch channel ID it was turned on for; and whether the inviting workspace’s participation is suspended and why. The name is shown only if the inviting creator opted in and their own Twitch account is the workspace’s main channel; this is checked again each time the page is shown, and the inviting creator can turn it off at any time. Anyone who opens a referral link can see whether it currently works. A link stops working while the inviting workspace has no active subscription, its participation is suspended or its owner has not accepted the current terms.
- Referral records: which workspace invited which, and through which referral link; whether the link was opened or its code typed in; the dates of applying, the first payment, qualification and the end of the referral welcome; the referral’s standing, the state of the welcome, and review or block reasons; the discount amounts on both sides; Paddle discount, subscription, transaction and adjustment (refund, chargeback and chargeback-warning) IDs; each time the inviting workspace’s referral discount is changed, which referrals counted then and the Paddle subscription status of each; the version of the program terms each side accepted, when, and a fingerprint (SHA-256) of that version’s text; if the check when the link was applied found a match, which kinds of detail matched (for example the email address or a Twitch channel, and whether they matched the inviting workspace or another customer), never the matched values themselves; and the member IDs of both workspaces when the link was applied. If an invited creator leaves the program, the referral record is deleted. The referral event log still shows, by workspace and link ID, which workspace applied which referral link, which workspace had shared it, whether it had paid, and when it left the program; a workspace that paid with a referral cannot apply another after leaving. We keep that event log and the discount history (IDs, amounts and the statuses on which they were based) for the retention period below, to document the discounts granted and to establish, exercise or defend legal claims.
- Billed-identity hashes of all paying customers: for every workspace that has paid for VODPilot, whether or not it takes part in the program, we store keyed one-way hashes (HMAC-SHA256 with a secret key) of the owner’s Twitch account ID, the workspace’s connected Twitch channel IDs, the owner’s email address in normalized form (lower case, without “+” suffixes and, for Gmail, without dots), the tax ID and the invoice address (country, postal code and first address line). With each hash we store the workspace ID, the dates of the workspace’s first and last payment, and when we last checked it; with the tax ID and invoice address hashes we also store Paddle’s reference to the address or business record they came from, but only while the workspace has a subscription that has not been canceled. These hashes are pseudonymised personal data: the original values cannot be read from them, but we can check whether a given value matches one. We use them only to prevent self-referral and repeated use of new-customer referral offers, never for marketing, other offers or decisions about your VODPilot account. The secret key is kept in our hosts’ configuration, separately from the database.
- Payment-card comparison: at an invited workspace’s first payment, we compare the payment-card details Paddle holds for it (card type, last four digits and expiry date) with those of the latest payment of each other subscription that has not been canceled. The comparison happens in memory; the card details are not stored.
- Checks and reviews: when a referral link is applied, at checkout, at the first payment, before a referral starts counting, before each of the inviting creator’s renewals, and in our hourly checks while the referral exists, we check whether the invited workspace is a new customer and not the inviting creator’s own or a related workspace (as the Referral Program Terms define these), whether payments were refunded or charged back or a card issuer warned of possible fraud, and whether the two workspaces share team members or a team member owns another paid workspace (these two team checks affect only whether the referral counts for the inviting creator). When a referral link is applied, a match does not refuse the link: the referral is created under review by a person, and the referral welcome is paused until that review (section 13). At the later checks, a match puts the referral under review by a person; some matches also pause the referral welcome (section 13). A referral is also reviewed if either workspace is linked to an affiliate commission (section 6d). Our administrators can also put a referral under review by hand, and pause the referral welcome, when there are concrete indications, for example from a report, that the invited workspace may not be a new customer or may be a self-referral.
- Legal bases. Art. 6(1)(b) GDPR: taking part as an inviting creator under part A of the Referral Program Terms (your link, your participation record, your referral discount, the copy of the accepted terms we email you, and showing your channel name if you choose to); and the invited creator’s referral welcome under part B, which the invited creator accepts when applying the referral link, including the order confirmation or the email with the welcome conditions, and the reminder about its end. Art. 6(1)(c) GDPR: keeping the discount history, and the referral events that set, withhold, end or correct a discount, as records relevant for tax purposes under § 147 of the German Fiscal Code (AO), for which we apply the 8-year period for accounting vouchers (Buchungsbelege). Art. 6(1)(f) GDPR: (1) using the invited workspace’s subscription, refund and chargeback status to calculate the inviting creator’s referral discount, and showing the inviting creator the two numbers described below; our legitimate interest, and the inviting creator’s, is a referral discount they can follow. (2) The eligibility and misuse checks, the payment-card comparison and the billed-identity hashes of all paying customers; our legitimate interest is preventing self-referral and repeated use of new-customer offers, and preventing fraud is recognized as a legitimate interest (Recital 47 GDPR). (3) Keeping the other referral events and our administrators’ actions on referrals, and keeping the referral records for any part of that period that tax law does not require, to document the discounts granted and the decisions behind them and to establish, exercise or defend legal claims. Weighing of interests: for the checks and hashes we took into account that they use only identifiers we already hold, that you enter at checkout or that Paddle holds for your subscription, and no special categories of data; that other customers’ identifiers are kept only as keyed hashes, used for nothing but these checks and deleted 24 months after the last payment, in line with the definition of a new customer in the Referral Program Terms; that a match affects only the referral welcome or referral discount, never your access to VODPilot, and that a person reviews every match, pause and block, also a match found when a referral link is applied (section 13); and that customers can reasonably expect a provider to stop new-customer offers from being claimed again. For the two numbers we took into account that the inviting creator sees numbers, never names; that the invited creator is told before applying what the inviting creator can infer from them; and that you can object (see the notice after this section).
- What the inviting creator sees: their own referral link; two numbers, namely how many workspaces currently hold a referral from their link (a workspace drops out of this number if it removes the referral, leaves the program, has the referral withdrawn or is deleted) and how many of them currently count toward their discount; and their referral discount as set for each of their renewals. They are never shown which workspaces these are, or the invited creator’s name, email address, channel, workspace, payment dates, or review or refund state. With few referrals, they can infer some of this from the numbers. The invited creator is told so before applying: “The creator who invited you sees two numbers: how many workspaces currently hold a referral from their link, and how many of them count toward their discount right now. They are not shown which workspaces these are. But if you are the only one, or one of only a few, with a referral from their link, they can tell that you applied it; from changes in the second number, when your workspace starts or stops counting; and, if the first number goes down, that you removed the referral, left the referral program or deleted your workspace. A workspace stops counting, for example, if a payment fails, the subscription is paused or canceled, a refund is requested, or we are checking the referral. They are not told why.”
- Recipients: Paddle, our reseller and merchant of record, which acts as a separate controller for the payments it processes, receives the referral discounts on the subscriptions on both sides and shows them on its invoices; we read the card and billing details for the checks above from Paddle. Our email provider sends the copy of the accepted terms, the order confirmation, the email with the welcome conditions and the welcome reminder, and our hosting providers process referral data on our behalf (section 5). The inviting creator sees the two numbers described above. Other participants learn nothing about you beyond what this section describes.
- Carrying the referral code through sign-in: when you open a referral link and then sign in, the code travels in the return address and in the existing sign-in callback cookie. This is strictly necessary to provide the sign-up you requested (§ 25(2) No. 2 TDDDG; see section 10). The code is stored with your workspace only when you click Apply.
- Leaving the program: as an invited creator, you can remove the referral in Settings → Referrals before your first payment, or use “Leave the referral program” there afterwards. Leaving ends the referral welcome from your next renewal, and your workspace cannot apply another referral link. Inviting creators can leave by writing to support@vodpilot.com (Referral Program Terms, A11). Anyone can make a request under section 11 about referral data, including former customers about their billed-identity hashes, at the same address. How to object is set out in the notice after this section.
- Retention: participation records (enrollment, the accepted terms version and its fingerprint, and any suspension), referral links, referral records and discount settings are kept as long as the workspaces they belong to. Entries about referral actions in our general audit log are deleted after 30 days. A referral link that stopped working is deleted 90 days later if no current referral came through it. Records of failed attempts to apply a referral link are deleted after 90 days. The discount history, and the referral events that set, withhold, end or correct a discount (checkout welcomes and skipped welcomes, first payments, qualification, reviews and manual flags with their outcome, blocks and their removal, revocations and reinstatements, leaving and withdrawals, reopened entries, partial refunds and the welcome-ending reminder), document the prices invoiced and are relevant for tax purposes: we keep them until the end of the eighth calendar year after the year in which they were written (we apply the 8-year period for accounting vouchers, § 147(1), (3) and (4) AO). Other referral events, and discount settings that were only simulated and never sent to Paddle, are kept until the end of the third calendar year after the year in which they were written (the civil limitation period, §§ 195 and 199 BGB). Records of our administrators’ actions on referrals (which administrator acted, when, and the IDs of the referral, workspaces and referral link concerned) are kept in our admin activity log, also after the referral record itself has been deleted: 8 years for the actions that clear a review, flag a referral, set or remove a block, revoke or reinstate a referral, withdraw it, record a partial refund or reopen the entry window, 3 years for the others. One exception: the latest record of a referral discount that is still in place on a subscription that has not been canceled is kept for as long as that discount remains in place; once the discount is removed or the subscription ends, it is deleted under the same rules. Billed-identity hashes are kept for 24 months after the workspace’s last payment, also after the workspace is deleted, because the Referral Program Terms define a new customer by reference to payments in the previous 24 months.
Your right to object to referral processing (Art. 21 GDPR)
Where section 6c relies on Art. 6(1)(f) GDPR, you can object at any time, on grounds relating to your particular situation, by writing to
support@vodpilot.com. We then stop that processing unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or need it to establish, exercise or defend legal claims. If you are an invited creator and object to being included in the inviting creator’s two numbers, we assess your objection and tell you the outcome; an objection never ends your referral welcome. Because the checks against misuse are a condition of the new-customer offers, we generally continue them while you hold a referral; if you do not want them, you can leave the program (section 6c). If you do not take part in the program, we assess an objection to your billed-identity hashes individually and tell you the result; if your workspace has been deleted, we delete them unless our interest in preventing repeated use of new-customer offers overrides yours (for example while a review concerning your workspace is open).
6d. Affiliate commissions
- VODPilot pays some partners a cash commission for workspaces they introduced. For this, our administrators can link a workspace to the partner’s VODPilot user account. We use the workspace’s subscription status, plan and extra storage to calculate the partner’s commission. The link is removed when the workspace or the partner’s account is deleted.
- Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is calculating and paying the commissions we agreed with partners. Commission payments are recorded under Art. 6(1)(c) GDPR for tax and accounting.
- A workspace that is linked to an affiliate commission and also takes part in the referral program is reviewed by a person before its referral counts (section 6c).
7. International transfers
Some of the providers used by VODPilot may process personal data outside the EU or EEA, including in the United Kingdom and the United States. Where a recipient is located in a country without an adequacy decision, transfers are intended to be based on appropriate safeguards such as the European Commission’s Standard Contractual Clauses, together with any supplementary measures offered by the relevant provider.
8. Retention periods
- Account and workspace data is generally kept for the duration of the customer relationship and then for up to three years for defence against legal claims, unless longer retention is legally required.
- Terms acceptance records may be retained for the duration of the contractual relationship and the applicable limitation period so we can document which terms governed the relationship.
- Billing, invoice, and tax-relevant records are retained for the statutory retention period, generally up to ten years.
- Commercial and support correspondence may be retained for up to six years where required by commercial or tax law, otherwise for as long as necessary to handle the request and any follow-up.
- Verification codes are retained only until expiry or use.
- Referral program records follow the retention periods in section 6c.
- Viewer game accounts are scheduled for deletion after 90 days without qualifying activity; individual game records after 30 days. Unsent game replies expire after one minute. Duplicate-event identifiers and pseudonymous participation-stop records are kept for 20 minutes. Expired game data is removed by the scheduled cleanup, which runs every five minutes. Private game exports are generated on request and are not stored as files.
- Deleted production game data may remain in backups for a limited period until regular backup rotation. The limited security, legal and evidence-preservation exceptions described in this policy also apply where necessary; they do not change the normal game-account retention periods.
- Connected-service data and stored content are retained until deletion, disconnection, account closure, or expiry of any mandatory retention obligations. Twitch disconnection removes local access/refresh tokens and related EventSub subscriptions from active use, subject to backup, security-log, legal-report, and statutory retention limits.
- Security logs, audit records, moderation records, abuse reports, enforcement history, and evidence related to suspected illegal activity, prohibited content, fraud, rights infringement, or service abuse may be retained for as long as necessary to investigate, prevent repeat abuse, cooperate with competent authorities, comply with legal obligations, or establish, exercise, or defend legal claims.
- Content that is disabled or deleted from normal product access may still be preserved in backups, logs, evidence stores, or authority reports for the limited purposes described in this policy.
9. Provision of data
Providing personal data is necessary where it is required to create an account, authenticate you, connect third-party services, process subscriptions, or provide support. If required data is not provided, VODPilot may not be able to conclude or perform the contract.
10. Cookies and similar technologies
VODPilot uses essential technologies required for authentication, security, fraud prevention, workspace selection, upload progress, import indicators, dismissed notices, and session continuity. These may include HTTP-only session cookies, OAuth state cookies, localStorage, and sessionStorage. The private viewer-game area uses a necessary, short-lived session cookie valid for up to 10 minutes. The anonymous page and click counters described in section 6b do not use cookies or other browser storage. Public Twitch preview images on the homepage are loaded from Twitch's CDN and may create a direct browser request to Twitch. We do not currently describe optional marketing or advertising cookies because they are not part of the present implementation.
11. Your rights
- You may request access to your personal data.
- You may request correction or deletion where applicable.
- You may request restriction of processing or object to certain processing.
- You may request data portability where applicable.
- You may withdraw consent at any time where processing is based on consent.
- Some requests may be limited where necessary to protect other people, prevent abuse, preserve evidence, comply with legal obligations, or avoid interfering with an investigation or legal claim.
- You may lodge a complaint with a competent data protection authority.
12. Supervisory authority
13. Automated decision-making
- Apart from the referral checks below, VODPilot does not make decisions based solely on automated processing, including profiling, within the meaning of Art. 22 GDPR.
- What is checked. When a referral link is applied, at checkout, after the first payment and regularly while a referral exists, our system compares the invited workspace with the inviting workspace and with our records of paying customers (section 6c). It looks only for exact matches, after normalization, of: the owner’s user account; the owner’s email address; the owner’s Twitch account and the workspace’s Twitch channels; another workspace of the same owner that has or had a subscription; the Paddle customer account; the tax ID and invoice address (country, postal code and first address line); and, after the first payment, the payment card (type, last four digits and expiry date). It also checks for chargebacks and for fraud warnings from card issuers that Paddle passes on. There is no scoring and no profiling: one match is enough, and nothing else about you is evaluated.
- What follows from a match. Whether the match is found when you apply a referral link, at checkout or later, the referral welcome is paused until a person has reviewed the match: within 2 business days if it happens before your first payment, otherwise before your next invoice. A match when you apply does not refuse the link: the referral is recorded under review, together with the kinds of detail that matched (never the values). If you check out before that review, your first invoice may be charged without the welcome. If the review finds that the match does not hold up, the referral link applies to your workspace as normal. If it confirms the match, the referral welcome ends (Referral Program Terms, B5); you can still use and subscribe to VODPilot at the regular price. For the inviting creator, a referral under review does not count toward their referral discount until a person has reviewed it (Referral Program Terms, A7). A match is not an accusation: a shared office or apartment-building address, or a card used in one household, can cause one. That is why a person decides.
- Legal basis and safeguards. These decisions are necessary for entering into and performing the referral welcome and the referral discount agreed under the Referral Program Terms (Art. 22(2)(a) GDPR). You have the right to obtain human intervention, to express your point of view and to contest the decision (Art. 22(3) GDPR); write to support@vodpilot.com with your workspace name. A person reviews every pause and can end it, including a pause after a match found when you apply a referral link; you can express your point of view and contest the result. If a pause is cleared, it ends and we refund the amounts you missed, including the VAT charged on them.
- Blocks that end a referral or a referral welcome are always decided by a person.
14. Security
We use reasonable technical and organizational measures to protect personal data, including access controls and operational safeguards for media storage, authentication, logs, and support access. No internet-based service can guarantee absolute security, but we aim to minimize unauthorized access, loss, misuse, and alteration.
15. Changes to this policy
We may update this privacy policy when the product, legal requirements, or third-party processing arrangements change. The current version is always the one published on this page.
16. Business customer DPA
Where VODPilot processes personal data on behalf of a business customer, the
Data Processing Addendum describes processor obligations, sub-processors, assistance, deletion, and audit handling. It continues to apply to customer-directed media, workspace and connected-channel processing within its scope. VODPilot’s own optional viewer-game processing described in section 6a is carried out as controller and is outside that processor scope. This does not remove a channel operator’s obligations for their own independent processing or channel activity.