On this page
- 01We never sell your data
- 02The data belongs to your company, not to us
- 03Your account and your company
- 04Your location
- 05Live tracking and its limits
- 06Hours, clock-out answers and injuries
- 07Photos and files
- 08The File Vault, and who opened what
- 09Company files and your employee file
- 10Looking at a drawing together
- 11Dictating a daily log or an estimate’s job
- 12Phone numbers and text messages
- 13Messages between your coworkers
- 14Pay rates and job money
- 15Paying for FieldLink
- 16Estimates, invoices and your Parts & Labor List
- 17The phone you work on
- 18What FieldLink AI reads and what it does not
- 19Email in and out
- 20Visiting our website
- 21Cookies and browser storage
- 22Signing in and staying signed in
- 23Who sees what inside your company
- 24The companies that help us run it
- 25How long we keep it
- 26Getting a copy of your data, or deleting it
- 27Keeping it safe
- 28Children and changes to this page
01 // Where we stand
We never sell your data
FieldLink is sold to contractors for one flat price, and that is the only way we make money. The information in it is not a second product, and there is no version of this product in which it becomes one.
We do not sell personal information. Not to a data broker, an advertiser or anyone else, at any price. We do not rent it, trade it or include it in a deal, and there is no anonymized copy of your records for sale.
No advertising and no trackers. No advertising network, no tracking pixel, no third-party analytics package and no crash-reporting service in FieldLink - not on the website and not in the phone apps. We count page views on our public pages without storing your IP address or knowing who you are, as explained below.
Your company owns its records. We only process them. We hold them to run FieldLink for your company and to help when someone asks. We do not mine them to build a profile of anyone, and we do not sell such a profile as "insights".
Who sees it: the people at your company, according to their role and permissions, and FieldLink support. A named FieldLink administrator can enter your company’s account to help you. Support staff get no more access than one of your admins has, never HR, and less wherever this page says so, and every entry and exit is recorded under their name.
The outside companies we use are suppliers, not customers. The suppliers run parts of the service for us: the database, email, the robot check, FieldLink AI that reads receipts, the maps and address lookups, the weather service, Intuit when your company connects QuickBooks Online, and Stripe and PayPal when your company pays for its plan. Every supplier gets only what it needs for its job. None of them pays us in your data or may sell it on. The suppliers are listed below, with what each one gets.
Location has firm limits. FieldLink reads your GPS when you punch, and when you do something that records where it happened, like a work photo or checking out a tool. FieldLink shows your position on your company’s live map only if your company turns that on, only if you agree and only while you are clocked in with the app open. Nobody is followed off the clock or on a day they do not work. We are not building a record of where anyone goes, and we would not sell one if we had it.
We never volunteer anything to a government. Nothing is handed to any federal, state, county or city agency without valid legal process served on us: a warrant, a subpoena or a court order. No standing arrangement with anyone, no bulk feed and no back door in FieldLink.
When a legal demand arrives, we narrow it to exactly what the law compels and hand over nothing beyond that. We push back on any demand that reaches past a fair reading. Wherever the law allows, we tell the company whose records are being demanded.
We have no interest in being a source of information about people. The best protection we can offer is not collecting or keeping information for that purpose in the first place, which is what most of this page is about.
02 // Whose data
The data belongs to your company, not to us
FieldLink is software your company rents. Everything entered into it (hours, photos, receipts, customers, job records) belongs to your company, and we hold it for your company. In privacy law terms, your company is the controller of that information and we are the processor.
If you work for a contractor, the records FieldLink holds about you belong to your employer, so your employer decides what happens to them. We will help one of you find out what is held, and we never hand one company’s records to anyone else.
Every record in FieldLink is tagged with the company it belongs to, and the database refuses to give it to anyone outside that company. The separation is a rule in the database itself, not a setting anyone can switch off, and we test it on every release.
03 // Accounts
Your account and your company
FieldLink keeps what your company needs to run its crew, and no more. No place in FieldLink for your date of birth, your home address, a bank account or card number, a driver’s license number or any other government ID number. Your company’s own records can still show things like these: a customer’s service address is often a home, and a document your company files in your employee file can show a date of birth or an address.
Your name, work email and phone number. Your email is how you sign in and how we reach you. The phone number is optional for most people and lets your company reach you about work.
A notification email, if you add one. You, or your company’s office, may add a second email address for your alerts and reminders. FieldLink keeps it with your profile until it is changed or cleared. While the box is empty, alerts go to the email you sign in with. Signing in and password emails always go to the sign-in email.
Your password. Our hosting provider’s sign-in service stores it only as a scrambled hash. Nobody at FieldLink or at your company can read it. An owner or admin can only send you a reset link or set a new password.
Your profile picture, if you add one. The picture is kept in private storage and never shown on a public page.
Your language. Whether FieldLink shows you English or Spanish, or follows your phone’s or browser’s own language, is kept on your account and on your device, with the language the app last showed you, so FieldLink speaks to you in it on every device. Only you change it. The choice changes only what you read: the estimates, invoices, reports and emails your company sends its customers and general contractors stay in English.
Your role and permissions. The role and permissions decide what you can open. An owner or admin can switch a module off for you.
Your company’s own details: its name, trade, logo, business address, phone number, email address and website, plus its web address on sagetechfieldlink.com, the crew size it signed up for and the settings it chooses. Its name, logo and contact details are printed at the top of the reports your company sends its customers and general contractors.
When you were last active. While the app is open, it marks the time on our server. The stamp is how your office sees who is online and how we tell a quiet account from a busy one. The mark is a timestamp and nothing else: it does not say which screen you were on. The places FieldLink records you opening something are the File Vault, Company files and the documents in an employee file, described below.
04 // Location
Your location
FieldLink records your location when you punch. Your company can switch on live tracking, which shows where you are while you are clocked in, but only after you agree and only while the app is open in front of you. Three things read your location between clock-in and clock-out, and none of them starts by itself: driving to your next job and the drive from home, which check only whether you have reached the job (below), and live tracking (next section). Nothing is read while the app is shut or the phone is in your pocket. Off the clock, FieldLink sends no position anywhere, except for something you do yourself that records where it happened (A few other moments, below). The Clock page’s distance to the job is worked out on your phone and never sent.
At clock-in and clock-out, the app reads one GPS fix and stores it on the punch, with how accurate the phone said it was. The fix shows where you were when you punched, and it is what the job site’s geofence is checked against.
If you punch outside a job site’s geofence, the app asks why. The reason you type is kept on the punch, and nobody, including the office, can edit it afterward.
Driving to your next job, you can tell the app you are leaving. Your hours move to the next job right away and count as drive time until you arrive. On the way, the app checks your position against that one job site and asks our server whether you have arrived. When you have, the same punch carries on as time on the job and your phone tells you. You start it and you can cancel it. The drive check runs only while the app is open in front of you, and all it leaves behind is the punch itself: how much of it was driving and when FieldLink saw you arrive. Driving between jobs is paid and counts toward your overtime.
When your employer pays the drive from home or back, the app offers Driving from home at your first clock-in when the drive there is paid, and Drive home at your last when the drive back is paid. FieldLink keeps when each drive started and ended, and how each was paid. FieldLink never keeps where your home is: starting that drive and saying you are home send no position, and live crew positions pause from the moment you set off until you reach the job, and again from Drive home. If FieldLink never sees you reach the job, the whole punch counts as work until the office says when you got there; that change is kept with its reason, and you are told. A drive your employer does not pay is not clocked at all.
On the office’s live map, a pin is where someone clocked in. The pin shows a newer position only if your company has switched on live tracking and you have agreed to it (next section). When the punch is closed, its location drops off the map. Only owners, admins, the office, and anyone an owner or admin has given the live map permission can open that map.
A few other moments. A location is saved where the record needs it: a photo taken on a service call or in a daily log, a tool checked out, checked in, handed over, scanned or reported damaged, lost or found, a job’s pin dropped where you stand, and the spot where a customer signs for completed work. Where a tool moved is seen only by owners, admins and the office, never by a coworker.
When you file a fuel purchase from a pump photo, a photo you take uses this phone's location once, while the photo is prepared and sent, when location is already allowed, so the station can be named. A photo you choose from the library uses the location the photo library keeps for that photo, when it has one. The time saved in the photo, when it has one, is used as the time of the receipt. When the library has none, the location written in the file is used. FieldLink AI reads the street, city, state and ZIP printed on the picture. When a line is missing, FieldLink's own server sends that point to OpenStreetMap to look up the station's name and the missing lines. When no station is found, or that search does not answer, the same point fills the street, city, state and ZIP. When a US ZIP comes back with no city, the server then sends the five-digit ZIP to Nominatim's postal search so the city can be named. The point is kept on the receipt with how it was found. The station's ZIP is kept on the receipt with the address when one is known. The pump photo lookup is not live tracking, and it does not run in the background. If there is no location, or the map does not answer, the brand read from the pump is put in the station box until someone types over it or the map answers.
Inside a work photo, only if your company chooses. If your company turns off "Remove photo details", a work photo keeps the location your phone saved in the file, if it saved one. For a pump or receipt photo chosen from the library, the location the photo library keeps for it is written into the uploaded copy. Your company can read it, and so can anyone it sends the photo to, in a report or its accounting program. Everyone in your company is told in FieldLink the moment it is turned off, before any photo of theirs keeps its location, and told again if it is turned back on. With that switch on, as every company starts, no photo carries a location inside it (see Photos and files).
Call and Directions on a service call. On a service call, Call opens your phone’s own dialer with the customer’s number, and Directions opens the service address in your phone’s own maps app, or in Google Maps in a browser. FieldLink sends the number and the address nowhere itself, does not read where you are for it, and keeps no record of the call or the route.
Anything new that reads your location, beyond what this section names, will start switched off. Your company will have to turn it on. Your crew will be told before it is turned on, and this page will say so first.
05 // Live positions
Live tracking and its limits
Your company can switch on a live map showing where each person is while they are clocked in. Live tracking is the most sensitive thing FieldLink does with anyone’s information, so here are its limits.
Only while you are clocked in. Clocking out stops it. Nothing is reported off the clock, even with the app open.
Only while the app is open in front of you. Nothing is collected while the app is in the background or the phone is in your pocket with the screen off. FieldLink does not ask for "Always" location and has no background location mode on iPhone or Android.
You agree to it once, before anything is reported. A screen explains what would be shared and asks whether you agree. You can withdraw your agreement at any time in Account settings. Reporting stops at once, and the positions already stored for you are deleted.
Saying no does not stop you working. You clock in as usual. The only difference is that your company sees no live position for you.
You can see whether it is on. Account settings shows whether you share your location, and lets you stop at any time.
Live tracking starts switched off, and your company has to turn it on. Turning it off again deletes the positions and the trail that went with them.
Who can see it: owners, admins and anyone they have given the live map permission. Nobody else in your company sees anyone’s position, unless an owner or admin has given them the live map permission, and your company can see who holds it.
What is stored: your latitude and longitude, how accurate the phone said the fix was, the time, the job site and whether you were inside its geofence. The day’s trail of points is kept, and it is purged every night.
None of this reaches your time off the clock: no tracking between shifts, none at night and none on a day you do not work.
06 // Time clock
Hours, clock-out answers and injuries
What a punch holds: when you clocked in and out and on which job, plus the cost code if your company uses cost codes. When a crew lead punches for you, it records who.
Your pay classification for overtime. An owner or an admin can choose Hourly, Salary non-exempt or Salary exempt. Only Salary exempt stops FieldLink from calculating overtime. The classification is kept with the pay week it starts, and you are told when it changes. You and your office can see it; coworkers cannot.
Which shift you work. Your shift decides when your workday starts, so a late night counts for the day it started. Every change is kept with the day it starts, and a change that moves your workday is kept with the reason given for it. You are told when it changes. You and your office can see it; coworkers cannot.
Two questions at the end of the day, if your company turns them on: whether you were hurt today and whether your time is right. Your answers are yours, and nobody can change them later.
Your company’s own questions at clock-out. Your company can add up to eight of its own, such as whether you locked up the job or how many miles you drove your own vehicle. Your answers are kept with the punch in the words you were asked, even if the punch is later deleted. You and your office can read them; coworkers cannot. Nobody can change them afterward. A crew lead who clocks you out never answers them for you. You answer them yourself when you confirm that day.
An injury report. Answering "I was hurt" opens a draft incident report with what you typed, the day, the job and the punch. Owners, admins and anyone with the safety permission can read it and add office notes. The report holds no medical records and no photos.
Punches taken with no signal. The punch waits on your device and is sent when you have service. We keep the time and GPS as they were recorded, plus how far off your phone’s clock was, so a punch cannot be quietly back-dated.
Every change to a punch is recorded: who changed it, when and why, whether it was a clock-in, a clock-out, an automatic close, an office edit or a correction you asked for. You are told when someone changes your time, and a pay week you already signed has to be signed again.
Time off you ask for. FieldLink keeps the days, the kind (vacation, sick, personal or other), any note you write and the office’s answer, with who gave it and any note of theirs. You and your company’s owners, admins and office can read the request; coworkers cannot. The note is optional, so write only what you want your office to read, and the notice telling the office you asked leaves it out. The request is kept as long as your company’s other time records.
07 // Photos
Photos and files
Your photo at clock-in and clock-out. Your company decides. The clock-in photo is on unless your company turns it off; the clock-out photo is off unless your company turns it on. The two photos are always taken live with the camera, on a phone or in a browser. You cannot pick a picture from your gallery, so nobody can punch for a coworker with an old photo of them.
Who sees a clock photo: you and your office, never another technician. A clock photo is never replaced or deleted from its punch. When a crew lead punches for you, no photo of you is taken; the app shows "clocked in by" and the lead’s name.
Your clock photo is checked on your own device. Before a clock-in or clock-out photo is used, the app looks at it on your phone, or in your browser, for three things: one face clearly seen, nobody else in it, and not taken inside a vehicle. The photo is never sent anywhere to be looked at: the models that look at it are part of the app. The check only finds a face; it never recognizes who anybody is, and no face template, measurement or other biometric is made, kept or sent. The app measures how light the photo is, as one number worked out from its own pixels on your device, and keeps that number with the punch, with whether it was taken in the dark. In the dark the camera page can light your face by turning the whole screen white at full brightness for a moment, or with your camera's own front light where it has one; for its Auto setting it measures how light the live picture is, on your device, and keeps none of it. The flash setting you pick stays on that device. When the photo does not pass, you are asked to take it again; after that you choose to take another or to use it, and only then is the punch taken, keeping only what was found ("no clear face", "dark photo, no clear face", "someone else in it", "taken inside a vehicle") for your office to review, and your office is told. A photo the app could not check is used only if you choose it, and the punch keeps that it was not checked. A check never stops a punch.
Job, receipt and daily log photos, and the files your office keeps for receipts, HR, safety, prints, branding, service reports, daily reports, punch lists, each job’s File Vault, Company files and employee files, are kept in private storage. Nobody outside your company can open them. The one exception is a service report, which the customer it was written for can open.
A fingerprint of each daily log photo, so the same picture is not filed twice. When a photo is added to a daily log, your phone works out a small fingerprint of what the picture looks like - a short number, not the picture itself, and nothing leaves your phone to make it. FieldLink uses it to tell when the same photo is filed twice, inside one log or across the daily logs in your own company, so a shared photo is not counted more than once. The fingerprint is stored with the photo and compared only within your company. Where an older photo has none, our server works out the same fingerprint from the photo already stored in your company; the photo never leaves your company’s private storage to do it.
Photos are made smaller and cleaned on your device before they are uploaded. Unless your company turns that off, the app shrinks each one and strips out every EXIF, XMP and GPS block, so hidden details like the location and the camera’s serial number never leave the device. Where a record needs a location, it is stored on the record where you can see it, not hidden inside the picture.
Your company decides for work photos. An owner or admin can turn off "Reduce photo size", and job, receipt, daily log and other work photos are then not made smaller. An owner or admin can turn off "Remove photo details", and those photos then keep the details your phone saved in them: where and when each one was taken, and the phone or camera that took it. Your profile picture, your clock photos and the photos a customer sends with a service request are always made smaller and always cleaned, whatever your company chooses.
Square photos. Photos for a daily log, a service call or a punch list, your clock photos and your profile picture are cut to a square from the middle of the picture on your device, before they are uploaded; a tool’s photos are cut to the square you drag over them. The part cut off is never sent, not even in the small preview a phone keeps inside a photo. A clock photo or a profile picture your device cannot cut goes up as it was taken, so a photo never stops a punch. A receipt is never cut: the whole receipt goes up on a white square. A Live Photo’s short video is the one exception: it is kept in the shape it was recorded.
Live Photos from an iPhone. While "Reduce photo size" is off, a Live Photo chosen from an iPhone’s photos for a daily log, a service call, a tool or a job’s File Vault keeps its short video and sound. Your phone makes a smaller copy of the video before it is uploaded. While "Remove photo details" is on, that copy leaves out where and when it was taken and which phone took it. The video is kept beside its photo, and exactly the people who can see the photo can play it. With "Reduce photo size" on, a Live Photo is saved as a plain picture. Any other short video a phone saves with a photo is never sent.
HEIC pictures from an iPhone. A picture in Apple’s HEIC format is turned into an ordinary JPEG on your own phone or in your own browser, before it is uploaded or shown. The picture is never sent anywhere to be converted. Where a browser cannot open HEIC itself, FieldLink loads a free converter, libheif, from FieldLink’s own website, only when you choose one. The JPEG keeps none of the details hidden in the picture, whatever your company’s photo settings say.
Signing for a tool. If your company asks people to sign for its tools, whoever checks a tool out, asks a coworker for one or is handed one reads the terms and signs with a finger on the screen. Until someone handed a tool signs, the office sees that it is not signed for yet. FieldLink keeps the signature, the exact words signed, the tool’s name, asset tag and serial number, the person’s name and the time with the tool’s record, for as long as the tool is in FieldLink. The person who signed and the office can see it, and nobody else can. No location is kept with it.
A photo of your face when you sign for a tool. If your company asks for a photo at tool check-out, right after you sign for a tool FieldLink opens your front camera for a photo of your face, which the office can review beside your signature. The photo is taken live, right then, and never chosen from your saved pictures. FieldLink makes the photo smaller and removes its photo details, such as where and when it was taken, before it is sent. The photo is kept with the signature and the tool’s record for as long as the tool is in FieldLink, and only you and the office can see it. No location is kept with it. If your camera is blocked or will not open, you can sign without a photo: FieldLink keeps that reason instead and tells the office.
Punch lists. If your company uses Punch Lists, each item on a list keeps a photo of what needs fixing, the words said or typed for it and, when someone adds them, where it is, how many people and how long it takes, its circuits at an electrical or low voltage company, a note for the office, who it is for and a picture cut from part of a PDF in the job’s File Vault, with the name of the file and the page it came from. The crew sees only that picture, never the PDF. A finished item keeps a photo of the finished work, what was done, who finished it and when; one that can’t be finished keeps who said so, when and why. Your owners, admins and office read every list, and anyone else reads only a list sent to them, from when it is sent until it is put away. Your office can email a list’s PDF to the job’s general contractor, the people its daily reports go to and anyone else it types in.
Sent daily reports. Every daily report your company sends, by hand or by itself, goes to the job’s crew lead by email, and a copy of its PDF is filed in that job’s File Vault, in a Daily Logs folder, where everyone who can open the job’s files can read it, the crew’s names and hours included. Sending an unchanged report again changes nothing there; a changed report’s copy takes the old one’s place, and the old one is kept as a removed file.
A PDF you save on an iPhone or iPad. Save PDF and Download PDF put the PDF in FieldLink’s own folder on that iPhone or iPad, which the Files app shows under On My iPhone (or On My iPad) > FieldLink. From there you can open, print or share it. The PDF stays on that device until you delete it or remove FieldLink, even after you sign out, so anybody using that iPhone or iPad can open it there. FieldLink never reads it or sends it anywhere.
08 // Job files
The File Vault, and who opened what
A job’s paperwork can be filed on the job itself - prints, submittals, permits, spec sheets, install manuals, safety data sheets, change orders - in folders your office or the job’s crew lead makes and names, so the crew works from the current revision. FieldLink records who opens these files, and the same goes for Company files and employee files.
The office or the job’s crew lead decides, file by file, what the crew can open. A file nobody has decided about stays with the office, and keeping a file in the office keeps its older revisions there. The files are your company’s, like every other record in FieldLink, and are never shown to another company.
Every time one of these files is opened, we write down who opened it. The person, the file, the date and time, and whether it was an iPhone, an Android phone or a web browser. The list stops there: no IP address, location or phone number, nothing that identifies the device and nothing about how long it was open or what you did next.
Why it is kept: to answer two questions that come up later - how a drawing left the job, and whether the crew had the current revision on the day they built it.
You can always see your own record. Whatever your role, the list of job files you opened is yours to read, and nobody can hide it from you. Owners, admins and the office read it for the people at their own company. A technician never sees a coworker’s, and no other company ever sees any of it.
What the list of files shows. Every file shows its name (as it was on the computer or phone it came from, without that device’s folders), its size, who uploaded it and when. Owners, admins and the office see who opened it last and when, and how many people have opened it. Everybody else sees only when they last opened it themselves.
A safety data sheet can ask you to confirm you have read it. Opening the file is not that confirmation - you say so yourself. The confirmation is recorded once, with who said it and when. Only you can say it, and nobody can take it back.
You agree to the terms for job files once. Before a job file opens, you agree to the terms it is handed to you under. We keep which version of the terms you agreed to and when, so you are asked again only when the terms change. Your company’s owner and admins are never asked. The record is kept with your company’s records, like the list of who opened a file, and only you can read it.
A file in the File Vault is never handed out as a link. Other private files in FieldLink open through a temporary web address that could be forwarded. The file is drawn inside the app and never handed to the phone itself: there is no Save, no Share, no Print and no Open in, and no link to it exists that anyone could paste into a message. Your name and the time are drawn across the page while it is on screen, unless you are your company’s owner or one of its admins.
Nothing here can stop somebody pointing a second phone at the screen, and no product can. The name across the page shows whose screen a photo was taken from.
How long we keep the record of who opened a file: as long as the file it belongs to. The log is not cleared on a timer, because the questions it answers usually come up long afterward. Erasing your company’s records erases it with them.
09 // Employee files
Company files and your employee file
At the top of the File Vault are two folders every company has. Company files holds the company’s own documents, like the employee manual and the vehicle policy. Everybody in the company can open them, and the office adds and removes them. A removed company file is kept under Removed files until the office deletes it permanently.
Your employee file. Your company can keep documents about you in FieldLink, like a written warning, a bonus letter or a certificate. You can open every document in it. The owner and the people your company gives HR access add and remove them. Nobody else at your company can open it, and FieldLink support never can.
How your file is kept. Documents in your employee file are kept in private storage and handed only to you, the owner and people with HR access. A document that shows your address or another personal detail is protected the way the file is.
Opening your own file. You type your account password again. We check it against your sign-in and never keep what you typed in a log. Once the file opens, it stays open for 15 minutes, on that sign-in only. Another phone or computer signed in as you stays closed. Five wrong tries in a row lock it for 15 minutes, and a third lock within a day lasts 24 hours. Your owner and HR are told about a lock in the app, without the password. We keep a note of each try, right or wrong, for 90 days, and that note never holds the password.
Opening your file with Face ID, Touch ID or a fingerprint. In the iPhone and Android apps, after your password opens your file, you can choose to open it next time with your phone’s own Face ID, Touch ID or fingerprint or face check. Your phone then makes a key that stays inside its secure hardware and works only after that check passes. FieldLink never receives your face, your fingerprint or your passcode. Turning it on sends the password you just typed once more with the key, checked and never kept, and a wrong one counts as a wrong try. You are told in the app, never by email, every time a phone is added, with its name and the time. We keep the public half of the key for each phone you turn it on for, with the kind of phone and when it was last used, until you stop it in Account settings, sign out on that phone, change or reset your password, or leave the company. Every opening signs a one-time code we check and then forget within an hour. A check that does not match counts as a wrong try, exactly like a wrong password, and the same 15 minutes and the same locks apply. Your password always works instead.
Who opened what. Opening a company file or a document in an employee file is recorded like a job file: who, when and what kind of device. The office sees who opened a company file last; the owner and HR see who opened the documents in an employee file. You always see when you opened one yourself. The record lasts as long as the file.
When something is added to your file, you are told in the app, never by email, and the message never names the document.
Removing a document from an employee file takes it out of your file, but your company keeps it, with who removed it and why, until the owner or someone with HR access deletes it permanently from Removed files. Then the document is gone for good, and so is the record of who opened it. The audit log records that a document was removed or deleted, by whom and from whose file, but never its name or the reason.
Confirmed time clock deficiencies are kept in a running record at the bottom of your employee file. FieldLink flags a punch problem for your office to review, and your office can flag one itself when it reviews your time, with a note of what happened. A problem your office confirms is added to this record. Only the owner, people with HR access and you can open it, the same as the rest of your employee file.
10 // Job files
Looking at a drawing together
Someone viewing a drawing can invite a coworker to look at it with them, and anyone allowed to open that file can ask to join a drawing that is already open. The two screens then move together, on the same page and the same spot, and each person can point at something on it.
No screen is shared. The two people are already allowed to open the file, so only the page and the spot on it pass between them, about a hundred characters. No picture of anyone’s screen is sent to us or anyone else, and the drawing never leaves the File Vault.
Joining gives no one new access. Whoever joins must already be able to open that file on their own account. If they could not open it alone, they cannot open it together, and the invitation is refused before it is sent.
Nobody is joined without saying yes. Whoever is asked answers first, every time, and the session ends the moment one of the two ends it or closes the file.
No microphone and no camera. The feature never asks a phone for the microphone or the camera, and FieldLink does not carry your voice. To talk, people call each other and use speakerphone.
What we keep: who looked at which drawing with whom, and when it started and finished. Your office can read that list for its own employees, and you can always read your own. Nothing that was said or pointed at is stored.
11 // Microphone
Dictating a daily log or an estimate’s job
You can speak a daily log, or the job an estimate is for, instead of typing it. The microphone comes on only when you tap the microphone button on that screen, and it goes off when you tap it again, press Done or leave the page.
Your phone does the listening, not FieldLink. The words come from the speech recognition built into your phone or browser. Depending on the device and its settings, it may send the audio to Apple or Google to turn it into words, under their terms rather than ours. FieldLink never receives or stores a recording of your voice. FieldLink gets only the text, which is added to what you have already written (never over it) and becomes part of your daily log, or of the description of the job, as if you had typed it.
Punch lists work the same way. The words for an item on a punch list, and the crew’s words when they finish one or can’t, can be spoken with the same promises. FieldLink keeps the words and whether they were spoken, never a recording.
The microphone is never listening in the background. Not on another screen, not while the app is behind another app and never before you tap the button. If a device has no microphone, or you have not allowed it, the app says so and you type instead. You never need dictation to file a log or write an estimate.
12 // SMS
Phone numbers and text messages
Sagetech LLC does not share mobile numbers, text messaging originator opt-in data, or consent with any third parties or affiliates for marketing or promotional purposes.
Text messaging originator opt-in data and consent will not be shared with any third parties, excluding aggregators and providers of the text message services.
In plain terms: if you give us your mobile number and agree to be texted, we use that number only to text you. The number and your consent are never sold, passed to an advertiser or given to another company to market to you. The only outsiders who could see them are the carrier and the messaging service that delivers the text.
Today the FieldLink app sends no text messages, and no texting provider is connected to it. The section covers the texts we will send you about your account, such as support replies and service updates. The notice is written now so the rules are in place before we connect a texting provider. If we ever give your number to a messaging provider or an aggregator so a text can reach you, that is the one exception allowed above.
Text STOP to end the messages. Reply HELP or write to support@sagetechfieldlink.com to reach a person. The Terms of Service page has the details.
The phone number for our messaging program is +1 (864) 263-2317. The phone numbers your company keeps for its employees and customers are your company’s records, and we never use them for marketing.
13 // Messages
Messages between your coworkers
Messages lets the people in your company write to each other inside FieldLink: one chat for the whole company, called Everyone, groups anybody in the company can start, and chats between two people. Nobody outside your company can read one, join one or be added to one, and your company’s customers never can. Messages travel inside FieldLink and are never sent as text messages.
What is kept. The words of every message, the photos, GIFs and voice messages sent with it, who sent it and when, which message it replies to, who it mentions, the effect it was sent with and any bold or italic words, its reaction from each person and who gave it, a poll's question, choices and who voted for each, and each earlier version of a message that was changed. A mention is kept with its message as long as the message is. For each chat, FieldLink keeps who is in it, when they joined, how far each of them has read, its name, its group photo and its background. Your alert, mute and read receipt choices (for every chat or for one chat), the chats you pinned or marked unread, the chats you deleted from your list and the messages you deleted from your own view, and who you muted or blocked, are kept for you alone, and nobody learns that you muted or blocked them. Whether somebody is typing is shown to the others in the chat while it happens and is never stored.
Who reads a chat. Only the people in it. Everyone in your company reads the company chat and its whole history, somebody who joins later included. Somebody added to a group reads what is sent from the moment they were added. A message changed after it was sent says so, and everyone in the chat can read what it said before. In a chat between two people, each sees when the other has read a message, unless one of them turns read receipts off, for every chat or for that chat alone. A group and Everyone show only that a message was delivered, never who read it or how many. Somebody who turns read receipts off stops seeing when others read theirs.
Your company’s owners, admins and office. Owners, admins and the office read the company chat and any group they are in, like anybody else, and cannot read a group or a chat between two people they are not in. When somebody reports a message, the owners, the admins, the office and anyone given the Message reports permission are told, and they read a copy of that message as it was when it was reported, with who sent it, who reported it and why, so they can decide what to do about it. Once the report is decided, only the owner and an admin holding the HR permission read that copy. The notice that tells them carries no words and no name. Reports are kept with your company’s records, with no time limit, unless the owner permanently deletes the removed message a report is about, which deletes the report with it.
FieldLink support reads them only with your company’s approval. FieldLink support can ask to read your company’s messages only to answer a support request, or to help with Messages when your company asks for help with it, and must say why when it asks. Your owner, admins and office are told, and one of them approves or denies the request. Once it is approved, the one person at support who asked can read your company’s chats, their messages and photos, and the reported messages, for 24 hours at most, and your company can end it sooner. Support only reads: it never writes, reacts, deletes, removes or reports a message. The request and its reason, who approved or denied it and when, when it ended, and each chat support opens are kept in your company’s activity log, which your owners, admins and office see under Recent activity on the Dashboard. Without an approval, support reads nothing: no message, no list of your chats and no photo sent in one. If a report of illegal content reaches us, we can act on an account, such as switching a sign-in off, without reading the messages.
Deleting and removing. Anybody can delete a chat between two people, or a group, from their own list. The chat goes from their list only: everyone else keeps it, nothing in it is wiped, and its messages stay with your company’s records. The chat waits in their Recently Deleted for 30 days, where they can recover it as it was. If somebody writes in it again, it comes back for them showing only what was sent after they deleted it. Everyone, the company chat, cannot be deleted, and nobody is ever taken out of it: it is everybody in your company. Any member of a group can take somebody out of that group. Whoever sent a message can delete it for everyone at any time, and can unsend it in the 2 minutes after sending it. Deleted or unsent, it goes from the chat for everybody: the chat shows a line saying who deleted or unsent it, such as "Riley Ramos deleted a message", nobody can reply to it or react to it, its reactions are gone, and its words, photos, voice message and earlier versions are kept where only the owner and an admin holding the HR permission can read them, until the owner deletes them permanently. A report somebody made of it keeps its own copy, as described above. Separately, anybody can delete any message from their own view only: it goes from their screen, everyone else keeps it, and it stays with your company’s records. An owner or an admin can remove somebody else’s message in a chat they are in, whoever reviews reports can remove one that was reported, and only the owner can remove one the owner sent. The chat then shows "Removed by" and the name of whoever removed it, unless an owner or an admin removed it without a trace, which leaves nothing where it was. In both cases the message’s words, earlier versions and photos are kept where only the owner and an admin holding the HR permission can read them, because they may be needed if a complaint is made. The kept copy stays until the owner deletes it permanently. The audit log notes each removal and each decision on a report, never the words. An owner, an admin or the office can take the line a deleted or removed message leaves away for everyone in a chat they are in, as if nothing had been there; the kept copy and any report stay as they are, and the audit log notes who did it, never any words.
Photos. A photo sent in Messages is always made smaller, and its hidden details, such as where and when it was taken, are removed before it leaves the phone or computer, whatever your company’s photo settings say. A Live Photo is sent as a still picture. A GIF file saved on the device is sent with its hidden comments and extra data taken out. Photos are kept in your company’s file storage with their chat, and only the people in that chat can open them, besides the people who may read a reported or removed message, and FieldLink support while your company has approved it, as described above. A group's photo and a chat's background picture are made smaller and cleaned the same way, kept with that chat, and opened only by the people in it.
Voice messages. A voice message is recorded on the phone or computer, 2 minutes at most, and sent as a sound file with its length. The recording is kept with its message, opened only by the people who can read that message, and deleted with it, exactly as a photo is.
Polls. A poll keeps its question, its choices, who added each choice and who voted for each, and everyone in the chat sees who voted for what.
Send Later. A message scheduled to be sent later is kept for the person who wrote it alone until it goes, up to 14 days ahead. FieldLink then sends it as them. If it cannot be sent, such as when they have left the chat, it stays for them with the reason, and nothing more is done with it. Deleting it before then deletes it.
Translating a message. Anybody can have FieldLink AI translate a message on their own screen. Only that message's words and the language asked for are sent, as What FieldLink AI reads and what it does not says. The message itself never changes, and the translation is not kept.
GIFs from GIPHY. Unless your company turns GIF search off, the GIF button searches GIPHY, a service owned by Shutterstock. Your phone or browser asks GIPHY directly, as GIPHY requires, and only for GIFs rated G. GIPHY receives the words you search and the language FieldLink is shown in, which GIFs are shown and which one is sent, a random ID GIPHY gives that install of FieldLink, and the device’s IP address, as any web request carries. A message keeps only the GIF’s ID, and every phone or browser that shows it asks GIPHY for it, so GIPHY sees the IP address of each device that shows a GIF. GIPHY is never sent your name, your email, your company or the words of a message.
Links. When somebody types or pastes a web address in a message, FieldLink’s own server reads that page’s title, description, site name and picture to show a preview, as other messaging apps do. The page sees FieldLink’s server asking, never the person’s phone or computer, and is sent nothing about them, their company or the message. The preview and its picture are kept with the message, read only by the people who read the message, and deleted with it; the picture of a preview nobody sent is deleted once it is an hour old, the next time anybody pastes a link. FieldLink counts how many previews each company asks for each day, a number and nothing else, and keeps that count 90 days. The address and the page are never written to a log.
Alerts on your phone. Once you allow it, the iPhone and Android apps alert you to a new message while FieldLink is closed. The alert goes through Apple’s push notification service on an iPhone and Google’s Firebase Cloud Messaging on Android. As on an iPhone, an alert names the chat and who wrote and shows the start of the message, unless you turn off Show the words in alerts, which leaves only who wrote, such as "Riley sent a photo". Every message alerts on its own. When somebody reacts to your message, you are alerted, such as "Riley reacted 👍 to your message". A mention says so, such as "Riley mentioned you in Yard crew", and reaches you even when you muted that chat, but never when you blocked or muted the person who wrote it or turned alerts off; more mentions in that chat within a minute come as one alert. Alerts play FieldLink’s own sound, and a mention has a sound of its own. While FieldLink is open on the phone, it plays the same sound for a new message in a chat you have not muted. To reach your phone, FieldLink keeps a push token for it: a code Apple or Google gives that phone for FieldLink, with whether it is an iPhone or an Android phone and the app’s build number. The token is deleted when you sign out on that phone (with no signal then, the next sign-in on that phone deletes it first), when you are switched off or leave the company, and when Apple or Google says it no longer works. The office web app sends no alerts; it shows how many messages you have not read.
What the phone or browser keeps. So Messages can be read with no signal, FieldLink keeps on that phone or in that browser a copy of your list of chats and the newest 50 messages of the 10 chats you opened most recently, and which voice messages you played there, so one you have not played keeps its dot until you do. The copy is kept for one person in one company at a time, is never read for anybody else, and every sign-out clears it. A message written with no signal waits on the device, with its photos, until it is sent, and is kept the way a waiting daily log is, as described under Cookies and browser storage. The emoji you used recently and GIPHY’s random ID for that install are kept on the device and are never sent to us.
How long messages are kept. Messages are your company’s records and are kept until they are deleted, like the rest of them; nothing removes them on a timer. When a person leaves the company or deletes their account, what they wrote stays under their name. Erasing your company’s records erases its messages and their photos.
14 // Money
Pay rates and job money
Pay is kept separate on purpose. Your pay rate, employee number and the name your company uses for you in QuickBooks Online are stored apart from your profile, because anyone who can see your name could otherwise see your rate.
Who can see a rate: your office and you. Not a coworker and not a crew lead.
Job budgets and job costs. Budgets and job costs are kept separately, the same as pay rates. The job cost report shows a technician the hours with the dollars left blank, so nobody can work a rate back out of a total.
We hold no card number and no bank account number. FieldLink has no place for a card number or a bank account number. Your company’s plan is paid on Stripe’s or PayPal’s own pages, as the next section says. A photo of a receipt shows whatever the receipt printed, which can include the last digits of a card.
15 // Payments
Paying for FieldLink
An owner or an admin pays for your company’s plan in Company settings > Plan and billing in the FieldLink web app: by card, Apple Pay or Google Pay through Stripe, or through PayPal. The iPhone and Android apps show the plan’s status, and take no payment.
We never see a card or a PayPal password. Card, Apple Pay, Google Pay and PayPal details are entered on Stripe’s or PayPal’s own pages and stay with them. Stripe and PayPal keep their own records of each payment, under their own privacy policies.
What we keep about your plan: whether it is paid through Stripe or PayPal, the numbers Stripe or PayPal gives your company and its plan, the plan, monthly or yearly, the price, any extra storage it pays for, its status, when the period paid for ends, whether it is set to end, when the last payment went through and, after a failed payment, when it failed and the day FieldLink locks if it stays unpaid. Your company’s status, number of users and monthly or yearly choice are kept with its other details. When FieldLink cancels the plan because your company closed or was removed, it keeps which company, Stripe or PayPal, the number they give the plan, why and when, and a short note of any error, even after the company is erased.
A record of each message from Stripe and PayPal: its number, what kind it was, which company it was about, whether FieldLink used it and a short note of any error. The message itself is never kept, and FieldLink never receives card details in one.
Who sees it. Owners and admins see the plan, its price and its renewal or end date in Plan and billing, and only they start, change or cancel it there. Nobody else in your company is shown it. FieldLink administrators can see the plan and the record of each message, to help when a payment goes wrong.
Who is told about a failed payment. Owners and admins get a notice in the app and an email when a payment fails, again three days before FieldLink locks, and when it locks. The rest of your company is not told, and sees only that FieldLink is paused if it locks.
How much your company stores. FieldLink adds up the size of the files your company keeps, to compare it with the storage its plan includes. Anyone in your company can see how much is used, and only owners and admins can add more. Owners and admins are told in the app and by email when your company has used 80% of its storage, and again when it is full.
16 // Estimates
Estimates, invoices and your Parts & Labor List
If your company uses Estimates & Invoices, FieldLink keeps the estimates and invoices your people write and the Parts & Labor List they write them from.
Invoices and payments recorded by hand. An invoice keeps its customer, addresses, number, work, prices, taxes, terms, due date, notes, files, signatures, PDFs and revisions, why its charges were reopened, who reopened them and when, and which estimate or change order it bills. For each payment your company records, FieldLink keeps the amount, date received, method, optional reference and note, who recorded it and when, and who voided it, when and why. A voided payment stays in the history, and removing its recorder keeps the entry and the recorder’s name. Payment records stay with the invoice for as long as your company keeps it.
Who reads invoices and payment records. Owners, admins and the office read the company’s invoices and payments. People with Billing read their own documents and documents for service calls they work or jobs they lead. FieldLink support may read them and help with drafts while helping that exact company, but cannot send or settle the paperwork or record or void its customer payments. The customer’s copy shows invoice charges, payments received and the balance; private costs, private notes and the payment reference and note are not on that copy.
No customer payment is collected here. Your company records a check, cash, a card charged elsewhere, a bank transfer or another payment it already received. FieldLink does not collect or process that invoice payment or ask for card or bank account details. Never put a card or bank account number in a reference or note. A payment or correction is audited as an event, without its amount, reference, note or the person’s reason for reopening charges. Payments for your company’s FieldLink subscription are separate and are described under Stripe and PayPal below.
Invoice emails and notices. Your company can email each recipient a link to the customer copy. Anyone it is forwarded to can open it. The company may be told that a recipient’s link was opened, that an invoice is overdue or that it is paid in full. Opening identifies the link and its intended recipient, not a verified person. A paid invoice’s link keeps opening. The online-copy and email rules below apply to invoices; the notices do not confirm that a bank or payment processor received money.
What an estimate holds. The customer and the person you deal with there, their billing and work addresses, the type of work, the job it is for or the job made from it (on an older estimate, a service call), each line’s name, words, quantity, unit, price, discount and tax rates, photos, files attached to it, the contract and notes for the customer, your private notes, its dates and number, who wrote, sent, approved, declined or voided it and when, its signatures, and every PDF made of it.
Every change of answer. An estimate’s answer can be moved between Pending, Approved and Declined. FieldLink keeps every move: who made it and when, the revision, how an approval was given, and the approval’s note or the reason it was declined, word for word. The history stays as long as the estimate, even after the answer changes again, and is read by the same people as the estimate. The audit log notes that the answer moved, never the words.
Change orders. A change order is kept the same way as an estimate, on the job it changes: its title, whether it adds work or is a credit, whether it is a lump sum or time and materials with an amount not to exceed, the cause and why the work changed, the RFI, ASI, directive or other document it answers and its number, your customer’s own number for it, the days it adds, whether the work is done under protest, your reservation of rights, the estimate it changes, and your customer’s answer, including an amount and days approved that differ from it. A customer who signs one on your phone, tablet or computer can add their title to their name, and FieldLink never records where it was signed. All of it is kept with the change order’s revisions and answer history for as long as the change order, and read by the same people as the estimates. When one is approved or rejected, the same people as for an estimate are told, never with an amount.
Daily T&M tickets. A T&M ticket keeps one day of extra work on a job: who worked and their hours, the materials, the equipment, its photos and what the work was. When the general contractor’s superintendent signs it on a phone or tablet, FieldLink keeps their name, the title and email address picked or typed for them, the drawing of their signature, the words they signed under and when the phone recorded it, and never where it was signed; a ticket signed on paper keeps a photo of the paper, and one they would not sign keeps why. Your office, the job’s crew lead, people with the Crew lead permission and the person who wrote it read a ticket, and only your office and the job’s crew lead see the signer’s email address. Tickets are kept with your company’s records, and their PDF is emailed only to the people your office or the crew lead picks. FieldLink keeps when somebody started and stopped being allowed to write tickets on a job for 400 days, only to decide whether a ticket they finished with no signal is taken; nobody at your company reads it.
A job’s contract and budget. The original contract amount your office types for a job, with its note, and what each approved change order added to the job’s budget, with who added it and when, are kept with your company’s records. FieldLink adds up the job’s current contract from them each time it is shown and keeps no total of its own. Only the people who see job money read them: your owners, admins and office, and someone with the Billing permission on the jobs they lead.
A picture for an item. An item on the Parts & Labor List can carry one picture, added on the item or taken from the first photo of an estimate line added to the list. The people who read the list see it. A line that picks the item shows the same picture, and a new or removed picture on the item shows on every estimate not yet sent. A sent estimate keeps the picture it was sent with for as long as it is kept.
Search Google for Image. The Search Google for Image button on an item opens Google Images in your own browser, searching for the item’s name. FieldLink sends Google nothing itself, and a picture you find there is added to the item only if you save it and add it yourself.
Your cost and markup stay inside your company. A line or an item on the Parts & Labor List can carry what it costs your company and the markup on it. Those figures and the private notes are never printed on the customer’s copy.
Who reads them. Your owners, admins and office read every estimate and the whole Parts & Labor List. Someone your company gives the Billing permission reads only the estimates they wrote, ones for service calls they work and ones for jobs they lead, and never on an access level built on Technician. Nobody else in your company sees an estimate or a price. A FieldLink administrator helping your company in support mode can read them and save a draft, but never marks one sent, approved or declined, signs one or voids one.
Signatures. A customer who signs on your phone, tablet or computer types their name and draws a signature, kept with the time, the revision they signed and who at your company recorded it. Someone who signs for your company signs with the one signature they saved in Account settings. FieldLink never records where an estimate was signed. A change after an estimate is sent or signed makes a new revision, and every revision a customer saw or signed stays on record as it was.
An estimate or invoice can have a page of its own online. If your company leaves the online copy on, each estimate or invoice it makes a PDF of has a link to a page that shows exactly what the PDF prints, including your customer’s name, the person you deal with there, their email, phone and addresses, the lines and totals, and the names of who signed, and the PDF the page offers carries the signatures. Anyone who has the link can open it without signing in, including anyone it is forwarded to. The page never shows your cost, markup or private notes. Search engines are told not to list it.
The link stays out of our server logs. The part of the link that opens the page comes after a # sign, so browsers do not send it to FieldLink’s servers or to other websites. The page takes it off the address and keeps it in that browser tab only, so a refresh still shows the document, and forgets it when the tab is closed.
What is recorded when the page is opened. FieldLink records the date and time it was first opened, the last time and how many times, and shows them to your company. FieldLink itself never records the IP address, browser, device or location of whoever opened it; our hosting provider’s request logs keep the IP address and browser for a limited time, as said under Supabase. Openings from FieldLink itself are not counted, and the page is never counted as a visit to our website. To stop one machine making thousands of requests, a scrambled form of the IP address is held in memory for up to an hour and never written down.
An estimate emailed through FieldLink. When somebody at your company emails an estimate from FieldLink, the email carries no PDF. The email has a link of that person’s own to the estimate’s page, where they can download the PDF. FieldLink keeps the email address it went to, and the person’s name when they are one of your customer’s people, with the estimate. FieldLink records when that person’s link was first and last opened and how many times, shows it to your company, and tells your company the first time it is opened. As with every online copy, FieldLink itself never records where it was opened from: no IP address, browser, device or location, beyond our hosting provider’s request logs described under Supabase. Only a scrambled form of the link is kept; the link itself is only in the email.
A change order answered online. Unless your owner or an admin turns it off, a change order emailed from FieldLink that asks for your customer’s signature can be approved or declined from the link in each person’s email. Only that person’s own link answers, once, and for no longer than the end of the change order’s Valid until day or, when it has none, 30 days after the email; the link printed on the PDF only shows it. Whoever answers types their name and, if they like, their title; an approval takes a tick agreeing to sign electronically and a drawn signature, and a decline takes the reason. FieldLink keeps with the change order that name and title, the drawing or the reason, the exact sentence they approved or declined, which answer they gave, when, the revision they answered and the email address the link was sent to, because anyone a forwarded email reaches can answer with it. An approval’s drawing becomes your customer’s signature on the change order, and prints on its PDF once your company makes the PDF again. FieldLink itself never records the IP address, browser, device or location of whoever answers, beyond our hosting provider’s request logs described under Supabase. All of it is kept for as long as the change order and read by the same people, and the same people are told as for any answer, with the name typed and never an amount. The audit log notes only that it was answered online and which answer, never the name, the words or the drawing. FieldLink counts how many answers each company gets a day, with nothing about who gave them, to keep every company under its daily limit. When your office revokes a person’s access, gives them a new email address or takes them off the customer, the links already emailed to them stop opening, and a link in an email to them still waiting to go out only shows the change order and never answers.
When a link stops working. When the document is changed into a new revision, canceled or deleted; when its customer is archived; when your company closes; when your company turns the online copy off for that document; 90 days after an estimate was due to expire or was answered; and 12 months after an invoice is paid. Turning the online copy off for everything pauses links, and turning it back on brings back those that have not stopped for another reason, unless your company chooses to make new links.
Your licenses and insurance. Your owner or an admin can add license, insurance, bond and certification documents and choose, one by one, which to show online. One shown online appears as pictures of its first six pages, at most, on the page of every estimate and invoice with a link, and anyone with such a link can see them. The page has no download button, but a screen can always be saved or photographed. The original file is kept for your company’s owners, admins and office, and is emailed only when somebody at your company attaches it. A document is taken off the page, and off new PDFs, on the day it expires. FieldLink does not check these documents.
Attachments. Files your people attach to an estimate or invoice are kept with it and every revision that had them. Their names print on the PDF. Pictures of each file, at most its first 10 pages and with photo details removed, show on the estimate’s online page to anyone with its link, with no download button. The original file is read only by people at your company who can open the estimate. FieldLink support can look at them but never adds or removes them.
Your web links. Your company’s website and its Facebook, Google, Instagram and Yelp addresses print on your estimates and invoices and show on their pages. Clicking one leaves FieldLink, and nothing from those services is loaded on the page.
Your Parts & Labor List. The items your company sells: each one’s name, description, unit, kind, part number, barcode, category, price, taxes, your cost and its markup, your private notes about it, and when it was last used. Anyone who reads estimates can add to it, and every line typed on an estimate or an invoice is added to it when that estimate or invoice is saved. Owners, admins and the office change it and retire its items.
A spreadsheet you import. A spreadsheet imported into the Parts & Labor List is read on the office’s own computer, and only its rows reach FieldLink. The file itself is never uploaded or kept.
Your tax rates, markups and paperwork. Your saved tax rates, markups, labor rates by skill level and your own named hourly labor rates, contracts, footer and other paperwork settings are your company’s, read by the same people as the estimates. The contractor license numbers you type are kept with your company’s details and print under your address on estimates, service reports and daily job reports.
Deleting and voiding. An estimate draft that was never sent can be deleted: it leaves every list and its number is not used again, and we keep the record with your company’s other records. A voided estimate stays on record with the reason given.
Who is told. When an estimate is marked approved or declined, your owners, admins and office and the person who wrote it are told once for each answer on each revision, never with an amount and never the person who recorded the answer. Moving it back to Pending tells nobody. When someone outside the office adds a customer from an estimate, the office is told.
17 // Phones
The phone you work on
FieldLink remembers which phone is yours, so your company knows when someone clocks in on a phone that is not theirs.
What is kept. The first time you sign in, the app makes an ID for that phone. The ID is not a serial number and tells us nothing about the phone, the SIM or anything on it. On an iPhone it is a random ID kept in the phone’s keychain for that phone alone. On Android it is worked out on the phone, one way, from the ID Android gives the FieldLink app alone, which no other company’s app sees; the ID Android gives is never sent to us. From the app’s November 2026 update, deleting the app and installing it again on the same phone keeps the same ID, and a factory reset makes a new one. Every time you sign in, we note which ID that sign-in is on. We keep the phone’s model name, such as "iPhone 15" or "Pixel 8", so your office can tell your phone from a new one.
iPhone backups. An iPhone’s iCloud or computer backup can hold what FieldLink keeps on the phone, such as your sign-in, a punch waiting to be sent, drafts and the copies of your company’s Parts & Labor List and T&M job facts. On Android, nothing FieldLink keeps goes into a backup.
What your company sees. Your name beside the phone’s model name and when you last used it, and the ID of that phone. Nothing else on your phone.
Which FieldLink your phone has. The iPhone and Android apps tell FieldLink which version and build of the app they are, on what kind of phone, and when they were last used. Your company’s owners, admins and office see it on the Employees page, so they can tell who needs to update FieldLink, and you can see your own. FieldLink keeps it while you are in the company and deletes it when you are switched off or leave. A browser is never counted.
Clocking in on someone else’s phone. If you leave your phone at home, you can sign in on a coworker’s phone and clock in as usual. Which phone you use never stops a punch. Your company’s owners, admins and office are then told, in the app and by email, that you clocked in or out on that person’s phone, with the job and the time. The message names only you and the person whose phone it is. Nothing on their phone changes, and your own phone stays yours.
Getting a new phone. Ask from the app, and your office can make the new one your phone. The office can clear the old one, and nothing about it is kept once it is cleared.
Not on a computer. None of this applies to the office web portal, which works in any browser.
Unlocking FieldLink with Face ID or a fingerprint. In the iPhone and Android apps you can choose to unlock FieldLink with your phone’s own check: Face ID, Touch ID, a fingerprint or face, or the phone’s passcode. The phone does the check and tells FieldLink only whether it passed. FieldLink never receives or stores your face, your fingerprint or your passcode. Whether you turned it on is kept on that phone only, and signing out turns it off.
Updates. When the iPhone or Android app opens, it asks FieldLink which versions still work. The question carries no name, no account and no location. The app then asks the phone’s own store whether a newer FieldLink is out: Google Play on an Android phone, the App Store on an iPhone. On an Android phone, Google Play downloads and installs an update itself, and FieldLink sends Google nothing for it. When a newer FieldLink is out, the app must be updated before it opens.
Checking the app is genuine. About once a day, and after you sign in, the iPhone or Android app asks Apple or Google to confirm it is a genuine, unchanged FieldLink from the App Store or Google Play: Apple’s App Attest on an iPhone, Google’s Play Integrity on Android. The phone sends them a one-time code from FieldLink and FieldLink’s app name, never your name, your work or your location. FieldLink keeps the latest answer for each phone (genuine or not, the app’s build, whether it came from the store, and on Android whether the phone passed Google’s device check), with the phone, the person signed in and when. Only FieldLink staff see it. Nobody is refused because of it.
Permissions. The first time the iPhone or Android app opens after it is installed, your phone asks you about each thing FieldLink may use: notifications, the camera, the microphone and your location while you use it. An update that adds one asks about that one only. Saying no never stops you using FieldLink. Your answers stay with your phone. FieldLink keeps on the phone only which of these it has already asked, so it never asks the same one again by itself. Account settings > Permissions shows each one at any time.
18 // AI
What FieldLink AI reads and what it does not
FieldLink uses an AI service for a few narrow jobs.
Which company. Anthropic, the maker of Claude. FieldLink AI uses Anthropic and no other AI company. Anthropic gets exactly what is described below and nothing more.
Asked first. Before someone first uses FieldLink AI on a phone or in a browser, FieldLink says which company may get what, and asks. If they say Not Now, nothing is sent: they type it in themselves, and a receipt opens without being read. The answer is kept on that device for that account until they sign out, and they can change it in Account settings. A daily report your company sends by itself is written up without asking anyone, once your company turns that on for the company or for a job.
Reading a receipt. When someone scans a printed receipt, the photo or PDF is sent to that company so the store, date, items, tax, any tip, the total, how it was paid as printed (such as a card's last four digits, never a full card number) and any printed station street, city, state and ZIP can be read from it. The request includes your company’s name and trade, so the results use your trade’s own terms. When someone photographs a pump display, that photo is sent so the sale, the gallons, the posted prices, any brand on the pump and any printed station street, city, state and ZIP can be read. When the grade prices sit in a row the phone can cut out, a second image of that grade row is cut on the phone and sent with the same request so every posted price can be read; that cut-out is not kept as its own file after the read. The person checks those numbers before the receipt is kept. If your company keeps photo details, they are still inside the photo that is sent.
Tidying up a note. When someone asks for help with a note, the text they typed is sent with your company’s name and trade and the details of the job, call or tool the note is about, such as the job name, the customer and the address. Nothing else goes with it: no photos, no pay and no coworkers’ records.
Tidying an estimate’s words. When someone asks for help with a line’s description, the description of an item on the Parts & Labor List or the notes for the customer on an estimate, only those words are sent, with your company’s name and trade. No price, cost, total, customer or address goes with them.
Drafting an estimate. When someone asks FieldLink AI to draft an estimate, only the description they typed or said is sent, with your company’s name and trade. Nothing from your Parts & Labor List goes with it, and no price, cost, labor rate, customer or address. FieldLink then looks the lines up in your own Parts & Labor List on our servers, so every price on the draft is your own, and a line it cannot find comes back with no price. The draft is a suggestion on the screen: nothing is saved or sent to a customer until a person checks it and saves it, and the words asked for are not kept on our servers.
Writing up a daily report. A job’s daily report lists the day’s work as one account, which FieldLink AI writes from the crew’s daily logs: when someone who approves the report asks for it or approves it, and by itself for a report your company sends automatically. Opening a report sends nothing. Only the words of that day’s logs are sent, with your company’s trade. No names, photos, hours, prices, customer or address go with them. The crew’s own logs are never changed: the account written is kept with the report, so it is printed the same way every time.
Tidying a punch list item. When someone asks for help with the words for an item on a punch list, only those words are sent, with your company’s trade. No names, photos, job, customer or address go with them. The words as said or typed are always kept, and the tidied version is kept beside them only if the person accepts it.
Translating a message. When someone asks FieldLink AI to translate a message in Messages, only that message's words are sent, with the language asked for. No names, photos, chat or company go with them. The translation is shown on that person's screen and is not kept.
Cleaning up a message you type. When someone uses Clean Up With FieldLink AI on a message they are writing in Messages, only the words they typed are sent. No names, photos, chat or company go with them. The words as typed are kept until the person accepts the cleaned-up version, and nothing is sent to the chat until they send it.
Training. We send all of this through Anthropic’s commercial API. Anthropic says, in the terms for that API, that business data sent through it is not used to train its models. We do not train a model of our own on your data.
What we keep. Every time someone asks FieldLink AI for help, we note who asked, which kind of help, how many characters were sent and when. A daily report written up by itself is noted under your company, with nobody named. The note is how we keep each person, and each company’s automatic reports, to a daily limit. Nothing that was sent or sent back is kept in that note. You and your office can read it, and so can FieldLink administrators.
19 // Email
Email in and out
All FieldLink email - invitations, password resets, free trial reminders, notification emails, appointment reminders, service visit changes, the weekly payroll summary, daily log reminders, service reports, daily job reports, T&M tickets, estimates, change orders, invoices, punch lists, notices about paying for your company’s plan and announcements - is delivered by Resend.
Service visit emails to your customers. When your office saves a new, changed or removed visit time, or a different technician, on a service call and ticks the box to email the customer, FieldLink emails the person who sent the service request and the customer’s main contact, each unless your office revoked their access to your service-request page, and the email address on the customer’s record. The email gives the day and arrival window, the service address, the call number, the assigned technician’s first name, and your company’s name and phone, with a link to your service-request page when the customer uses it. The email never holds prices. Replies go to your company’s email address when it has one. Nothing is sent unless the box is ticked.
What we log about an email: who it went to, its subject, what kind it was and what happened to it: sent, delivered, delayed, bounced or marked as spam. Open and click tracking stay off, so we do not record whether a message was opened or which link was clicked. The log never holds the body of the email. An estimate’s own page is the one exception: when somebody opens the link in an estimate emailed to them, the page records it, as described under Estimates.
The email queue. Automatic emails, such as reminders, summaries, notification emails, daily job reports sent by themselves and announcements, and the service reports, daily job reports, T&M tickets, estimates, change orders, invoices and punch lists your company emails, with any message typed for them, go into a queue before they are sent. Unlike the log, the queue holds the text. A sent, failed or skipped message is cleared from it 90 days after it was queued.
A blocked address. When an address bounces or someone marks a message as spam, we stop sending to it and note why. Only a FieldLink administrator can lift the block.
Replies from customers. A customer can reply to a service request by email. We keep the sender’s address, the subject and the text of the reply as part of the job record. The older messages quoted underneath are trimmed off.
Announcements can be turned off. Every announcement has an unsubscribe link. The link stops announcements only, not emails you need, like a password reset.
20 // Public pages
Visiting our website
We count page views on our public pages without knowing who you are.
No IP address is stored. Our page-view records have no place for one. Your IP address is used briefly, in memory, only to stop one machine sending thousands of views a minute, and it is forgotten a minute later. The address is not written down, logged or sent anywhere. To stop one machine inventing visitors, a scrambled form of it that cannot be turned back into the address and changes every hour is kept for two hours beside the random IDs it brought in, never with a page view, and then deleted.
What is stored: the page, the site that sent you here (only its name, such as google.com, not the full address) and your device type (phone, tablet or computer). We store the country, state and city our hosting network reports, and a random ID your browser creates and keeps in its own storage. The ID is not a cookie and is not based on anything about you or your device.
Who is never counted: anyone signed in, our own staff, bots and our development machines.
The robot check. In a web browser, sign-in, sign-up, password reset and the customer pages show Cloudflare Turnstile’s check, which runs in your browser and talks to Cloudflare directly. When you start a free trial, we check the result with Cloudflare, and your IP address is sent with it because the check requires it; we do not keep it. The iPhone and Android apps do not use it.
Fonts and the page itself. Our website - the product page, What’s New, the legal pages and "What this site counts" - is plain web pages, and their fonts come from our own address. Nothing on them is fetched from Google or anyone else. The FieldLink app, from the sign-in page on, draws its screens with an engine and fonts that come from our own address. So do the extra fonts a screen needs for a character our usual fonts do not have, such as an emoji, an accent in a company name or another alphabet: your browser fetches only the ones a screen really draws, from our own address. Your browser used to fetch all of these from Google, and it no longer does.
No trackers. No advertising network, no Google Analytics, no Facebook pixel and no crash-reporting service in FieldLink.
Global Privacy Control. If your browser sends the Global Privacy Control signal, we count nothing. The page checks for it before sending anything, and our server checks for it again when a page view arrives. You do not need to do anything else.
Turning it off yourself. With or without that signal, you can turn counting off or back on from the "What this site counts" page at www.sagetechfieldlink.com/privacy-choices. Turning it off deletes the random ID from your browser, so nothing before is linked to anything after.
The service status page. Our status page at www.sagetechfieldlink.com/status shows whether each part of FieldLink, and each outside service it relies on, is working, and how the last 90 days went. The page records nothing about you: it is never counted as a visit, and reading it sends no cookie and no ID. The status comes from a small program of ours on Cloudflare that checks FieldLink, and reads those services’ own public status pages, every few minutes. The program keeps only whether each check passed, for 90 days, and the incidents we post, and it holds no personal data. The status button and Service status in the FieldLink app read the same page.
A short note the first time. The first time you open a page we count, a short note at the bottom of the screen says what we count, with OK and Do Not Count Me. OK keeps counting on. Do Not Count Me turns it off and deletes the random ID. Counting is on until you answer. Your answer is kept in that browser, and the note does not come back.
21 // Storage
Cookies and browser storage
We set no advertising cookies and no tracking cookies, and no one else sets one through us. The list is everything we keep in your browser.
The random page-view ID. The page-view ID is the only item here that FieldLink does not need to run. The ID is kept in your browser’s storage, not in a cookie, so it is never attached to a request and leaves only inside a page view. You can switch it off, and Global Privacy Control switches it off for you.
Your counting choice. If you turn counting off or on, your choice is kept in that browser only. The choice cannot follow you to another computer, because no account is attached to it, and clearing your site data or using a private window clears it.
Our own staff’s browsers. A browser a FieldLink staff member signs in on keeps a note that stops it being counted. The note holds nothing else and is never sent to us.
Your sign-in. Once you sign in, your browser keeps the session so you are not asked for your password on every screen. Signing out ends it. Our website’s pages only look whether it is there, to offer Open FieldLink instead of Sign in; they never read it or send it anywhere.
Your screen settings. The light or dark look you pick on the website or the office portal, and whether the calculator works sums in scientific or standard order, are kept on that device only and never sent to us. The website and the office portal share that choice in the same browser. The calculator setting is kept for each person, so a workmate on the same phone keeps their own.
Your language on our website. If you pick English or Español on our website, the choice is kept in that browser only and never sent to us, and FieldLink’s sign-in page in the same browser follows it. The first time a browser set to Spanish opens one of our English pages, the website opens the Spanish page instead and keeps a note that it has, so it never does that again.
Your office menu order. On the office website, a copy of the left-menu order you chose is kept in that browser so the menu does not jump while your account loads. The same order is saved to your account, as described under Signing in and staying signed in. Only you can read or change that order.
What the app keeps so it works without a signal. FieldLink keeps the jobs and cost codes it last saw, the open service calls you can clock into (each call’s number, customer name and service address), the punch you have open, your company’s clock-out questions, how far the device’s clock was from ours, and any punch it could not send. Every person’s copy is kept apart, so nobody else who signs in on that device can see yours. FieldLink does this in the browser on an office computer exactly as it does on a phone. A waiting punch holds everything the punch itself would send: the GPS fix taken at the moment you punched, the job and cost code, your clock-out answers (about being hurt, whether your time is right and any questions your company added) and the clock-in photo of your face. The waiting punch stays on that device until the punch reaches us, and then it is removed.
Daily logs, receipt photos and service call photos waiting to be sent. While you write a daily log, FieldLink keeps a copy of its words, and of any photo not sent yet with where it was taken and any Live Photo video that goes with it, on that phone or in that browser, so a lost signal or a closed app does not lose the work. A receipt photo is kept the same way until its receipt is started, with your answers about how you paid and whether you want to be paid back, and where and when the photo was taken. A photo taken on a service call with no signal is kept the same way, with where it was taken, until it is sent. An item walked on a punch list with no signal is kept the same way, with its words and photos, until it is sent. A waiting photo is kept as the camera or the photo picker handed it over; your company’s photo settings are applied when it is sent. A copy is removed once it is sent, when you discard it, or when you choose to sign out, which counts what is waiting and asks first. Signing out from the page that says your account is switched off keeps the copy for when the account is switched back on. If FieldLink ends your session instead, the copy stays on that device for your next sign-in there, and nobody else who signs in on it can see it. If you do not use FieldLink on that device for 30 days, your copies are removed the next time someone else opens FieldLink there. Clearing the site’s data in a browser removes it at once. Nothing in a copy reaches us until it is sent.
An estimate saved with no signal. A new estimate saved on a phone or in a browser with no signal is kept there, with everything typed on it, your cost, markup and private notes included, until it is sent. The copy goes when the daily logs and photos above go, and nobody else who signs in on that device can see it. Photos are added to an estimate only once it is saved with a signal.
A T&M ticket written or signed with no signal. A T&M ticket written or signed on a phone with no signal is kept there until it is sent: its rows and photos and, once it is signed, the signer’s name, title and email and the drawing of their signature. The copy goes when the daily logs and photos above go, and nobody else who signs in on that device can see it.
The job facts for T&M tickets. So a T&M ticket can be written with no signal, the phone keeps what FieldLink last said about each job and day it was asked about: the job’s name, number and address and its customer, who clocked in there and for how long, the job’s people who may sign, the classifications, the change orders by number and title, the machines on the job, the parts and their units and your company’s own words above the signature. No price, no rate and no email address is in it. The copy is kept for one person in one company at a time and is never read for anybody else, and every sign-out clears it.
Your company’s Parts & Labor List. When somebody who sees your company’s prices opens its Parts & Labor List, FieldLink keeps a copy on that phone or in that browser, so items can be found for an estimate with no signal. The copy holds every item, retired ones included: its name, description and any FieldLink AI version of it, unit, kind, skill level, part number, barcode, which of your categories it is filed under, and where its picture is kept; its price, whether it is taxed and at which of your saved rates; your private notes about it; your cost, where that cost came from and on what day, and which markup it takes; when it was added, changed, last used or retired, and why it was retired; and the name of whoever added it. The copy is kept for one person in one company at a time and is never read for anybody else, and opening the Parts & Labor List again replaces it. Every sign-out clears it, whether you choose to sign out or FieldLink ends your session. A FieldLink administrator helping your company in support mode keeps the same copy in their browser until they sign out.
What the app keeps so it can open without a signal. The app keeps a copy of what FieldLink last told it about the person signed in: your name, sign-in name, email, phone, role, access level and job title, the days you were invited, chose your password and joined, where your profile picture is stored, your company’s name, address, phone, plan and settings, which parts of FieldLink you can use, your permissions, the order of your buttons, and when the app last reached us. Your pay rate, employee number and payroll name are never in it. The copy lets the app open with no signal when it last reached us in the past 30 days, and it only decides what the app shows; FieldLink still checks every punch and draft when it is sent. The copy holds one account at a time and is never used for anybody else: another account signing in on that device removes yours. Every sign-out clears it, whether you choose to sign out or FieldLink ends your session, and so does FieldLink saying the account is switched off or removed. No copy is kept for a customer’s sign-in or a FieldLink staff member.
How a phone keeps these copies. On an iPhone or an Android phone, FieldLink locks everything it keeps there, the copies above, your messages and the work waiting to be sent, with a key that only that phone holds, in the iPhone’s keychain or the Android Keystore. Without that key the files cannot be read, even by copying them off the phone. A punch waiting on an iPhone is kept as before, so a phone restored from its backup can still send it. A copy that can no longer be opened is fetched again, and waiting work that can no longer be opened is kept, never deleted. In a browser, nothing about this changes.
Signing out, and deleting your account. Choosing to sign out clears the jobs, cost codes, service calls and the rest of what the app keeps so it works without a signal, the copy it opens from, the copy of your company’s Parts & Labor List and the T&M job facts, and any daily log, punch list item, T&M ticket, receipt photo, service call photo or estimate not sent yet once you say so, but keeps any unsent punch, because it is hours you have not been paid for, and the app tells you how many are still waiting. Deleting your own account from Account settings on that device clears those, because a deleted account can never send them. If your account is deleted any other way, such as the office approving your request to be deleted or removing you, any punch still waiting stays on that device, and so can the rest of what the app keeps so it works without a signal. Signing out from the page that says your account is switched off clears the same as choosing to sign out, except the daily logs, punch list items, T&M tickets, photos and estimates, which wait with your punches for when the account is switched back on. If FieldLink ends your session, the copy the app opens from, the copy of the Parts & Labor List and the T&M job facts are cleared, phone unlock is turned off, your FieldLink AI answer is forgotten and the phone’s key to your employee file is removed. Your waiting punches, daily logs, punch list items, T&M tickets, photos and estimates stay as described above. The jobs, cost codes, service calls and the rest of what the app keeps so it works without a signal stay on that device, kept apart for your account, until you sign in there again and choose to sign out, or the site’s data is cleared in a browser.
22 // Sessions
Signing in and staying signed in
Sessions. While you use the app, we keep one record per session, not one a minute. The record holds when the session started, when it was last seen and which platform it was on, and there is no list of screens on it. We use it to see whether FieldLink is being used and, if a punch is left open, to find when you last used the app. The only things FieldLink records you opening are job files, company files and documents in an employee file, as described above.
Sign-in records. Our hosting provider’s sign-in service keeps its own log of sign-ins, sign-outs and password resets, including the IP address each sign-in came from, and keeps the IP address and browser of each signed-in session until that session ends. We use it to count sign-ins and to look into an account someone is worried about. FieldLink’s own screens never show an IP address or which browser you used.
Signing in with a username. To stop anyone guessing passwords, FieldLink counts the tries made with each username and from each network address. The username and the address are kept only as a scrambled code, never as typed or as sent, and each count is deleted within about two hours.
Authenticator app. If you set one up, its recovery codes are shown once on screen and are never emailed.
On your device. The app keeps your session and a few preferences on it, plus the work waiting to be sent and what it needs without a signal: the copy it opens from, the job facts kept for T&M tickets and, for people who see your company’s prices, a copy of its Parts & Labor List, as listed under Cookies and browser storage. Signing out clears the session and those copies.
Office menu order. On the office website, the order you put the left menu in is saved to your account so it follows you to another browser or computer. Only you can read or change that order. Saving an order never turns on a page your role cannot open. Reset menu order clears it. A copy is kept in the browser so the menu does not jump while the account is loading.
FieldLink support mode. To help your company, a FieldLink administrator can enter your company’s account with no more access than one of your admins has, never HR, and less wherever this page says so, except that with your company’s approval support may read your messages, as Messages between your coworkers says. Every entry and exit is written to an audit log, and support is never counted as one of your employees.
The control panel activity list. FieldLink’s control panel lists changes made there: companies, plans, staff and settings. What your people change inside your company stays on your company’s own record. Owners, admins and the office can read that record on the company dashboard. A technician cannot. Pay rates and job money stay off that list for anyone who cannot see them.
23 // Inside
Who sees what inside your company
Your company’s owners and admins decide, using roles, access levels they add on top of Technician, Office or Admin, named permissions for sensitive areas (HR, safety, live map, purchasing, billing, fleet and crew lead) and switches that turn a module off for one person, a whole role or one of those levels. A level built on Technician never sees a job’s money or a coworker’s pay rate, whatever its switches say.
Phone Settings. An owner or an admin in your company’s account can open Phone Settings and look at another employee’s FieldLink phone as that person sees it: their button layout, jobs, daily logs, receipts, punches, hours, service calls, customer requests, tools, rental equipment, the File Vault, crew list, shared looks and live map. The viewer stays signed in as themselves; nothing signs the viewer in as the employee. Buttons that would change data, take a photo, use this computer’s location or send a notice are blocked in the preview. Job money and rates follow what that employee is allowed to see. The unlock that opens that employee’s personal documents stays shut in the preview. A FieldLink administrator cannot be the person previewed.
Some things are locked, no matter who asks. Only the owner grants HR. A technician never sees a coworker’s pay rate or clock photo. A technician sees a job’s money, the customer charges on a service call they work, or an estimate, only if an owner or admin gives them the Billing permission, and never on an access level built on Technician. Only the owner and people with HR access open somebody else’s employee file. Only the owner changes their own employee file. People fix their own time by asking for a correction, and someone else in the office decides it. The owner, and anyone the owner gives Edits own time, may change their own punches instead; each change still needs a reason, and the reason, who made it and when are kept in the punch’s history.
Search and desktop list exports. On an iPhone, an iPad or an Android phone, in the app or in a browser, no list offers Export and no spreadsheet or payroll file can be downloaded. Search, filters, counts, document attachments and report PDFs work there as they do everywhere else. Search finds matching rows among the records your role can already open. On a computer, a list that offers Export writes the matching rows the person can already see, every page of them, to an Excel or CSV file on that computer, so names, emails, phone numbers, addresses, job and customer details, hours, incident notes and the other columns that list shows can leave the app that way. Job money columns stay out of the file unless that person is allowed to see job money. Pay rates are not put in any export. A full bank or tax number is never put in an export. Every export is noted with who asked, which list, how many rows, Excel or CSV and the search words, never the cells: under your company, or under FieldLink’s own record for a FieldLink administrator with no company open. A File Vault drawing itself is still never handed out as a file; Export on a vault list writes only the names and details on that screen.
Your customer list. Owners, admins and the office keep your customer list. With Estimates & Invoices on, a technician with the Billing permission sees each customer’s name, main contact and address while picking the customer for an estimate, and can add a new customer and its main contact from there. The office is told, and the audit log records who added it.
Messages. Only the people in a chat read it. Owners, admins, the office and anyone given Message reports see a message from a chat they are not in only when somebody reports it, and only the owner and an admin holding the HR permission read the words of a message an owner or an admin removed. FieldLink support reads them only after your owner, an admin or the office approves its request, for 24 hours at most, and every look shows in your Recent activity. Messages between your coworkers, above, says the rest.
Your customers, when they sign in, belong to no company inside FieldLink. Customers can send a service request, see their own requests and read the report for work done for them, and nothing else. While the customer is archived, portal sign-in cannot send a request or open those pages, and a restore turns it back on.
24 // Others
The companies that help us run it
Here is every one of them and what each gets.
Supabase - the database, sign-in service and file storage. Everything in FieldLink is stored with them, in the United States. Some of the map and address services below are in Europe, and what each one is sent is said under its name. Like any web service, Supabase’s own request logs keep, for a limited time that Supabase sets, the IP address and browser of every request that reaches it and the address it asked for, whether from the app, an online estimate or invoice being opened or answered, an address suggestion or an unsubscribe link. FieldLink does not copy those logs, and uses them only to look into a problem or an account someone is worried about.
Anthropic (Claude) - the AI service behind FieldLink AI, and the only one FieldLink uses. Anthropic gets the photo of a receipt being scanned and, for a pump display, the grade-row cut-out described above when one is sent, the text of a note, a punch list item or an estimate’s words being tidied, the description of the work for an estimate being drafted, the words of a day’s daily logs for its daily report, and the words of a message being translated or cleaned up, along with the details described above. Nothing else.
Resend - email out and email in: the address, the subject and the message.
Cloudflare - the robot check on our sign-in, sign-up, password reset and customer pages in a web browser, and the network our website, the FieldLink web app and the pages your customers open from a link are served through.
Intuit (QuickBooks Online) - only if your company connects it. FieldLink reads your QuickBooks employee list (names, email addresses and whether each is active) and customer list (names, main contact details, billing addresses and whether each is active) so your office can match and maintain them. An owner or an admin can review and send nonblank customer name, main contact, email, phone and complete billing-address changes back to QuickBooks. FieldLink sends approved receipts with their photos as the sync runs, and a week's approved hours only when an owner or an admin sends that approved week from Timesheets, for the employees and customers matched between the two. An owner or an admin can add someone who is in FieldLink and not in QuickBooks as a QuickBooks employee. FieldLink sends that person’s name, email and phone, and does not send a home address, a hire date, a pay rate, a tax form or direct deposit. Payroll setup stays in QuickBooks. Once FieldLink turns on sending service call invoices, whoever sends one (the office, or someone with the Billing permission) gives QuickBooks the customer, the service address, the call number and the day it was completed, each line’s description, product, hours or quantity and price, which lines are taxed, and the tax, never a technician’s name. FieldLink then reads back whether that invoice was paid, emailed, voided or deleted. To offer them on an invoice, FieldLink reads the names of your QuickBooks products and services, never their prices. Whenever your office presses Sync Now, FieldLink keeps a read-only copy of your QuickBooks records: customers, employees, vendors, items, accounts, invoices, estimates, payments, bills, purchases, time activities, journal entries, deposits, attachments and the rest of your company file. Bank and account numbers and tax IDs are taken out before it is kept. Only FieldLink support can read the copy, inside your company in support mode, to help with a QuickBooks problem; nobody in your company and no customer can. FieldLink keeps the newest complete copy and deletes the one before it. Disconnecting QuickBooks deletes the copy and the employee and customer lists read from QuickBooks, and so does your company closing or being deleted. The connection’s keys are stored where nothing in the app can read them, and disconnecting revokes them.
Stripe - card, Apple Pay and Google Pay payments for your company’s plan, only when an owner or an admin pays that way. FieldLink sends Stripe the email that person signs in with, your company’s FieldLink ID, the plan and whether it is monthly or yearly, the plan’s name and price in US dollars, any extra storage your company buys and its price, the addresses of the FieldLink pages to come back to and, when trial or paid time is left, the day billing starts. To open Stripe’s billing page, change the plan or its extra storage, or cancel it when your company closes or is removed from FieldLink, FieldLink sends Stripe its own numbers for your company and its plan, and the new price. Stripe takes the card, Apple Pay or Google Pay details itself, and FieldLink never sees them. Stripe tells FieldLink when a payment goes through or fails and when the plan or its extra storage changes or ends.
PayPal - PayPal payments for your company’s plan, only when an owner or an admin chooses PayPal. FieldLink sends PayPal our product’s name and each plan’s name and price in US dollars and the price of extra storage, and for your company’s plan the plan, any extra storage it has, your company’s FieldLink ID, the email the owner or admin signs in with, our name to show on PayPal’s pages, the addresses of the FieldLink pages to come back to and, when trial or paid time is left, the day billing starts. FieldLink asks PayPal to cancel or change the plan when an owner or an admin does it in FieldLink, and to cancel it when your company closes or is removed from FieldLink, sends every message PayPal sends us back to PayPal to check it is genuine, and reads the plan’s current state from PayPal. The person paying signs in to PayPal on PayPal’s own pages, and FieldLink never sees their PayPal password or what they pay with.
GIPHY (Shutterstock) - GIF search in Messages, while your company leaves it on. Your phone or browser asks GIPHY directly, never through us: the words searched and the language FieldLink is shown in, which GIFs are shown and which one is sent, and a random ID GIPHY gives that install of FieldLink, with the device’s IP address as any web request carries. GIPHY is never sent a name, an email, a company or the words of a message.
Apple Push Notification service and Google Firebase Cloud Messaging - the alerts for new messages on an iPhone and on an Android phone, once the person allows them. FieldLink’s own server sends Apple or Google the phone’s push token, the alert’s title and words, the number on the app’s icon and which chat to open. The title is the chat’s name, or who wrote in a chat between two people. The words name who wrote and carry the start of the message, up to 120 characters: a poll’s question, or for a reaction the message reacted to. Everybody’s alerts carry those words unless the person turns off Show the words in alerts, which leaves only who wrote, such as "Riley sent a photo".
The National Weather Service - a job site’s coordinates, to put the day’s weather on a daily report. The National Weather Service is a US government service and needs no account or key. Nothing about a person goes with the request, only a point on the map. When someone opens a report, the request is made by their phone or browser, so it carries its IP address, as any web request does. For a daily report your company sends automatically, FieldLink’s own server asks, so nothing about any phone goes with it.
Photon (Komoot) - the addresses suggested under an address box while you type one. FieldLink’s own server sends Photon the words typed and, on a job that already has a pin on the map, that pin rounded to within about half a mile, so nearby addresses come first. Without a job pin, it may send a point near your company’s own business address instead, rounded the same way, so addresses near your company come first. To find that point, FieldLink’s own server sends the five-digit ZIP of that address to Nominatim’s postal search, or uses the middle of its state. Where no company address is on file, the ZIP and state typed on the same form are used the same way: on sign-up, on a customer’s service request, when FieldLink staff type a company’s address, and for a company with no ZIP or state saved. A pin put where your phone or computer is, with "Use my current location", is never sent, and nothing else about where your phone or computer is goes with the lookup. Photon is not told who is asking or which company they work for. Nothing it sends back is kept, except an address somebody picks, which is saved like one typed by hand. On a job, the point it gives for that address becomes the job’s pin on the map. Photon is a free search of OpenStreetMap data, run by Komoot in Germany. No account and no key.
OpenStreetMap - the street map behind the live map and the job site map, and "Find on map" on the job site page, which sends them the address typed there to put the job’s pin on it. For address suggestions in a box with no job pin, FieldLink’s own server sends Nominatim’s postal search a five-digit ZIP: the company’s own, or one typed on a form where there is no company address. A fuel receipt built from a pump photo sends the photo’s location, through FieldLink’s own server, to free public Overpass mirrors to name the nearest fuel station. The mirrors are overpass-api.de (run by FOSSGIS e.V. in Germany), overpass.kumi.systems and overpass.private.coffee. One mirror is asked at a time, starting with overpass-api.de. A timeout or an error does not ask another mirror; the other mirrors stay listed for a network where the first is blocked. When no station comes back, Nominatim reads the street, city, state and ZIP at the photo's point. Only the point is sent to those mirrors, not who is asking or which company. If the station’s address is incomplete, Nominatim fills in the missing street, city, state or ZIP from that station’s point. When the station still has a US ZIP and no city, FieldLink’s own server sends the five-digit ZIP to Nominatim’s postal search so the city can be named. The ZIP search is not told who is asking or which company. A job site with a pin and a blank city or state sends that pin to Nominatim, through FieldLink’s own server, to fill the blank. A city or a state somebody typed is kept. Nominatim is not told who is asking or which company. Loading the map from a browser tells their servers the device’s IP address and which part of the map is on screen, as any web map does. No account and no key.
The U.S. Geological Survey (The National Map) - the Terrain and Satellite views of the live map and the job site map, only when someone picks one of them. Loading those views tells their servers the device’s IP address and which part of the map is on screen, the same as the street map. The National Map is a US government service run by the U.S. Geological Survey and needs no account or key.
Apple and Google (the dictation built into your phone) - only when you tap the microphone to dictate a daily log, an estimate’s job or a punch list item, and only what your own device sends them to turn speech into words, under their terms. FieldLink never receives the audio, and nothing else about you goes with it.
Apple (the App Store lookup) - an iPhone asks it for FieldLink’s latest version number only, to know whether an update is out. The question names FieldLink and nothing about you; Apple sees only the phone’s IP address, as for any web page.
Apple and Google (checking the app is genuine) - the iPhone app asks Apple’s App Attest, and the Android app Google Play Integrity, to confirm it is a genuine FieldLink, with a one-time code from FieldLink and nothing about you. FieldLink’s server checks Apple’s answer against Apple’s own certificate and asks Google to read its answer. Apple and Google see the phone, the app and the code, under their terms.
Apple and Google (the barcode reader built into your phone) - when you scan an equipment label, the phone reads it itself. The picture never leaves the device, though Google’s reader on Android may report its own usage to Google under their terms.
What they may do with it. Supabase, Resend and Cloudflare handle what we send them under data protection terms that limit them to providing their service to us and require them to keep it secure. The one exception is Cloudflare’s robot check: Cloudflare uses what the check gathers in your browser to improve how it tells people from bots. Anthropic keeps what we send for up to 30 days to check for misuse, and longer only for a request it flags as misuse or where the law requires it, and does not train its models on it. Intuit receives only what your company sends to its own QuickBooks Online account, under your company’s agreement with Intuit. Stripe and PayPal take payment details themselves, under their own privacy policies, and FieldLink never sees those details. The free public map, address and weather services are sent only the words typed in an address box, a point on the map or a ZIP code, never a person’s name or company. The dictation and the barcode reader built into your phone run under your own agreement with Apple or Google. GIPHY answers a GIF search under its own terms and privacy policy, and Apple and Google deliver an alert to your phone under theirs.
No one else. We do not give your records to data brokers, advertisers or "partners", and nobody can buy access to them.
25 // Keeping
How long we keep it
We do not delete your work records on a timer. Hours, punch history, injuries and job records are what a contractor needs years later, when someone asks about an old job. Nothing your company puts into FieldLink (a punch, a receipt, a daily log, a photo, a service call, an estimate, a customer, a tool or a piece of equipment) is ever removed on a schedule.
What is removed on a schedule is FieldLink’s own housekeeping: its messages, queues and logs. The list below is complete.
A notification you have already read, 180 days after it was made. One you have not read yet stays until you read it, however old it gets.
A queued email we are done with, 90 days after it was queued. "Done with" means it was sent, it failed or it was skipped because there was no point sending it. An email still waiting its turn is never touched.
The email log, 400 days after the email was logged. The window is a year and a month, so this month can still be compared with the same month last year. The recipient, subject, outcome and delivery history are removed together. A blocked address stays blocked.
The record of a QuickBooks Online sync run, after 180 days. The row is the note of when the QuickBooks sync ran and how it went. The record of what was sent to QuickBooks is kept, and so is the list of sync problems waiting for your office.
The record of one app session, after 200 days. The row is a line saying someone had FieldLink open, on what kind of device and for how long. Our internal dashboard counts are built from it, and they never look back more than 90 days.
The record of looking at a drawing together, 90 days after it ended. The row says who invited whom to look at a file in the File Vault, when, and how it ended. The file itself is not touched.
A request to make a new phone yours, a year after the office answered it. The row says which phone asked, when, and the office’s answer. A request still waiting for an answer is never touched, and the phone paired to you stays yours.
The record of a punch that was sent in late, after 90 days. When a phone takes a punch with no signal, FieldLink keeps a small record of it so the punch cannot be saved twice if it is sent again. A punch older than 30 days is not accepted, so by 90 days that record has no work left to do. The punch itself is never removed, only this record.
The note that your office has already been told something, after 180 days. The row is how FieldLink avoids telling your office the same thing twice, such as someone still clocked in late at night, a camera that would not open or a punch on someone else’s phone. A note about a punch that is still open is never removed, however old it gets.
The record that a customer’s reply reached us, after 400 days. The row is the line saying an email came in and what we did with it, kept as long as the email log. The reply itself stays on its service request.
An invitation or password reset link, the night after its 24 hours end. The row is the email address it went to and a scrambled form of the link.
Sign-in records, after 400 days. Our hosting provider’s log of sign-ins, sign-outs and password resets, with the IP address each came from, is trimmed after a year and a month.
The note of each FieldLink AI use, after 400 days. The row says who used it, for what and how many characters were sent, never the words.
The note of each list export, after 400 days. The row says who exported which list, how many rows, Excel or CSV and the search words, never the cells.
Which phone a sign-in was on. The record is removed 30 days after it was last seen. What your office was told about a punch on someone else’s phone stays with its other notifications and email.
The daily count of address suggestions, after 400 days. The row is one number a day, how many address, station and ZIP-city lookups were made, and how many of them were from people not signed in. The ZIP search the server runs inside a station lookup counts as that one station lookup. The city lookup the phone runs on its own afterward counts as its own lookup. What was typed, the point, the ZIP, and who asked are never written down with the count. The lookup server remembers a point, a ZIP, or the words typed for up to a day, in memory only, so it does not ask the map service twice, and then forgets them.
The daily count of reads of online estimates and invoices, after 400 days. The row is one number a day for each company, how many times its online estimates, invoices and their files were read. Nothing about who read them is written down with the count.
An estimate’s online link and its openings. Kept with the estimate or invoice for as long as your company keeps it, with the email addresses it was emailed to. A link that has stopped never opens again.
A try at opening an employee file, after 90 days. We keep who tried, when, whether the try was right and whether it was the password or the phone’s own check, never the password typed or the phone’s signature. Only the last 15 minutes decide whether a file is open or locked.
A phone’s key for opening an employee file, until it is stopped. Only its public half, the kind of phone and when it was last used. The key goes when you stop it, sign out on that phone, change or reset your password, are switched off or leave the company, or when a sixth phone takes the place of the one you used longest ago. The one-time codes it signs are gone within an hour.
A try at a recovery code, after 90 days. We keep who tried, when and whether the try was right, never the code typed. Wrong tries in the last 15 minutes decide whether recovery codes are locked.
The day’s trail of live positions, at your company’s own midnight, as described above. Only the current day is ever kept.
Anonymous page views. A page view on our public website is removed 180 days after it was counted. Our internal dashboard never looks back more than 90 days, so there is no reason to keep them longer.
The note that owners and admins were told about a failed payment, until your company pays. The note is how FieldLink tells them only once about each step, and it is removed the moment the plan is paid.
Your plan, and the record of each message from Stripe and PayPal, with no time limit. The plan stays as long as your company’s records do, and erasing them erases it. The record of each message stays after that, with no company named on it. Stripe and PayPal keep their own records under their own rules, and the billing emails follow the email rules above.
The audit log is never trimmed. The record of what has gone to QuickBooks is kept for good, because losing it would send the same hours and receipts again, and so are the records of who opened a job file, a company file or a document in an employee file (as long as the file) and the history of an estimate’s answers (as long as the estimate).
A daily log or daily report your office deletes goes to an archive first. The item leaves every list, and a log leaves the day’s report. Its words, photos, signature and PDFs stay in the archive until an owner, an admin or the office restores it or deletes it permanently. Nothing empties the archive on a timer. Deleting permanently erases it and every file that is only its own, for good. A daily report that was already approved keeps its own copy of that day until it is reopened or deleted. The audit log keeps a short note of what it was: the job, the day, who wrote or signed it, where it was sent and who deleted it, but never its words or photos.
A punch list that was sent is put away, never deleted. The list stays with your company’s records, its photos and PDFs included, like the job’s other records, and an owner, an admin or the office can bring it back. Only a list nobody was sent can be deleted, and its photos and PDFs go with it. The audit log keeps a short note of what was done to each list and item, never their words or photos.
Messages are kept until they are deleted or removed for everyone. A message and its photos stay in the chat until the person who sent it deletes or unsends it for everyone, or it is removed for everyone; deleting a message from your own view keeps it for everyone else. A chat you delete from your list waits in Recently Deleted for 30 days. A message waiting to be sent later is deleted when it is sent or its writer deletes it. The words and photos of a message deleted, unsent or removed for everyone stay for the owner and HR until the owner deletes them permanently, and a report stays with no time limit. The queue of alerts waiting to reach a phone is removed 30 days after each alert was sent.
A customer your office deletes moves to Archived customers. The customer, its people, jobs, service calls, estimates and receipts stay on file. Owners, admins and the office can archive or restore, when Customer Portal or Estimates & Invoices is on. While archived, portal sign-in cannot send a request or open those pages, and a restore turns it back on. Nothing erases a single customer from Customers; only removing or erasing the whole company can take that company’s customers off FieldLink. The audit log records every archive and restore.
A receipt in any status can be deleted for good. The person who made it, or anyone who can already review receipts, can delete it whether it is a draft, waiting for approval, sent back, approved or in the books. Flags, reimbursement status and payment method do not prevent deletion. The receipt and its photo are removed for good, with no archive and no audit-log note of the delete. The office’s note and review stamp are part of that receipt and go with it. A receipt that named it as a duplicate stays, with the link cleared. A QuickBooks send record for it stays with the receipt cleared off, and an open QuickBooks problem for it is removed with the receipt.
A document removed from Company files or an employee file waits under Removed files. Nothing deletes it on a timer. The office can delete a removed company file permanently, and the owner or someone with HR access a removed document in an employee file. Deleting permanently erases the document, its file and the record of who opened it, for good. The audit log keeps a short note of it: for a company file, its name, who added it, who removed it and why, and who deleted it; for an employee file, only whose file it was and who deleted it, never the document’s name or the reason.
When a person leaves a company, their sign-in is deleted and their profile stays behind as a marker. The name is kept so their hours still carry it, and their email, phone number and picture are wiped. Their employee file stays with the company’s records. Their email address stays in three places: our audit log’s note that the account was deleted, the email log until it is removed after 400 days, and our list of blocked addresses if mail to it bounced.
A sign-up nobody verified. The name, company and business address typed on the sign-up page stay until the same address signs up again.
Closing a company takes thirty days. The owners are emailed, and any owner or admin can cancel the closing in that time. At the end, everyone in the company is locked out, their sessions end, every owner’s sign-in is deleted and its paid plan is canceled with Stripe or PayPal. The records are kept, and nothing reopens a closed company.
When we remove a company from FieldLink, everyone in it is locked out, its customer portal stops taking requests, nothing more is emailed, the QuickBooks Online sync stops and its paid plan is canceled with Stripe or PayPal. Every record stays, and the removal can be undone, though undoing it does not start the plan again. Erasing everything, files included, is a separate step. A FieldLink administrator must type the company’s name to confirm it, and it is written to an audit log.
If your company wants its records erased, write to us and we will erase them.
26 // Your rights
Getting a copy of your data, or deleting it
Owners and customers delete their own accounts in the app. Open Account settings and choose Delete account, then type DELETE and your password again. Account deletion deletes your account and no one else’s. A company’s only owner must first hand the company over on the Employees page, or close the company.
Employees ask from the same place. Your account holds your employer’s record of your hours, so Account settings offers Request account deletion instead. An owner or admin at your company approves or declines it, and you can withdraw the request until they answer. If it is approved, your sign-in is deleted, and the work you logged stays with your employer under your name.
Turning off page-view counting, without asking us. The "What this site counts" page, at www.sagetechfieldlink.com/privacy-choices, turns it off and back on for the browser you are using, and Global Privacy Control turns it off automatically. None of that needs an account, and every page still works the same.
What else you can ask us for: a copy of what we hold about you, a correction, a deletion or a plain answer about anything on this page.
Where to write: legal@sagetechfieldlink.com for accounts and data requests, and support@sagetechfieldlink.com for anything else. A person answers, not a form, and we aim to reply within a few business days.
If you work for a contractor, your employer owns the records of your work, so a request to erase your hours is theirs to decide. We will pass it on and tell you who has it.
27 // Security
Keeping it safe
The rules live in the database. Hiding a button is a courtesy; the database is what refuses. Every record is kept separate by company, every change made in a module is checked again on the server and sensitive actions are audited.
Keys never ship in the app. FieldLink AI, email, Intuit, Stripe and PayPal keys exist only on our servers. Nothing on a phone holds a secret that could reach another company’s data.
Files are private by default. A file is served only after the server checks who is asking and which area the file belongs to.
No system is perfect. If something puts your records at risk, we will tell the affected companies what we know, what we are doing and what they should do, as soon as we have something worth saying.
28 // Changes
Children and changes to this page
FieldLink is a tool for people at work. FieldLink is not meant for children, and we do not knowingly collect anything about anyone under 18. If you believe a child’s details are in FieldLink, write to us and we will remove them.
When the product changes, this page changes with it. A feature that collects something new does not ship until this page says so. The date at the top shows when the page last changed.
For a major change, such as sharing something with anyone not named above, we will tell you in the app and by email rather than quietly editing a line.