Acceptable Use

Allowed

• Tracking the maintenance and compliance of aircraft you own, co-own, or are a delegate for.
• Issuing single-use signing links to mechanics performing actual maintenance on those aircraft.
• Sharing public verification links and API tokens with buyers, insurers, brokers, or integrations like Foreflight.
• Importing scanned paper logbook history for aircraft you legitimately own.
• Exporting your own data in any format we provide, at any time.

Not allowed

• Falsifying signatures. Don’t enter someone else’s certificate number. Don’t sign as a mechanic if you aren’t one. The cryptographic chain captures whoever signs, and we cooperate with FAA enforcement when called.
• Forging records. The whole point of Yolog is tamper-evident logbooks. Trying to fabricate maintenance history defeats the product and probably violates 14 CFR 43.12.
• Tracking aircraft you have no relationship to. Add only aircraft you own, co-own, or are a delegate for.
• Scraping or rate-abuse. The /api/v1/ endpoints exist for legitimate integrations under your own bearer tokens. Don’t aggregate other users’ data, don’t pound endpoints, don’t share tokens beyond their issuing aircraft’s scope.
• Spam, phishing, or harassment via the mechanic-link or contact channels.
• Uploading malware or files unrelated to maintenance recordkeeping.
• Reselling or relicensing the platform without written permission.

Enforcement

Repeated or egregious violations may result in account suspension or termination. Where suspected fraud touches a signed entry, we cooperate with the FAA. We will always notify you of the issue, give you a chance to respond, and preserve your data through the cancellation window in our DPA — we don’t weaponize data deletion.

Reporting abuse

If you believe an account is being used to falsify records, impersonate a mechanic, or otherwise abuse the platform, email abuse@yolog.aero with whatever evidence you have. We respond within two business days.

Last updated: pending. Effective: pending counsel review.