Mechanly – Privacy Policy
Mechanly – Privacy Policy
Mechanly is made by an indie developer.
Your privacy is respected and terms & services are simple.
1. What you do in Mechanly
Your AI provider. Mechanly uses a Bring Your Own Key model. The conversations you have and the tasks you run are processed by the AI provider you connect (such as OpenAI / ChatGPT) using your own account or key, under their own privacy policy and terms as well as ours. Your keys stay on your device.
How long we keep it. We don’t store your conversations or task data on our servers at all — everything happens directly between your device and the AI provider you connect. A few things you explicitly choose to do are kept: if you send us feedback on a chat, we keep that feedback (after removing anything sensitive) so we can act on it; and if you save a Mech or Mech App, we keep a copy so it keeps working (see Section 4 for what that copy is and how it’s used, including Private saves).
Feedback. If you explicitly send us feedback on a chat, we receive that chat’s content with sensitive information removed, so we can review and act on your feedback.
2. On-device data you allow
Some tasks need access to things on your phone. You grant each of these with an Android permission and can revoke them at any time. This data is read on your device and may be sent to your chosen AI provider as context for the task you asked for. We do not receive, store, or share it.
Contacts. Mechanly can read and create contacts when you grant contacts permission (for example, “Add John to my contacts”).
Calendar. Mechanly can read and create calendar events when you grant calendar permission (for example, “Schedule a meeting for tomorrow”).
Notifications. When you grant notification access, Mechanly reads notifications from your other apps so the AI can summarize and act on them.
3. Backups
Backups are stored locally, not on our servers. When you create a backup, Mechanly writes an encrypted file to a location you choose on your device (or your own cloud storage, like Google Drive, if you pick a synced folder) — we don’t keep a copy of that file ourselves. Backups are linked to your signed-in AI provider account. Manual backup and restore work without Mechanly Pro; automatic scheduled backups are a Pro feature.
4. Saving & sharing Mech Apps
Mechanly lets you build and save “Mech Apps.”
Saving. When you save a Mech or Mech App, we keep a copy in our systems so it keeps working. It is not public. It may be sanitized before being shared with other users, and can be read by Mechanly’s administrators for audit, support, and abuse review.
Sharing. If you choose to publish a Mech App, we host a sanitized, recipient-safe version at a public link (for example, mechanly.app/share/…). Only that sanitized version is public. Your raw data, logs, conversations, and account are never included. A published app stays available until you unpublish it.
Private (Pro) apps. Marking an app private keeps it out of public sharing, discovery, and example queues, and it’s never used to improve the product. We still keep a backup copy for up to 30 days purely for abuse-prevention and support — after that it’s gone unless you’re still actively using it.
5. Diagnostics & account data
To run and improve the app we also collect a small amount of operational data. Unlike your activity above, this is handled through Firebase and Google and kept according to their standard retention, which can be longer than 30 days.
1. Crash & error reports – only so I can fix bugs and make the app better.
2. Basic app usage info – helps me understand which features are useful.
3. Firebase Analytics data – tracks your app usage to improve your experience.
4. Firebase Crashlytics data – crash reports and error data to help fix bugs faster.
5. Device IDs – needed for app integrity and license verifications.
6. Email – only if you subscribe to the developer newsletter or make in-app purchases/subscriptions.