PARTS COUNTER / 11 NOVEMBER 2026

Privacy & your workshop records

Parts Counter is operated by Yolleg Ltd (company 10455920). Contact [email protected] for privacy, export or deletion requests. Production origin: https://inventoryprograms.com/. Workshop records are held on our private single-server PHP/SQLite installation. This service does not offer a contractual UK-only or EU-only data-residency guarantee.

What the service keeps

Account email, display name and password hash; organisation membership and roles; SKU, supplier and bin catalogue; stock movements, allocations, count corrections, drafts, imports and their hashes; private evidence files; server timestamps and named actors; accepted terms and provider billing identifiers. Use coded job/order references rather than unnecessary customer personal details. Do not store sensitive personal records or credentials in parts descriptions or files.

Records live in a private server SQLite database, not browser localStorage. Passwords are hashed. Private file bytes are encrypted at rest with AES-256-GCM and checked with SHA-256 when downloaded. Catalogue, references, account emails and ledger fields are not application-encrypted; access depends on server isolation, file permissions and production storage controls. This is not end-to-end encryption.

Access and providers

Signed-in administrators manage catalogue, access and billing. Storekeepers record operational changes; viewers read and export. Current membership is checked on every request, including file downloads. Administrators can generate a matching-email invitation link; the app does not send staff invitations. Shared links expire in seven days and can be used once.

Our hosting mail service handles account verification and password recovery email. Stripe handles subscription checkout and billing; the private Labs Billing Service checks app-scoped payment state. These providers may process data internationally under their applicable terms. Card details are entered at Stripe and are not stored by this app. No analytics SDK, advertising pixels or AI processing receives workshop records. The fictional local demo is isolated per session; mail is captured privately and no payment is taken.

Retention and recovery

Records remain readable/exportable after subscription expiry while the service is available. Staff editing and over-capacity organisation edits stop. Cancelling renewal does not erase records. Contact support for account/organisation deletion; deletion is an operator process and must respect another member’s authority and any required retained billing records. The app offers no destructive self-service history edit. Keep independent copies of required records.

Required session cookies use HttpOnly and SameSite=Lax; Secure is enabled on HTTPS. Sessions expire after 12 hours and password recovery revokes all existing sessions. No browser database or localStorage is used as the production record. Private encrypted snapshots run hourly (48-hour retention), with one daily snapshot retained for 30 days on the same server. A verified release snapshot is also held on the operator’s computer; automatic off-host replication is not configured. A server-wide incident can affect both live data and hourly snapshots. We aim to process verified deletion requests within 30 days; expired backup copies age out within 30 days. Keep your own exports for operational continuity.