SignatureMakerOpen the studio
Legal

Privacy

The short version: your signature and files stay on your device. Visit counts come from cookieless analytics pings; cookies and product events need your explicit allow. The phone hand-off sends stroke coordinates through a realtime relay for the length of the session and stores nothing.

Your content

Signature drawings, typed names, photos, graphics and PDFs are processed locally in your browser and are not transmitted to or stored on our servers. Downloads are created on your device.

Saved in this browser

Your kit (the signature variants as PNG), drafts, job settings, recent file names and your theme choice are saved in this browser's local storage so they survive a reload. Nothing is synced anywhere. The Vault can export them as a .sigkit file or clear them.

Phone hand-off relay

If you use Sign on phone, the pen strokes you draw on the phone travel to your desktop through a realtime relay channel named by a random code. The relay forwards messages between the two devices for the duration of the session; strokes are not stored on the relay and the channel is abandoned when either side leaves.

Usage analytics

On public tool and guide pages, Google Analytics 4 loads with Consent Mode v2 defaults: analytics_storage and every advertising signal start denied. In that state Google receives cookieless measurement pings — a fixed allowlisted page name and path, with query strings and fragments removed — which give us aggregate visit counts without setting cookies or enabling ad features. If your browser sends Do Not Track or Global Privacy Control, the analytics tag does not load at all. Use Privacy choices below to allow or withdraw measurement; guest tools work either way. Allowing upgrades consent (analytics_storage granted): Google may then set analytics cookies, and bounded product events such as creation method, job opened and export format are sent. Choosing to keep measurement off stops every send. Advertising signals are never enabled. Vercel page measurement runs only after an explicit allow. Account pages, phone-pad tokens, unknown routes and URLs with queries or fragments are excluded. We do not send names, strokes, images, uploaded content, file names, handles or free text. Google and Vercel may process technical data such as IP addresses under their policies. Withdrawal stops new sends without clearing your kit; it does not delete data already sent. Your preference is stored in this browser.

Optional account

You can keep using the signature tools without an account. If you sign in, Supabase Auth processes your email and password for a shared AImasterz identity. A short-lived, secure session cookie keeps this portal signed in. Joining SignatureMaker records your product membership and plan in our shared database; signing in does not upload or sync your signatures, photos, PDFs or local Vault. Account pages do not load usage analytics. Contact the support team for account-data requests; deleting a shared identity may affect other AImasterz products.

Third parties

Fonts and analytics are loaded from Google on tool and information pages; the relay runs on Supabase Realtime and optional accounts use Supabase Auth. There is no cloud signature library or payment collection in this release.

Changes

If this notice changes, the date at the top of this page is updated. Questions belong on the support page.

Updated October 10, 2026.