Privacy

This website

The site is static pages. It sets no cookies unless you allow analytics cookies (below), shows no advertising and embeds no social media trackers. The host keeps ordinary access logs, with IP addresses, for a short time for security. Signing in talks only to the account provider and the licence server, and to Google if you sign in with it.

• Visitor counting

  Daily totals only, with no cookies and nothing stored in your browser. Each page sends the licence server one short note: which page, whether you came from another site (its name, such as google.com, never the address), whether the screen is a phone, tablet or computer, and how long the page took to load. The server adds one to that day's totals, plus your country for an arrival, and keeps nothing else: no address, no identifier. The note passes only through the access logs above and is shared with no one. The admin pages send nothing.

• Cloudflare Web Analytics

  The public pages also use Cloudflare Web Analytics, from Cloudflare, which hosts this site. It counts page views, the site a visitor came from, their country, browser and type of device, and how fast pages load. It sets no cookies, stores nothing in your browser and does not use your IP address to recognise you. It is not used on the account, sign-in, checkout or admin pages.

• Analytics cookies (Google Analytics)

  Nothing from Google loads, and no cookie is set, unless you press Allow. If you do, Google Analytics sets the cookies _ga and _ga_…, which tell a returning browser from a new one for up to 13 months, and records the pages you open, where you came from, your approximate location from your IP address (the address itself is not stored), your device and browser, and when you press Buy. It is used only to see which pages lead to a sale. Advertising features, ad personalisation and Google signals are off. Google may process the data in the United States. It never loads on the account, sign-in, checkout or admin pages. Change your answer any time with Cookie settings at the foot of any page; declining removes the cookies.

• What your browser keeps (not cookies)

  • Your sign-in session.
  • Your email address and whether you own Ball Tracer, which only decide what the menu shows.
  • If you have used the chat, that conversation's ID and secret key, so you can come back to it, and whether you already gave an email address (a yes or no, never the address).
  • After you pay, Paddle's order reference, until it is attached to your account or two days have passed.
  • While you sign in, the page to return to, in that tab only.
  • Your answer to the analytics cookies question, for up to 13 months.

  Signing out removes the first two.

• The Will it run on my machine? check

  It asks your browser for your graphics card's name to show it to you. The name and your answers stay in your browser.

Your account

Buying and downloading need an account. The account provider keeps your email address and your password if you set one, or, if you sign in with Google, what Google shares, such as your name and email address. Messages about your account — confirming your address, resetting a password — are sent by email. Your licence key never is.

• How licences are matched to you

  By the email address on your account. Asking for a licence from your account page, possible only before the store opens, keeps a record of the request: your email address and the date.

When you buy

Payment is taken by Paddle.com Market Ltd as the reseller. Your card details go to them and never reach this site. They keep what they need for payment and tax under their own privacy policy. The checkout opens with your account's email address already filled in; that is the one thing this site passes to them. When you press Buy, your browser loads the checkout from Paddle's servers, which see your IP address like any website.

• What is kept from the order

  • The email address you gave at the checkout, even when the order is attached to an account with another address, so a receipt can always be matched to its licence.
  • Paddle's order reference, the date, and what you bought: the licence, how many computers it activates, and when your included updates end.
  • Whether the order was refunded or charged back.

  No country, postal address or name is kept here. Paddle works out the tax and keeps that information.

• What the licence server keeps

  • Your licence key, encrypted, so your account page can show it again. The key that decrypts it is not in the same database.
  • Which account the order belongs to, and when it was attached to it.
  • A note of that attachment for support: the account, the first characters of the key and the checkout address. These notes are deleted after a year.
• Refunds, and how long orders are kept

  A refunded key is kept, marked as revoked, so it cannot be used again. The order record is kept for as long as the licence exists, plus whatever period tax law requires: up to seven years after the sale.

When you download

Pressing Download asks the licence server for a link that works for five minutes. The link carries no email address and nothing that could activate the plug-in. Each link is logged with when it was made, the installer version, the licence, and a keyed hash of your IP address, never the address itself. The log is deleted after 180 days; it shows when a licence's links are being passed around.

• What a keyed hash means

  A one-way code made from the address and a secret kept only on the server. It cannot be turned back into the address without that secret.

When you activate the plug-in

Activating or re-checking a licence sends the licence server your licence key, a machine fingerprint, the plug-in version and the host program it runs in. Your IP address arrives with any internet request; it is stored only as a keyed hash.

• The machine fingerprint

  A one-way hash built from identifiers on your computer. It cannot be turned back into them, and it identifies the computer only to count activations.

• What activation never sends

  • Your footage, frames, project file or timeline.
  • File names or folder paths.
  • Your name, your email address or anything you typed into Resolve or Premiere Pro.
• How long activation records are kept

  While the licence is active, so activations can be counted and released. To stop abuse, requests are counted per hashed address a minute at a time, and the counts are cleared every night. Server request logs are kept for three days and then deleted.

The AI Ball Finder

The AI Ball Finder looks for the ball on your own computer. Ball Tracer sends nothing from it: no footage, frames or results.

• Microsoft DirectML

  It runs on your graphics card through Microsoft DirectML, installed with the plug-in. DirectML's licence says it may collect information about its use and send it to Microsoft, under Microsoft's privacy statement. Ball Tracer does not receive it.

Diagnostics in the plug-ins

The Ball Tracer plug-ins for Premiere Pro and DaVinci Resolve can send diagnostics, linked to your licence, used only to find and fix bugs, help you faster when you write in, and improve Ball Tracer. Each time you press Trace Ball, the plug-in asks until you tick Don't show me again:

Help improve Ball Tracer? Send diagnostics - errors, trace results, performance and hardware info, linked to your licence so we can help you faster. Never your footage, file names or personal details. You can change this anytime.

Nothing is collected or sent unless you choose Yes. No, or closing the question, keeps it off. Your answer sets the Send diagnostics box on every Ball Tracer effect, in the plug-in's Support section, where you can change it any time. If you said yes before diagnostics were linked to licences, the plug-in asks you once more, and nothing is linked until you have seen this wording.

• What is collected, only after Yes

  • Errors and crashes: a short fixed code for what went wrong (for example that a trace could not start), the plug-in version, the host program and its version, and your operating system's main version only (for example Windows 10.0, release 26200, or macOS 14.5).
  • Trace results, per Trace press:
    • The trace: how many frames the ball was seen on and how many were filled in (and how), how far the drawn flight misses where the ball was seen, whether the ball was seen coming down, how many frames the flight takes from impact to landing, how long the trace took, and why a trace was refused.
    • The landing: whether it was found, estimated or not found, how wide the estimate's range is, and where the drawn landing sits against the picture's horizon and how sure the plug-in was of it.
    • The clip: its video file's codec, bit depth, colour format, range and tone curve, frame size and rate, rotation, whether its frame rate varies, and its type from the file extension, never its name; how it sits on the timeline and at what speed; and how closely the frames the plug-in read matched the picture the editing program showed.
    • What you did: the buttons and settings used (as on/off values, choices from a fixed list, or numbers), whether the AI Ball Finder was on and had enough memory, and whether you then corrected the result (moved a handle, added Ball Marks, or traced again).
    From version 0.2.4, also:
    • Refusals: how far a refused picture was shifted, scaled or turned, what kind of clip a refused one was (for example a compound or multicam clip), which refusal message was shown and whether pressing Trace again changed anything.
    • The clip: whether it has a position, zoom, rotation, stabilisation, crop, lens correction or other effects applied in the editing program; how uneven a varying frame rate is; the camera's maker as one word from a fixed list (for example Apple or Sony, never the model or serial number); which end of a clip's range falls outside its file and by how many frames, the clip's in and out points and the file's length in frames, and whether the clip has a speed change or a freeze frame.
    • The trail: how far the drawn landing sits from a Landing marker, the horizon row the trace used, and which handle you dragged and how far.
    • Check pictures: why a press found no check picture to compare against (for example proxies are on, or another effect sits before Ball Tracer), and what the render side did about taking one: how many pictures the render side asked for, kept or got back empty, which render path and graphics API it used, whether proxies are on, whether Ball Tracer is the first effect, and whether the media path contains a non-ASCII character (a yes or no, never the path).
  • Performance and hardware: your graphics card and processor model (the maker's model name only, such as NVIDIA GeForce RTX 4090), the graphics card's and computer's memory and the processor's cores, each rounded to a common size (for example 8, 12, 16, 24, 32 or 64 GB); the clip's frame size and rate, how long frames and traces take, memory warnings, whether frames were drawn on the graphics card or the processor, and how many graphics adapters of each maker the computer has (for example one NVIDIA and one virtual display adapter).
  • Usage counts: how often each feature is used.
  • Support bundles you send (from version 0.2.4): whether a bundle was made, uploaded or failed (and why, as a fixed code), its size, how many of its pieces were sent, and the bundle's reference and upload id (a random code the support server gave that upload), so the bundle you sent can be found, even a half-finished one.

  The time of each report is rounded to the minute.

• What is never collected

  • Your footage, video frames, pictures or thumbnails.
  • File, folder, project, sequence or clip names, or file paths.
  • Your licence key, or the ID your licence uses for this computer (only the code worked out from the licence, below).
  • Your email address, name, user or account name, or your computer's name.
  • MAC or IP addresses. The server sees the address a report arrives from, but the IP address is not stored, nor the program identification (user agent), and the server's request logs leave diagnostics out.

  The plug-in can only send numbers, on/off values, words from a fixed list, version numbers, hardware model names, and the reference and upload id of a support bundle you sent, and the server rejects anything else.

• The random diagnostics ID, and your licence

  Each computer that says yes gets a random diagnostics ID, not based on your hardware or anything about you. It shows which reports came from the same computer. Turning diagnostics off deletes the ID and anything not yet sent; turning them on again later makes a new one.

  When the plug-in has an activated licence, each report also carries a code worked out from that licence. It is not your licence key, and the key cannot be worked back from it, but it lets Ball Tracer see which licence, and so which customer, the reports came from, and read them together when you ask for help. Reports from a computer without an activated licence carry no such code. A new diagnostics ID does not separate a licensed computer's reports from its licence: they stay linked to it.

• Why, and who sees it

  Only to fix bugs, solve problems and improve Ball Tracer; never for advertising, never sold. Most of it is read in combined form, such as how often tracing fails on one graphics card. When a problem needs it, or when you ask for help, one computer's or one licence's reports are read in order to see what led up to an error. Reports may be given to an AI assistant used for software development. Apart from that and the host (below), they are not shared.

  When the server turns a report away (too large, or too often), it notes why for 14 days: the reason, the plug-in version and host, the first 8 characters of the ID and the size. Never the report or the address.

• Where it is stored, and for how long

  Sent over HTTPS to the licence server, hosted by Cloudflare, and kept for 180 days, then deleted automatically. The database's own backups, kept up to 30 days, can hold a report a little longer.

• Legal basis, and deleting your reports

  Your consent, which you withdraw by unticking Send diagnostics; nothing more is sent after that. Write to support.balltracerplugin@gmail.com with your licence key, your order, or the diagnostics ID the plug-in shows in its Support section, and every report for it is deleted (for a licence: every report from each computer that sent under it, its earlier reports included).

The diagnostic log, and sending one to support

The plug-in writes a diagnostic log only if you create the debug_log file yourself, and it stays on your computer. Send to Support uploads a copy only when you press it twice: the first press writes the file so you can read it, the second sends it. Nothing is uploaded on a crash or in the background. If you quote a bundle's reference, or your diagnostics ID, when you write to support, it may be filed with your email in the admin console so your case can be found again. If diagnostics are on, the plug-in also reports the reference of a bundle you send with your diagnostics (from version 0.2.4), so the bundle is filed with your diagnostics, and with your licence if your diagnostics are linked to it. Nothing else connects a bundle to you.

• What is in the file

  • The plug-in version, build date, host and operating system.
  • Whether it is licensed, and whether this computer can be identified for licensing at all (a yes or no).
  • The plug-in's settings and its session log, and the diagnostic log if you switched it on.

  File paths are reduced to their shape — the volume, extension and length, such as <C: path, .mov, 63 chars> — never a folder, file, share or server name. Your account name becomes %USER%. The licence key is left out, and anything key-shaped is blanked.

• How it is stored, and for how long

  The file is sent in small pieces. Pieces of an upload that never finishes are deleted within a day. A finished upload is kept for 90 days and then deleted automatically; you get a reference like BT-7K3Q-2M to quote if you want it deleted sooner. It is stored with a keyed hash of the sending IP address, never the address, so one sender cannot fill the store; the hash goes with the upload, and the upload counter that uses it is cleared within a day.

Live chat

The chat button at the corner of the public pages sends what you type to the licence server, where support reads it and replies. A conversation is kept for 90 days after its last message and then deleted automatically.

The first time you open the chat it only asks the server whether support is online. If you have chatted before, opening it fetches that conversation, using the ID and key your browser saved. Nothing you type is sent until you press Send.

• What is kept

  • Your messages and the replies, each with the time it was sent.
  • The email address, only if you typed one into the chat, so the reply can reach you.

  No IP address is stored with a conversation, and no name, no account and no cookie: the chat works without signing in. To stop abuse the server counts messages per keyed hash of the sending address, a minute at a time, as it does for every other request to it (see How long activation records are kept above). The database's own backups, kept up to 30 days, can hold a conversation a little longer after it is deleted.

• What your browser keeps

  The conversation's ID, a secret key that proves it is yours, the number of the last message you saw, and whether you already gave an email address (a yes or no, never the address), in your browser's local storage, so reopening the chat even days later shows the same conversation. Not the messages, and not a cookie. Clearing this site's data in your browser makes it forget the conversation; the copy on the server stays until it expires.

• Who reads it

  Support, in the admin console. The first message of each new conversation, and your email address if you gave one, is also emailed to the support inbox, which is a Gmail address. That copy is not covered by the 90 days: it stays until it is deleted, and a deletion request removes it too. Nothing is used for advertising or sold.

• Having a conversation deleted

  Write to support.balltracerplugin@gmail.com with the email address you gave, or what you wrote and roughly when, and the conversation is deleted, together with its copy in the support inbox.

Who else sees anything

• Paddle.com Market Ltd: payment, invoicing, tax and refunds.
• Supabase, which holds your account, and Google if you sign in with it.
• Cloudflare, which hosts the site, the licence server, support uploads and live chat, and stores the data above.
• The email service that sends messages about your account.
• Google, through Gmail, which holds the support inbox: email you send to support, and the first message of a chat.
• Google, through Google Analytics, only if you allow analytics cookies.
• Microsoft, through DirectML in the AI Ball Finder, as above.

Nothing is sold, rented or shared for advertising, and you are not added to a mailing list without asking.

Your rights

You can ask what is held about you, and have it corrected or deleted. Deleting your account and its records ends the licence tied to it and your access to the download, and the key cannot be shown again. Write to support.balltracerplugin@gmail.com; you get an answer within 2 business days.

Who is responsible

Ball Tracer, support.balltracerplugin@gmail.com.