Privacy Policy
What SpoolSwift collects when you run a farm on it, why, who processes it for us and how long we keep it.
Last updated 20 October 2026
Who we are
SpoolSwift is print farm software. It is its own company in the SortSwift family, made by the team behind SortSwift, with its own terms and this privacy policy. This policy covers the SpoolSwift website, the app, the bridge you install at your farm, and the quote pages a farm offers its buyers.
What we collect and why
Your account and sign-in
You sign in with "Sign in with SortSwift". SortSwift holds your account, your password and your two-step sign-in settings, as a processor for SpoolSwift. SpoolSwift never stores your password or a two-step sign-in secret.
SpoolSwift keeps your farms, your memberships and your farm's data under your SortSwift account id. It also keeps its own sign-in session for you, with when you signed in, when you were last active, your IP address and your browser's user agent. We use these to keep you signed in, to let you see and end your sessions, and to keep your account safe. When someone invites you to a farm, we keep the email address the invitation was sent to.
Your farm
To run your farm, SpoolSwift keeps:
- The farm's name, time zone and currency, and its members and their roles.
- Your printers, with each one's name, serial number, model, firmware version, and its address on your network for display.
- Your jobs, files, plates, queue and print history.
- The answer to "Plate cleared?" after every print (Collected or Not collected), with the reason when there is one.
- The audit log. It records who did what and when, on which printer or job, from which IP address or bridge, and the result. It never holds secrets or full customer addresses.
We use this to queue and start your prints, to show live status to your team, and to give your Owners and Managers a record they can check and export.
What the bridge sends, and what stays at your farm
The bridge talks to your printers on your own network and sends the cloud printer status (turned into plain status first, never raw printer traffic), the start and end of each print, and its own version, operating system, uptime, printer count and connection errors. When you pair a bridge, we keep the computer's host name and IP address with the pairing.
These stay at your farm:
- Your printers' access codes. They are stored encrypted on the bridge computer. When you add a printer, your browser seals the code for the bridge, and the cloud passes on only the sealed copy and never holds a readable code.
- Camera frames from the failure check. They are checked on the bridge and stay at the farm, except the snapshot attached to an alert and frames an Owner chooses to share for training. Sharing is off by default.
- Secrets. Diagnostics bundles leave them out, and the bridge's health reports never carry secrets or file contents.
Shop and marketplace orders
When you connect a shop (Shopify, Square, WooCommerce and eBay), SpoolSwift reads its paid orders so they become jobs in your queue. It stores the order number (for example #1042), its payment status and when it was paid, and each line's SKU, variant and quantity. It does not store the buyer's address or phone number. Buyer details stay in your shop, one click away.
The token that connects your shop is stored encrypted, with a key for your farm alone. When Shopify asks SpoolSwift for a customer's data, or asks for it to be deleted, SpoolSwift answers.
Quote pages
A farm can offer a quote page. A buyer uploads a model, chooses material, colour and quantity, and pays through the farm's own Shopify checkout. Buyers have no SpoolSwift account. For each quote we keep the uploaded file, the quote, the buyer's email address once they give it, and a hash of their IP address rather than the address itself. The link to a quote is stored only as a hash.
Payments
Plans and the usage wallet are paid through Stripe, and you manage your card in Stripe's customer portal. Stripe holds the card. SpoolSwift never sees or stores card numbers. It keeps your Stripe customer and subscription ids so it can match payments to your farm.
Email and push notifications
SpoolSwift emails invitations, and emails your Owners when SpoolSwift staff open your farm. You choose which events notify you (a run finished or failed, a printer error, a bridge offline, a printer idle with jobs waiting, an order with an unmapped SKU) and how, by email or by web push to your phone. For web push we keep the push address and keys your browser gives us.
Who processes it
These services process data for SpoolSwift.
| Who | What for |
|---|---|
| SortSwift | Holds your account, your password and your two-step sign-in settings, and signs you in through "Sign in with SortSwift". |
| Stripe | Takes payment for plans and the usage wallet, and holds your card. |
| DigitalOcean | Hosts the SpoolSwift cloud, and stores model files, sliced plates, quote uploads, camera snapshots and their backups. |
| Database provider | Runs SpoolSwift's database, with daily backups. |
| Email provider | Sends invitations, notifications and other email from SpoolSwift. |
| Error monitoring and logs | Collects errors and logs from the SpoolSwift cloud, with secrets stripped out first. |
The shops and printers you connect are not our processors. They are your own accounts, and their own terms and privacy policies apply.
How long we keep it
| What | How long |
|---|---|
| Sign-in sessions | End after 12 hours without use, and after 30 days at most |
| A sign-in that is not finished | 10 minutes |
| Invitation links | Expire after 7 days |
| A record that your account was signed out everywhere | Kept for good, so a sign-in from before it cannot come back |
| Bridge pairing records | 24 hours after the pairing code expires, or 48 hours after it is used |
| Printer access codes sealed for the bridge | A few minutes in the cloud, and never readable there |
| Bridge events | 90 days |
| Events the bridge holds while the internet is down | Up to 7 days or 100 MB, on the bridge computer |
| Messages from Stripe and Shopify | The message body is kept encrypted for 14 days, then dropped |
| Archived models | Until you delete them |
| Files you delete | 30 days, then purged |
| Quote uploads that do not become orders | 30 days |
| Camera snapshots in the cloud | 24 hours |
| Frames from the camera check | 30 days with the run, then deleted unless labelled for training |
| The audit log, on paid plans | 2 years, then deleted with the farm |
| A shop connection token | Deleted when you uninstall SpoolSwift from your Shopify store |
| Data a Shopify redact request covers | Deleted or anonymised within 30 days |
| A farm an Owner closes | Viewable for 30 days with nothing starting, then closed |
The database has daily backups, and stored files are copied each night to a second region.
Cookies
This website (spoolswift.com) sets no cookies and loads no analytics or third-party scripts. Its fonts are served from this site.
The SpoolSwift app sets one cookie to keep you signed in, named __Host-fc_session. It holds a random value, is sent only over HTTPS, cannot be read by scripts on the page, and is not sent with requests that other sites start in the background. The app keeps only a SHA-256 hash of it. The session ends after 12 hours without use, and after 30 days at most. While you sign in, the app also uses a cookie that ties the sign-in to your browser, so it works only in the browser that started it.
Your rights and how to ask
To ask what data we hold about you, or to ask us to correct or delete it, write to [email protected]. Owners and Managers can export the farm's audit log as CSV at any time.
Security
How we protect your farm, from the bridge to the audit log, is on the Security page. To report a security issue, write to [email protected].