Privacy Policy

Operator: Owen Peever. Legal content owner: Owen Peever.

Public website: https://dieselbench.ca. Intended public application URL: https://app.dieselbench.ca. These addresses do not establish that this project has been deployed there.

Version 2026-10-01.1 · Effective: 2026-10-01. DieselBench is an independent mechanic training application. This policy describes the current application; it is not a claim that legal compliance has been certified.

What DieselBench stores

The application does not require a real name, address, phone number, date of birth, location, contacts, advertising identifier or uploaded vehicle information. It does not store the platform email or real-name header in new records. A historical private display-name field can remain in an older account and is included in export and deleted with the account; new interfaces use the public nickname instead.

Upgraded accounts can retain legacy aggregate XP, test counts and star totals. Levels, streaks, achievements and mastery displays are calculated from stored training records rather than kept as separate identity records.

Sign-in and service providers

The Cloudflare application uses Clerk for sign-in, sign-up and browser session management. Clerk processes account and authentication information under its own terms and privacy practices. DieselBench's Worker verifies Clerk-issued session tokens and stores only a deterministic, one-way account key derived from the signed issuer and subject; it does not store Clerk email or name claims. The original Sites deployment can continue to use its platform-verified identity. Hosting services may process technical request information such as IP addresses, URLs and HTTP headers; these are not fields collected in the DieselBench training database. Hosting and database services process requests and DieselBench records; provider logs, backups and sign-in records are separate from the live D1 database. Their exact retention and processing locations have not been independently verified here. Apple and Google sign-in providers are not configured by this integration.

Device storage and connections

A service worker may cache public lessons, diagrams, scripts and images for faster reopening and limited offline practice. It never caches account API responses, private formal assessment answer keys, tokens or private results. Circuit-board tools may retain current unsaved UI state in memory. Account results require a working connection; an unsaved result is labelled as pending rather than synchronized. Pending results are held in memory and can be lost when the page closes. Clearing browser site data removes public caches; downloaded exports are separate files and are not erased by clearing site data or deleting an account. Sign-in cookies are managed by the platform.

Public rankings

Public leaderboards show public nickname, rank, verified ranked XP, lifetime level, streak and a normalized performance metric. Practice-only learners with saved XP-earning completions this month appear in a separate trainee list with public nickname and lifetime level, without practice scores or test details. Community counts measure mechanics with saved XP-earning completions, not visitors. Weekly rankings show nickname and verified diagnostic score. Real names, email addresses, account identifiers, test answers and saved boards are not returned in public ranking responses. A generic pseudonym is used when no suitable nickname is set. Nicknames are filtered on the server and must not include identifying information you do not want public.

Why data is used

Records support account access, saved training, assessment marking, diagnostic evidence, progression, rankings, abuse prevention and account controls. The current application contains no advertising, third-party analytics SDK, sale-of-data feature or payment collection. The DieselBench backend does not call an AI service or send account records to one. On browsers that support the optional assistant integration, an assistant can operate the visible sensor simulator and receive its meter reading and circuit-state values. Processing of that interaction by the browser or assistant provider is separate from DieselBench’s training database.

Retention, export and deletion

Your training history is retained while your account exists. Profile & account > Account & data lets you select Download my data for a JSON export and permanently delete the live DieselBench profile, events, completions, boards, assessments, work orders and plan records in one database transaction. Leaderboard entries disappear because they are computed from those deleted records.

A non-public deletion marker contains the internal account identifier and timestamps. It prevents accidental recreation by open tabs and in-flight writes for 30 days; after that, the protection expires. A deliberate Create fresh profile action removes that marker. Expired marker rows can remain stored until an authenticated request triggers cleanup; no scheduled removal exactly at day 30 is claimed. Request counters become eligible for cleanup after two minutes and are removed on subsequent account writes or account deletion. A deletion challenge becomes invalid after five minutes, but its hash can remain until another challenge replaces it or the account is deleted. Deleted content may remain in provider backups/logs until their separate retention policies expire; immediate backup erasure is not claimed.

The JSON training export contains profile and acceptance records, events, completions, saved board, assessments, workshop jobs and plan records. Internal ownership keys are removed from exported rows. Security request counters, deletion challenges, deletion markers and hosting-provider records are not included. There is no self-service export of those security/provider records in this release.

Deleting DieselBench data does not delete your Clerk account or other provider data. The app asks Clerk to sign out the current browser after deletion, but does not delete the Clerk account. Export/deletion controls require verified access to your own account and remain available without renewed policy acceptance. Clerk manages its own session records; DieselBench does not persist a separate Clerk session or provider-link table. A Clerk identity is not automatically linked to a historical Sites identity.

Your choices and questions

Use a pseudonym, avoid personal details in board names, export your records and delete your account whenever needed. The public account-deletion page explains how to reach the authenticated controls. Privacy requests can be sent to the operator contact configured on this site. The operator and support contact are identified on this page. Provider retention, processing locations, mailbox operation and legal compliance have not been independently verified by this technical document update.

Changes

This page will be updated if storage, providers or monetization change. Subscription/payment data is not collected in the current release. Future billing requires an updated disclosure before that functionality is enabled.

Open profile & account controls

Operator contact: support@dieselbench.ca

Policy acknowledgement

Before creating or continuing a DieselBench profile, you must actively agree to the Terms of Use and acknowledge this Privacy Policy through an unchecked checkbox. The current accepted terms version, privacy version and server-recorded acceptance date are stored privately with your profile. They are included in your data export and removed when the live profile is deleted. This agreement does not opt you into marketing. If a substantive policy update requires a new agreement, account-based training pauses until you accept the updated versions; existing progress is preserved. You can still export or delete existing data without accepting. Public content and unsaved practice remain available.