How eServiceHunter uses marketplace data.

Information eServiceHunter handles

Depending on how you use the service, eServiceHunter may process account details, provider business information, saved vehicle details, service-request descriptions, service locations, offers and quote versions, messages, appointments, approved change orders, completion feedback, security logs and technical session data.

Why the information is used

eServiceHunter uses this information to authenticate accounts, match service requests with relevant providers, operate quoting and scheduling workflows, preserve transaction history, send requested or material notifications, prevent abuse, troubleshoot the service and calculate explainable marketplace outcome metrics.

Marketplace sharing

Information is shared according to the marketplace workflow. Matching providers can receive the service information needed to evaluate and quote a request. Private customer contact details are not intended to be exposed to every bidder. Contact exchange is reserved for the selected provider when the transaction reaches the appropriate post-acceptance stage.

Location data

Repair matching may use city, region, postal area and derived coordinates. Street-level customer addresses are not sent to the configured geocoding provider unless that feature is deliberately enabled. Towing requests may require more precise pickup information because location is part of the requested service.

AI-assisted features

When an AI-assisted feature is enabled and invoked, eServiceHunter sends only the information needed for that feature to the configured AI service. Repair-request assistance is designed around vehicle and problem details rather than account identity. Offer comparison is designed around the structured request, quote scope and recorded provider outcome metrics. AI output is advisory and is constrained by eServiceHunter's marketplace rules.

Garage directory information

eServiceHunter may maintain public business-directory information about automotive service providers from provider claims, historical marketplace records and configured external business-data sources. Historical lead data is treated as stale evidence and is not automatically published as a current verified business record.

Payments

When provider billing is enabled, eServiceHunter may store payment-provider customer or subscription references and billing status. Card or bank credentials should be handled by the selected payment provider rather than stored directly in the eServiceHunter application database.

Retention and security

Marketplace and audit records may be retained when needed to operate the service, preserve accepted commercial history, investigate abuse or disputes, and meet applicable operational or legal obligations. eServiceHunter uses server-side authorization, hashed passwords, encrypted sessions where configured, audit events and restricted production secrets as part of its security design.

Your choices

You can update supported account and provider-profile information from the application. Additional access, correction or deletion requests may be subject to records that must remain available for security, transaction history or legal reasons. Material changes to this notice may be published as a new version and may require renewed acceptance.