FieldNest is licensed to companies, not sold to the public, and it is built to hold as little about a person as it can. This page says what this website collects, what the portal collects, and what happens to a company’s own records. Last updated 4 October 2026.
There is no tracking on this site of any kind. No analytics, no advertising, no pixels, no session recording, and nothing at all loaded from anybody else’s server — every page here is plain HTML sent by us, and it runs no JavaScript.
The public pages set no cookies, so there is nothing to consent to and no banner to click.
Like any website, ours runs on a host (Render) that keeps ordinary server logs of requests: the network address a request came from, which page, the time, and whatever the browser says about itself. They are used to keep the service running and to look into faults, they are kept for a short period, and they are used for nothing else.
What it collects: your name, your company and its address, your email address and telephone number, roughly how many people would use FieldNest, and anything you write in the message box.
What happens to it: it reaches FieldNest and a person replies to you. Nothing is created — no account, no company, no charge. It is never sold, never shared with anybody else, and never used for advertising or added to any mailing list.
How long: we keep it while we are talking, and after that until you ask us to remove it. Ask in your reply to us, or send the form again saying so, and it goes.
The portal has three cookies. __Host-fn_portal keeps a
company’s administrator signed in; __Host-fn_owner
does the same for FieldNest’s own sign-in, and a browser only ever
holds the one for whoever signed in on it. Each is marked
http-only, secure and same-site, holds a signed session number and
nothing else, and stops working when the person signs out, after 30
minutes with nothing done, or 8 hours after signing in.
__Host-fn_known signs nobody in: it remembers, for 180 days,
that this browser has signed in to that account before, so that
somebody guessing at the password from elsewhere cannot keep its owner
out. It holds a signed account number and nothing else. All three are
what privacy law calls strictly necessary — without them, signing
in cannot work, or cannot be kept safe.
There are no other cookies and no analytics.
The portal runs no JavaScript, with two exceptions: the page where
an administrator fixes the boxes on an uploaded document loads one small
script from this site (/static/box-editor.js) so the boxes
can be dragged with a mouse; it is our own and it talks to nobody. And
the page where an administrator places a job’s plan on the map
loads our own /static/plan-placer.js and Apple’s
MapKit JS, from Apple, to show Apple Maps — only once the company
has set Apple Maps up, and only on that page. Apple sees the map being
viewed, as with any Apple map; nothing about the company’s people
is sent to it. Every other page tells the browser to refuse any script
at all.
Two-step sign-in. FieldNest’s own sign-in, and a company’s chief and full administrators, give a six-digit code from an authenticator app after the password; a company can require it of every administrator. The app’s key is kept on our server so the code can be checked, and the recovery codes are kept only as fingerprints that cannot be turned back into the codes.
Change history records what each administrator does to their own company, including anything FieldNest itself does. That record belongs to the company and is visible to its administrators.
Employee records, jobs, documents, photographs and messages belong to the company that licenses FieldNest. We hold them so the app works, on that company’s behalf, and for no purpose of our own. Every company is walled off from every other one by the database itself.
We never sell or share personal information, show advertising, profile anybody, or use one company’s records to do anything for another.
How long they are kept is the company’s choice. Unless an administrator chooses a period, nothing is deleted. A company can set how long messages, call records and the location an emergency alert was raised from are kept; past that they are deleted within minutes, and the change is in its change history.
An administrator can take everything out at any time — Take your data out in the portal produces a zip of ordinary spreadsheets, with no approval needed from us.
FieldNest can reset an administrator’s password, because a company whose only administrator has left needs a way back in, and that reset is written into their change history.
When FieldNest support helps a company, it can open that company’s portal. Opening it is written into their change history, every page it sees says so, and anything it changes is recorded as FieldNest support rather than as any of the company’s people. It cannot open the company’s documents or take the data export unless the company’s chief administrator has switched on Let FieldNest support see documents and exports, which is off unless they turn it on. It cannot read messages at all.
What the app asks a phone for — the camera, photographs, location — is decided by the company that licenses it and set in the portal, and the phone still asks the person before granting any of it. The app never reads the contacts on a personal phone, and never reads a personal calendar: the Coworkers list and the company calendar are the company’s own.
Two things in FieldNest watch people rather than help them work. Both are off unless the company turns them on, turning either on asks an administrator to confirm that their people have been told, and every change is in the company’s change history and on the portal’s Monitoring page.
Live location. Where each person is right now on the job site, shown to the roles the company chooses and to its administrators. Only on the job site and only during the working day the company sets. Company phones share it automatically; a personal phone only if its owner turns it on. Only the latest position is kept — never a trail. It stops being shown fifteen minutes after the phone last reported, and the phone removes it when it leaves the site or the working day ends. Everyone can see who can see them.
Showing where you are, by choice. Separately, a person can choose to show their own live position on the map to people they pick — named coworkers, or everyone in their own company on FieldNest, never anybody outside it — for as long as they pick, and stop it at any time. It goes directly to phones nearby over FieldNest’s own locked link, and through the company’s FieldNest service to the people they picked and nobody else. Only the latest position is kept — never a trail — and it is deleted when they stop, when their time runs out, or an hour after their phone last reported. If the company asks for it and the job’s plan has been placed on the map, it also stops when they leave the job site. Starting and stopping are written in the company’s change history.
The Wing activity record. Wing is the web browser inside FieldNest. With the record on, the phone sends the site and page of each address opened in Wing — never the rest of the address — and the searches typed there, to the company’s own FieldNest service and nowhere else. The company’s administrators can read them, and every time one opens a person’s record it is written in the company’s change history. FieldNest support cannot read it. Nothing outside Wing is recorded, and the service keeps nothing while the record is off. Each line is kept for the number of days the company sets, normally 90, and then deleted, and the phone tells the person that Wing is being recorded. The company also sets Wing’s filter, the sites it allows and the search engines it offers.
If you have written to us through this site, you can ask what we hold about you, ask for a copy, ask us to correct it, or ask us to delete it. California residents have those rights under the CCPA; we give them to everybody. We do not sell or share personal information, so there is nothing to opt out of, and nobody is treated differently for asking.
If your employer uses FieldNest and your question is about your own employee record, ask your company’s administrator — those records are theirs, and we act on their instructions.