EngineHoursLog
Privacy

What we don't do.

The privacy notice most companies should write but don't.

Version 1.0 · Last updated 2026-04-21

EngineHoursLog is designed to work without signal and still survive device loss. The app keeps a working copy in your browser's local storage for field use, and production accounts keep a server recovery copy so a phone upgrade, app removal, or browser reset does not destroy a decade of records.

Summary in five lines

  1. We do not sell or rent your personal data. Ever. This is in our Terms of Service as a binding commitment.
  2. We do not run ads, and we will not introduce an ad-supported tier. Also binding.
  3. We do not use third-party analytics that track users across the web (no Google Analytics, no Meta Pixel, nothing of that kind).
  4. Your logbook data is stored locally for offline use and backed up server-side for account recovery in production.
  5. You can export everything you've given us and delete your account at any time.

What data we collect

Free tier accounts

The production Free tier requires an account. We collect the email address needed to identify and recover the account, passkey metadata needed to authenticate your device, and the logbook records needed to provide backup and recovery. The app also keeps a local IndexedDB working copy so you can log hours and service while offline.

When you visit enginehourslog.com, our hosting provider (Netlify) logs ordinary HTTP request metadata — IP address, user agent, page requested, timestamp — for a short period for operational purposes (debugging, DDoS protection). This is standard web-server logging, not analytics. We do not build user profiles from it.

Free tier — optional waitlists

If you submit your email to the paid-tier launch waitlist or the community-translation waitlist, we store that email address and (for translations) the language you asked for. That's it. We use it only to email you once or twice, on the topic you signed up for. You may request deletion at any time — email privacy@enginehourslog.com.

Paid tiers — when they launch

Paid tiers add active multi-device sync, mechanic sharing, ownership transfer, email reminders, and higher engine limits. They use the same account-backed storage model as the Free tier. When paid features launch, this section will describe exactly what additional data is stored, where, for how long, and who can access it. The binding commitments from our Terms of Service apply: no sale, no ads, no cross-site tracking.

Speech-to-text (Dictation)

The app offers two ways to dictate text into note and description fields:

Third-party processors

We use a small number of external services to operate EngineHoursLog. Each is listed below with what it does for us and what data it touches.

ProcessorPurposeData they see
NetlifyStatic-site hosting and formsHTTP request metadata; waitlist form submissions
NamecheapDomain registrar and email forwarding for *@enginehourslog.comInbound email destined for our addresses, forwarded to the operator's inbox
Google FontsServes the web fonts used on the siteIP address and user agent of font requests

We do not use Google Analytics, Meta Pixel, LinkedIn Insight Tag, TikTok Pixel, Hotjar, Mixpanel, Segment, or any similar tracker. None.

When the paid tier launches, additional processors will appear in this table — expected additions: an email-delivery provider (Resend or Amazon SES) and a payment processor (Stripe). Each will be listed here with the data they see before they start handling real user data.

Cookies and local storage

We do not set tracking cookies. The app uses browser storage (IndexedDB, localStorage) to store your offline working copy and interface preferences (theme, locale). Production logbook records also sync to your account's server recovery copy when connectivity is available.

Your rights

You can, at any time:

We aim to respond within 30 days. If you're in a jurisdiction with statutory privacy rights (GDPR, CCPA, etc.), those rights apply and we will honor them.

Children

EngineHoursLog is not directed to children under 18. We do not knowingly collect data from children. If you believe a child has given us information, email privacy@enginehourslog.com and we will delete it.

Security

We take reasonable technical and organizational measures to protect data entrusted to us. Production account data will be encrypted in transit (TLS) and at rest where the underlying storage supports it, with server backups designed for recovery after device loss. No system is perfectly secure; we do not claim otherwise.

If you believe you've found a security issue, please report it to security@enginehourslog.com. We will acknowledge within 72 hours.

Changes to this Notice

We may update this Notice as the Service changes. Material changes (new processors, a new data category being collected) will be announced on this page and — for account holders, when accounts exist — by email at least 30 days before taking effect.

Contact

Privacy questions: privacy@enginehourslog.com. General contact: hello@enginehourslog.com.