askLAD — Privacy Policy

Version 1.13 · Effective date: November 9, 2026 · askLAD mobile and Dev logout and account recovery disclosure

This Privacy Policy explains how HahaTech LLC ("HahaTech," "askLAD," "we," "us," or "our") collects, uses, discloses, retains, and protects personal information when you use the askLAD mobile and web applications, websites, and related services (the "Service"). This Policy is a notice about our practices, not a request to waive privacy rights.

The short version. askLAD processes information needed for truck-aware routing, legal-information tools, subscriptions, support, and the features you choose. My Defense File can hold sensitive recordings, transcripts, tickets, DataQ drafts and PDFs, documents, locations, and related records. Signed-out artifacts may be stored under a protected device credential and can be claimed by an account later. We do not sell personal information, share it for cross-context behavioural advertising, or use private Defense File or legal content to train unrelated AI models.

1. Scope and privacy contact

HahaTech LLC, a Florida limited liability company, is responsible for the personal information described in this Policy. Questions, access or correction requests, deletion requests, consent withdrawals, and privacy complaints may be sent to support@hahatech.team, Attn: Privacy Officer, or mailed to HahaTech LLC, 4640 Lucerne Lakes Blvd West, Apartment 101, Lake Worth, FL 33467.

This version is written for adults using the Service in the United States and Canada only.

2. Information we collect

Account, setup, and driving preferences

My Defense File and legal-workspace content

Fleet, facility, community, and support information

Information collected automatically

Native diagnostics, timing, and support

askLAD can automatically send crash reports to help us diagnose failures and keep the app working. Native reports are linked to your account and app-generated device identifier. They contain the app version and build, iOS version, device model, the MetricKit reporting window and receipt time, exception, signal and termination details, and a bounded call-stack excerpt. The reporting window is not an exact crash timestamp. We do not attach the recent app-activity log, a duplicate user ID in the report context, location, photos, audio, credentials, or available-storage measurements to automatic native crash reports. These reports are not used for tracking across other companies' apps or websites. Google Maps separately collects SDK crash and performance information for analytics; that does not make native reports anonymous.

A bug report you choose to send can include your description, account and device identifiers, app and device information, a bounded recent app-activity log, and a photo you choose. The activity log can describe navigation or device state. Support-log exports omit recorded available-storage measurements and storage-derived failure details. Manual bug reports and log sharing are separate actions from automatic crash reporting.

If you choose voice input for a diagnostic report, it may be sent to the transcription provider. The diagnostic record can retain the transcript, but the current diagnostic handler does not retain a separate audio clip.

The device-local activity log normally expires after about seven days and is size-capped. An uploaded diagnostic or support report is a separate server record. We retain that record while its owning account remains active and delete it with the account. We do not promise seven-day server deletion or anonymous diagnostic reports.

The app uses elapsed-device-time readings for timing and to timestamp in-app motion events. Automatic native crash reports do not attach raw uptime or boot-time readings. Available-storage checks support local offline-map and navigation-cache decisions; their measurements and derived storage-failure details are not included in support-log exports.

3. Signed-out artifacts, device ownership, and account claiming

Some recordings, tickets, DataQs, rights incidents, and related research can be created before you sign in. These artifacts may be uploaded privately and associated with an app-generated device ID plus an independent random device-owner credential kept in the device Keychain. We store a one-way credential hash, not the secret itself.

Creating an account or explicitly signing in can claim eligible artifacts created on the current device. Claiming links them to the authenticated account, permits account-based access across supported devices, and prevents the former guest credential from continuing to act as the owner. Documents remain account-owned under their existing access controls.

Deleting or reinstalling the app before claiming may remove the credential needed to access signed-out artifacts that remain in private storage. Use each feature's deletion control before uninstalling, claim the artifacts to an account, or contact the Privacy Officer for assistance.

4. How we use information

5. AI processing and model training

The Service uses AI providers to perform tasks you request, including legal-information responses, ticket and document analysis, transcription, and DataQ document preparation. Relevant content is sent to the provider needed for that task. We do not use your private legal questions, Defense File items, ticket photos, recordings, transcripts, or documents to train our own or third parties' models for unrelated purposes. Provider processing remains subject to contractual and technical controls and the provider's applicable service terms.

6. Service providers and disclosures

We disclose information to providers that process it to operate the Service. We require providers to protect personal information consistently with their role and applicable law. The list below identifies personal-data recipients; it is not an inventory of proprietary datasets or internal sourcing strategy.

Provider or categoryPurposeTypical information
SupabaseAuthentication, database, private storage, access controls, and Edge FunctionsAccounts, device ownership, Defense File, fleet, facility, rights, support, and app records
Apple and GoogleProvider sign-in when you choose itProvider account identifier and the email, name or profile details you permit; authentication remains with that provider
HERE Technologies and Google Maps PlatformRouting, maps, geocoding, places, imagery, and SDK operationRoute/search coordinates, truck profile, place queries, map/SDK diagnostics; not Defense File content
Anthropic, Google, and OpenAIAI answers, analysis, document preparation, and transcription when the applicable feature is usedRequested prompts, documents, images, audio, transcripts, and pseudonymous safety identifiers as needed for the task
Voyage AI, Tavily, and CourtListener / Free Law ProjectLegal retrieval, embeddings, web research, and case-law searchLegal search text, violation/jurisdiction facts, and research terms without account identity where feasible
StripeCheckout, billing, subscription management, fraud preventionEmail, optional name/phone, plan, and payment information held by Stripe
ResendTransactional messages and separately consented product emailEmail, name, and requested message or attachment
PostHogNative product analyticsUsage events, identifiers, subscription/offer state, surveys; not private Defense File or legal content
Traffic and operational feed providersTraffic, closure, hazard, and road informationRoute-area coordinates without account identity

We may also disclose information when legally required, to protect rights or safety, to investigate abuse, or as part of a merger, financing, acquisition, or sale of assets, subject to required notice and protections.

7. Local evidence recorder and traffic-stop rights

With your separate Evidence recorder choice, the app keeps real GPS, time, speed/accuracy/course, derived braking, device-motion peak g-force, and available navigation context in protected, account-scoped rolling files on this device for about seven days. iOS location permission alone is not this product choice. Turning the recorder off stops new collection and removes that account's rolling files on this device. A selected excerpt deliberately saved in an accident report is separate and follows that report's controls. The raw rolling trail is not automatically uploaded, included in analytics, or shared with a fleet. Ending the app process does not erase the rolling files; collection after termination depends on iOS and can have gaps.

Deliberately saved accident reports, their selected trail and media are separate from the rolling files. Earlier askLAD Dev versions let you separately choose managed account recovery when logging out; archives created that way remain available as described below. Each app uses its own backend and account access controls; a Dev/Labs account or archive does not authorize access to Production. This choice does not enable accident-report backup for other apps or enroll you through an unrelated backup choice. Accident-report backup is a separate choice described below. Current app versions no longer use the older accident-report sync path, but older installed versions may have created, and until updated may still create, cloud copies there. Those older copies remain until you delete the report in the app or delete your account.

Account recovery, offline copies, and logout

Current app versions do not create a recovery archive when you log out. If you made an explicit account-recovery choice in an earlier version, or a logout that began in an earlier version is still finishing, askLAD preserves an encrypted archive of account-owned saved reports and selected media; inspection recordings; insurance records and card images; deliberately downloaded documents and their metadata; annotations; searches; trip records; account diagnostics and temporary files; preferences; Rights records; and pending work such as repair cases. The raw rolling trail, authentication credentials and offline maps are excluded. askLAD manages keys that allow recovery: this is not end-to-end encryption. Our service and authorized providers process the encrypted files and recovery keys under account access controls. Recovery-key release requires a fresh owner sign-in and is audited.

Logging out ends this phone's session. It does not remove this account's app data from the phone. Saved reports, recordings, documents, offline downloads, preferences and other account-owned records stay on this phone in storage tied to the account: another account signed in on the same phone cannot open them, and they are available again when the same account signs back in. Logging out on one phone does not sign the account out on its other devices. Recordings and other items that had not finished uploading wait on the phone until the same account signs back in, and the account's scheduled reminders are cancelled. You cannot log out while an inspection recording is in progress. To remove this data from the phone, delete your account in the app; removing the app from the phone also removes its stored files. A logout that began in an earlier app version and was preserving a recovery archive finishes under that process: it verifies the completed archive and its managed-key recovery before removing this account's app data, offline document downloads, and local credentials from the phone, and an unavailable service, expired sign-in, unfinished upload or failed verification can delay it while your saved data or saved preservation progress remains protected. Finished cloud archives survive logout. In Settings, Account recovery lets the signed-in owner download complete archives for offline viewing or export. Recovered records are inert copies: they do not automatically replay uploads, Rights events, repair work, sharing permissions or other actions. Some supported report content may also have a separate import control.

Recovery archives remain until you remove the retained copy or delete the owning account; there is no automatic expiry promise. Stopping future recovery backups does not delete existing archives. The current app does not provide a control to delete an individual retained archive. Contact the Privacy Officer to request removal and confirmation that all archive components have been removed. A request alone is not proof of deletion, and removal does not recall exports already saved elsewhere. Account deletion includes retained recovery archives under the account-deletion process. Contact the Privacy Officer if an archive cannot be accessed or removed. Service or key availability can affect recovery, so keep independent exports of records you must retain.

Documents and recovery files you deliberately download are stored in protected account-owned app storage and are available without a network connection after download verification. Logout keeps those local downloads on the phone under the account, as described above; account deletion removes them. If you choose Save to Files or share an export, the destination app, Files provider, recipient or device backup provider may retain an independent copy. askLAD cannot remove those external copies; you control their retention and deletion. Feature availability depends on the installed app and the service enabled for that app. A Dev feature or this notice alone does not activate a Production feature.

Saved truck-insurance records and card images have their own askLAD backup choice. If you turn it on, askLAD keeps an encrypted copy under your account so it can be restored when you sign in on another phone; askLAD manages the recovery key, so this is not end-to-end encryption. After askLAD confirms that its copy matches what is on your phone, the phone stops including those insurance files in ordinary device backups. Until then, and whenever the choice is off, they can be included in ordinary device backups under your device/provider settings. Deleting your backup copies also deletes the insurance copy. askLAD's local deletion controls do not themselves remove copies already held by your device-backup provider.

Accident-report backup (optional). If you choose “Back up my saved accident reports,” askLAD uploads an encrypted copy of each saved accident report under your account: its text (including other parties' names, contact, license, vehicle and insurance details you enter), the photos, video and audio you attach, the trail excerpt with location you saved in it, and its PDF. It does this shortly after each save or edit. You can restore these copies when you sign in on another phone; releasing the recovery key requires a recent sign-in. askLAD manages the recovery keys, so this is not end-to-end encryption. Your seven-day rolling trail, sign-in credentials and offline maps are never included. In Settings › Report backups, “Stop future backups” blocks new uploads but leaves finished copies available for restore; “Delete my backup copies” stops future backups and starts permanent cloud removal of report and truck-insurance copies. Deleting a report in the app also deletes its backup copy, and deleting your account deletes them all. Finished copies have no automatic expiry. An upload that is not finished within seven days can no longer be completed; its partial files are removed the next time the app checks that report or during service cleanup.

Rights incidents can remain available offline and synchronize when a connection is available. On supported devices, translation uses Apple's on-device Translation framework only when the requested language is installed. The reviewed English version controls; machine translations are labeled.

8. My Defense File, search, sharing, and exports

My Defense File is an index over existing source records rather than a second copy of every artifact. A recording and its transcript, media, location, duration, and linked rights session appear as one incident bundle. Search runs against item metadata and available transcripts; search queries are not sent to analytics.

Hide from Recent is not deletion. A hidden item remains stored and appears under Hidden until restored or permanently deleted. A DataQ shown as Filed means the driver explicitly marked it filed and may have entered a date or confirmation number; it is not independent verification by askLAD or FMCSA.

When you share an item or create a multi-item export, the app may request short-lived private download links and assemble an index, documents, PDFs, and transcripts in a temporary local folder. Recording media is included only when you choose it. The app removes its temporary export files after the share flow finishes or is cancelled, but recipients, share extensions, cloud providers, or other apps you choose may retain their own copies.

9. Roadside recordings and safety-contact alerts

Recording starts only after the driver takes an explicit recording action and receives the applicable permission and recording notice. Selected video, audio, transcript, location label, and upload metadata are stored privately so the incident can be reopened or exported. Recordings remain until you delete them or delete the account that owns them.

If an actively uploading roadside recording becomes silent unexpectedly for more than approximately two minutes without being ended with its passcode, the Service may email the single selected primary safety contact. The alert can identify the driver and incident and may contain time-limited signed links to footage already uploaded. Phone numbers are not used for this watchdog alert in the current version.

If the phone's motion sensors detect a possible crash (a hard hit at road speed followed by a stop) and nobody taps “I'm OK” within one minute, the app sends the detection time and, when available, the phone's reported location and its accuracy to askLAD. The Service then emails your single selected primary safety contact once. The email names you, states the detection time, says the alert does not confirm that a crash happened, and can include a Google Maps link to the reported location. We keep the alert record, including its time, location, the recipient's email address and the email provider's delivery result, for about 30 days, then delete it automatically. Phone numbers are not used for this alert.

10. Fleet, team annotations, and facility access

Fleet location sharing is off by default and operates only under the in-app conditions described when enabled. Fleet managers may access the driver and route information identified in Section 2. Team-annotation content is private to eligible fleet members and authorized support or platform personnel, subject to role-based permissions and audit history.

Facility-access and venue submissions may be attributed to an account or protected device, reviewed, edited, versioned, or moderated. Content may be displayed to eligible users to help with planning, but user-supplied guidance can be wrong or stale and is not treated as verified routing law.

Where the reviewed company-history retention feature is enabled, completed deletion of a former fleet member can leave approved company operational history available within that fleet. The service removes the deleted account link and uses an opaque fleet-specific attribution displayed as Former member. Identity-capable shared text, metadata and media require review of the exact retained content by another authorized reviewer, either an active fleet owner or manager or an authorized platform administrator. Private records and unapproved, changed or unverifiable identifying content are removed or sanitized through the deletion process. Retained activity can still be linked within the fleet and may identify someone from context; this is not a promise of complete anonymity. If the required review, access controls or deletion checks are unavailable, the account-deletion process can remain pending and require support; it must not report completion for an unfinished deletion.

11. Payments, transactional messages, and marketing

Stripe processes payment details on its hosted pages. We receive subscription status and identifiers, not the full card number. We may send transactional messages you request or that are necessary to administer an account, subscription, security event, export, or report.

Marketing or product-update email requires a separate opt-in where required. A subscription or account does not by itself enroll a Canadian user in indefinite promotional email. Commercial messages identify HahaTech and include a working unsubscribe method; unsubscribe requests are applied within the period required by applicable law.

12. Retention and deletion

Account deletion can take more than one attempt while uploads, private files and account-owned records are checked and removed. Older app versions may report only cloud-account deletion and cannot verify erasure of copies on this phone or another device. askLAD may retain the account identifier, deletion-operation identifier, state and completion time to prevent delayed uploads or offline activity from recreating deleted records, to finish or verify a failed deletion, and for security. These limited records are not described as anonymous, and there is no automatic expiry promise. These deletion and security records do not themselves contain or authorize keeping private recordings, documents, message content or recovery archives; approved shared fleet history is described separately in Section 10. Contact the Privacy Officer about a pending deletion or retained security record.

InformationGeneral retentionDeletion or expiry
Defense File artifactsUntil the owner deletes the item or accountPer-item permanent deletion removes the source record and associated private media/PDF where supported; hiding does not delete
Rights incidentsUntil deletedA non-content HMAC tombstone and deletion time may remain to prevent a deleted offline item from returning
Temporary exports and signed linksOnly as needed to build/share the exportLocal temporary files are removed after completion/cancellation; signed links expire automatically
Local rolling evidence trailAbout seven days in protected, account-scoped on-device files after a separate recorder choiceExpires as the rolling files are pruned; explicit switch-off removes that account's rolling files, not deliberately saved reports
Local activity logNormally seven days with a size capAuto-purges unless a limited tail is deliberately submitted with a bug report, or the log is included in a managed account-recovery archive you choose
Accident-report and truck-insurance backup copiesUntil you delete the item, delete your backup copies, or delete the account; finished copies have no automatic expiry, and stopping future backups does not delete themUnfinished uploads cannot be completed after seven days and their partial files are removed when the app next checks that item or during service cleanup
Possible-crash alert recordsAbout 30 daysDeleted automatically, including the reported location and recipient email address
Uploaded native diagnostic/support reportsWhile the owning account is active; not a seven-day server expiryVerified account deletion removes account-owned diagnostic records; automatic reports remain linked until deletion
Account contentWhile the account is active or as needed to provide the ServiceUse in-app deletion controls or contact the Privacy Officer. Some legacy content or failed deletion steps require support; a request or hidden item is not proof that all copies were removed
Approved company history after former-member deletionRetained for company operational history under fleet access controls; the current implementation has no automatic expiryThe deleted account link is removed and replaced by fleet-specific Former member attribution. Private and unapproved identifying content is removed or sanitized. Contact the Privacy Officer for retention or removal requests; a request is not proof of completed deletion
Billing, acceptance, security, and deletion recordsOnly as needed for accounting, acceptance evidence, fraud, dispute, legal, security, or resurrection-prevention purposesAcceptance evidence includes document versions/hashes, account/device identity and timestamps and may outlive account deletion; contact the Privacy Officer for access or a retention/deletion request. Minimized or de-identified where feasible
Community parking history and training recordsRetained to provide history or a durable training recordDeletion may be requested with the associated account or verified device record

13. Your choices and consent

14. United States privacy rights

Depending on where you live and whether an applicable state law covers HahaTech, you may have rights to know or access personal information, correct it, delete it, receive a portable copy, limit certain sensitive-information uses, or appeal a request decision. We do not sell personal information or share it for cross-context behavioural advertising, so there is no sale/share opt-out needed for our current practices. We will not discriminate against you for exercising an applicable privacy right.

For California notice-at-collection purposes, the categories include identifiers; contact information; precise geolocation; audio, visual, and other user content; commercial/subscription information; internet or app activity; and inferences limited to preferences such as DriverPattern. They are used for the purposes described in Section 4 and retained as described in Section 12.

15. Canada privacy rights and cross-border processing

Canadian users may request access to their personal information, ask how it has been used or disclosed, challenge its accuracy and request correction, withdraw consent subject to legal or contractual limits, and challenge our compliance through the Privacy Officer. We will explain any lawful reason we cannot fulfill all or part of a request. You may also complain to the Office of the Privacy Commissioner of Canada or the applicable provincial regulator.

HahaTech and many providers operate in the United States. Personal information from Canada may therefore be processed or stored in the United States or another country used by a disclosed provider and may be accessible to courts, law enforcement, or national-security authorities under that country's laws. HahaTech remains accountable for information transferred to service providers for processing and uses contractual, organizational, and technical safeguards appropriate to the information's sensitivity.

16. Security

We use safeguards intended to match the sensitivity of the information, including encryption in transit, private storage, access controls, short-lived signed links, device-owner credentials, role restrictions, and audit records. No system is perfectly secure. If a breach creates a legally reportable risk, we will notify affected individuals and regulators as required.

17. Children

The Service is intended for adults and commercial drivers and is not directed to anyone under 18. We do not knowingly collect personal information from a child under 18.

18. Changes to this Policy

We may update this Policy. Material changes will receive a new version and effective date and, where appropriate, an in-app notice or renewed acceptance. The effective version remains available from Settings and the public legal page.

19. Contact

Privacy Officer, HahaTech LLC · 4640 Lucerne Lakes Blvd West, Apartment 101, Lake Worth, FL 33467 · 561-908-4123 · support@hahatech.team