Never
Security
Your job data stays on its own circuit.
Each company’s jobs sit in a closed loop. Every request is checked on our server before it touches a record, and the database is copied out, encrypted, every night. This page says what the software does, in plain words.
Walled off
Every request, checked on our server.
The app never takes the browser’s word for who you are or which company you work for. Our server works it out on every request, from records only it holds.
What the phone sends
Our server looks it up
Backed by the database too
Who are you?
This device’s sign-in, looked up in our database every time. A signed-out, removed or expired device gets nothing.
Which company?
Whether you’re on that job today, and which company’s space you’re in. A job id from another company opens nothing.
What role?
Office, super, foreman, estimator or crew, and what your company’s settings let that role do.
One locked-down roleThe app reaches the data through it. It can see nothing else.
Row level securitySwitched on and forced on every table
Public sign-in rolesRefused outright
Who sees what
On a shared job, each company keeps its own.
The model and the clashes between trades are shared. Everything else stays with the company it belongs to, unless someone shares it on purpose.
One jobJob 214Your company, a mechanical sub and the GC all work on it
Your companyOffice, supers, foremen, estimators and crew
10 of 10
- ClashDuct vs conduit, level 2
- Sent to themMove the hanger off the conduit, level 3
- Shared with themSleeve sizes, level 2
- Shared with the GCCeiling height, level 2
- Shared with the GCFire stopping at the riser, level 1
- ItemPanel LP-2A, photo of the fix
- Price fileYour price file
- QuoteYour quote for level 3
- TeamYour team list
- ChatYour crew chat room
Who can invite, share, upload model versions or clear a fix is a setting your company controls.
Another tradeThe mechanical sub
3 of 10
- ClashDuct vs conduit, level 2
- Sent to themMove the hanger off the conduit, level 3
- Shared with themSleeve sizes, level 2
- Shared with the GCCeiling height, level 2Hidden
- Shared with the GCFire stopping at the riser, level 1Hidden
- ItemPanel LP-2A, photo of the fixHidden
- Price fileYour price fileHidden
- QuoteYour quote for level 3Hidden
- TeamYour team listHidden
- ChatYour crew chat roomHidden
Sees only what involves them: items they made, items sent to them, clashes with their trade, and what you share with them.
The GCThe general contractor
2 of 10
- ClashDuct vs conduit, level 2Hidden
- Sent to themMove the hanger off the conduit, level 3Hidden
- Shared with themSleeve sizes, level 2Hidden
- Shared with the GCCeiling height, level 2
- Shared with the GCFire stopping at the riser, level 1
- ItemPanel LP-2A, photo of the fixHidden
- Price fileYour price fileHidden
- QuoteYour quote for level 3Hidden
- TeamYour team listHidden
- ChatYour crew chat roomHidden
Sees what you share with the GC.
Never shown to another trade or the GC
- Price files
- Quotes
- Team list
- Documents
- Drawing sets
- Your own chat rooms
The GC, by default
Chat with you in the GC roomOn by default
Clearing your itemsOff unless you turn it on
Signing in
Links that work once. Devices you can see.
No passwords to share or forget. People join by a link, and every phone has its own sign-in that your office can end.
Links
15 min
Emailed sign-in link
Works once
A mail scanner that opens it first doesn’t use it up.
7 days
Invite link
Works once
We keep only a fingerprint of it, never the link itself.
Signed-in phones
30 days
A phone left unused
Then signed out
Signed out after 30 days without use.
180 days
Any signed-in phone
Then signed out
Signed out after 180 days, however much it’s used.
-
Still good
A mail scanner opens itIt only sees this page. The link is still good.
-
Used up
You open itYour browser takes the next step and signs you in. The link is used up.
-
Refused
Someone opens it againRefused. It worked once.
Signed-in devices
MikeForeman · iPhone
Signed inSigned outDanaSuper · Android phone
Signed inSigned outDanaSuper · iPad
Signed inSigned out
Activity log
- Device signed outMike’s iPhone, by the office
- Dana removedBoth of her devices signed out at once
What you and your office control
- Sign out on any of your devices, any time.
- Your office sees every signed-in device on a job, and can sign one out.
- Remove someone and every device they have is signed out at once.
- Joins, invites, role changes, removals and device sign-outs go in the job’s activity log.
Encryption
Locked on the way. Locked at rest.
On the way, a record is unreadable to anyone in between. At rest, it is encrypted on disk, and the file store has no public links.
On the way
At rest
HTTPSPlain HTTP is sent to HTTPS, and browsers are told to stay on it
EncryptedThe database’s certificate is checked first
Database
Encrypted, AES-256
By our database host, Supabase
Photos and files, from your phone
Straight to private storageA permission for one file, one type and its exact size, good for 15 minutes
File store
Encrypted, AES-256
By our file store, Vercel Blob. Private, with no public links.
Taken out of every photo before anyone on the job sees it
On the way
- Every connection is HTTPS. Plain HTTP is sent to HTTPS, and browsers are told to stay on HTTPS.
- Our servers talk to the database over an encrypted connection, and check the database’s certificate first.
- Files go from your phone straight to private storage, with a permission for one file, one type and its exact size, good for 15 minutes.
At rest
- The database is encrypted at rest with AES-256 by our database host, Supabase.
- Photos, models and documents are encrypted at rest with AES-256 by our file store, Vercel Blob. The store is private, with no public links.
- Download links run out within minutes.
- Location and camera details are taken out of every photo before anyone on the job sees it.
Backups
Copied out every night, sealed before it leaves.
Every night at 10:00 UTC the whole database is copied, every table, and encrypted with AES-256-GCM before it’s written. It goes to a separate private store kept only for backups, with its own access key. One of our founders also keeps an encrypted copy of our backups, including the photos and files stored in Sightgrid, on the computer that founder works from in British Columbia, Canada.
The whole databaseEvery table, copied
Encrypted, AES-256-GCMBefore it’s written
Separate backup storePrivate, kept only for backups, with its own access key
DailyThe last 14 days
WeeklyThe last 8 weeks
No key, no backup
Nothing is ever written unencrypted. The key for the copy in the United States is kept apart from the backups.
- Row count, every table
- Checksum, every table
- Every link between records
Restores are checked, not assumed
Every table’s row count and checksum must match, and every link between records must hold, or nothing is restored.
Shared jobs come back whole
Our tests restore a job shared by two companies and check that each company’s people come back in their own company. The same drill can run on the newest nightly copy, in a scratch database.
In the copyEvery job record, sign-off, message and setting
Not in the US copyPhotos and model files. They stay in the private file store. The founder’s copy in Canada also holds them, encrypted.
What the copy holds
The database: every job record, sign-off, message and setting, and a list of every file the database points to. The copy in Canada also holds the files.
On your device
The model opens on your phone.
The building is read, drawn and scanned on each device. Here is exactly what stays there and what goes to the job.
On the phone
Sent to the job’s private storage
- Opens and draws the model
- Scans it for clashes
- Saves photos first
The model fileUploaded once per version, so everyone opens the same building
What the scan foundEach clash, where it is and the distance
Photos, sign-offs and chatSent when there’s signal
Stays on the phoneA copy of the model, so a job it has opened opens again with no signal
Our servers, on a model file
ISO-10303-21;The first bytes of every IFC file
Checked: it’s an IFC fileOur servers never open the building inside it.
Your data
Your data, your call.
We never sell it. Sightgrid learns from job data only with your company’s yes, and some things are never used at all.
Only with a yes
Sightgrid learns from job data only if your company says yes.
Today it learns nothing from it. The switch, Help improve Sightgrid, isn’t in the app yet. When it is, it starts off and your office controls it.
Company settings
Help improve SightgridOff, and not in the app yet
Even with a yes, never used
- Names, emails and phone numbers
- Chat messages
- Photos of people
- Price files and quotes
- Your model and drawing files
- Anything that identifies your GC or your project
Never
No outside AI company trains on it.
Our AI provider, Anthropic, and our speech-to-text provider, OpenAI, don’t train on what we send them, under their commercial terms.
What the AI gets
- Ask in words: the words you type or say, and the lines you paste
- A spreadsheet’s column headings, with a few sample rows
- Restoration: a meter photo you choose to have read, with its location data removed
- Restoration: a voice note, to turn it into text
Never sent to it
- Models
- Drawings
- Chat
Never
We don’t track where your crew is.
The app can’t ask a phone for its location.
Location, in our app’s permissionsgeolocation=()
Never
Our error reports don’t record your screen.
They’re also set not to collect personal details.
Screen recordingOff
Personal detailsOff by default
Leaving
Take your records with you.
Your office can export a job as a zip file at any time. It can be downloaded for a day, through links that last five minutes. A big job comes in parts, one finished part at a time.
Also
CSVReports
BCFClashes
project.jsonThe jobmembers.jsonEveryone who has been on it, with role, join and removal datesitems.jsonEvery item, with its sign-off stateevents.jsonThe full history, in order, unchangeablemodel-versions.jsonEvery model version: names, sizes, who published itactivity.jsonJoins, invites, role changes, removals, sign-outschat.jsonEvery chat room and messagedocuments.jsonThe job documents and drawing setsfiles.jsonEvery file in the export, and where it isphotos/Every photo, one folder per itemmodels/The building model’s files, every versionchat/The chat’s photos and voice notesdocuments/The job documentsdrawings/The drawing setsdrying/Restoration jobs: the drying record
Found something?
Tell us first.
If you think you’ve found a security problem in Sightgrid, email hello@getsightgrid.com with what you saw and how to see it again. Please don’t open or change other customers’ data while you look.
- We don’t hold a SOC 2 or ISO 27001 report today. This page says what the software does instead.
- No system is perfectly secure. If something goes wrong, we tell the companies it affects.
- Written for the Sightgrid app as of October 28, 2026.

