Your data is yours. We don't want it.
This isn't a policy bolted on after the fact — it's how the app is built. Every claim below is something you can verify in how Trend & Tend actually works, not just something we say. This page covers Trend & Tend specifically — see WrinkleByte's broader privacy philosophy on our main Privacy page.
Fully offline, no account required
Every asset, maintenance record, fuel log, and trip lives in a local database on your device from the first launch. Trend & Tend is usable forever with zero account creation and zero network connection.
Sync is opt-in, to a server you control
Want backup or multi-device sync? Point the app at your own self-hosted instance of the open-source backend. We do not operate a hosted version of Trend & Tend and never receive a copy of your data as part of using the app.
Attachments never leave your control
Receipt, odometer, and service photos are stored as local files — there's no third-party cloud storage step. Self-hosted sync only ever moves them to a server you own.
Deletion means deletion
Delete something and your device briefly marks it as deleted so your other devices catch up during sync — then that marker clears out too. That handshake happens only between your own devices and your own self-hosted server. Trend & Tend has no server in the loop to hold onto it, because we never receive a copy of your data in the first place.
No analytics or tracking SDKs
This is a currently-verifiable fact, not an unfalsifiable promise — the backend and web app are source-available, so it can be checked against the code rather than trusted on faith.
Exceptions require disclosure
If a future feature ever needs to send data off-device (for example, optional cloud backup or receipt scanning via a third-party API), that will be a deliberate, opt-in decision — never a silent default.
What this page isn't
This page describes the engineering philosophy Trend & Tend is built against — it is not a substitute for a formal legal privacy policy. App Store and Google Play listings will have their own required privacy policy text (for example, covering payment processing), written to match the principles described here.
Want to self-host?
The sync backend is open-source and runs via Docker Compose on hardware you control. A published container image is coming soon.