Privacy notice
BenchPing helps workshops track work and keep customers informed. For questions about personal information, access, corrections, or deletion, contact support@benchping.com.
Information used to run the service
We store account names, email addresses, password hashes, workshop profiles, and the customer and job information a workshop supplies. This can include names, email addresses, phone numbers, items, estimates, schedules, notes, messages, and communication-consent settings. Delivery history includes message content, recipient information, delivery results and provider identifiers. Billing records include Stripe customer and subscription identifiers and the SMS credit ledger. Payment card details are handled by Stripe checkout.
How it is used
We use this information to authenticate accounts, show workshop and customer records, send requested updates, manage billing, provide support, and investigate problems. Customer replies are emailed to the workshop, and workshop replies are emailed to the customer. New-account details are sent to our support mailbox for account administration.
Tracking links and spreadsheet imports
Customers do not need to sign in to a tracking page. Anyone who possesses its unique link can view the customer-facing record and messages and respond to an estimate. Keep links confidential. Internal notes are not part of the customer-facing record.
For CSV or XLSX file import, the file is processed for preview and import rather than retained as an uploaded document; confirmed records are stored in your workshop. Public-link spreadsheet connections require a source accessible without signing in. Anyone holding that source link may be able to read its contents. Use file import if the source should not be publicly accessible.
Service providers
BenchPing uses Microsoft Azure for hosting and storage, Stripe for payments, Resend for transactional email, Twilio for SMS, Sentry for error diagnostics, and Google Analytics when you allow optional analytics. These services process relevant information to perform their functions and may process it outside your country. Provider records are also subject to their own retention practices and privacy notices.
Microsoft · Stripe · Resend · Twilio · Sentry · Google
Activity and diagnostics
Signed-in activity records help authorized administrators understand account use and troubleshoot errors. They include account and workshop identifiers, action names, outcomes and timestamps; administrators may see them alongside account names and emails. Routine activity cleanup targets records older than about 90 days. Error reports retain full exception details, which may include operational information or information present in an exception message. Diagnostic information is not guaranteed to be anonymous.
Browser storage and optional analytics
Essential browser storage keeps your session and preferences. The landing site and web application ask before enabling Google Analytics; declining does not prevent use. Their preferences are managed separately. We use analytics for page visits and selected feature actions, not to intentionally collect password fields, message contents or uploaded spreadsheet cells.
Retention and your choices
Workshop data is retained while needed to provide the service. Workshop owners can delete their account in settings after confirming their password and workshop name. This removes operational workshop records, but does not instantly erase backups, payment-provider records, previously delivered emails or data retained to meet applicable obligations. Contact support for access, correction, or retention questions. If you are a workshop customer, contact that workshop first about its records and communication choices; you can also contact us for assistance.
Workshop responsibilities
Only supply information you are authorized to use and keep customer contact details and consent settings accurate. Do not include unnecessary sensitive information in notes, spreadsheets or messages. Workshops are responsible for explaining their own use of customer information and obtaining permissions required for their communications.