Privacy

V3KTR makes Dimensional FX: browser apps for your images and clips, which are processed on your own device and never reach us. This page explains what we do collect, why, who else touches it, and how to make us stop — in plain language, no surprises.

Updated 03-Oct-2026

Who's collecting it

V3KTR is run by Patrick John Martin (ABN 77 516 147 302), a sole trader based in the Australian Capital Territory, Australia, trading under the registered business name V3KTR2173. That’s who’s responsible for the data described here, and who to contact about it: patrick@v3ktr.com.

Your images and clips never leave your device

V3KTR processes your images and clips entirely in your browser, on your own device. They are never uploaded to us, never stored by us, and never seen by us. The apps have no upload step at all. The site does have two small server functions, the newsletter sign-up and the contact form, and each receives only what you type into it (both are described below). Nothing you make here is used to train anything.

One thing worth being precise about, because it’s the obvious follow-up question: your media never goes out, but the model comes in. The depth feature downloads a machine-learning model (about 50 MB, plus around 22 MB of runtime the very first time) to your browser the first time you use it, then caches it. That download is a normal web request, so the services hosting it — jsDelivr and Hugging Face — see your IP address, the same way any site you visit does. They don’t see your images or clips, because those never go anywhere.

What we collect

Anonymous crash reports — when the app hits an error it sends us a compact report: the error message and where in the code it happened, the app version, your browser, your GPU vendor, the window size, the address of the app page (without anything after a ? or #), which effects were in the stack, and the same per-tab visit number as the counters below. No image data, no account details, nothing that identifies you. It’s how a one-person operation finds out something is broken for people it can’t see.
Anonymous counters in the app — six plain tallies: the app was opened, an image was loaded, a video was loaded, an effect was applied, an export finished, or the browser couldn’t run it at all. Each is counted once per visit, and each carries only the name of the thing, the app version, a rough label for where you arrived from (the referring site sorted into a fixed list, such as “search” or “direct”, never the full address), and a random visit number that lives in that browser tab and is gone when you close it. No account, no device, no location, no cookie, nothing that could be traced back to you or joined up between visits. It is how a one-person operation knows whether the app works for people it can’t see — and it needs no consent, because there is nothing here to track with.
A cookieless page count — the website AND the app both tally page views through Cloudflare Web Analytics. It sets nothing on your device, uses no cookie, builds no fingerprint, and names nobody — it’s how we see which pages get read without tracking who read them. EU visitors aren’t counted at all, and, like the app counters above, it needs no consent, because there is nothing here to track with.
Your email address, if you join a list — and only then. The sign-up form stores the address and nothing else (no name, no location, nothing about you), on each list you tick. The newsletter tells you when new effects land and gives you first word before commercial licences go on sale. Each app waitlist (for example Kompositor) is a separate list: it sends one email to confirm, and one when that app opens. Every list email has a way out, and you can also just reply “unsubscribe”.
What you send through the contact form — your name, your email address and your message, plus which app and version you came from if you opened the form from an app’s Help menu (the form shows it before you send). It’s emailed to us so we can reply, and that’s all: the site keeps no copy and puts you on no list.

Why we collect it

Crash reports— to fix bugs and keep the app stable.
The anonymous counters— to know whether the app works for people we can’t see.
Your email, if you join the list— to send you the emails you asked for, and nothing else.

We don’t sell your data. We don’t share it for advertising. We don’t build a profile on you. If that ever changed we’d have to say so here first, and it isn’t going to.

If you’re in the EU or UK and want the formal version of the above: legitimate interests for security and crash diagnostics; and your consent for the mailing list, which you give by joining it and can take back any time. Nothing else here identifies you.

Cookies and analytics

We set no cookies, and there is no consent banner, because nothing we use needs one. There was one until September 2026, when Google Analytics was removed from this site — it was the only thing here that ever set a cookie, and it went with the rest of the tracking.

What remains is a cookieless page count through Cloudflare Web Analytics (named above under “What we collect”). It sets nothing on your device, builds no fingerprint and names nobody, so it needs no consent — and it isn’t served to EU visitors at all.

There are no ad networks, no pixels, and no third-party trackers.

Who else touches it

We’re one person, so we use other people’s infrastructure. Here’s all of it, and what each one sees:

Cloudflare— as well as hosting, it runs the cookieless page count and the small service that receives the anonymous counters and crash reports. Those live in a Cloudflare database in Sydney.
Cloudflare — hosts and serves the site, and runs the cookieless Web Analytics page count described above. Sees IP addresses and request logs, as any web host does.
Resend— delivers the one weekly summary of those counters to us, and holds the mailing lists: if you join the newsletter or an app waitlist, Resend stores your email address and sends that list’s emails. It also delivers contact-form messages to our inbox, without keeping them as contacts. If you don’t sign up or write to us, it sees no visitor data at all.
Cloudflare Turnstile— checks that a sign-up or a contact message comes from a person, not a script. It runs only when you submit a form, Cloudflare doesn’t use it for tracking or advertising, and we don’t keep anything it sees.
jsDelivr and Hugging Face — serve the depth model to your browser. They see the request (and therefore your IP), not your images.

These services run in various countries, including the United States and the European Union, so your data may be stored or processed outside Australia. Each is a substantial provider with its own privacy commitments; we’ve picked them on that basis. If you want to know exactly where something sits, ask and we’ll tell you.

How long we keep it

Purchase records — the optional Founder licence is paid through Polar, who hold the payment details; we keep the order record (your email, the order and the date). Purchase records are kept for tax and record-keeping (generally five years under Australian law). It’s the one thing we can’t delete on request.
Crash reports — 12 months, then deleted.
Your email on the list — until you unsubscribe or ask us to remove it.
Messages you send us — as long as the conversation is useful, then deleted.

Your rights

Email patrick@v3ktr.com and you can:

get a copy of what we hold about you;
have it corrected;
have it deleted (except the historical records noted above);

No forms, no hoops. It goes to a real person and we’ll sort it. If you’re in the EU or UK you also have the right to object to processing and to data portability, and you can complain to your local data protection authority. In Australia, you can complain to the Office of the Australian Information Commissioner.

Security

Everything is served over HTTPS. Crash reporting and the counters are insert-only — the app can send a report but cannot read anything back, and there is no account, no login and no stored personal data for anyone to reach. If you buy the Founder licence, Polar takes the payment, so no card details reach us.

No system is perfectly secure, and we’re not going to pretend otherwise. If there’s ever a breach that could cause you serious harm, we’ll tell you and the relevant regulator promptly — and we’ll tell you what actually happened, not a press release.

Children

V3KTR isn’t aimed at children and we don’t knowingly collect data from anyone under 16. If you think a child has given us personal information, email us and we’ll delete it.

Changes

We may update this policy — most likely to name a new service as the app grows. The date at the top always reflects the current version. If a change materially affects how we handle data, we’ll say so on the feed rather than quietly editing the page.