Privacy policy
Last updated: November 5, 2026
Phammad runs no intermediary server: your device talks directly to your Zammad instance. LaCobble (contact@lacobble.dev) publishes the app but never sees your support data.
1. No Phammad server
Phammad has no database and no backend. All requests go directly from your device to the Zammad instance address you entered. The app includes no audience measurement or tracking tool.
2. Credentials
Your token or OAuth sign-in token is kept in the iOS Keychain, for each saved instance. If you use a login and password, they are used to create a token with your instance. None of this is sent to LaCobble or to a third party.
3. Your instance's data
Tickets, profiles and other displayed data come only from your Zammad instance and remain subject to its own privacy and retention policy.
4. What stays on the device
Drafts and pinned tickets stay on the device. The widget and Apple Watch receive the number of tickets to handle and the latest tickets; an option hides titles in the widget. If you turn it on, the Spotlight index of tickets stays on the device.
5. Summary
The thread summary and draft reply (iOS 26 with Apple Intelligence) are computed on the iPhone, with nothing sent to LaCobble or a third party.
6. Background alerts
If you turn them on, the app queries your instance when iOS allows it and shows local notifications. No notification relay is used.
7. No advertising profile
Phammad sells no data and includes no third-party advertising SDK.
8. Showcase website
This website may use Google Analytics only if you allow it through the cookie banner.
9. Deleting data
Closing a desk in the settings erases its credentials from this device. Do so before deleting the app: iOS may keep the Keychain after an uninstall. Your data stays managed by your Zammad instance, independently of Phammad.
10. Contact
For any privacy question: phammad@lacobble.dev