Privacy
Privacy Policy
TorqueLedger helps repair shops manage customer, vehicle, inspection, invoice, payment, reminder, and account workflow data.
Last updated: May 24, 2026.
Who this covers
This policy covers TorqueLedger shop accounts, staff users, customer portal visitors, and people who submit a product inquiry or trial request. Customer data is intended to remain scoped to the shop tenant that created or imported it, subject to administrator access needed to operate, secure, and support the service.
Information we may collect
TorqueLedger may store shop account details, staff user details, customer names, contact information, household or business account details, vehicle details, VINs, service history, inspection findings, photos, document uploads, OCR extraction results, media links, estimates, invoices, e-signature approval records, payment status metadata, appointment details, reminder notes, email or SMS workflow content, consent or opt-out records when messaging is enabled, audit logs, backup records, and website inquiry submissions.
Why we use it
We use this information to run repair orders, prepare estimates and invoices, show customer portal views, capture customer approvals, support scheduling, prepare or send communications when enabled, reconcile payments, export accounting data, process uploaded documents with OCR, maintain backups, investigate security issues, support users, and improve the product.
Payment and integration data
TorqueLedger is not intended to store raw card numbers, CVV codes, payment terminal secrets, or full magnetic stripe or chip data. Card-on-file workflows should use tokenization supplied by the payment provider, with TorqueLedger storing only references such as customer IDs, payment method tokens, last-four metadata, expiry metadata, authorization status, transaction IDs, and payment status. Payment, accounting, booking, calendar, parts, email, SMS, OCR, hosting, and storage providers may receive the limited data needed for their function if those integrations are enabled by the shop.
Approvals and communications
Customer portal approvals, e-signatures, timestamps, IP or device metadata, and related audit records may be stored to document estimate, invoice, work authorization, or policy acceptance activity. Shops are responsible for collecting and honoring any required customer consent, opt-out, unsubscribe, and quiet-hours requirements for their jurisdiction and communication provider.
Sharing
We may share information with hosting providers, payment processors, accounting providers, booking or calendar providers, parts vendors, communication providers, OCR or document processing providers, support contractors, and professional advisors where needed to operate, secure, or support the service. We do not sell shop customer lists.
Storage, backups, and retention
Data may be stored on hosted infrastructure, in tenant-scoped application records, audit logs, and restricted backups. During a two-month trial or account lockout, shop access may be paused while data is preserved for a limited recovery, export, billing, dispute, security, or legal review window. Shops should avoid entering unnecessary sensitive notes or unrelated personal information.
Security
TorqueLedger uses HTTPS, secure shop sessions, role-based access, audit logs, tenant-scoped records, and server backups. No system is perfect, and this policy does not promise a particular security certification or compliance status.
Access, correction, and deletion
For requests about access, correction, export, or deletion, contact the shop that created the record or the TorqueLedger operator supporting that shop. Some records may need to be kept for invoices, taxes, safety, backup integrity, or dispute handling.
Updates
We may update this policy as TorqueLedger adds features, providers, support processes, or billing options. The date above will reflect the latest posted version.
