Privacy & data handling

This project exists to share technical service knowledge, not personal information. Design goal: original invoices are never stored.

What we process

• Your PDF upload(s) are held in server memory long enough to merge (if multiple), extract text, redact PII, and analyze — then discarded.
• Automated redaction removes emails, phones, VINs, street addresses, ZIPs, plate numbers, invoice/RO IDs, and long numeric identifiers.
• You review draft issues before publish — only what you confirm goes to the public board.

What we store

• Vehicle model and model year (not full VIN)
• Mileage as a range bucket (e.g. 25–50k)
• Symptoms, diagnosis, resolution, parts, labor notes
• Optional broad region only (e.g. US-West)
• Category tags, fix status, and confidence score
• Anonymous hashes used only for duplicate detection

What we do not store

• Original PDF files
• Customer name, phone, email, address
• Full VIN or license plate
• Payment / credit card data
• Exact service center street address

AI provider

Extraction uses the xAI API (Grok) with a server-side API key. Redacted technical text is sent to xAI for analysis. Do not upload documents you are not comfortable processing with that provider.

Early beta limits

To control cost and abuse: limited analyses per IP per day and a low global daily cap. Re-uploading the same PDF does not call Grok again.

Disclaimer

Not affiliated with Tesla, Inc. Community-shared notes may be incomplete or incorrect. Always follow official service procedures and applicable law when handling customer data. Only upload invoices you have the right to share.