Maintenance Due

Privacy

Privacy policy

Maintenance Due is a free system of record for a shop, a fleet, or one van. This page says what the org stores, who can open it, and what the MCP endpoint does with a subscription.

The log holds every Asset, Service, Reading, Rule, and completion Event for the org. Assets are the trucks, cars, boats, houses, and equipment on the board. Services are named jobs. Readings are meter values written in as they happen. Rules are the intervals the org sets. Events are completed work. Oil on Truck A at 87240 miles, Winterize the Bayliner on October 15 — those are rows in the same log.

Everything is org-scoped. The org holds the board. A membership token, sent as Authorization: Bearer, opens that org and nothing else. A Muse or agent token is scoped to one membership. Offboard that member and the token dies the next time it asks what's due. There are no accounts, usernames, or passwords beyond that token.

Readings are append-only. A later odometer does not overwrite an earlier one, and history is never rewritten. The log is the record.

The MCP endpoint is public at /mcp (streamable-http). MCP Events (protocol 2026-07-28) let a connected client — for example the ChatGPT plugin — subscribe to service.due, service.completed, event.appended, asset.created, and asset.archived. Delivery is webhook only: notices go to the webhook URL the subscriber provides. Subscribing stores the subscription and its filter (asset or service name). It does not copy the log. Muse can subscribe for you.

There is no payment data. The origin is free forever, and commerce is none. The log is not sold or shared.

Questions about data go to support@maintenancedue.com. The terms live on /terms; help is on /support.