Privacy | Tattoo Stencil Maker

Short version: in private mode the tools process your images in your browser and never upload them. If you use AI clean lines, the photo is sent to our AI provider to be redrawn (see "AI clean lines" below). No account is needed for either. If you subscribe to a Studio plan, you sign in with Google (we get your name, email address and profile picture), Stripe handles your payment (we never see your card number), and the finished stencils you choose to save are stored with your account. We set one first-party analytics cookie (HttpOnly, 1 year) that holds a random visitor id, plus a sign-in cookie if you have an account. Pseudonymous usage events are also processed by our self-hosted analytics (Umami) on infrastructure we operate. There are no third-party trackers, no ad tracking and no advertising cookies.

Tattoo Stencil Maker is operated from Hong Kong SAR and is responsible for your data. Contact: support@tattoostenciler.com. This version takes effect on the day the Studio plans launch.

Your images

In private mode the stencil maker decodes and processes every photo inside your own browser, in a background thread of the page. Images, stencils, PDFs, PNGs and SVGs are created on your device and are never uploaded to us or to anyone else. The same goes for the text you type into the name generator. Gallery designs you open in the editor are loaded from this site.

AI clean lines

For photos the editor offers AI clean lines, which redraws the photo as stencil linework with an image model. You choose it or private mode above the upload area, and you can switch at any time. When you use it:

What is sent. A copy of the photo, scaled down to at most 1024 pixels and saved as a JPEG in your browser (which drops its location and camera data), plus the style you picked. Nothing else about you is sent to the AI provider.
On our side. The copy is held in this site's Cloudflare R2 storage under an unguessable link for at most 15 minutes, so the AI provider can fetch it, and is deleted as soon as the run ends. The redrawn image is sent back to your browser and is not kept by us. Your stencil is then finished on your device, as in private mode.
Our AI provider. The image is processed by SeeAPI, which runs the model for us (by default OpenAI's GPT Image 2) and works with that model's provider to do so. Per SeeAPI's data-handling terms (read 15 November 2026): SeeAPI does not use API inputs or outputs to train AI models; input files and generated files stored by SeeAPI have no scheduled automatic expiry; request records and logs are kept for 60 days. If you don't want a copy of a photo to be processed or stored outside your device, use private mode.
Counting runs. To apply the free daily AI allowance without an account, we store a salted one-way hash of your IP address with a count for the current day; old days are deleted. Signed-in runs are counted on your account. A run that the provider refuses or that fails costs nothing.
Refusals. The provider refuses some images, for example famous people or protected characters. You then get the private-mode result instead, free.

The one exception is Save to Studio (paid plans only). When you name the design and press Save, the finished stencil lines (a PNG and an SVG of the lines plus a small preview, never your original photo) are uploaded to your Studio library, together with the name, tags and note you gave it.

Studio plans: your account

You only have an account if you sign in with Google, which you need to do to subscribe to a Studio plan. We never see your Google password.

From Google we receive your name, email address, profile picture link, whether Google has verified the email address, and a Google account id. We store them to run your account and to contact you about your subscription. We don't ask Google for anything else (no contacts, no Drive, no calendar).
The sign-in session. When you sign in we store a session record with an expiry date, the IP address and the browser user agent string it was created from (to spot misuse of an account), and set a session cookie (HttpOnly, Secure, SameSite=Lax) that keeps you signed in for up to 30 days and is renewed at most once a day while you use the site. A second, short-lived cookie caches the session for 5 minutes, and a few short-lived cookies protect the Google sign-in step itself. Signing out deletes the session.
Plan and usage records. We record when you last signed in (to apply the 24-month deletion rule below). We store your plan, its status and billing period, and a count of what you use: designs saved, flash sheets and print batches saved or printed, ZIP exports and AI stencil runs. We need these to apply your plan's limits and allowances and to decide refund requests (see the terms).
Your Studio library. Each saved design is stored as a PNG image of the stencil lines, an SVG of the same lines and a small preview image, with the name, tags and client note you gave it, its print size, the editor settings and the date, linked to your account. Only you can see your library. Flash sheets are laid out and turned into PDFs on your device; we only count that one was made.
Where it is stored. Account, session, plan and usage data and your library's names and settings are stored in a Cloudflare D1 database, and the library's image files in Cloudflare R2 storage, both belonging to this site (Cloudflare acts as our processor).

Payments (Stripe)

Payments are processed by Stripe. You enter your card details on Stripe's own checkout page, not on this site, so we never see or store your card number. Stripe acts as our payment processor and also has its own legal obligations (for example fraud prevention and keeping payment records), for which it is responsible itself.

From Stripe we receive and store your Stripe customer and subscription ids, your plan, the subscription status and period, and for each payment the amount, currency, date, the email address on the invoice, and any refund or dispute. We keep this order log, linked to your account, to run your plan, handle refunds and keep our accounts. You manage your card, invoices and cancellation in Stripe's billing portal.

AI generations

AI generations are the AI clean lines described above: the only AI feature on this site, provided by SeeAPI. A scaled-down copy of your photo is held in our R2 storage for at most 15 minutes so SeeAPI can fetch it. Without an account you get 3 free AI runs a day, counted by a salted hash of your IP address; signed in you get 5 a day, and the Artist and Pro plans add a monthly allowance (60 and 200 runs). A run that the provider refuses or that fails is never charged.

For runs on your account we record the time, the feature and the units used, not the content of your request.

How long we keep account data

Your account, plan records and library are kept while you have an account, also after a plan ends, so you can still view and download your designs.
Inactive accounts. An account that has no plan and that nobody has signed in to for 24 months is deleted automatically (a daily job), with its library, sessions and usage records.
Deleting a design removes it from your library at once.
Sessions expire after 30 days without use.
Payment records (amounts, dates, Stripe ids) are kept for as long as tax and accounting law requires, for 7 years, even after your account is deleted. The consent you gave at checkout (that access starts at once) is kept with them.
To delete your account and everything linked to it, email support@tattoostenciler.com from the address you signed in with. Cancel your subscription in the billing portal first.

Your rights

You can ask us for a copy of the data linked to your account, to correct it or to delete it, by emailing support@tattoostenciler.com. Depending on where you live (for example in the EU, UK or California) you have further rights, including to object to processing and to complain to your data protection authority. We use account data to perform our contract with you (running your plan), to meet legal obligations (payment records) and, for security logs and analytics, on the basis of our legitimate interest in running a safe and useful site. Some of our providers (Cloudflare, Google, Stripe, Railway) may process data outside your country, under their standard data-transfer safeguards. We have not appointed a representative in the EU or UK; we will appoint one if the law requires it.

When you open a page, the site sets one first-party cookie named _v:

What it holds: a random visitor id (for example v_ followed by 20 random characters) and the date of your last visit. It contains nothing about you or your images.
How it is set: HttpOnly (scripts on the page cannot read it), Secure, SameSite=Lax, and it expires after 1 year.
What we store with the id, once, on your first visit: the first page you opened and where you came from (the referring site, any utm_ campaign tags or ad click id in the link), your country as reported by our host, a rough device type (iPhone, Android, Mac, Windows or other) and a one-way hash of your browser's user agent string, used only to spot automated traffic. Our analytics never store your IP address or the user agent itself.

Search engine crawlers and other self-identified bots do not get the cookie; we only count them per day.

Usage events

The page sends small events to this site at a few steps: when a page has loaded, when an image is opened in the stencil maker (and how: uploaded, dropped, pasted or a sample), when its first stencil preview is drawn, and when you export a stencil (the format, PDF, PNG or SVG, the stencil style, the paper size and, for PDFs, the number of sheets). The halftone generator sends one event per export (the format, the pattern and the cell size in millimetres, and for PDFs the number of sheets). The design composer sends one event when you finish composing (the layout, the number of art pieces and whether there is lettering, never the text) and one per export (the format, the paper size and for PDFs the number of sheets). The flash sheet maker sends one event per export (the format, the paper size, the grid, how many designs and whether numbers or prices are on, never the title, the text or the prices you typed). The idea and name generators send similar events (for example which lettering font was used, never the text you typed). They never contain your image. Each event is stored with the page it came from and your visitor id, so we can see how many people get from opening the tool to a finished stencil. Individual events are kept for 120 days, then only daily totals remain.

We use this data only to see whether the tool is useful and to improve it. We do not sell it, share it with advertisers or combine it with data from other sites.

Our self-hosted analytics (Umami)

To cross-check our own numbers, this site's server also sends each of the events above (and your first visit of the day, with the referring site and any utm_ tags) to our own installation of Umami, an open-source analytics tool. It runs on a server we operate and control (hosted by Railway, a cloud provider); no analytics company receives the data, and no script, pixel or extra cookie is added to the page: the event is sent from our server, not from your browser.

With each event our server passes along your random visitor id, your browser's user agent string, your browser's language and your IP address. Umami uses the IP address only to look up an approximate location (country, region and city) and, together with the user agent, to group events into visits; it does not store the IP address or the user agent string, only the derived browser, operating system, device type and approximate location. Events from automated traffic and from our own tests are never sent.

No third-party tracking

No third-party analytics, advertising or tracking scripts are loaded, and no advertising cookies are set. The analytics described above are our own, self-hosted, and never used for advertising. If that changes, this page will be updated first.

What our host sees

The site runs on Cloudflare Workers. Like any website, Cloudflare receives the technical data needed to deliver pages (such as your IP address, browser user agent and the URL requested) and keeps short-lived request logs (including the logs of this site's own Worker) for security and reliability. We use those logs only to fix errors. See Cloudflare's privacy policy.

Your choices

You can delete the _v cookie or block cookies for this site in your browser settings at any time. The stencil maker and every other tool keep working without it.

The sign-in cookie is needed to use a Studio plan; if you block it you can still use every free tool, but you can't sign in.

Changes

We will update this page if the way the site handles data changes.