Privacy Policy

Who is responsible for your data

The controller of the personal data described in this policy, the party the GDPR holds responsible for it, is Juan Gabriel Mazzoleni, based in Argentina, operating as Zoom to Fill. For anything in this policy, write to contact@zoomtofill.com.

Paddle, who run our checkout as merchant of record, are an independent controller of the data they collect from you when you pay; their processing is governed by Paddle's privacy policy.

What stays on your device

Everything you configure stays in your browser's own extension storage: your settings, your per-site preferences, which sites you disabled, your shortcuts, and the state of every panel. Chrome may sync some of it between your own signed-in browsers, using Google's sync rather than any server of ours. None of it is sent to us.

The extension processes video frames locally, on your machine's GPU, to do the cropping, sharpening, motion smoothing and the ambience glow. No frame, screenshot or audio ever leaves your computer, and we have no way of knowing what you were playing.

What the extension downloads

The buttons the extension adds to a video player need to know where that player keeps its controls, and those details change whenever a site redesigns. Rather than waiting for a new extension release, the extension fetches that small description file from our own website: once when it is installed, when Chrome starts, and when you open one of the supported video sites. On any other site it does nothing at all.

The request carries no identifier, no account and nothing about you or the page: it is a plain download of a public file, the same file for every site and every user. The most our server can see is that some connection asked for it at a given time, which is less than any website learns about its own visitors. The file is kept in the extension's storage, so if you are offline the buttons keep working from the last copy. Nothing is uploaded, and turning off the reports described under Analytics does not affect this: there is nothing about you in it to switch off.

What we collect, and only if you buy PRO

On the free extension there is nothing that identifies you: no account, no email, no name (the two reports are described under Analytics, below). When you purchase PRO, we store:

• your email address, which Paddle collects at checkout and passes to us;
• Paddle identifiers for your customer record, your subscription and your transaction;
• the install identifier of the extension your subscription is used from (the same random identifier the daily report below carries). The extension sends it each time it renews its PRO session, so we can read how a paying install actually uses the product, and notice when it has stopped;
• your plan and its state: which plan, whether it is active, trialling, past due or cancelled, and the dates that go with it (trial end, period end, cancellation);
• whether access was revoked and why, where a chargeback, refund or misuse ended it.

We also keep the raw events Paddle sends us about your purchase. These are stored as received, for debugging and for reprocessing a payment that failed to apply, and they contain more than the fields above: typically your email, Paddle's identifiers, the amounts, and the country used for tax.

Card details are collected by Paddle and stay with Paddle. They never reach our systems, so this policy has nothing to say about them beyond that.

Signing in again

If you ask for a link to restore PRO on another device, we hold your email address together with a single-use token and a six-digit code. They expire automatically after fifteen minutes and are deleted once used. We also keep a short-lived counter per email address to rate-limit those requests.

Once activated, your PRO status travels in a signed token stored in your browser. It carries your email, your tier and the relevant dates, and your browser verifies it without contacting us, which is why PRO keeps working offline.

Analytics

There is no analytics SDK and no tracking pixel, in the extension or on this site, and nothing here follows you across the web. What the extension does send is two reports, both of which you can switch off in its settings, under Privacy.

The first is a daily report. Once a day, the extension tells us that this installation is still alive, what it runs on and how much use its features got, and nothing else beyond:

• a random identifier, generated on your own machine the first time the extension runs. It is drawn from nothing: not your account, not your hardware, not your address. It exists so that one installation reporting for a year is not counted as three hundred and sixty-five. If you subscribe to PRO, this identifier is also stored with your subscription (see above), and from then on the report is tied to your account;
• the extension version, the version it last updated from, and how many days ago it was installed, so we know which builds are still in the field and how people move between them;
• your browser and operating system, as families and major versions only (Chrome 125, Windows 11), never build numbers;
• your graphics hardware: the name of the GPU as the browser reports it, whether graphics acceleration is switched on in the browser, and whether WebGPU is available. Every effect the extension sells is decided by these, and they are how we learn on which machines an effect breaks or cannot run;
• your display: its size in pixels, its refresh rate, and whether it is an HDR display. The cropping maths, the motion smoothing and the HDR mode each depend on one of these;
• your interface language and your country;
• feature usage: how much the extension's own features get used, as plain numbers. Never which video, which site, or anything about what was on the screen;
• your subscription tier (free, trial or pro), as a single word.

The country comes from your connection, not from anything you type. Like any server, ours keeps a short-lived network log of the requests it receives.

The second is a site-break report, sent when one of the video players we build a button for changes underneath us: the player's controls keep appearing and our button never lands in them, or a video plays for a while and the extension never recognises it. It names that player (Netflix, YouTube and the other services listed on this site), which of the two things went wrong, the part of our own configuration that stopped matching, and the same version, platform and tier fields as above. It is sent at most once per player per day, and only for the players we explicitly support. It never carries the address of the page, the title of what was playing, or anything else about it.

Neither report can say what you were watching. There are no page addresses, no titles, no frames and no audio in either of them; the only name of a service in them is the one in a site-break report, and only when that service's player broke. Nothing in them is used for advertising or profiling. On the free extension neither can say who you are either; on PRO both are tied to your subscription as described above, and to nothing else. Both are held by Cloudflare's analytics engine and deleted automatically after 90 days.

If you turn the switch off in the extension's settings, both stop immediately. Uninstalling stops them too.

When you uninstall, Chrome opens a short survey page asking why. Answering it is optional. If you do, your answer is stored together with the same random install identifier, so we can read the reason against that install's daily reports (how long it was in use, on which platform, whether one of the supported players had stopped working for it). The survey rows are kept in our database and are not deleted automatically.

Why we may process it

The GDPR requires a legal basis for each use of personal data. Ours, purpose by purpose:

• Providing your PRO subscription: storing your email, plan and purchase identifiers, and issuing the signed token, is performance of a contract (article 6(1)(b)). Without it there is nothing to grant your purchase against.
• Sign-in links: the short-lived token, code and rate-limit counter when you restore PRO on another device are also performance of that contract.
• Keeping payment event records: the raw Paddle events are kept under our legitimate interest (article 6(1)(f)) in debugging failed payments, handling disputes and preventing abuse of the free trial and refund window, and in part under legal obligation (article 6(1)(c)) where tax and accounting rules require the transaction trail.
• The two reports: our legitimate interest in knowing the extension is alive, what it runs on and which of the players we support has stopped working. On the free extension they identify nobody; on PRO, reading them against your subscription is part of providing and improving the service you pay for. The switch that stops them is in the extension's settings, so objecting is one toggle rather than an email.

We do not process personal data based on consent today, so there is no consent to manage.

Where your data comes from

The personal data we hold arrives from Paddle, who collect your email at checkout and send it to us with the purchase events, or from you: when you type your email to request a sign-in link, or when you choose to send us feedback from the extension or from this site.

The site does count its visits, with Cloudflare Web Analytics. It records which pages are viewed, from which country and how fast they load, as aggregate numbers. It sets no cookie, and Cloudflare describes it as fingerprint-free and as storing no IP address.

Cookies

This site sets no tracking or advertising cookies. Paddle's checkout runs in its own overlay and sets what it needs for the payment to work, under Paddle's privacy policy.

Who else handles your data

• Paddle, our merchant of record: checkout, payments, invoicing, tax and refunds. They are the ones who collect your email and payment details in the first place.
• Cloudflare, our infrastructure: this website, our API, the database holding the records above, and the delivery of activation emails.

Both operate globally, so this data can be processed outside the country you live in, including in the United States. Those transfers rest on the safeguards the GDPR accepts: standard contractual clauses and, where the provider is certified, the EU-U.S. Data Privacy Framework. The commitments are published by each provider: Cloudflare's GDPR commitments and Paddle's privacy policy.

We do not sell your data, and we do not share it with anyone for advertising.

How long we keep it

We keep your subscription record and its associated payment events for as long as you have an active plan, and for 24 months after it ends. That window exists because the record can still be needed after the plan is over: card disputes can arrive up to about thirteen months after a charge, and the trial history is what keeps a second free trial from being free. After 24 months an automated job deletes the record and its events.

Paddle keep their own transaction records independently, for as long as their obligations as merchant of record require. Deleting our copy does not delete theirs, and their retention is governed by their policy rather than ours.

Your rights

Over the data we hold about you, you have the right to access it (a copy of everything), rectify it (correct what is wrong), erase it, restrict or object to its processing, and receive it in a portable format. If you are in the EU, the EEA or the UK these are your rights under the GDPR.

Write to pro@zoomtofill.com from the address on the account and we will act on it as the GDPR requires. Note that deleting your record ends PRO access, since that record is what grants it, and that we cannot delete what Paddle hold as merchant of record: for that, contact them directly.

If you believe we have handled your data unlawfully, you also have the right to lodge a complaint with your data protection authority: the supervisory authority of the EU or EEA country where you live or work, or the Information Commissioner's Office in the UK. We would appreciate the chance to fix it first, but nothing requires you to give us one.

No advertising profiles, no automated decisions

We do not build advertising profiles, and no decision with legal or similarly significant effect on you is made by automated means. The only automation touching your record is the billing state machine that mirrors what you and Paddle do.

Children

Zoom to Fill is not directed at children under 16, and we do not knowingly collect data about them. If you believe a child's data reached us through a purchase, write to us and we will remove it.

Changes to this policy

We update this page when what we collect changes, and the date at the top always reflects the current version. If a change means we start collecting something new, this page changes before the collection starts.

Contact

Privacy questions and data requests: contact@zoomtofill.com. Zoom to Fill is operated by Juan Gabriel Mazzoleni, based in Argentina.