The documents, and what each is for
Four documents. The privacy policy is the one most people want, the terms are the one procurement wants, and the sub-processor list is the one a security review asks for by name.
Privacy policy
UpdatedWhat the apps, the cloud service and this website collect, the legal bases for it, how long it is kept, and the rights you can exercise over it.
Terms of service
UpdatedPlans, seats and billing; ownership of your season; the safety terms governing machine control; warranties, liability and how either side ends the agreement.
Acceptable use policy
UpdatedThe limits on how Fieldbase may be used: the service itself, other people's data and land, and the safety rules governing machine control.
Sub-processors
UpdatedThe dated list of every third party that touches data on our behalf, what each receives, where it sits, and how to be told before the list changes.
Who you are dealing with
Fieldbase is made by b0gy LLC, a Nevada limited liability company based in Las Vegas, Nevada, United States — the same company behind b0gy.com. These documents cover Fieldbase. The ones at b0gy.com cover that company’s other products, and neither set applies to the other.
Where to send what
| What you need | Where |
|---|---|
| A privacy question, or a request about your own data | privacy@fieldba.se |
| Contracts, notices, a data processing addendum | legal@fieldba.se |
| A vulnerability report, or permission to run a penetration test | security@fieldba.se |
| Anything else at all | hello@fieldba.se |
If your security review needs more than these pages hold — a questionnaire to complete, a DPA to sign, or a dedicated hosted instance in a particular region — that is the Enterprise conversation, and a person who can answer it will reply. The Security page is written for the same reader and covers sign-in, encryption, device controls and how you leave.