Request data
Vehicle and part details, fitment reference, budget, location, deadline, market, language, and supplier business contacts are used to create the reviewed call plan.
Menu
Privacy
Collect what the sourcing decision needs—and no more.
This notice describes the current hackathon pilot, not a generally available commercial service.
Call records
Approval timestamps, provider call identifiers, status, summaries, confidence, evidence, and structured supplier quotes are retained for audit and comparison.
Authorization and consent record
Live plans require an authenticated operator and exact server allowlist match, then store the consent attestation and authorized calling window. SpareScout does not infer consent from possessing or submitting a number.
Protected display
Full supplier numbers are needed by the trusted server to place an approved call. User-facing plans and history mask them, and signed browser approval data removes them entirely.
History access
Each request receives a separate random history credential remembered by the originating browser. The server stores only its cryptographic hash and refuses history reads without the credential.
What is excluded
SpareScout does not ask for payment cards, banking credentials, or authority to purchase. Do not enter unrelated personal or sensitive information.
Thirty-day retention
Sourcing requests and their related supplier, approval, call, quote, and webhook records are pruned after 30 days when the service next handles database activity.
Your deletion control
The browser-held history credential can permanently delete its matching durable request at any time. Forgetting a request on one device removes only that device’s credential.
Fixture mode
The public demo path uses synthetic contacts and generated outcomes. It does not send the request data to a phone recipient.
Last updated 31 August 2026. Live testing must use authorized contacts and follow applicable calling, recording, and privacy rules.