Draft, not yet in effect. This page is waiting for review by a lawyer. Highlighted parts still need to be filled in.
RepairDoc legal
Privacy Policy
Last updated 29 October 2026
The short version
- We collect what's needed to run RepairDoc: your account, your shop's records and basic technical data.
- If you're a repair shop's customer, the shop decides what's collected about you. RepairDoc processes it for them.
- We don't sell personal information and we don't use advertising or tracking cookies.
- Phone numbers and text consent are never shared with anyone for marketing.
- You can ask to see, fix, export or delete your data.
1.Who we are and what this covers
Company legal name ("RepairDoc", "we") makes RepairDoc, a point-of-sale and repair app for repair shops. This policy explains how we handle personal information when you visit our website, sign up, or use RepairDoc, and when RepairDoc processes information for the shops that use it.
Two roles. For our own website and for shop owners' and staff accounts, we decide how data is used (we're the "controller"). For the information a shop keeps about its customers and team, such as repairs, sales, phone numbers and chats, the shop is in charge and we process it on the shop's behalf (we're a "processor" or "service provider"). If you're a shop's customer, the shop's own privacy notice applies too, and you can contact the shop directly.
2.What we collect
- Shop owners and admins
- WhatName, email, password (stored hashed), business name, addresses, tax and opening hours, plan and billing details
- Where it comes fromYou, when you sign up and set up
- Staff
- WhatName, role, PIN (stored hashed), clock-in and break times, schedules, sales and repairs they handled, and pay rate if the owner adds one
- Where it comes fromThe shop and the staff member
- Shop customers
- WhatName, mobile number, email, devices, IMEI or serial number, repair notes, passcode if given, check-in photos, quotes, purchases, chat messages and files, text preferences, review link taps
- Where it comes fromThe customer (QR check-in, kiosk, chat) or shop staff
- Card payments
- WhatAmount, status, card brand and last 4 digits, provider reference. Never the full card number
- Where it comes fromStripe or Square, when the shop connects one
- Everyone
- WhatIP address, browser and device type, pages used, error logs, and the cookies described in our Cookie note
- Where it comes fromYour browser, automatically
- Connected apps
- WhatWhich app was connected, when, by whom, and what it did
- Where it comes fromThe connection flow and the actions it takes
| Who | What | Where it comes from |
|---|---|---|
| Shop owners and admins | Name, email, password (stored hashed), business name, addresses, tax and opening hours, plan and billing details | You, when you sign up and set up |
| Staff | Name, role, PIN (stored hashed), clock-in and break times, schedules, sales and repairs they handled, and pay rate if the owner adds one | The shop and the staff member |
| Shop customers | Name, mobile number, email, devices, IMEI or serial number, repair notes, passcode if given, check-in photos, quotes, purchases, chat messages and files, text preferences, review link taps | The customer (QR check-in, kiosk, chat) or shop staff |
| Card payments | Amount, status, card brand and last 4 digits, provider reference. Never the full card number | Stripe or Square, when the shop connects one |
| Everyone | IP address, browser and device type, pages used, error logs, and the cookies described in our Cookie note | Your browser, automatically |
| Connected apps | Which app was connected, when, by whom, and what it did | The connection flow and the actions it takes |
We don't ask for and don't want sensitive information such as health data, government ID numbers or full card numbers. Please don't put them in notes or chats.
3.How we use it
- To run RepairDoc: sign-in, sales, repairs, check-in, tracking pages, chat, schedules, reports and exports.
- To send messages the shop or you asked for: repair texts, sign-in codes, receipts and account emails.
- To keep RepairDoc secure: preventing fraud and abuse, protecting accounts, and keeping audit logs.
- To support you and improve RepairDoc, using account data and usage data. We prefer aggregated or de-identified data for this.
- To bill shops and meet our legal obligations.
If you're in the EU or UK, our legal bases are: performing our contract with you, our legitimate interests in running a secure and useful service, your consent where we ask for it (you can withdraw it any time), and legal obligations.
4.AI features
When a shop owner asks the RepairDoc assistant a question, we send the question and the shop data needed to answer it (for example sales totals or repair counts) to our AI provider, Anthropic, which returns the answer. The assistant can only read what that person's role is allowed to see. Under our agreement, the provider may not use this data to train its models. Lawyer: confirm.
If a shop connects an outside AI app (such as Claude or ChatGPT) through our connector, that app receives the data the owner allowed, and handles it under its own privacy policy.
5.Text messages
Shops can text customers about their repairs only when the customer agreed, for example by turning on "Text me updates" at check-in. Message frequency varies (about 2–6 texts per repair). Reply STOP to any text to opt out, or HELP for help. See the Text message terms.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent are not shared with any third parties, except the service providers that deliver the messages for us.
7.How long we keep it
We keep shop data while the shop's account is open. After an account closes we keep it for 30 days so the owner can come back or export it, then delete it. Backups roll off within 35 days. Billing records are kept as long as tax law requires.
Inside a shop, the owner controls customer records and can edit or delete them. Customer sign-in sessions last up to 90 days; staff and owner sessions up to 30 days.
8.How we protect it
Each shop's data is kept separate and every request is checked against the signed-in business. Passwords and PINs are stored hashed. Payment provider keys are encrypted. Data travels over HTTPS. RepairDoc team accounts need two-factor login, support access is read-only, and every team action is logged. No system is perfectly secure, and we'll tell affected shops and people about a breach as the law requires.
9.Your choices and rights
Depending on where you live, you may have the right to access, correct, delete or export your personal information, to object to or restrict some uses, and to withdraw consent. US state laws (such as California's) give you the right to know, delete, correct and opt out of sale or sharing. We don't sell or share, so there's nothing to opt out of, and we won't treat you differently for using your rights.
Shop owners and staff: ask us at privacy email. Shop customers: contact the shop first, since it controls your repair records; if you contact us we'll pass your request on. You can always stop texts by replying STOP.
We'll confirm your identity before acting, and answer within the time the law sets (usually 30 to 45 days). You may use an authorized agent. If you're in the EU or UK you can also complain to your data protection authority.
10.International transfers
RepairDoc is run from the United States and our providers may process data in other countries. When we move personal data out of the EU, UK or Switzerland, we use safeguards such as the European Commission's Standard Contractual Clauses.
11.Children
RepairDoc is a business tool and isn't directed at children. We don't knowingly collect information from children under 13 (or 16 where that's the rule). If a child's information was entered by a shop, contact the shop or us and we'll help remove it.
12.Changes to this policy
We'll post any change here with a new date. If a change is significant we'll tell shop owners in the app or by email before it takes effect.
13.Contact
Company legal name, Mailing address. Privacy questions: privacy email.