Skip to content
ChairCode
TermsPrivacyLog in

Last updated November 3, 2026

Privacy Policy

Privacy Policy

Effective date: November 3, 2026. Operated by Keslie Wester, doing business as ChairCode. This is a plain-language first draft for a lawyer to review. It is not a finished policy or contract.

  • Who we are
  • Information we collect
  • Children
  • Why we use it
  • Photos and AI
  • Photo consent
  • Who can see a cut
  • Who processes it
  • We do not sell personal data
  • How long we keep it
  • Access and deletion
  • Security
  • Changes
  • Contact

Children under 13

ChairCode does not offer accounts to children under 13. A parent or guardian provides any information about a child. Read the Children section before you add a child profile or upload a photo of a child.

Who we are

ChairCode is a software service that helps a client describe a haircut and helps a barber read that description in the chair. You upload photos, answer a short set of questions, and get an AI breakdown in barber terms. A barber can open that breakdown from a QR code or a checkout link. Clients can sort cuts into folders and see a suggested maintenance date. Barbers can keep a public page with a booking link and portfolio photos they upload.

The service is operated by Keslie Wester, doing business as ChairCode, based in the United States. This policy describes what the software does today. In-app messaging between a client and a barber is not part of the product. If messaging launches, this policy will be updated before it collects those messages.

Information we collect

We collect the information below because the product stores it, sends it to a provider named in this policy, or shows it to someone you choose. We do not run a separate advertising or product-analytics service in this app.

Account

When you sign up we ask for:

  • Your full name.
  • Your email address.
  • A password. Supabase Auth stores the password. The ChairCode database stores your email, name, and role, not the raw password.
  • Whether you are a client or a barber.

If email confirmation is turned on for the project, Supabase sends you a confirmation link and the app asks you to check your email. A login cookie keeps the session. Signing out clears that session.

Photos and cut details

A new cut starts with one or more photos. People often photograph their own head and face. The server resizes each photo to a JPEG whose long edge is at most 1024 pixels and stores it in a private storage bucket named cut-photos, under a folder for your account. You can also type a free-text description. That description is saved on the cut and is sent with the photo for the AI read.

After the AI read, the app asks the discovery questions a barber would ask: where the front lays, part, growth patterns, sideburns, how the sides connect, ears, neckline, back length, how often you get cut, and what bothered you about a previous cut. One question is “Any moles or spots to be careful around?” Those answers are written into the zone breakdown and saved with the cut. They are not sent as their own field on the first AI call. They can be included later if that breakdown is sent for a refresh, or if a barber correction of that text is saved as an example. See Photos and AI.

A saved cut can also hold:

  • A style name, zone-by-zone breakdown, product suggestions, and tags produced by the AI.
  • A maintenance window and a next-due date shown in the app. That date does not trigger its own email.
  • A folder name you pick, such as Current or Favorites.
  • A checkout code and a QR code that point at a page anyone with the code can open.
  • A note when the photo looks heavily edited or professionally lit.
  • An optional link to a child profile, if you tag the cut for a child.

A later visit can add a new photo for a “refresh.” That photo is stored the same way and sent for a new AI read, together with the earlier breakdown and about how many weeks have passed. A barber who has the cut can upload an after photo of the finished haircut into the same private bucket. The after photo is stored and shown. It is not sent to the AI provider unless someone uses a photo in a refresh.

Sharing a cut with a barber

You can send a cut to a barber who has an account. Until you mark the cut as booked, the barber can see the photo and the breakdown, and the app keeps your name off that view. When you choose “I’ve booked this,” the barber can read your profile row, which includes your name and email. A barber who knows the checkout code can also claim the cut. You can leave feedback after an after photo is added: a star rating, optional notes, and whether you want to save the look for rebooking.

Child profiles

From a client account, a parent or guardian can add a child profile. The only fields are an optional first name and an optional age range. The ranges in the product are Under 5, 5–8, 9–12, and 13+. Both fields can be left blank. There is no child login, no child email, and no child date of birth. A cut can be tagged with that profile. See Children.

Photo consent flag

Each cut has a photo-consent flag. It starts off. You can turn it on with the checkbox “Let this barber use my photo in their portfolio if they use my cut.” You can turn it off again. The choice is stored on that cut. See Photo consent.

Barber profile, portfolio, and tools

A barber can save a city, a booth type (independent booth, or a shop name), and a booking link. The public page at /b/ plus the barber’s id shows the barber’s name, city, booth type, booking link, and portfolio, and it can be opened without an account. That page does not print the barber’s email. The database rule that allows this public read applies to the whole barber profile row, including the email column, so a lawyer should confirm whether that email can be queried even though the page does not show it. The booking link leaves ChairCode for the address the barber typed. ChairCode does not take the booking.

Portfolio photos are pictures the barber uploads, with a title, tags, zone notes, and optional style notes. They are stored in a public bucket named portfolio-photos. Anyone with the photo address can view them. Client consultation photos stay in the private bucket. The app does not copy a client photo into that public portfolio by itself.

Barbers can also track their own tools (a label, a task, and dates). That is the barber’s business note, not a client’s information.

When a barber corrects a breakdown, the app stores the zone name and the before-and-after text, with no name attached, and keeps the 60 most recent snippets. Those snippets are reused as examples on later AI calls. If the corrected sentence included a client’s answers, those words can be inside the snippet.

Email we send

The app sends two kinds of email:

  • Account email, through Supabase Auth, such as a confirmation link when confirmation is required.
  • One feedback reminder. About seven days after an after photo is added, if you have not left feedback, a daily scheduled job emails you once. The message includes your name, the style name, and a link to that cut. It is sent through Resend. The from-address in the code today is a Resend test sender, ChairCode <onboarding@resend.dev>, and should be replaced before this draft is final. The email does not include an unsubscribe link.

What we do not collect in the app

  • No payment card. The app does not charge a fee today.
  • No advertising identifier, and no analytics product in this codebase.
  • No precise location. A barber may type a city.
  • The ChairCode database does not store your IP address. Our host may keep ordinary server logs. See Who processes it.

Children

No accounts for children under 13

Children do not create ChairCode accounts. Do not sign a child up with their own email. If you believe a child under 13 has an account, email Westerkeslie@gmail.com and we will delete it.

A parent or guardian may add a child profile from their own client account. The profile is an optional first name and an optional broad age range only. You may tag a cut as being for that child. If you upload a photo of a child, including a child’s face, that photo is stored in the private cut-photos bucket and is sent to the AI provider the same way as any other cut photo. The checkout link for that cut shows the photo and the breakdown to anyone who has the code.

Only a parent or guardian should provide information about a child, or a barber who has that parent or guardian’s permission. This parent and child flow has not had a formal children’s-privacy review. It needs one before it is relied on for real family data.

Why we use it

  • To create and protect your account, and to tell clients and barbers apart.
  • To store your cuts, folders, and maintenance dates, and to show them back to you.
  • To produce an AI breakdown and, on a later visit, refresh guidance.
  • To let a barber you choose, or anyone you give the checkout code, see the plan.
  • To remember whether you allowed a barber to use a photo in a portfolio.
  • To send the account email and the single feedback reminder.
  • To show a barber’s public page and the portfolio photos that barber uploaded.
  • To keep short correction examples so later breakdowns can follow how barbers actually talk.

Photos and AI

Consultation photos are sent to Anthropic for analysis. Before the send, the app resizes the photo on our server. Anthropic receives the resized image and, if you typed one, your free-text description. The request also includes up to twelve recent correction snippets, which are text, not photos. The model named in the code is claude-sonnet-5. The request does not include your email address or your account name.

A refresh sends today’s resized photo, the saved zone text from last time, and the number of weeks since that cut. The saved zone text can include the answers you confirmed, including an answer about moles or spots if you gave one.

The breakdown is guidance for a barber. It can be wrong. Read the Terms for what the AI output is, and is not, a promise of.

Photo consent

Photo consent is optional. It is off until you turn it on, and you can use ChairCode without turning it on. The checkbox applies to that cut and that barber’s portfolio. Turning it on records your permission. It does not, by itself, publish the photo. A barber’s public portfolio is made of photos the barber uploads. The Terms require the barber to honor the flag. The app stores the choice and does not currently block a portfolio upload that ignores it.

Who can see a cut

  • You can see your own cuts, photos, child profiles, and feedback.
  • A barber you sent the cut to can see the photo and the breakdown. Your name and email stay unavailable to that barber until you mark the cut booked.
  • Anyone with the exact checkout code or QR link can open a page that shows the photo, the style name, and the breakdown, without an account. That page does not show your name. The code works like a key. Do not post it if you do not want strangers to see the photo.
  • A barber’s name, city, booth type, booking link, and portfolio photos can be viewed without an account. The public page does not display the barber’s email. Client profiles are not public.
  • We do not give client photos to a barber’s portfolio unless the barber uploads them. Consent is the client’s recorded choice about that use.

Who processes it

These are the companies the code actually sends data to. We do not list vendors we might use later.

  • Supabase stores accounts, the database, and both photo buckets, and it sends auth email. That includes names, emails, passwords in Auth, photos, cut text, child profiles, consent flags, feedback, barber profiles, and portfolio photos.
  • Vercel hosts the app and runs the daily job that sends feedback reminders. Photos are resized on that server. Vercel may keep standard host logs, which can include an IP address and the page requested. We do not add Vercel Analytics in this project.
  • Anthropic receives resized cut photos, an optional description you typed, refresh context (earlier zone text and weeks elapsed), and short correction snippets, to produce the breakdown.
  • Resend receives the client’s email, name, style name, and a link to the cut, to send the one feedback reminder.

This codebase does not choose a data-residency region for those providers. A lawyer should confirm where each one stores data.

We do not sell personal data

We do not sell personal information. We do not share it for cross-context behavioral advertising. We do not run ads in the app. The providers above process data so ChairCode can function, not so they can market other products to you on our behalf.

How long we keep it

We keep your account, cuts, photos, answers, child profiles, feedback, and consent choices while the account is open. The app does not delete old cuts or photos on a schedule. Correction snippets are capped at the 60 most recent rows, and older rows are deleted. The feedback reminder is sent once, and the cut stores the time it was sent.

Signed links to private photos expire after about one hour. The files themselves stay until they are deleted. Hosting and database backups may outlive a deletion for 30 days.

Access and deletion

Email Westerkeslie@gmail.com to ask for a copy of your personal information, to correct it, or to delete your account. There is no delete button in the app today. We will ask you to confirm that you control the account before we delete it.

Removing the login user is set up to remove the profile and, through database links, that person’s cuts, child profiles, barber profile, portfolio rows, and tool-care rows. Photos in storage are not removed by that database link alone. When you ask us to delete the account, we will also delete the photos stored for it. A barber may already have seen a breakdown. A portfolio photo the barber uploaded stays until the barber deletes that entry, or until we remove it after a request we are required to honor. We do not have a self-serve export.

Parents and guardians can ask us to delete a child profile and the cuts tagged for that child the same way.

Security

Most of the app requires a login. Consultation photos sit in a private bucket. Database rules limit which rows a logged-in person can read: you read your own cuts and child profiles, and a barber reads a client’s name and email only after that client has marked a cut booked with them. The reminder job checks a secret before it runs. Passwords are handled by Supabase Auth.

No method is perfect. The checkout code is a short code, not a long secret, and anyone who has it can view that cut’s photo and breakdown. Portfolio photos are public by design. You are responsible for keeping your password and your checkout links to the people you mean to show.

Changes

We will post changes on this page and change the effective date. If a change is material, we will also email the address on the account before the new date, when we have one. The banner at the top stays until a lawyer has reviewed the text and the placeholders are filled in.

Contact

Keslie Wester, doing business as ChairCode
Westerkeslie@gmail.com

Questions about this draft, a copy of your data, or deletion all go to that email.

ChairCode

HomeTermsPrivacySign up

Last updated November 3, 2026