Privacy Policy

1. Information handled

• Account information such as name, email address, sign-in identity, profile preferences and assigned access roles.
• Training information such as assessment attempts and answers, verified scores, certificates, continuing education, assignments and practical sign-offs.
• Shop information such as organization details, membership, manager actions and team training records.
• Subscription, access-grant and order records, including shipping and tracking details where relevant. Payment card information is handled by Stripe rather than entered into TrailerPro’s training records.
• Information submitted in AI prompts, manual uploads, OEM proposals, partner comments, signatures and invitation records.
• Event lead forms, challenge entries and leaderboard results; demo usage counts, duration and steps; administrative audit records and technical diagnostics.

2. How information is used

Information supports sign-in, access eligibility, training delivery, secure grading, credentials, shop oversight, purchases, invitations and service communications. Audit and technical records help investigate misuse and maintain the service. Event contact information supports the information or challenge requested by an attendee; any additional marketing must follow the permissions collected and applicable law.

Sample demo results are illustrative, not real credentials. Demo usage tracking is separate from ordinary business reporting.

3. Who can see it

Authorized shop owners and managers can see training records for their current team. Authorized platform staff administer users, access grants, content and support. Invited OEM contacts receive only documents shared with them. Investor information is accessible through its separately controlled sharing links.

Certificate verification links intentionally expose a limited credential record, including the holder’s name and credential status. Shop warranty-auditor links expose a limited roster of qualifying current members and credentials. Event leaderboards use a first name and last initial alongside results. Consider this visibility before sharing a verification or auditor link.

4. Service providers and external links

The application uses Lovable Cloud for hosted account and application services, Stripe for payments, a connected Gmail/Google Workspace account for configured emails, and Lovable AI services for AI-assisted features. Optional Google or company sign-in uses the selected identity provider. Information needed to complete these services may be processed by the relevant provider.

Configured shop HR/LMS integrations can transmit credential or completion information to the shop’s authorized systems. Shipping information may be included in fulfillment communications to authorized staff or vendors. External manufacturer and seller websites have their own privacy practices.

Provider agreements, processing locations and any required international-transfer disclosures must be confirmed before this policy is finalized. This draft does not promise that a provider never retains data or uses it for model training.

5. Browser storage and security

Browser storage supports sessions, preferences, cached progress and unfinished responses. Kiosk sign-ups may be queued on the device while offline until they can be submitted. Shared devices should be reset and users should sign out after use.

Access restrictions and server-verified results help protect records, but no online service can guarantee absolute security. The final policy must confirm any additional analytics, cookie-consent requirements and operational security procedures.

6. Retention and your choices

Training, credential, billing and audit records serve different purposes and may require different retention periods. A production retention schedule, backup-deletion process and handling of legal recordkeeping obligations have not yet been approved. Turning off sample sandbox data removes its sample records; it is not a general account-deletion mechanism.

Depending on applicable law, you may have rights to access, correct, obtain a copy of or request deletion of personal information, or object to certain uses. A verified privacy-request contact and process must be established before launch; no automated account-deletion promise is made here. Subscription cancellation alone does not delete training or credential records.

7. Students and policy contact

Schools and employers should confirm appropriate authorization before inviting students or sharing their records. If minors will use the service, age eligibility, guardian consent and applicable student-privacy obligations must be addressed before enrollment; this draft does not claim compliance with child-specific privacy laws.

The operator’s legal name, address and privacy contact have not yet been supplied. These details, the final retention schedule and an effective date are required before this draft becomes the published policy.