Privacy Policy
Effective [EFFECTIVE DATE]
Draft — not in effect. Highlighted items are decisions still to be made. This policy has not yet been reviewed by a lawyer.
CutSight (cutsight.ai) turns a barbershop's Square bookings into figures for the shop and for each barber. It is run by [ENTITY NAME] ("CutSight", "we", "us"). This policy says what information CutSight holds, where it comes from, what we do with it, who else handles it, how long we keep it, and what you can ask us to do. Where CutSight can't yet do something you might expect, this policy says so. It goes with our Terms of Service.
1. Whose information this covers
- Shop owners who connect a Square account to CutSight.
- Barbers and other team members whose details are in the shop's Square account, including those who accept an invitation to use CutSight.
- The shop's clients, whose names, contact details and appointments are in the shop's Square account, or in a Google Calendar the shop's owner connects. Clients don't use CutSight. We hold their information for the shop; see section 9.
- Visitors to cutsight.ai.
2. What we collect
From Square, when an owner connects it
Connecting Square gives CutSight read-only access. CutSight cannot create, change or cancel anything in Square. It reads and keeps:
| What | Details we keep | What we don't keep |
|---|---|---|
| The business | Business name, country, currency, locations and their time zones | — |
| Team members | Name, email address, phone number, whether Square shows them as active, and whether Square marks them as the account owner | Anything else in their Square profile |
| Clients | Name, email address and phone number — only for clients who have a booking in a period CutSight reads, not the shop's whole client list. Where Square holds more than one record for the same person, CutSight groups them (see below). | Addresses, birthdays and notes |
| Bookings | Date, time and length, status (for example cancelled or no-show), how the booking was made, the services booked with their listed prices, and the barber | Booking notes |
| Services | Service names and listed prices | — |
| Payments, if Square grants that permission | Amount, tip, total, status, payment type and the barber | Card numbers or any other card details |
Grouping a client's records. Square often holds several records for one person. When two client records share an email address or a phone number, CutSight treats them as one person and keeps, for that person, how many records it grouped, which detail matched (email, phone or both) and how sure the grouping is. A name alone never groups two records — it can only stop a grouping, when the surnames clearly differ. Square's own records are left exactly as they are.
How far back CutSight reads, and what it doesn't update. The first time a shop connects, CutSight reads the 180 days before that day and the 60 days after. Every later sync — including one an owner starts with Sync now — reads from 14 days back to 60 days ahead. That has two consequences:
- A booking more than 14 days old is not read again. If it is moved, cancelled or re-priced in Square after that, CutSight keeps the version it already has.
- CutSight copies a client's name and contact details the first time it sees them and does not update them, so a change made later in Square does not reach CutSight.
If you need a record corrected, see section 10.
When you sign in
- Owners sign in through Square. Square tells us the owner's email address, name, business name and Square account ID, and we create the owner's CutSight login from them.
- Barbers sign in with an email address, which we use to find their login and create a one-time sign-in link.
When you agree to the terms
Which version of the Terms of Service and this policy you agreed to, when, and on which screen (an owner's sign-in or shop connection through Square, or a barber's invitation), and for a barber, which shop.
What owners enter
Rent agreements for each barber (commission rate or chair rent, caps, rent period, whether tips and no-shows count, dates and an optional note), the day the week starts, the shop's display name, and a barber's phone number or email address when the owner invites them.
When you use the CutSight Assistant
The question you ask, and how many questions you've asked that day, which CutSight uses to apply a daily limit. We don't keep Assistant conversations: the conversation stays in your browser tab and is gone when you close it. See section 4 for what the Assistant sends to process a question, and for the one place written AI output is kept.
If an owner adds a Google Calendar
A shop owner can also connect a Google Calendar from Settings, with read-only permission, for when Square won't connect. Barbers can't. CutSight then reads the calendar's events and keeps, for each appointment, the client's name, the date, the price, the client's phone number and email address where the event has them, and the appointment's status. It also keeps the access tokens Google issues, so it can keep reading the calendar. Goals and profile answers entered on that dashboard (your trade, years in the trade and weekly capacity) are stored in your browser, not by us. They are sent to our servers with each request so the dashboard can use them, and its written coaching and Assistant pass your goals, trade and years in the trade to Anthropic (section 4).
Automatically
- Server logs. Our servers record what they do: account, shop and Square IDs, sync activity, partly hidden phone numbers and email addresses, and — because CutSight doesn't yet send messages — the full text of every invitation and sign-in message, including the names in it and a working link (see section 6).
- Request records. Our hosting provider records each request made to CutSight: your IP address, your browser's identifying string, the page or address requested (without anything after a "?"), and the time. Our database and sign-in provider, Supabase, records sign-ins, sign-outs and session refreshes in its own logs, including the IP address. CutSight itself holds IP addresses only briefly in memory, to limit how many sign-in attempts come from one place.
- In your browser. CutSight stores your sign-in session, your light or dark theme, the last shop you viewed, and a few display preferences in your browser's local storage, and the Assistant conversation in the tab's session storage. During sign-in it sets two short-lived cookies that only carry the sign-in through.
CutSight uses no analytics, advertising or tracking tools.
Sensitive information
Some of what CutSight holds counts as sensitive personal information under California law, because it would let someone into an account: the access tokens Square and Google issue to CutSight, the session tokens that keep you signed in (held by Supabase and in your browser), and one-time sign-in and invitation links. We use these only to sign people in and to read Square or the calendar, and never to work out anything about anyone. CutSight holds no Social Security numbers, financial account numbers, card details or health information.
3. How we use it
Only to provide CutSight: to show owners and barbers their figures and rent and commission calculations, to answer Assistant questions, to sign people in and control who can see what, to keep the service secure and working, to fix problems, and to meet legal obligations. We don't sell personal information, we don't share it for advertising, we don't give it to anyone for their own marketing, and we don't use it to train AI models.
4. The CutSight Assistant and AI
The Assistant is an AI model. Its answers are written by Anthropic's Claude, not by a person, and every conversation opens by saying so. To answer a question, CutSight sends Anthropic the question, up to six earlier exchanges from the conversation, and the figures needed to answer it:
- On a barber's account: that barber's own figures and, when the question is about clients, for each client: their name, number of visits, last and next visit, how often they usually come, a short status label (such as overdue), their average and total spending, and whether a phone number is on file. It never sends clients' phone numbers or email addresses.
- On an owner's account: the shop's figures and each barber's figures, with barbers' names. It sends no client details.
- On the Google Calendar dashboard, the written coaching and the Assistant also send the barber's goals, trade and years in the trade if they gave them, and the coaching panels send the names of clients who seem overdue for a visit or haven't rebooked, with their visit pattern. CutSight keeps the text Claude writes for those panels, which can name those clients, and reuses it until the figures behind it change. It is deleted when the login is deleted.
Anthropic processes this under its commercial terms, which include a data processing addendum and don't allow it to train its models on what we send. Anthropic deletes API inputs and outputs within 30 days, except where it keeps them longer to enforce its usage policy (up to two years if a conversation is flagged) or where the law requires. CutSight sets a daily limit on questions, currently 25 per person.
5. Who can see what inside a shop
- The owner can see all of the shop's data in CutSight, including every barber's figures and what they owe the shop calculations, except each barber's own coaching score.
- A barber can see only their own bookings, figures and rent or commission calculation, and their own clients, including those clients' names, phone numbers and email addresses. A barber can't see another barber's data.
- A barber can see shop data only while they have accepted an invitation and Square shows them as active. When the shop marks them inactive in Square, that access ends the next time CutSight reads the shop's team. An owner can also ask us to end it. Ending access doesn't delete the barber's login: they can still sign in, but see no shop data.
6. Text messages and email
CutSight does not send text messages or emails. When an owner invites a barber, or someone asks for a sign-in link, CutSight creates the invitation or link but does not deliver it: the message, including the working link, is written to our server logs. An invitation link works for 7 days; a sign-in link works once. Server logs are kept for up to 90 days. If CutSight starts sending messages, we will update this policy first, and it will say which company sends them and how to stop them. Separately, we may write to you ourselves from presentiahair@gmail.com — for example about a change to this policy.
7. Who else handles information
Companies that process information for us
| Company | What it does for CutSight | Our terms with it |
|---|---|---|
| Supabase | Stores everything CutSight keeps, and runs sign-in. The database is in the United States (Oregon); requests to it pass through Cloudflare's network as part of Supabase's service. | Its terms of service, which include a data processing addendum |
| Railway | Runs CutSight's servers in the United States (US East), so everything CutSight processes passes through it, and keeps the server logs | Its terms of service |
| Anthropic | The AI model behind the Assistant; receives what section 4 describes | Its commercial terms, which include a data processing addendum. It may keep flagged content for up to two years (section 4). |
Where the information comes from
Square — and Google, if an owner connects a calendar — are where the shop's information comes from. They hold it already under their own agreements with the shop; CutSight reads it from them with the owner's permission and sends them nothing but those requests.
Files your browser fetches directly
When you open a CutSight page, your browser fetches fonts and code libraries directly from Google Fonts, cdnjs (run by Cloudflare), jsDelivr and esm.sh. Those services receive your IP address and browser details, as any website you fetch a file from does, under their own policies. We have no agreement with them and send them nothing ourselves.
We may also disclose information if the law requires it, to protect people's safety or our rights, or to whoever takes over CutSight, who would have to keep to this policy.
8. How we protect it
- Square access tokens are encrypted (AES-256-GCM) before they are stored. Google access tokens are not given that extra encryption; like everything else in the database, they are covered by the database's own encryption.
- Our database provider encrypts stored data (AES-256) and all traffic to it (TLS).
- Every request for a shop's data is checked against the person's role and shop, so a barber's account can only reach that barber's own data.
- CutSight never sees or stores anyone's Square or Google password, or any card details.
- Backup copies we make of the database are encrypted.
No system is perfectly secure. If we discover a breach affecting a shop's data, we will tell the owner immediately, and tell anyone else the law requires us to.
9. For the shop's clients
If you're a client of a shop that uses CutSight, your information is here because the shop keeps it in Square, or in a Google Calendar the owner connected. You can ask the shop or us about it. If you write to us at presentiahair@gmail.com, we'll handle your request ourselves, as section 10 describes, and let the shop know — or, if the shop no longer uses CutSight, simply handle it. Deleting your details only in CutSight won't remove them from Square, and CutSight will copy them again if you have a booking in a period it reads, so ask the shop to remove them from Square too.
10. How long we keep it, and your choices
How long we keep each kind of information
CutSight doesn't delete anything automatically. Server logs expire on their own; everything else below is kept until it is deleted on request, and deletion on request is done by hand today.
| Information | How long it's kept |
|---|---|
| Shop data from Square (business, team, clients, bookings, services, payments) and what owners enter | Until the owner asks us to delete the shop's data — including after the shop stops using CutSight. If an owner removes CutSight in their Square account, CutSight can no longer read new data, but it doesn't yet delete what it holds on its own; that stays until the owner asks. |
| Grouped client records (how many records, which detail matched, how sure) | Worked out again on every sync, and deleted with the shop's data |
| Logins (email address, name, and the link to a Square account) | Until the person asks us to delete their login. Deleting a shop's data doesn't delete the logins of its owner or barbers, and a barber's login stays after their access ends. |
| Sign-in in progress (a scrambled code, the page to return to, and for a signed-in person their login) | Each stops working within 10 minutes (a sign-in hand-over within 60 seconds), but the records aren't yet cleaned up: ones tied to a login are deleted with it; ones made before anyone signed in, which identify no one, are not deleted at all today |
| Square's notifications (the booking and Square account they were about, and when) | Until the shop's data is deleted. Notifications for a Square account CutSight doesn't know are dropped without being stored. |
| Records of agreeing to the terms | Until the login is deleted, including after the shop's data is deleted |
| Sensitive information (section 2) | Square tokens: until the shop's data is deleted. Google tokens: until the calendar is disconnected. Session tokens: until they expire or you sign out, and in Supabase's records until the login is deleted. Sign-in and invitation links: up to 90 days in server logs. |
| Google Calendar appointments | Until the login is deleted. Disconnecting the calendar stops CutSight reading it and deletes the tokens, but keeps the appointments already imported. |
| Assistant question counts, and written coaching kept for the Google Calendar dashboard | Until the login is deleted |
| Server logs and request records | Up to 90 days, then deleted by our hosting provider. Supabase keeps its sign-in logs under its own retention. |
| Backups | Backup copies are not yet deleted on a schedule, so deleted data can remain in a backup until that backup is deleted. Backups are used only to restore lost data. |
What you can ask us to do
Anyone — an owner, a barber, a client, or anyone else — can ask us to tell them what personal information we hold about them, to give them a copy, to correct it, or to delete it. An owner can also ask us to delete all of their shop's data. A shop can't exist in CutSight without its owner's login, so deleting an owner's login means deleting their shop's data too; we'll say so before we do it. Write to presentiahair@gmail.com. We may need to confirm who you are first, usually by replying to the email address we hold for you. We'll do what you ask, or explain why we can't, within 45 days, and tell you when it's done. We won't treat you differently for asking.
California
The California Consumer Privacy Act gives California residents the rights described above: to know what personal information a business collects, uses and discloses, to delete it, to correct it, and not to be treated differently for using these rights. CutSight doesn't currently meet the thresholds that make that law apply to us, but we honour those requests from anyone. In the past 12 months we collected the categories in section 2 — identifiers and contact details; commercial information (bookings, services and payments); information about work (the rent agreements owners enter); the figures and scores CutSight works out from these; sensitive personal information (account credentials, as section 2 describes); and technical information — from the sources and for the purposes this policy describes, and disclosed them only to the companies in section 7. We have not sold or shared personal information, and we don't use sensitive personal information to infer anything about anyone. You can make a request yourself, or through someone you authorise.
California's "Shine the Light" law lets residents ask which third parties a business has given personal information to for their own direct marketing. CutSight hasn't given anyone's personal information to anyone for that.
Do Not Track
CutSight doesn't track people across other websites and doesn't let anyone else do so through CutSight, so it treats every visitor the same whether or not their browser sends a Do Not Track signal.
11. Children
CutSight is for businesses and is not meant for anyone under 18. A shop's Square account can include clients who are children, and CutSight holds their details as described here, on the shop's behalf. We don't knowingly collect information directly from children.
12. Where information is held
CutSight is offered only to businesses in the United States. Its database and servers are in the United States (section 7), and the companies that process information for it are US companies.
13. Changes to this policy
We'll update this policy when CutSight changes what it collects or how it uses it, and show the new effective date at the top. If a change matters, we'll write to owners and barbers at the email address on their account at least 30 days before it takes effect.
14. Contact, and other formats
[ENTITY NAME] · [BUSINESS ADDRESS] · presentiahair@gmail.com
If you need this policy in another format — for example because of a disability — write to us and we'll provide it.