Draft: a plain-language draft that a lawyer hasn't reviewed yet. It may change before it's final.
Data processing agreement
For a business (a "shop") that needs a data processing agreement (DPA) for its employees' personal data in HQ, one is available on request. Email formbusters5000@gmail.com with your business's name.
What it says, in short
- Roles. The shop decides whose data is in HQ and why. Formbusters LLC, a Texas limited liability company, processes it for the shop, as its service provider.
- Purpose. We process the shop's data only to provide HQ to the shop, and never sell it or use it for advertising.
- Personal data. The names, mobile numbers, roles, work email addresses (if the shop's admins add them) and birthdays (the month and day only, if a person adds theirs) of the shop's people, their profile pictures and devices, the group chats they start or are added to, what they send and post in HQ, the documents its admins add, the van service records its people make in Field, with their photos, and its vehicles' daily odometer readings, the receipts its people send in Field, with their photos, the parts requests its people send in Field, with their photos, the van inspections its people make in Field, with their photos, the license and card expiry dates it keeps for its people (and card photos, if it turns them on), the toolbox talks it posts and its people's sign-offs, the incident reports its people send in Field, which can include health information about an injury, with their photos, its people's check-ins (times, notes, and a location only when shared), whether a vehicle left or entered one of the shop's Samsara areas, when a shop uses the Helper, and the messages each person saves and the drafts they leave, which only they see, and a record of what the shop's admins do in it (who, what, to whom and when; never what was written), as the privacy policy describes.
- Confidentiality. Only the people who run HQ can reach the data, only when they need to (support, legal reasons, reviewing reports), and they keep it confidential. To make a link's card, our server visits the web page a chat message links to, once; that website sees the address and nothing else.
- Service providers. Railway (servers and database), Cloudflare (file storage, encrypted so it can't read it), Backblaze (encrypted backup copies of the database and of the files, which it can't read), Apple (iPhone and iPad notifications, which from build 37 carry no message words, except check-in and incident-report alerts, which carry a person's name, a time or a report's kind, Siri if you use it, and street addresses for a location you share), and, for HQ on computers, Google and Microsoft (browser notifications, encrypted end to end). We'll tell the shop before adding another.
- Where the data is. The shop's data is stored in the United States.
- Security. Encryption in transit, sign-in secrets stored only as one-way hashes, and each shop's data kept apart from every other shop's by the database itself. Incident reports are seen only by the shop's owner and its safety person, and a backup if the owner names one.
- Breaches. We tell the shop without undue delay if its data is affected by a security breach.
- Requests. We help the shop answer its employees' requests to see or erase their data. Employees can also delete their own accounts in the app.
- End of service. When the shop closes, its owner can export its data, and it's erased 30 days after closing, or once we've reviewed any report in it still waiting for us then (and from our backups within 27 days more).