Privacy Policy

Version 1.9 · Last updated 31 October 2026

Version 1.9, 31 October 2026: at the studio's closest setting one reference photo goes with your description by default (up to three when I set more); the counts below say so. The design log now also keeps which strength a request asked for and, when a different one ran, why, in the engine's own words (for example: no photo attached).

Version 1.8, late on 30 October 2026: at the studio's closest setting (section 8 of the Terms describes it), when the AI copies one of my reference photos, neither my craft notes nor your style words go with the request, because that photo sets the standard then. It copies one only when a photo shares a word with your description beyond a colour (or, when your description names only colours, one of those colours) and your own photos leave it a nail; otherwise the request runs as the next setting down, with both, and the design log records that setting. At most three reference photos go along at the closest setting. Nothing else changed.

Version 1.7, later on 30 October 2026: a Do Not Track statement under Cookies and browser storage, saying plainly that nothing on these pages tracks you across other sites, and a line on which outside companies see a request and for what. Nothing about what is collected or kept has changed. The Terms changed the same evening: California law instead of Arkansas, and a fixed rule for refunds of a pack you have started.

Changed on 30 October 2026: the studio's newer design engine has been the one in use for everyone since 29 October, so everything below applies to every design you make now. New with it: from time to time Google's text model reads my reference library (photos I chose for it, never yours or anything from your account) and writes short notes about my craft; those notes ride along with every request while I have them switched on (not when the closest setting copies one of my photos; the log records no version then), and the design log notes which version of them was in use. They describe the craft in my library, not you. The changes of 29 October stand: the description you type is kept for 90 days in a design log, with the shape, length and difficulty you picked, which of my reference photos were used and, when you are signed in, any 👍 or 👎 you tap on the result (saving a design to your phone counts as a 👍 unless you already voted), so I can see what the AI does well and badly; when you are signed in, your 👍s, saves and downloads build a short list of style words on your account (“almond · nude · chrome”) that the AI can lean toward a little, which you can see, switch off, reset or delete in the app; and photos you attach to a request go to Google with it, each marked with the finger you chose, used for that design only and not stored by me; the design log notes only which finger each photo was for. This version also corrects details I checked line by line against the code: what the design log keeps, how style words are kept, what Stripe asks you for, where my reference photos come from, and what the free-tier code is. The Terms changed the same day.

The short version

The only thing you have to give me to use NailMind is a phone number (a 10-digit North American number). No password, no name required. If you buy online, Stripe asks for your email and a billing address.
I never see your card number. Stripe handles payment on its own page.
Your typed description goes to Google to make the images, with a few photos from my reference library and my short craft notes (not the notes when the closest setting copies one of my photos). The photos you attach to a design go too, each marked with the finger you chose, and so can up to ten words of your style when it is on and ready. Photos in My Work never go.
Each description is also kept for 90 days in a design log so I can see what the AI does well and badly. Then that copy is erased.
Signed in, your 👍s build a style: a short word list on your account that you can see, switch off, reset or delete in the app. I tell the AI that what you type wins.
When you are signed in, every design you generate is saved to your account automatically.
Email support@nailmind.app to see or delete everything. If you have unused credits, ask for a refund first — deleting removes them.

This explains what NailMind collects, why, who else sees it, and how to get rid of it. It is written plainly on purpose. If anything is unclear, email me and ask.

Who runs NailMind

Minh Pham, a sole proprietor. I work as a nail technician in Vacaville, California; my legal home is Arkansas. One person, no company, no staff. Contact: support@nailmind.app.

The two design engines

The studio has two design engines. The newer one has been in use for everyone since 29 October 2026, and it is the one this page describes. The older one stays as a fallback I can switch back to: under it, a photo you add next to your request is only read for its colour in your browser and never leaves your phone, and no difficulty, style words or craft notes go to Google.

What is collected, and why

Your phone number

This is your account — it is how your credits and designs find their way back to you. It has to be a 10-digit North American (+1) number, as used in the US and Canada. An optional first name is kept next to your number; the app does not show it, and I see it in my admin list so I know who is writing to me.

Your credit balance and its history

Every movement of credits — bought, spent, granted, refunded — is recorded as a line in a ledger, with a date and a reason. A credit I add by hand at the front desk is a line too. That is how I can answer "where did my credit go?" and how refunds stay correct.

The designs you generate

When you are signed in, every image you generate is saved to your account automatically, as a smaller copy (about 720 pixels on its longer side) with the first 140 characters of the description that made it. This is deliberate — it is what fills your Recent album, which keeps your newest 60 — but it means saving is not something you opt into per image. That includes a design painted onto a photo of your own hand: the saved image shows that hand and its background, and you can delete it from Recent at any time.

When you are not signed in, the images stay in your browser (the newest 8); if you later sign in on that browser, they move into your account. Any photos you attach pass through my server on their way to Google and are not kept. Your description and picks are kept only in the design-log line described next (the description for 90 days), linked to nothing; the only other thing my servers keep is the free-tier counter described below. Neither holds anything that identifies you. A 👍 or 👎 from a guest moves the counters on my photos without naming anyone.

Descriptions you type

Each description is kept for 90 days in a design log, together with the shape, length and difficulty you picked, which of my reference photos were used, and technical details: which engine and model drew it, member or guest, how strongly my photos were set to steer it, the image size and count, how long it took, when it was made, any error text Google sent back, which finger each attached photo was for, which version of my craft notes was in use, and, when the strength asked for could not run (for example when no photo could be copied at the closest setting), which strength was asked for and why a different one ran, in the engine's own words. It is linked to your account when you are signed in, and linked to nothing when you are not. After 90 days the description is erased and the entry is no longer linked to your account (the clean-up runs about once a day, with a design); the rest of the line stays, linked to no one, so I can still count what the engines did. I read the log in my database; no page shows it.

If you tap 👍 or 👎 on a design (saving a design to your phone counts as a 👍 unless you already voted), that vote is kept with the same line when you are signed in, and it comes unlinked from your account 90 days after the vote. A guest's vote is never stored as a line of its own: it only moves the counters on my photos, and my server remembers it for a day so it is not counted twice. To stop one address flooding the votes, my server also holds a guest's IP address and the times of their votes in memory for an hour; that is never written to the database. What a vote does: once a photo in my library has three votes, its score helps the engine choose between photos that fit a request equally well, for everyone; my own votes count five times. Those score changes stay with my photos after your vote is unlinked or your account is deleted, and nothing in them names you.

Your style

When you are signed in, each set you like (a 👍 on any of its designs, or saving or downloading one) adds a few words to a style kept on your account: the words of your description, the labels of my reference photos behind that set, and the shape, length and difficulty you picked. A 👎 takes some away. Up to 40 words are kept with a weight each; the ten strongest are shown in your account sheet, such as “almond · nude · chrome”, with the first few under the pickers. Any word you type can become a style word, so keep names and private details out of your descriptions. Once a style has three liked sets, the AI can lean toward it a little where your request leaves room; I tell the AI that what you type wins, and one design in each set deliberately goes a different way unless you attached photos; when the closest setting copies one of my photos, the style stays out. You can keep up to five named styles, switch it off (Freestyle) at any time, which stops both the leaning and the learning, reset a style or delete it, all in the app. A deleted style is gone; if it was your only style, your next 👍 starts a new one unless My style is off. A style holds words only, never your photos or the designs themselves. Guests have no style: nothing is built until you sign in.

Photos you upload

Four different things use uploads, and they behave differently:

My Work — photos you add from your camera roll are shrunk on your phone (about 720 pixels on its longer side, which drops their location and camera details), uploaded and stored on my servers, attached to your account, until you delete them or they fall past your newest 200. They sit at long web addresses, as explained below. Only add photos you have the right to use; a photo of a client's hands needs that client's say-so.
Photos next to your request — each photo you add there is sent to Google together with your request, marked with the finger you chose for it (or “whole set”, or “my hand”), so the AI can reproduce that photo's design on that nail, or paint the set onto a photo of your own hand. It goes more than once: first to Google's text model for a one-line description (not for a photo of your own hand), then once with each picture of the set (two by default, so three times in all), and again to a stand-in model if the one Google tries first is unavailable. The photos are shrunk on your phone first, used for that design only, and not stored by me: the design log keeps only which finger each photo was for, never the photo. (A design painted onto a photo of your own hand is a new image that shows that hand; signed in, it is saved to your account like every design, see above.) The studio says so right under the photos before you generate, and a photo added before that note was on screen is not sent until the studio has brought you back to the note and you tap Generate again. Only add photos you have the right to use; a photo of someone else's hand needs their say-so.
Gallery albums — photos you add to an idea gallery with the pencil stay in your browser and are never uploaded.
Colour matching, on the older engine — if I ever switch it back on, a photo added next to your request is read for its colour in your browser and never leaves your phone.

I only ever open your photo library when you tap the button that asks for it.

A free-tier counter

When you use the free design without an account, your IP address and your browser's identifying string are mixed together into a one-way code, and that code is stored with a count of free images used today. I never store the IP address itself, and the code is not meant to be turned back into one; it exists only so one visitor cannot use up everyone's free designs. It is deleted after about eight days, at the next daily clean-up (which runs with a design).

Basic technical data

My web host and database host keep ordinary server logs — IP addresses, times, which page was requested. A few of the app's own requests carry your phone number and sign-in token in their address, so both appear in my web host's logs; and my server looks your account up by phone number, so the number (never the token) appears in the database host's logs on most signed-in actions. The pages outside the studio (this one, the terms, the landing page and the guide) load their fonts from Google Fonts, which sees your IP address and browser details. I have not added any analytics, advertising, or tracking product.

What is not collected

Your card number. Ever. Stripe's checkout page handles it. In my Stripe account I can see the card's brand and last four digits, the email address Stripe asked you for so it could send your receipt, the billing address Stripe requires (I use the state to work out sales tax), and the phone number of the account that bought.
An email address is not required to sign up and I do not send marketing email.
Your device's location, contacts, calendar, or microphone.
Anything about you from anywhere else. No data brokers, no ad networks, no social logins.

Who else sees it

Five companies; Google does two jobs (the AI and the fonts), the others one each. Nothing is sold, ever, to anyone.

Google (Gemini API) — receives the description you typed, plus the nail shape, length and difficulty you picked, wrapped in my standard instruction text. When you are signed in with My style on and a style of three liked sets or more, up to ten words of that style can go along too (not when the closest setting copies one of my photos; for example almond, nude, chrome; they can come from your earlier descriptions), the same words your account sheet shows. A few photos from my reference library go along with the request, with their labels, so the result looks like real nails (up to six for members and up to four on the free design, as I set them, one to three for everyone at the studio's closest setting, or the usual number when that setting finds nothing to copy; fewer when your own photos fill the request); the library is my own work and nail photos I have collected as references. So do my short craft notes: from time to time Google's text model reads that library on its own (photos I chose for it, never yours or anything from your account) and writes a few plain sentences about how my sets are made, which the engine adds to every request while I have them switched on (not when the closest setting copies one of my photos); they describe the craft in my library, not you. The only images of yours that go to Google are the photos you attach to that request, each marked with the finger you chose, once for a one-line description and once with each picture; photos in My Work and saved designs never go, and the craft-notes study never reads them either. Nothing identifying is added to a request by me: no phone number, no name, no balance. A photo you attach goes as you took it (shrunk on your phone, which also drops its location and camera details), so keep faces and anything private out of it. Google's own API terms govern what it does with that request; that part is not mine to promise. I never train any model on your data.
Google Fonts — the pages outside the studio load their fonts from Google, which sees your IP address and browser details when they load.
Stripe — takes the payment and holds the card details; asks you for an email and a billing address; and receives your phone number with the checkout so the credits reach the right account. Stripe has its own privacy policy.
Supabase — hosts the database and the stored images.
Hostinger — runs the website itself and the support@nailmind.app mailbox.
Twilio — once sign-in texts are switched on (they are off today), it will receive your number and the text with your code.

Beyond those, I would only hand anything over if the law actually required it.

How your images are stored — please read this one

Saved designs and uploaded photos live at long web addresses that nobody can browse or list, and nobody can find yours by searching. Designs saved from 30 October 2026 on have random addresses that say nothing about you; older ones carry your account number and the time they were saved. But those addresses are not behind a password: anyone you send a link to can open it, and so could anyone who came by that link another way.

For ordinary nail photos this is fine, and it is how the app can show your album instantly. If a photo is sensitive, do not put it in My Work and do not use it as “My hand”. I would rather tell you plainly than let you assume otherwise.

How long things are kept

Account, balance and ledger — until you ask me to delete them.
Generated designs — your most recent 60 are kept; older ones drop off automatically to keep the album fast, and their files go with them. Uploaded My Work photos — your most recent 200. Download anything you want to keep forever.
Design log — 90 days, then the description is erased and the entry is unlinked from your account; the rest of the line stays, linked to no one.
Your votes — unlinked from your account 90 days after the vote; the score changes they made to my photos stay, with nothing that names you.
Your styles — until you reset or delete them in the app, or delete your account.
Photos attached to a request — not stored; they go with that one request and the design log keeps only which finger each was for.
My craft notes — kept, with every earlier version; they are about the craft in my library and hold nothing about you.
Your sign-in key — until your next sign-in, which replaces it; it does not expire on its own. Signing out removes it from that browser.
The free-tier counter — about a week.
Payment records — Stripe keeps its record of each online payment (card brand and last four digits, email, billing address, the phone number of the account) as long as tax rules require, even after your account is deleted. The credit history inside NailMind goes with the account; only the bare Stripe checkout ids that stop a payment being credited twice stay, with no account attached.
Server logs — kept by Hostinger and Supabase on their own schedules. I do not set the length, do not copy them anywhere, and do not build profiles from them.

Deleting your account

Email support@nailmind.app and tell me the phone number on the account.

Because the phone number alone is not a secret — text verification is not switched on yet — I will confirm the request is really yours before deleting anything, usually by checking a detail only you would know, such as a recent purchase. If I cannot confirm it, I will not delete the account. That is deliberate: it stops a stranger destroying your credits.

If you have unused credits, ask for a refund before you ask for deletion. Deleting the account removes the balance along with everything else, and there is nothing left to refund afterwards.

Deletion is done by hand. It removes your number, name, balance, ledger, saved designs and their files, uploaded photos, your styles, your votes and the design-log entries still linked to you (older ones were unlinked already). Stripe keeps its payment record. I aim to finish within 30 days.

Cookies and browser storage

No advertising or tracking cookies. The app stores a few things in your own browser: your sign-in token and the phone number it belongs to, so you stay signed in; your shape, length, difficulty and skin-tone picks; your 👍 and 👎 on your last 60 sets; if you are not signed in, your newest 8 designs and a count of free designs used; and the sketch pad's favourites and recents plus any gallery names and photos you added with the pencil. Signing out removes the sign-in token and number from that browser, so do that on a shared phone or tablet (💎 → Sign out). Clearing your browser data clears all of it. If you lose a phone that was signed in, email me and I will sign it out.

Do Not Track. NailMind does not follow you across other websites, and nothing on these pages is there to track you: no advertising network, no analytics script, no tracking pixel. So there is nothing for a browser's Do Not Track signal to switch off, and the site does not change what it does when it sees one. No outside company collects information about you across other sites through NailMind: the companies that handle a request are the ones listed under Who else sees it, each for the one job named there. Google's font server does see your IP address when a page outside the studio loads, and Google says it does not use font requests to build profiles or target ads.

Children

NailMind is not for children under 13, and I do not knowingly collect anything from them. If you believe a child has given me information, email me and I will delete it.

If you are in California

You can ask me to tell you what personal information I hold about you and where it came from, to delete it, to correct it, and to give you a copy. I do not sell or share personal information for advertising, so there is nothing to opt out of. Exercising any of these rights will never get you worse pricing or a worse service.

To make a request, email support@nailmind.app. I will confirm it is really you first, and aim to answer within 30 days — and in any case within the 45 days California allows.

If you are outside the United States

NailMind is run from the United States and your information is stored there. I will honour requests to see, correct, export or delete your data wherever you live — just email me.

If you are in the UK or EU: where you have bought credits, the basis for processing is performing that contract. Where you use NailMind without buying anything, the basis is your consent — you gave me a number to make an account, and you can withdraw it any time by asking me to delete it. Keeping the service running and stopping abuse rests on legitimate interests.

Security, honestly

What is true: no database key is in the web pages at all; your browser talks to my server for everything except loading your saved pictures, which it fetches straight from Supabase's storage at their long addresses (no key involved), and Stripe's checkout page. My server holds the database's secret key, and the database tables are locked down so nothing else can read them. Card details never reach me. Admin tools need a PIN, and repeated wrong guesses lock an address out. NailMind's data lives in a completely separate database from the nail salon's, and the salon's staff tools cannot reach it.

What is also true: this is one person's project, not a bank. There has been no third-party security audit and I hold no certifications. Stored images sit behind unguessable links rather than a password, as described above, and a sign-in key lasts until the next sign-in. If something ever goes wrong that affects you, I will tell you rather than hope you do not notice.

Changes

If this policy changes, the version and date at the top change with it. A change that materially affects you will be announced on the site, not slipped in quietly.

Contact

support@nailmind.app — one address, and a person reads it.