Privacy Policy
This is a draft.It stays a draft until the name of whoever signs, [legal name of whoever signs], is filled in and a lawyer has read it. Anything highlighted like this is still to be decided. Questions about this policy: help@barrierline.com.
1. Who this covers
[legal name of whoever signs] runs Barrierline for pest control companies. This policy covers:
- People at those companies who use it: owners, office staff and technicians.
- The companies’ customers (homeowners and businesses), whose details a company puts in. For them, the pest company decides what’s entered and why; we keep and process it for that company.
2. What we collect
From everyone who signs in (owners, office staff and technicians): name, email and login. A person signs in with an email and password. [If Google or Apple sign-in is switched on: a person can also sign in with Google or Apple, and then we get the name and email that service shares.] Passwords are handled by our login provider; we never see them. When a phone signs in, we record its model name (for example “iPhone 15”) so the office can tell its phones apart, and we keep when each phone last reached our server (the office sees it as “active 2h ago”).
Location, once per stop: when a technician taps Start service, the phone reads its location once and works out how far it is from the stop’s address. We keep that distance, how accurate the reading was and the time, so the office can see a stop was started at the house. We don’t keep the coordinates, and the app never reads the location in the background or between stops. The same reading is used to look up the weather at the stop for the record. On the owner’s phone, the morning summary can show the day’s wind and rain, only if the owner allows the location for it. A phone can say no to location; the app still works.
Push alerts: if a person allows notifications, we keep their phone’s push address (an Expo push token; Expo passes the alert on to Apple or Google) so their alerts can reach the phone. It’s deleted when they sign out with a connection, are removed from the team, or delete their login, or when another person signs in on that phone.
Email you send us: a message to help@barrierline.com reaches our inboxes, and you get one automatic note back that it arrived. We use it to answer you.
Problem reports: when the app or the website hits an error, it sends us the error message, where in the app it happened and the app’s version, so we can fix it. No customer data. Kept 90 days.
The work itself, as the company and its techs enter it:
- customers’ names, addresses, phone numbers and email addresses, and notes about the property
- the schedule, the service done, pests, areas treated, products and amounts applied
- photos, short videos with their sound, diagrams and customers’ signatures
- the time a visit started and finished, and the weather at the stop
- each technician’s clock-in and clock-out times
- each technician’s name, applicator license number and its expiry, supervisor, and phone number
- messages between the office and the techs, with the sender’s name
- leads: which customer asked for a quote, for what, and how it went
- the days a technician is marked out
- the invoices and payments the company records (the amount, how it was paid, and a check number or the last four digits of a card if someone types one) and what each customer owes
- a log of every change sent from a phone, so a change to a record leaves a trace; a change to a finished visit’s record also keeps what the record said before
What we don’t collect:
- the phone’s location in the background or between stops, or its coordinates
- the phone’s contacts
- advertising or tracking data (the app has no ad or analytics trackers)
We never sell personal information.
3. Who handles it for us
| Who | What for | What they get |
|---|---|---|
| Supabase | The database, logins, and photo storage | Everything in section 2, stored in [the United States] |
| [Resend] | Sending sign-in emails (confirm your email, reset your password) | The person’s email address and the email itself |
| Expo, Apple and Google push services | Delivering alerts to a phone | The phone’s push address and the alert’s short text |
| Cloudflare | The domain’s DNS, and receiving email sent to help@barrierline.com and passing it on to us | Every email sent to help@ |
| Slack | Telling us that an email reached help@ | The sender’s name and address, the subject and the first lines of the email |
| [Anthropic, only if switched on] | [Suggesting a reply to an email sent to help@; a person checks and sends every reply] | [The email] |
| Expo (app updates) | Delivering fixes to the app without a new store release | Each time the app opens: the phone’s internet address, the app’s version, iPhone or Android, and a random id for this install. No customer data |
| [Google and Apple sign-in] | [Only if a person chooses to sign in with them] | [What that service shares: name and email] |
| The US National Weather Service | The weather at a stop, and the owner’s morning wind and rain | The phone’s location, rounded to about 10 meters, never a name or a record. A free public service of the US government; it has no account with us |
| The phone’s own map service (Apple or Google) | Turning a stop’s address into a point, on the phone, for the distance at Start | The stop’s street address |
| [Claude Code, made by Anthropic] | Reading the files a company sends us, on our own computer, to test moving its customers in before its private account exists | The files themselves: the company’s customers (names, addresses, phone numbers, emails), plans, past visits, balances, techs and products. We delete those copies after the company approves its move. |
| The US Census Bureau’s address service | Putting addresses on the map, once each | The street address only, never a name, a phone number or a record. A free public service of the US government; it has no account with us |
| OpenFreeMap | The streets drawn under the map | No customer data: the map asks it for the streets of the area on screen, the way any web map does |
| [Dashboard host, e.g. Netlify] | Serving the dashboard’s pages | No customer data; the dashboard talks to Supabase directly |
| Apple and Google | Delivering the phone app | Their usual app store data, under their own policies |
If we add a provider that handles personal information, we’ll update this table first.
4. How we use it
- to run the service: show each company its own work, sync phones, make reports and exports
- to help when a company asks for support
- to protect the service and fix problems
We don’t use a company’s data to market to its customers or to anyone else.
5. How it’s protected
- Everything travels encrypted (HTTPS).
- Each company can see only its own data. That’s enforced by the database itself, not only by the app.
- A phone can only send and receive its own company’s work, and the office can disconnect it at any time.
- Photos are stored privately and are visible only to the company that took them.
- A company can give each of its customers a page by link, with no password: that customer’s next visit and their last service reports (what was treated, where, with which products, and when people and pets can go back in, in the label’s words). Anyone who has the link can open it, so it’s a long random link nobody can guess, and the company can replace it at any time (the old one stops working). It never shows prices, the office’s own notes, or anyone else’s records. From it, a customer can ask to move a visit, ask a question, or rate a visit (with a note if they like); the company sees those.
6. How long we keep it
- While the company uses the service.
- The log of changes sent from phones: 90 days after each change arrives, for a change the server applied. A change the server refused (one it could not apply) is kept until the office runs it again, or as long as the company keeps its records and never less than 3 years.
- Emails to help@barrierline.com: [while we need them to answer you and follow up, and no longer than [24] months].
- The files a company sends us to move in are loaded on our own computer and read with an AI tool to test the move (section 3). We delete those copies after the company approves its move, or within [30] days of the company telling us it is not going ahead. [lawyer to confirm]
- When a company leaves, it has [90] days to download its records. Arizona makes a pest control company keep its service records for 3 years, so it should download them first. After the [90] days we delete it from the service, within [7] days, and from our backups within [35] more days. [Unless the company asks us to keep a read-only copy for its state’s record-keeping period.]
7. Your choices
- Technicians and office staff: you can delete your own login in the app’s settings (the steps are at barrierline.com/delete-account). An owner’s login can’t be deleted on its own: the owner closes the company instead, and its data is deleted after the [90] days in section 6. Records you finished stay with your company, because state law requires pest control records to be kept. You can also ask your company, or write to us at help@barrierline.com, to see, correct or delete your information.
- A pest company’s customers: your information belongs to the pest company you hired, so please ask them first. If you write to us, we’ll pass your request to them and help them answer it.
- Some service records may have to be kept by law (Arizona requires 3 years). Deleting them is the company’s decision.
8. Children
The service is for businesses and isn’t meant for children under 13.
9. Changes and contact
- We’ll post changes here and tell companies at least 30 days before a change that matters.
- Questions: help@barrierline.com, [legal name of whoever signs], [address].