← Back to MTQ Now
🛡️ Security & Privacy
How we protect your data, your customers' data, and your business.
🔒 HTTPS Encrypted
🗑️ Zero PII Retention
🔐 SOC 2 Roadmap
📋 CCPA Compliant
🛡️ Patent Pending
Our Promise: We Don't Keep What We Don't Need.
MTQ Now is a tool, not a database. We process your input, generate your write-up, and delete your data. Your customers' names, addresses, VINs, and personal information never live on our servers. Period.
How Your Data Flows
Here's exactly what happens when you use MTQ Now:
| Step | What Happens | Data Retained? |
| 1. You input notes | Typed, spoken, or scanned — your input is captured on YOUR device | On your device only |
| 2. You hit Generate | Your notes are sent encrypted (HTTPS) to our AI processing engine | In transit only — not stored |
| 3. AI generates write-up | Our AI transforms your input into a professional document | Processing only — then purged |
| 4. You get the result | The write-up is returned to YOUR device | On your device only |
| 5. After generation | Your raw input, voice recordings, and scanned images are deleted from our systems | ❌ Nothing retained |
What We Keep
- 📊Anonymous usage counts — how many write-ups generated (no content, no PII)
- 📋Document type preferences — which types are most popular (for improving the product)
- 💬Suggestions you submit — only what you voluntarily tell us in the suggestion box
- 🐛Error logs — if something breaks, we log the error (never your content)
- 🔥Heatmap data — anonymous click/scroll patterns via Microsoft Clarity (no PII)
What We NEVER Do
- 🚫Sell your data. Not to advertisers. Not to data brokers. Not to anyone. Ever.
- 🚫Store customer PII. Customer names, phone numbers, addresses, VINs, and emails pass through our system and are immediately deleted after processing.
- 🚫Store voice recordings. Your recordings are transcribed on your device. The audio never reaches our servers.
- 🚫Store scanned documents. OCR processing happens in your browser. The images never leave your device.
- 🚫Train our AI on your identifiable data. We may use anonymized patterns to improve output quality, but never with customer names, VINs, or other identifiers.
- 🚫Share data with OEMs, dealer groups, or third parties without valid legal process (i.e., a court order).
- 🚫Keep data longer than necessary. If we don't need it to generate your write-up, we don't keep it.
For Shop Owners & Service Managers
Your Shop's Data Stays Your Shop's Data.
MTQ Now is designed so your technicians can create better documentation without your shop's sensitive information ever being stored on external servers. Here's what that means for you:
- ✅Customer records stay in your DMS — MTQ Now never stores them
- ✅No customer PII is retained after write-up generation
- ✅Voice recording and OCR processing happen on-device, not in the cloud
- ✅HTTPS encryption on all data in transit
- ✅No integration with your DMS means no access to your DMS data
- ✅Techs copy output to clipboard — nothing is pushed into your systems without your control
For OEMs & Dealer Groups
We Don't Touch Your Dealer Data.
MTQ Now operates independently from dealer management systems. We have zero access to:
- 🔒VIN databases or customer ownership records
- 🔒Warranty claim systems or manufacturer portals
- 🔒DMS inventory, billing, or financial data
- 🔒Employee records or performance metrics
MTQ Now simply helps technicians write better. The output is text that the technician copies into their existing workflow. No API connections. No data extraction. No backdoors.
Litigation & Data Discovery
What Happens If Someone Subpoenas Us?
Short answer: There's nothing to find.
Because we don't retain input data, voice recordings, scanned documents, or generated write-ups on our servers, a subpoena directed at MTQ Now would produce only:
- 📄Account information (email, subscription status) — if the user created an account
- 📊Anonymous usage logs (timestamps, document type counts — no content)
- ❌No customer names, no VINs, no repair details, no write-up content
This protects you, your customers, and your business. We designed it this way on purpose.
Technical Security Measures
| Measure | Status |
| HTTPS/TLS encryption (all traffic) | ✅ Active |
| Zero PII server-side retention | ✅ Active |
| Client-side voice processing (Web Speech API) | ✅ Active |
| Client-side OCR (Tesseract.js — runs in your browser) | ✅ Active |
| Content Security Policy headers | 🔜 In progress |
| API rate limiting | 🔜 In progress |
| SOC 2 Type I compliance | 📋 Roadmap |
| Penetration testing | 📋 Roadmap |
| Data Processing Agreement (enterprise) | 📋 Roadmap |
Need to show this to your IT team?
Download our security one-pager or request a technical review. We're happy to answer any questions from your IT, compliance, or legal team.
Contact Security Team
Questions?
For security or privacy questions: security@mtqnow.com
For general privacy requests: privacy@mtqnow.com
Read our full Privacy Policy and Terms of Service.
© 2026 L Emquitee LLC d/b/a MTQ Now™. All rights reserved. Patent pending.