Security
How CNC Setup Sheets protects your shop's setups, drawings and photos. Last updated November 10, 2026.
Setup sheets hold drawing numbers, part numbers, photos of parts in the machine and the know-how your machinists worked out. Many shops are also bound by ITAR, CUI or customer rules about where that information can go. The app is built so that information stays inside your shop. Each feature below says what it does, how it works and why it matters.
For IT and compliance reviewers
- On-premises only: one Windows server program on a shop PC. No cloud service and no vendor copy of any data.
- No outbound connections from the server: no telemetry, and license keys are checked offline.
- One inbound port (TCP 5050), limited by a Windows Firewall rule to the local subnet and, optionally, the shop's own Tailscale network.
- Access away from the shop is off for every person by default; an administrator must switch it on person by person.
- Unique sign-in for each person, PINs stored as salted scrypt hashes, lockout after 5 wrong tries, 60-minute idle timeout.
- Role-based access and a server-side activity log of sign-ins, views, changes and screenshot attempts.
- Known gaps are listed openly: HTTPS on the shop network and a code-signed installer are planned.
Where your information lives
Your shop's own server
How it works: Every setup, photo and name is stored on a computer your shop runs on its own network. There is no cloud service, and we have no copy.
Why it matters: Controlled drawings and part photos never leave the building, so the shop decides who sees them and can show an auditor exactly where they are.
Shop Wi-Fi only
How it works: The server answers only phones on the shop network and refuses connections from any other network. Off site, the app can't reach anything unless the shop chooses to set up Tailscale (next card).
Why it matters: A lost phone, or a phone at home, can't open a single setup.
Away from the shop: Tailscale, only if you choose
How it works: Tailscale is a separate app that builds a private, encrypted link between devices signed in to the same Tailscale account. If the shop installs it on the server PC and on a phone, that phone can reach the server over cellular. Nothing is opened to the internet: any device outside the shop's Tailscale account is still refused. Even then, an administrator must switch on "Allow away from the shop" for each person who may use it. It is off for everyone until then.
Why it matters: A lead can check a setup from the road, and the shop decides exactly which devices can do that. Removing a device from the Tailscale account cuts it off at once. With Tailscale switched off, or off the shop Wi-Fi, the app can't open any setup until the phone reconnects.
No accounts with us, no tracking
How it works: There is no sign-up with us. The app has no analytics, no ads and no third-party tracking.
Why it matters: Nothing about your work or your people is sent to us or anyone else.
Who can get in
A personal PIN for each person
How it works: Everyone logs in with their own user name and a 4 to 8 digit PIN. The server keeps only a scrambled (hashed) form of each PIN, never the PIN itself.
Why it matters: Every view and change is tied to a real person, and a stolen copy of the server file doesn't give away anyone's PIN.
Lockout after wrong PINs
How it works: After 5 wrong tries, that user name is locked for 15 minutes.
Why it matters: Nobody can guess a PIN by trying number after number.
Automatic log out
How it works: After 60 minutes without use, the server ends the session and the phone goes back to the log-in screen. Logging out also clears anything still waiting on the phone.
Why it matters: A phone left on a bench doesn't stay open to whoever picks it up.
Roles
How it works: Machinists record and update setups. Leads also approve them. Administrators manage people, machines and job numbers and can see the activity log. Administrators can also limit who may add or rename machines.
Why it matters: Each person can do what their job needs and no more, and an approved setup shows who checked it.
Photos
Taken only with the app's own camera
How it works: Photos are taken inside the app. The app never asks for your photo library, so it can't save to the camera roll or pick photos from it.
Why it matters: Part photos don't end up in a personal camera roll, a cloud photo backup or a text message.
Nothing kept on the phone
How it works: A photo goes straight to the shop server. If the Wi-Fi drops, it waits in the app's private storage, where it can't be viewed, and it uploads when the phone reconnects. Anything not uploaded within 12 hours is deleted. Photos are shown from the server each time and aren't saved for later.
Why it matters: A phone that leaves the shop carries no setups or photos with it.
Name and time on every photo
How it works: Each photo is stamped with the viewer's name and the date and time as it is shown.
Why it matters: If a picture of the screen ever turns up somewhere, it shows who was looking at it and when. That alone discourages it.
Screens
Screenshots and screen recording blocked
How it works: The app blocks screenshots and screen recording, and blurs itself in the iPhone app switcher. If someone takes a screenshot anyway, it is recorded in the activity log with their name, the time and the setup on screen.
Why it matters: Setups can't be copied out of the app with a couple of button presses, and any attempt is visible to the shop.
Records you can trust
Every change signed and dated
How it works: The app records who first recorded each setup, who saved each version, who approved it, who last changed each turret station, who took each photo and who linked each job number, with the date and time. Nobody types this in.
Why it matters: Anyone with a question knows exactly who to ask, and nothing changes without a name on it.
Version history
How it works: Updating a setup makes a new version. Saved versions are never edited or erased. Original photos are kept next to the brightened copies.
Why it matters: A mistake or a bad change can always be traced and undone, and the setup that ran last time is always there.
Activity log
How it works: The server logs log-ins, setups opened, created, updated, saved and approved, screenshot attempts, and changes to people, machines, job numbers and settings. Administrators can read it in the app.
Why it matters: The shop can answer "who looked at this, and when?" for any setup.
Security limits
No app can stop someone from photographing the screen with a second phone. The name stamp on every photo and a written shop policy cover that gap.
Encrypted connections (HTTPS) between the phone and the shop server are being added before general release. Until then, on the shop Wi-Fi the connection is protected by staying on the shop's own network. Over Tailscale the connection is already encrypted.
The demo mode uses made-up data kept in the app's own private folder on the phone, and it is erased when you leave the demo. Until then, an iPhone backup can include that folder.
Technical details
For IT and compliance staff reviewing the app. Applies to server version 0.7.3 and the current iPhone app.
Architecture
| Deployment | On-premises. One Windows program (Python, Flask, served by Waitress) on a PC the shop owns. The iPhone app is the client. |
|---|---|
| Service account | Starts at boot as a scheduled task under NT AUTHORITY\LOCAL SERVICE, a low-privilege built-in account. |
| Data store | SQLite database (WAL mode) and photo files in one data folder on the server PC's local disk, not on a network share. |
| Vendor access | None. There is no cloud service, remote support channel or vendor copy of data. |
Network
| Inbound | TCP 5050 (can be changed). Also mDNS / Bonjour (UDP 5353) on the local network so phones find the server by name. |
|---|---|
| Firewall | Windows Defender Firewall inbound rule, scoped to the server program. Remote addresses: LocalSubnet, 100.64.0.0/10 and fd7a:115c:a1e0::/48 (Tailscale). |
| Second check in the server | Any request from outside loopback, the private ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and the Tailscale ranges is refused with HTTP 403, even if the firewall rule is changed. |
| Outbound | None from the server. No telemetry, no analytics, no license server. License keys are Ed25519-signed and checked offline against a public key built into the server. |
| Transport | Shop network: HTTP, not yet encrypted (HTTPS planned before general release). Tailscale: WireGuard, encrypted end to end between the phone and the server PC. |
| Tailscale (optional) | Installed and owned by the shop. Only devices signed in to the shop's Tailscale account receive addresses in those ranges. Access can be narrowed further with Tailscale access rules. See Tailscale security. |
| Away access per person | Requests from the Tailscale ranges are refused unless an administrator has switched on "Allow away from the shop" for that person (off by default). Switching it off stops a phone that is away at its next request. Changes and refused attempts are in the activity log. The switch only appears when the server PC is on Tailscale. |
Identity and access
| Sign-in | A user name and a 4 to 8 digit PIN for each person. No shared accounts. |
|---|---|
| PIN storage | Salted scrypt hash (N=32768, r=8, p=1). PINs are never stored or logged in plain form. |
| Brute force | 5 wrong PINs lock that account for 15 minutes. An administrator can unlock it. |
| Sessions | 256-bit random token, kept on the server only as a SHA-256 hash. Ends after 60 minutes idle. One active session per account. Changing a person's PIN or role, or deactivating them, ends their session at once. |
| Device binding | Each account is linked to one phone. Another phone is refused until an administrator moves the account. |
| Roles | Machinist, lead, administrator. Checked by the server on every request, not only in the app. |
| Directory sign-in | Not supported (no Active Directory or SSO). The shop's administrator manages accounts in the app. |
Data on the phone
| Camera and photos | In-app camera only. The app never requests photo library access. |
|---|---|
| Offline queue | A photo that can't upload waits in the app's private storage and is deleted if not uploaded within 12 hours. Nothing else is kept on the phone. |
| Screen capture | Screenshots and screen recording blocked, screenshot attempts logged on the server, app blurred in the app switcher. |
| App updates | From the App Store, and small fixes from Expo's update service (expo.dev). Updates are signed by DelSpec Labs, LLC, and the app refuses any update without a valid signature. Updates download app code only; no shop data is sent. |
Records, backup and integrity
| Activity log | Server-side log of sign-ins, setups opened, created, updated, saved and approved, screenshot attempts, and changes to people, machines, job numbers and settings. Readable by administrators. |
|---|---|
| Version history | Saved versions are never edited or erased. Original photos are kept next to the brightened copies. |
| Backup | Optional nightly task copies the database (SQLite online backup, last 14 kept) and new photos to a folder or network share the shop picks. |
| Encryption at rest | Not done by the app. Turn on BitLocker on the server PC and the backup drive. |
Known gaps and plans
| HTTPS on the shop network | Planned before general release. Until then, traffic on shop Wi-Fi is not encrypted; use a WPA2 or WPA3 network that only shop devices join. |
|---|---|
| Installer signing | The Windows installer is not code-signed yet, so Windows shows "unknown publisher". Code signing is planned. |
| Certification | The app is not certified under ITAR, CMMC or NIST SP 800-171. It is built to keep controlled information on site, and its unique sign-ins, lockout, timeout, roles and activity log support those programs. The shop's own policies and systems remain responsible for compliance. |
Questions
Security questions about the app: email us. Questions about your shop's server or people go to your shop's administrator.