Subprocessor disclosure and DPA status.

Current DPA status

TorqueLedger does not currently offer a separate enterprise data processing agreement for self-serve or Founding 50 evaluation access. Shops should use the service for ordinary workflow records and avoid submitting unnecessary regulated, customer-sensitive, or confidential data that is not needed for repair order, approval, invoice, payment, support, or onboarding work.

If a production customer requires a signed DPA, custom retention terms, regional hosting review, or a detailed subprocessor list, that request should be reviewed before expanded production use.

Service provider categories

TorqueLedger may rely on hosting, monitoring, analytics, email, SMS, payments, backup, calendar, accounting, and parts-catalog infrastructure to run the product. These subprocessors are used for application delivery, reliability, secure sessions, customer notifications, payment workflows, support, abuse prevention, and operational reporting.

Data minimization

Shops should collect only the information needed to complete the service workflow: customer contact details, vehicle details, repair order notes, inspection findings, approval decisions, invoice lines, payment status, and follow-up records. Passwords, raw card numbers, private employee issues, and unrelated customer documents should not be submitted.

Contact

Questions about privacy, data processing, sub-processors, deletion review, export, correction, or support can be sent through the TorqueLedger contact page.

Workflow note

How this page fits the shop workflow.

TorqueLedger pages are organized around practical service-counter work: finding the customer, opening the vehicle record, documenting the inspection, explaining the estimate, recording the approval decision, creating the invoice, collecting payment, and queuing the follow-up. That structure helps a small repair shop keep daily work moving without losing owner visibility.

Use this page as one part of the operating map. The related feature, approval, invoice, payment, onboarding, and reporting pages show how each action connects back to the same customer and repair order record.