Privacy policy
This policy explains what information BroncoDesk keeps, why, where it is kept, who can see it and how long it is kept. BroncoDesk is the office and dispatch system of Bronco Home Solutions LLC (“we”, “us”), a garage door and locksmith service company. The policy covers the website broncodesk.com, the BroncoDesk web app our staff use and, from its release, the BroncoDesk iPhone app (section 11).
In short
- BroncoDesk is used only by our staff. There is no public sign-up.
- We keep what we need to run service jobs: staff accounts, customers’ names, phone numbers, addresses and notes, jobs, payments, schedules and their history.
- For a card payment we keep only the last 4 digits of the card. BroncoDesk refuses full card numbers.
- We do not sell information. BroncoDesk shows no ads and uses no analytics and no tracking cookies.
- Outside the company, information goes only to the services that run BroncoDesk for us, to the provider of our AI assistant (the Bot) for what it adds and reads, to a partner company for the jobs we do with it, and where the law requires it (section 6).
- To see, correct or delete your information, write to support@broncodesk.com.
1. Who uses BroncoDesk
BroncoDesk is a work tool for the staff of Bronco Home Solutions LLC: the administrator, the office assistant, dispatchers, managers and technicians. Accounts are created by our administrator, who can also give an AI assistant (the Bot) its own limited account (section 6). Our customers do not use BroncoDesk themselves: our staff enter a customer’s details when the customer asks us for service, or when a partner company passes a customer’s service request to us.
2. What we keep
Staff accounts
- E-mail address and password, to sign in. Sign-in is handled by Supabase Auth. The password is stored only in a scrambled form (a hash), so nobody at the company can read it. The sign-in service also records sign-in activity, such as the time and the device’s internet address (IP address), to keep accounts secure.
- Name and role, and which areas, teams or technician record the account may see.
- The BroncoDesk version the person used last, and when.
- The staff agreement the person accepted in BroncoDesk: the name they typed, the version and the time.
- Work details: a technician’s name, phone number and e-mail address, pay rate, schedule and time-off requests, weekly reports; pay records (amount, date and how it was paid, for example cash, check or Zelle).
Customers and jobs
- Customer: name, phone numbers, service addresses, notes, and labels the office adds (for example “VIP” or “prefers cash”).
- Job: the service requested, the date and time, the technician, the status, the price, the parts used and notes; the company the job is for and, when the job came with one, its reference number (for example a partner company’s lead number).
- Payment: the type (for example cash, check or card) and the amount. For a card, only the last 4 digits, the name of the card processor and its transaction reference. BroncoDesk refuses to save a full card number.
History of changes
For every change, BroncoDesk records who made it, when, and what changed (the old and the new value). This lets the office undo mistakes and check what happened. When someone prints, downloads or copies records out of BroncoDesk, that is recorded too.
The Bot account
For everything the Bot does, BroncoDesk records when, which way it connected (and with which of its keys), what it did and the result. For a customer search it records only the last 4 digits of a phone number or the name as typed, and which customer cards it was shown (not copies of them). For a job search it records only the job number or Job ID, the last 4 digits of a phone number, the house number and the first word of the street, or the name as typed, and which jobs it was shown. It never records message texts, notes, full phone numbers or the keys themselves.
3. What we do not do
- We do not sell or rent information, and we do not share it for advertising.
- BroncoDesk shows no ads and uses no analytics, no tracking pixels and no advertising or tracking cookies.
- The About, Privacy and Support pages set no cookies and run no scripts.
4. What BroncoDesk keeps on your device
When staff use the BroncoDesk web app, their browser keeps:
- the sign-in (a sign-in token in the browser’s local storage), so you stay signed in until you sign out;
- a copy of the records you are allowed to see (in the browser’s own database), so BroncoDesk opens fast and works without internet. Changes made offline wait there until they are sent. Signing out removes these records from the device;
- your changes not yet sent and your unfinished forms, in your own part of the device’s storage: they stay after you sign out (the sign-out asks first) until your next sign-in on that device, when they are sent; they are never sent with someone else’s sign-in;
- the app’s own files (through a service worker), so it loads fast and updates itself;
- small settings, such as Light or Dark mode, the report period you chose and which tips you have already seen. The Light or Dark choice is also kept in a small cookie of our own site, one per person who uses the device, named by an anonymous key (not your name or e-mail), so it is not lost. The browser sends these cookies with every visit to broncodesk.com, including these three pages, which do not use them. These settings stay on your device.
5. Where the information is kept
- Supabase (our database and sign-in service): the BroncoDesk database is in the United States (US West, Oregon). Supabase also keeps its own daily backups of it.
- Cloudflare delivers the website and the app’s files, and keeps our outside backup copies in Cloudflare R2 storage, in the company’s own Cloudflare account. Cloudflare encrypts everything stored in R2. Cloudflare also forwards e-mail sent to support@broncodesk.com to our mailbox and sends backup alerts to our administrator.
- Google keeps our mailbox: Cloudflare forwards the e-mail sent to support@broncodesk.com to the company’s Google mailbox, where our answers are kept too. Supabase’s sign-in service sends the password recovery e-mails.
- jsDelivr and Google Fonts: the web app loads two open-source parts (the Supabase sign-in library and an icon set) from jsDelivr, and its typeface from Google Fonts. Like any website, these services see your device’s IP address and browser type when the app loads them. No BroncoDesk records are sent to them.
- Google Maps: when staff tap a job’s map or directions link, the job’s address is opened in Google Maps, where Google’s privacy policy applies.
- The Bot’s AI provider: when our administrator connects the Bot (an AI assistant, xAI’s Grok Bot), what the Bot adds and what it reads from BroncoDesk passes through its provider, xAI, which says it keeps API requests for 30 days by default and does not train its models on them; the Grok Bot app also passes it through Cursor, which runs its connections. The requests to BroncoDesk’s Bot connection may also be kept for a short time in the logs of our database host, Supabase, which only our administrator can see.
- The company’s own computers and storage: the full copies of the database the administrator downloads (Setup → Backup → Download everything), the copy made by the monthly backup check, and the reports and files staff download or print from BroncoDesk (for example a weekly report as an Excel or PDF file). The full copies hold every record; they are kept only on the administrator’s company computer, and are never e-mailed or shared.
Information travels between your device and these services over encrypted connections (HTTPS). Like any web host, the services that run BroncoDesk handle technical information such as IP addresses and browser types when you connect, to deliver the pages and keep them secure. They handle our information only to provide their services to us, under their own terms and privacy policies, and we use them only on terms that protect our information at least as well as this policy describes.
6. Who can see what
What a person can see depends on their role. The database server itself enforces this, not only the screens.
- The administrator sees everything. The office assistant sees the office’s work: all jobs, customers, payments and reports. Some settings, such as backups, are for the administrator only.
- Dispatchers see the jobs and customers, the payments on jobs, and the technicians’ schedules and contact details (name, phone number and e-mail address; not their pay percentage), so they can book and send jobs.
- Managers see the jobs, technicians and reports of their own teams and areas, and the contact details of their own team’s technicians.
- Technicians see only their own jobs, their own schedule and their own report. The administrator can hide customers’ phone numbers from a technician.
- The Bot account (an AI assistant the administrator can connect) adds new jobs, sees who is on shift and finds customer cards. Who is on shift: the technicians’ names, trades, skills, companies and shift hours; never their phone numbers, pay, locations or jobs. A customer card: the name, phone numbers, addresses and recent jobs, without money, payments or notes. It may also look up any job by its number, its Job ID, the customer’s phone number, address or name, and list the jobs added on a day or still open. For a job it sees the number, the Job ID, the service, company, metro, status, day and time window, the address (not in a list), the customer’s name (only when it looks the job up by its number) and the first name of the technician once one is chosen; never money, payments, notes or the customer’s phone number. It may fill in a missing Job ID on a job it added, correct such a job or add a note to it while nobody has taken it yet, pass questions about any job to the office, and send a team cost that counts only after the office checks and adds it. It cannot change or delete anything else, it is limited in how much it can do each hour and day, everything it does is recorded for the administrator, and anyone in the office can stop it.
Outside the company, information goes only to:
- Partner companies, for their own jobs. Some jobs we do for a partner company, or receive from one. For such a job, that company gets the details needed to settle it with us, such as the job number and its reference number, the date, the technician’s name, the service address, the price, the parts, the payments and what each side is owed. A partner company does not get the details of other jobs.
- The service providers in section 5, which run BroncoDesk for us.
- The Bot’s AI provider (section 5), for what the Bot adds and reads, once the administrator connects the Bot.
- Anyone the law requires us to give it to, for example under a court order.
We give partner companies and service providers only what this policy describes, and we require them to protect it at least as well as this policy does.
7. How long we keep it
- Business records (customers, jobs, payments, schedules, reports and their history) are kept to run the business and for our tax and accounting records. BroncoDesk never deletes them by itself: they stay until the office deletes them, for example after a request under section 8, and then go to the Trash.
- The Trash: a deleted record first goes to the Trash, where it can be restored for 30 days. After 30 days the nightly run deletes it for good, with its history. A record that other kept records still need (for example a technician named on a kept job) stays until it is no longer needed.
- Accepted staff agreements are kept as a permanent record.
- The Bot account’s activity record: 90 days, then the nightly run deletes it.
- Backups of the whole database are kept so that nothing is lost by mistake:
- inside the database: the nightly copies of the last 14 days;
- Supabase’s own daily backups: 7 days;
- outside copies in Cloudflare R2: the last 30 nightly copies, one monthly copy for 7 years (tax records), and hourly copies of the changes for 8 days.
- Copies on the company’s own computers: the administrator keeps the newest full downloads as an extra backup and deletes older ones; the copy made by the monthly backup check is deleted after the next month’s check. Reports and files staff download are kept like the company’s other business papers.
- On a device: the records until you sign out; changes not yet sent and unfinished forms until they are sent at your next sign-in there; the small settings until you clear the browser’s data.
8. Seeing, correcting or deleting your information
You can ask us to show you the information we keep about you, to correct it, or to delete it. Write to support@broncodesk.com. We may ask you to confirm who you are. We may need to keep some records, for example payment records we must keep for tax purposes; if so, we will tell you. Staff can also ask their administrator.
9. Security
- Encrypted connections (HTTPS) to the website and the database.
- Passwords stored only as hashes; access by role, enforced by the database server.
- A record of every change, and full card numbers refused.
- Backups with two separate companies (Supabase and Cloudflare); every outside copy is read back and checked after it is made, and restoring them is tested.
No system is completely secure. If something happens that affects your information, we will tell you as the law requires.
10. Children
BroncoDesk is a work system for adults. It is not meant for children, and we do not knowingly collect information from children under 13.
11. The iPhone app (applies when the app is released)
This section applies from the day the BroncoDesk iPhone app is released. The app is for our technicians. It works like the web app, with these additions:
- Notifications: to alert a technician about job offers, the app asks the iPhone for permission to send notifications. If the technician allows them, Apple’s push notification service gives the app a device token, which we keep in our database with the technician’s account and the phone’s notification settings, the iPhone model (such as iPhone18,3, never the phone’s own name), the iOS version and the app’s version and build, so the office can see whether alerts will reach the phone. Notifications are delivered through Apple. They can be turned off at any time in the iPhone’s Settings.
- Job offers: each job offered to a technician and the answer (accepted, passed with an optional reason, or not answered) with its time, when the app was last open on the phone, a note when an offer reached the phone (or reached a phone where the technician is no longer signed in), and the result of the alert test. The office sees these to send jobs.
- Jobs on the phone: like the web app, the app keeps a copy of the technician’s own jobs on the phone so it works without internet. Signing out removes it.
- Photos (optional): a later version will let a technician take or add photos of a job. The app uses the camera or the photo library only when the technician chooses to. The photos are kept in private storage in our Supabase project and can be seen by the staff who can see that job.
- No location tracking: the app does not collect the phone’s location. If we ever add a feature that uses location, or any other new kind of information, we will update this policy before that feature is turned on. We will also update it before any new service provider gets information (for example a phone call service for job alerts, or another notification service).
- No ads, no analytics, and no tracking across other companies’ apps or websites.
- No outside parts: the app carries its typeface and its program parts itself; unlike the website (section 5), it does not load them from Google Fonts or jsDelivr.
- A link to this policy is in the app, where a signed-in technician can open it.
Apple’s own privacy policy applies to Apple’s services, such as the App Store and notifications.
12. Changes to this policy
When this policy changes, we update this page and its “Last updated” date. For important changes we also tell our staff in BroncoDesk.
13. Contact
Bronco Home Solutions LLC
E-mail: support@broncodesk.com
