Your Images Stay On Your Machine.

Tracing runs on your own machine. When you convert an image, it is decoded and traced by code running inside your browser, and every export — SVG, EPS, DXF and PDF — is generated there too. The image is not uploaded, and neither is the vector it produces. Turning off your network after the page loads does not stop a trace.

The palette editor, the preview, the node overlay and the before/after compare all work on that same local copy.

Every image you unlock is also kept in your browser for 48 hours, so you can come back and export it in another format without spending a second credit. That copy is held on your device the same way the trace itself is — it is never uploaded, it expires on its own after 48 hours, and you can clear it at any time from the account page. Each entry is tagged to the account that unlocked it and hidden from any other account signed in on the same device, but it is not encrypted: someone with access to that device and its browser developer tools could read it, the same way they could read your browser cache or history.

AI Cleanup is the one feature that sends your image to a server. If you use it, the image is posted to us and forwarded to OpenAI, which returns a cleaned version. We do not use your images to train anything, and we have no model of our own to train.

What we record for each cleanup is a SHA-256 digest of the image, an identifier for the attempt, its status, which provider and model handled it, what it cost us, token usage, and an error category if it failed.

If a trace comes out wrong you can send us a report. It carries what you write, the reasons you pick, technical details about the trace, and a reply address only if you give one. We keep a one-way hash of your IP address to limit how often reports can be sent, never the address itself.

Your artwork is attached only if you tick the box that asks. It starts unticked. If you do, the traced SVG and any screenshot you add are stored privately so we can reproduce the problem, and are kept until you ask us to delete them.

A download credit unlocks one image permanently, so that re-tracing at different settings and exporting every format stays free. To do that we have to recognise the image again, and we recognise it by a SHA-256 digest of the original bytes rather than by keeping the file.

Accounts are handled by Supabase. You can sign up with an email address and password, or with Google or GitHub, in which case we receive the email address and profile picture that service gives us. We store your email, your plan, your credit balances, your unlock and cleanup history, and nothing else about you.

Payments are processed by Stripe, which is the merchant of record. Card details go to Stripe and never reach us — we never see or store a card number. Stripe also calculates and remits any sales tax or VAT. What we keep is which plan or pack you bought, the amount before tax, and Stripe’s identifiers for the purchase and the customer.

We use PostHog to answer a small number of product questions, such as how many traces lead to a download. It is deliberately narrow:

• Ten named events. No automatic click, keystroke or page-view capture, and no session recording.
• Properties are restricted to a fixed list of fifteen — durations, counts, a format, a plan key. Anything not on that list is dropped before it is sent, including anything shaped like a digest.
• Identity is your account’s UUID and nothing else. Never an email, never a name.
• Storage is session storage, so nothing persists after you close the tab and there is no cross-session identifier. We cannot tell that you came back tomorrow.
• It is off entirely unless a PostHog key is configured for the deployment. With no key, nothing is collected and nothing is sent.

Five companies process data on our behalf, each for one job, and each receives only what that job needs.

• Supabase

  Accounts and our database

  Your email, sign-in details, plan, credits and unlock history

• Stripe

  Payments, as merchant of record

  Your card and billing details, entered on Stripe's own page

• OpenAI

  AI Cleanup, only when you use it

  The one image you send to cleanup, for that request

• PostHog

  Product analytics

  Ten anonymous events and your account's UUID

• Resend

  Email delivery

  Your email address and the message we send you

Your images, your filenames, and the vectors you produce — except the artwork you choose to attach to a problem report. No advertising or cross-site tracking, and no data sold or shared for advertising.

Account records, credit history, unlocks and cleanup records are kept for as long as your account exists. Deleting your account removes them, except where we have to keep a purchase record for tax or accounting purposes: those are kept for six years after the end of the tax year they fall in, which is what Canadian tax law requires, and then deleted.

Deletion is self-service: the account page has a Delete Account control that does this immediately, with no need to contact us.

You can export a copy of your data or delete your account yourself, at any time, from the account page’s Your Data section — no request needed. Correcting your data is one exception: change your email there directly, and reach us for anything else.

We handle personal information under Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA). If you are unhappy with how we have handled yours, you can complain to the Office of the Privacy Commissioner of Canada, or, if you live in the EU or UK, to your local data protection authority.