Effective April 28, 2026 · Prosolutions Technology LLC · Chip.IT Mechanical

1. General accuracy

Chip.IT Mechanical pulls from a mix of:

• data you entered into your own garage,
• data other users entered into their garages and chose to share with you,
• open-source third-party datasets (e.g. the Wal33D/dtc-database OBD-II code dictionary used by the DTC explainer), and
• third-party APIs that we relay without modification.

We do not independently verify the accuracy of any of those sources. The data you see may be incomplete, out of date, or wrong. Always cross-check anything that matters with the vehicle's official owner's manual, the manufacturer's service portal, an authorised dealer, a certified mechanic, or the relevant government agency.

2. DTC (Diagnostic Trouble Code) explainer

• The DTC database is sourced from a public open-source dataset and is provided as a generic glossary.
• The same OBD-II code can mean very different things on different makes, models, model years, and trims. The text shown in-app may describe a generic interpretation only.
• A DTC is a symptom indicator, not a diagnosis. The same code can be triggered by multiple unrelated underlying faults.
• Do not perform repairs, replace parts, or operate the vehicle in an unsafe condition based solely on the in-app explanation. Have the code read and interpreted by a qualified technician using the manufacturer's service procedure.

3. Recall lookups

• Recall data, when shown, is relayed from third-party sources for your convenience.
• It may lag behind the official manufacturer or government registry, omit recalls outside the U.S. market, or display recalls that have already been remedied on your specific VIN.
• The authoritative recall record for any U.S. vehicle is the National Highway Traffic Safety Administration (NHTSA) at nhtsa.gov/recalls, plus the manufacturer's own VIN lookup tool. Always confirm there before assuming a vehicle is, or is not, subject to an active recall.

4. Maintenance reminders

• Reminders are based on the dates and mileages you entered, plus generic intervals you (or a template you selected) configured.
• We don't validate them against the manufacturer's published service schedule for your specific VIN, trim, or operating environment (towing, off-road, severe-duty, fleet, etc.).
• Email and push delivery is best-effort. Reminders can be delayed or lost by your mail provider, your push provider, your spam filter, your network, or a service outage.
• Do not rely on Chip.IT reminders as your sole signal for safety-critical maintenance (brakes, tires, timing components, recalls, etc.). Treat them as a helpful nudge, not a regulatory schedule.

5. Voice diagnostics

• The voice-diagnostics feature transcribes spoken descriptions of vehicle behaviour and surfaces possible related codes, components, or topics.
• It is a search-and-suggestion aid, not a diagnostic instrument. It does not measure anything. It does not connect to your vehicle's OBD port. It cannot detect intermittent faults, mechanical wear, electrical shorts, or corrupted sensor data.
• Suggestions are generated heuristically and may be irrelevant, misleading, or simply wrong.
• Do not operate, drive, tow, or repair a vehicle based solely on a voice-diagnostics suggestion. Have any suspected fault diagnosed by a qualified technician.

6. Stolen-vehicle reports

• The "stolen" flag inside Chip.IT Mechanical is set by the vehicle's account-holder, voluntarily. It is not connected to NCIC, NICB, your local police records, or any insurance database.
• The presence of the flag does not prove a vehicle is actually stolen. The absence of the flag does not prove a vehicle is not stolen — most stolen vehicles will never have been entered into Chip.IT in the first place.
• If you encounter a vehicle that you believe is stolen — whether or not Chip.IT shows a flag — contact your local police, not us. Do not attempt to recover the vehicle yourself.
• Filing a knowingly false stolen-vehicle report inside Chip.IT is a violation of the Terms of Service and is also likely a criminal offence under your local law.
• Prosolutions is not a law-enforcement agency, an insurance company, a recovery service, or a vehicle title registry. We cannot recover your vehicle, file an insurance claim on your behalf, or update DMV records for you.

7. NFC chips & chip transfers

• An NFC chip's record reflects the data the current and previous owners chose to enter — not an inspection, certification, or warranty of the vehicle.
• The chip's history is not a substitute for a pre-purchase inspection, a Carfax/AutoCheck report, a state title check, or a VIN-decoded recall lookup.
• An accepted transfer permanently re-parents the vehicle and its history to the new owner inside our system. It does not transfer legal ownership of the vehicle — title and registration are matters for your state DMV.

8. Photos & uploaded receipts

• Image-quality, OCR, and automatic categorisation features (where present) are best-effort and may misread receipts, invoices, or part numbers.
• You are solely responsible for verifying that the data we extracted from any uploaded image matches the underlying document before relying on it for tax, warranty, or legal purposes.

9. Third-party links & resources

The app may link to third-party websites (NHTSA, dataset repositories, NFC writer apps, etc.). We do not control those sites and we are not responsible for their content, accuracy, availability, privacy practices, or terms.

10. No professional relationship

Using Chip.IT Mechanical does not create a mechanic-client, attorney-client, insurance-broker, fiduciary, or any other professional relationship between you and Prosolutions Technology LLC.

11. Limit of liability for accuracy issues

Without limiting the general limitation of liability in the Terms of Service, Prosolutions is not liable for any harm, loss, injury, or damage caused by acting on, or failing to act on, information surfaced by Chip.IT Mechanical — including but not limited to repairs performed or skipped based on a DTC explanation, a missed or late maintenance reminder, a recall not surfaced or surfaced incorrectly, a voice-diagnostics suggestion, the presence or absence of a stolen-vehicle flag, or any data inherited as part of an NFC chip transfer. Verify with a qualified professional before you act.

12. Acknowledgement

By creating an account, paring an NFC chip, accepting a transfer, or continuing to use the service, you confirm that you have read this disclaimer and that you understand and accept the limits described above.

13. Contact

Prosolutions Technology LLC · Attn: Chip.IT Mechanical Legal · legal@mychipit.com