Security
Your customers, your stock, your money.
Treated that way.
This page lists what we do to protect your data today, what we don’t do yet, and how to reach us if something looks wrong.
Principles
How we think about it.
Least access, always
Tinsmith connects to Spire with its own dedicated user, not an admin account, and people in Tinsmith only see the screens their role needs.
Your data stays yours
We don’t sell it, share it, combine it with other customers’ data or use it to train AI models. Spire remains your system of record, and you can ask us to delete what Tinsmith holds.
You hear it from us first
If an incident affects you, we tell you directly with what happened, what it touched and what we’re changing.
Controls
What’s in place today.
| Control | What it means |
|---|---|
| Dedicated instance | Each company gets its own server, database, sign-in user pool and file storage. No other customer’s data is on it. |
| Encryption in transit | TLS 1.3 on every public endpoint. The database only accepts encrypted connections, and file storage refuses unencrypted requests. |
| Encryption at rest | The database, its backups and all job photos and documents are encrypted at rest. |
| Connection to Spire | Spire Cloud over an encrypted connection. On-premises Spire through a private encrypted tunnel from a separate machine in your office. Nothing is installed on the Spire server and nothing on your network is opened to the internet. |
| Sign-in and roles | Accounts are created by your administrator only; there is no public sign-up. Four roles (admin, dispatcher, office, field tech) control what each person can see and do. Sessions use signed, short-lived tokens. |
| Files and photos | Stored privately and versioned. They are shown through links that expire after 15 minutes, so a copied link stops working. |
| Secrets | Spire credentials and keys are kept in a managed secrets vault, never in code. |
| Backups and recovery | Daily database backups kept for 30 days. An automated drill restores a backup every week to prove it actually works. |
| Monitoring | The app is checked from outside every five minutes, and errors alert the Gemini Logic team. |
| Activity log | Assignments, completions, transfers, counts and other changes are logged with who did them and when. |
| Safe retries | Every write to Spire carries a one-time key, so a retry on a bad connection can never create a duplicate order, transfer or adjustment. |
Hosting and subprocessors
Where Tinsmith runs, and who touches it.
Canadian customers are hosted in Amazon Web Services’ Canada (Central) region. These are the only outside services involved in running Tinsmith.
| Service | What it does | When |
|---|---|---|
| Amazon Web Services | Servers, database, file storage, sign-in and account emails | Always |
| Sentry | Error reports so we can fix problems quickly; we limit what personal data is sent | Always |
| Tailscale | The private encrypted tunnel to an on-premises Spire server | On-premises Spire only |
Where we are
Honest about what’s not done yet.
Security-first build
Dedicated instances, encryption, backups with restore tests, least-access Spire user and an activity log, from day one.
Multi-factor sign-in and single sign-on
Not switched on today. Tell us if you need it before rollout and we’ll prioritise it for your instance.
Third-party audit
Tinsmith has not been through a SOC 2 or ISO 27001 audit. We’re happy to fill in your security questionnaire.
Found something?
Tell us. We’ll take it seriously.
If you think you’ve found a security problem in Tinsmith, email us with what you saw and how to reproduce it. We acknowledge reports within one business day. For security questionnaires or a call with the engineering team, use the same address.
See it working on your own Spire data.
Book a 30-minute walkthrough with the team that built it. We’ll show you a real dispatch board and a real tech’s day, with no slides and no pressure.