PullScan may collect account information, email address, authentication information, vehicle information, vehicle modifications, tune information, fuel information, uploaded CSV files, uploaded screenshots, parsed telemetry, derived telemetry, analysis results, analysis history, user feedback, follow-up information, technical logs, usage information, device and browser information where applicable, and information associated with Support PullScan transactions.

Support transaction information may include payment status, transaction identifier, support amount, currency, timestamp, and information needed to associate or record the support transaction. PullScan does not store complete payment-card numbers.

PullScan uses information to provide analysis, generate telemetry views, maintain saved history, associate logs with vehicles, compare analyses, support sharing, process user feedback, improve reliability, prevent abuse, support account features, and operate the service.

Where legally permitted, PullScan may use de-identified or aggregated information to improve analytical systems, detectors, recommendations, platform quality, and service reliability.

CSV logs, screenshots, vehicle details, tune configuration, fuel information, modifications, notes, and follow-up logs may be stored and processed so PullScan can produce and maintain analysis results.

Analysis quality depends on the information available. Incomplete files, missing channels, inaccurate sensor data, or incomplete vehicle context can affect the analysis.

When a tuner accepts your request, PullScan stores the resulting customer relationship, tuning job, vehicle and analysis associations, messaging choice, job status, conversation sessions, and reopen decisions.

If messaging is enabled, PullScan collects message content and metadata such as participants, timestamps, referenced analyses, delivery-related identifiers, reports, notification preferences, and conversation open or closed status. Messages are shared with the customer and authorized members of the applicable tuner workspace.

PullScan personnel or service providers may access message information only as reasonably necessary for service delivery, support, security, abuse prevention and investigation, dispute handling, legal compliance, or enforcement of platform rules. Message text is not included in ordinary email or push notification content.

Message history may be retained while the relationship or account remains active and afterward for a period reasonably necessary for service continuity, security, abuse prevention, disputes, and legal obligations. Deletion and access requests remain subject to legal-hold, security, fraud, and dispute exceptions.

PullScan may use third-party providers for cloud infrastructure, file storage, database hosting, authentication, analytics, error monitoring, data processing, and payment processing for Support PullScan.

When Stripe or another payment processor handles a Support PullScan payment, payment-card details are processed directly by that provider. PullScan may receive transaction-related information needed to record payment status and support history.

PullScan stores information for as long as reasonably needed to provide the service, maintain analysis history, support security and abuse prevention, comply with legal obligations, resolve disputes, and operate the platform.

You may contact PullScan to request access, correction, or deletion of information. PullScan will respond as required by applicable law and may retain information where needed for legal, security, operational, or legitimate business purposes.

PullScan uses reasonable technical and organizational measures intended to protect information. No internet service, storage system, or transmission method can be guaranteed to be completely secure.

Depending on where you live, you may have rights to request access, correction, deletion, portability, or restriction of certain personal information. You can contact PullScan using the contact information below.

You can choose not to provide certain vehicle or telemetry information, but some PullScan features may be limited or less accurate without it.

PullScan user terms do not automatically grant rights to third-party forum content, external CSV files, or third-party comments. Any internal engineering case library based on external sources should preserve provenance and be handled separately from user-submitted PullScan data.

For privacy questions, contact PullScan at support@pullscan.com. PullScan may update this Privacy Policy as the product changes. Material changes may require acknowledgment of an updated version.