Privacy notice

Who is responsible?

Spool Studio is operated by Robin Edwards, the controller of the personal information handled for this service. ProductKit Digital is the public contact brand.

Contact: hello@productkit.digital · Website: productkit.digital.

Information we handle

Setup checklist

We store your optional setup steps and welcome-reminder preference with your account so they follow you across devices. Stock completion is derived from your library. Other completion marks are your own confirmations, not verified hardware status. These preferences are included in your saved-data export and removed when you erase saved application data.

Release-note indicator

This browser remembers the latest release notes you have viewed so the What’s New icon can highlight unread updates. This preference stays in local browser storage, is not linked to your account and does not sync across devices. Clearing site data removes it.

Community roll total

We calculate a combined count of available filament rolls across Spool Studio accounts and show it to signed-in users in App & device. The database returns only the aggregate count, not individual libraries, account identifiers, names or prices. Used-up rolls and unknown quantities are excluded. The feature does not retain a history of counts or send the statistic to an external analytics service.

Physical spools, QR labels and Spoolman

If you assign permanent IDs, we save a unique identifier and number for each counted reel, together with its used status, optional location, remaining-weight estimate and linked Spoolman ID. A spool QR link includes the random reel identifier, not your name or inventory. Opening its private record requires signing into the account that owns it.

The optional Spoolman transfer downloads a private file of available physical reels and filament specifications to your device. A local script imports reviewed data into your own Spoolman and produces a mapping file. The app saves only the mappings you explicitly confirm; no mailbox/order details or bridge credentials are included in the transfer. Keep these local files private and remove them when no longer needed.

The optional local bridge reads your configured Spoolman server and sends its spool IDs and remaining weights over HTTPS to this app. Only IDs you have linked are applied; unlinked snapshot records are not retained in the inventory. The server stores a hash of your revocable bridge credential. The private configuration downloaded to your computer contains the credential itself: anyone with it could submit weight updates to linked reels until it is replaced or revoked. It cannot read your library or control your printer.

Desktop printer bridge

The optional desktop companion stores your imported printer configuration, including its printer credential and local server addresses, encrypted using your operating system’s secure storage. It refuses to save credentials when secure encryption is unavailable. This copy remains until you choose Remove configuration; the original downloaded JSON is a separate unencrypted file you must keep private and remove yourself. Uninstalling the app may leave its stored configuration behind.

The printer bridge makes local requests to your configured printer and, where enabled, Spoolman. It sends capability/status summaries and the latest reviewed command result to Spool Studio over HTTPS. The server stores the printer credential as a hash, and keeps the latest status and request/result rather than a history. Revoke the printer key on the website to prevent future requests; this cannot recall an in-flight printer command. If you enable Windows startup, the app registers its executable path and a startup flag in your Windows user account, not your bridge key. It then uses its existing encrypted configuration to check and reconnect after sign-in. Disabling the option removes this startup registration. This preference stays on the computer and is not synced to your Spool Studio account. The desktop app has no telemetry or automatic update checks. Downloads are hosted on GitHub, which receives normal download connection information. This printer key is separate from the weight-sync key described above.

Optional external barcode lookup

“Find filament” sends the entered barcode to our server. The server first checks a bundled, dated snapshot of the Open Filament Database; this does not contact that project during your lookup. If the snapshot has no matching GTIN, the server queries UPCitemdb and, when configured, Firecrawl using the exact code plus the word “filament”. We do not send your email, account identifier or inventory to either provider. The providers receive the barcode query and our server’s normal connection information. Firecrawl may search and read the main content of matching public result pages even when UPCitemdb also returns an item; the server reduces that content to review fields and does not send the raw pages to your browser. Returned product details and source links are review drafts, not automatic stock additions. See UPCitemdb’s privacy policy and Firecrawl’s privacy information. Camera frames are decoded on your device. Choosing the separate web-search fallback opens Google with the entered barcode and the word filament; it does not send your inventory or account details in the query. To protect the shared lookup allowance, we store up to 100 request timestamps without barcodes, account identifiers or inventory. Old timestamps are discarded on the next successful reservation once outside the 24-hour window.

Gmail connection — staged, not generally enabled

A separate read-only Gmail importer is being tested, subject to Google setup and verification. Google sign-in alone does not grant mailbox access. Where enabled, the user must choose Connect Gmail and approve Google’s read-only mailbox permission. The permission covers the mailbox; the tool searches only on request, displays up to 20 subjects and reads the bodies of up to 10 selected messages when asked.

Gmail access tokens and message results stay in this page’s memory. The browser requests selected messages directly from Google; the app server receives neither tokens nor original messages. Attachments are not imported. HTML-only emails are converted to text on this device without rendering their content or loading remote images. Only spool fields you review and approve, and the import fingerprint, are saved. Disconnect revokes the token when Google accepts the request; copied import text remains until cleared or the page closes. You can also revoke access in your Google Account. There is no background mailbox sync or stored refresh token.

Product links and barcodes

Optional product lookup sends a normalised product URL to our server, which requests the public page from an approved retailer. When configured, a blocked or sparse page can also be sent to Firecrawl for main-page text extraction. Your sign-in cookies, email and library are not sent to the retailer or Firecrawl; each receives the server’s public-page request and normal connection information. Raw page content is not returned to your browser. Lookup results stay in page memory until you save a reviewed entry. Barcode camera frames are decoded on your device and are not uploaded. Local barcode matching searches your own saved library and a small bundled catalogue; the separate external search requires its own button. The barcode and source URL are stored with the entry only when you confirm saving it.

Sign-in and your library

Clerk handles account registration and sign-in. Spool Studio uses your Clerk account identifier to protect your records. Netlify hosts the app and its private Postgres inventory database. Spool Studio does not connect to your mailbox or receive your sign-in password.

The database stores the spool details you save, including brand, material, finish, colour, quantity, packaging, weight, dates, notes and used-up status, plus update timestamps, revision numbers and request identifiers needed to synchronise changes safely. Avoid putting addresses, payment details or other unnecessary personal information in notes.

Order text and images

Pasted text and selected JPG, PNG or WebP images are processed in your browser. English text recognition uses assets served by this site; source text and image files are not uploaded to the application server or sent to an external OCR or AI service. Review drafts are held in page memory rather than saved by the app.

When you confirm an import, the app sends only the selected, reviewed spool fields and a SHA-256 fingerprint of the normalised source to your account. The fingerprint helps prevent duplicate imports; it is not the original text, but remains associated with your account. Optional Gmail access is described separately below; other inbox connections are not implemented.

CSV files use the same on-device review flow: only approved fields and a source fingerprint are saved. The optional email-export guide gives you a prompt to use separately in ChatGPT. If you connect an email app there or paste emails into that chat, ChatGPT and the connected service process that information under their own settings and policies. That separate step is not covered by Spool Studio’s on-device processing description.

3MF projects, phone batches and tags

3MF file contents, geometry and embedded previews remain on the device where you open them. If you sync a selection to your phone, the project name and selected filament labels, materials, finishes and colours are saved as your latest phone batch.

A QR snapshot or transfer link contains the selected batch in the link itself. Anyone you share that link with can read that selection; it does not grant access to your full library. NFC tags contain the material, colour and any optional temperature values you choose, not your account identifier or email. Anyone with a compatible reader and physical access can read the tag.

Support enquiries and technical requests

If you email us, we receive your email address, message and any attachments through Zoho Mail at hello@productkit.digital. Send only what is needed to investigate your question. Hosting and sign-in services also handle technical information such as IP addresses, browser information and request logs to deliver and protect the service.

Why information is used

Account information and saved records let the app provide your library, prevent one user accessing another user’s records, synchronise your devices and avoid duplicate saves. Support messages are used to answer your enquiry and resolve problems. The app does not run marketing email campaigns or sell your inventory.

Proposed lawful bases for operator approval: providing the service you request for account and library processing; legitimate interests in operating a secure, reliable service and answering enquiries for security and support; legal obligations where applicable to rights requests. These bases and any required legitimate-interest assessment must be reviewed before publication.

Colour matching and import recognition offer suggestions for you to review. They do not make decisions with legal or similarly significant effects.

Hosting and other services

Spool Studio runs on Netlify Functions and Netlify Database (Postgres), with Clerk for authentication. These services process information needed for hosting, sign-in and storage. The operator and authorised service administrators may need access for maintenance, support or security; account separation is not end-to-end encryption.

For those providers’ own privacy information, see Clerk’s privacy policy and Netlify’s privacy policy. These links do not replace the operator’s responsibilities for your Spool Studio records.

Before publication, confirm the hosting and email provider arrangements, any processing outside the UK, applicable transfer safeguards and how users can obtain details. This draft does not promise UK-only storage or unverified contractual safeguards.

Storage, retention and browser settings

• Saved library: records and import fingerprints remain until you use the saved-data erasure control or request removal. There is no automatic inventory expiry. The erasure control clears application records, not your sign-in account.
• Latest phone batch: remains until replaced, erased through the saved-data control or removed administratively.
• Local preferences: the app stores your theme choice and may store a QR snapshot selection in your browser’s local storage. “Clear this phone” removes the saved local selection; browser site-data settings can clear local preferences.
• Local files: the app does not persist import drafts or uploaded image files. Your original files, downloaded CSVs and any browser-managed session restoration are controlled on your device.
• NFC tags: retain their written data until rewritten or erased separately.

Marking a spool used, clearing this phone, uninstalling the PWA or signing out does not delete your server-side library or phone batch. Use App & device → Erase saved application data to remove the saved library and phone batch and revoke bridge access. This retains the account reference, revision counters, erasure request identifier/timestamp and next spool number so old requests cannot restore erased records and printed numbers are not reused. It does not erase your sign-in account, local snapshots/downloads, NFC tags, support correspondence or provider logs/backups. Contact us for complete account removal and wider erasure requests.

The app’s service worker does not cache private pages or API responses. Spool Studio adds no analytics scripts or advertising pixels. Hosting and login services may use their own cookies or similar technologies; see their privacy information for details.

The approved proposed policy for ordinary support correspondence is deletion 12 months after the issue is closed, with longer retention only for a documented legal or dispute need. This is not automated mailbox deletion; the operator must confirm its implementation and Zoho backup/deletion handling. Hosting logs and database backups require separate confirmed retention criteria before this notice is finalised.

Shopping and affiliate links

Some Amazon UK searches are labelled paid links. As an Amazon Associate I earn from qualifying purchases.

Clicking a shopping link sends the selected search terms and our affiliate tracking identifier to Amazon, together with the normal technical information from your browser. The link does not include your account identifier or full library. Amazon handles its own cookies, browsing and purchases under its privacy notice. Affiliate links do not change filament matching rankings.

Links to ProductKit Digital and other external sites take you to separate websites with their own privacy practices.

Your choices and rights

You can download your complete saved Spool Studio library, physical reel records, import fingerprints and latest phone batch from App & device → Your saved data as private JSON, without library filters. This is a data copy, not an automatic restore file; it excludes sign-in secrets, bridge credentials, local files, support correspondence and provider logs. Contact us for a wider access request. You can also edit your filament entries and export the current inventory view as CSV. Clear filters and include used-up entries if you want them in that export. Sign-in is necessary for a saved private library; imports, phone syncing and shopping links are optional.

Depending on applicable law and the circumstances, you can ask to access, correct or erase personal data, restrict its use or receive portable data. You can object to processing based on legitimate interests. Where processing relies on consent, you can withdraw that consent without affecting earlier lawful processing.

Email hello@productkit.digital with “Spool Studio privacy request”. We may need to verify that the account is yours before providing or deleting records. Do not send passwords or identity documents in your initial message.

You can raise a concern with the UK Information Commissioner’s Office or your local data protection authority. You do not have to contact us first.

Changes to this notice

This page will be updated when the app’s data handling changes, with the revision date shown at the top. New integrations will be described here before you use them.