Skip to content

Privacy & Data Handling

Handle logs, exports, and reports responsibly to protect proprietary and personal data.

Data Classification

  • Confidential: Proprietary vehicle data, calibration values, unreleased feature information. Store in secure repositories with access controls.
  • Restricted: Logs containing VINs, driver identifiers, or other personal data. Follow regional privacy laws (GDPR, CCPA).
  • Public: Sanitized datasets approved for open sharing. Confirm with management before classifying data as public.

Storage & Access

  • Use encrypted drives or secure servers for confidential logs.
  • Limit access to authorized team members. Use group permissions rather than individual sharing where possible.
  • Archive completed projects to long-term storage with retention policies (e.g., 3–5 years or as mandated).

Anonymization & Redaction

  • Remove or mask personal data (names, addresses, VINs) from logs before sharing externally.
  • Replace unique identifiers with pseudonyms when evaluating performance across multiple units.
  • Document transformation steps so recipients understand what was changed.

Sharing Guidelines

  • Share projects via secure channels (VPN, encrypted file transfer, company-approved cloud storage).
  • Never email large logs or exports without encryption.
  • Include classification labels in filenames or accompanying README files.
  • Keep a distribution list showing who received which dataset.

Logs & Exports in Reports

  • Reports often include screenshots or data extracts. Ensure sensitive fields are blurred or removed.
  • Highlight any remaining confidential data so reviewers handle it appropriately.
  • When sending to external partners, follow contractual data-sharing agreements.

Injection Profiles & Scripts

  • Injection profiles may reveal proprietary message definitions. Treat them as confidential.
  • Store profiles with the same access controls as the matching project.
  • Remove sensitive payload values before sharing with third parties unless authorized.

Telemetry & Analytics

  • If TrueFidelity collects anonymous telemetry, ensure opt-in aligns with company policy.
  • Review telemetry to confirm no personal or proprietary information is transmitted inadvertently.

Device Hygiene

  • Lock workstations when unattended.
  • Avoid storing confidential data on personal devices unless explicitly allowed.
  • Use company-approved antivirus and patch management tools to reduce leak risk.

Incident Response

  1. Immediately report suspected data leaks to your security team.
  2. Provide details: what data, when, who had access.
  3. Follow company incident response procedures to contain and remediate.
  • Consult legal counsel for regulations relevant to your region (GDPR, CCPA, ISO 21434).
  • Maintain audit logs of who accessed or modified critical datasets.
  • Adhere to customer NDAs and project-specific confidentiality agreements.

Best Practices Checklist

  • [ ] Classify data before storing or sharing.
  • [ ] Use secure storage with proper permissions.
  • [ ] Anonymize personal identifiers.
  • [ ] Encrypt transfers and archives.
  • [ ] Document who received exports.
  • [ ] Review reports for sensitive content before release.
  • Support – Contact info if you encounter data-handling incidents.
  • Release Channels & Updates – Understand how updates may impact data features.
  • Troubleshooting – Ensure logs captured for support are sanitized before sharing.