In short
Suggello is an open-source (MIT) Android app for people who work with a self-hosted Palazzo server: it shows what is waiting for them and lets them approve, edit and send from the phone. It connects only to the server you enter. I, the developer, run no server for it and receive none of your data. The app has no accounts of its own, no analytics, no crash reporting and no advertising.
Who is responsible
The developer of Suggello is Luciano Nery, who can be reached at [email protected].
Everything the app sends goes to the server you choose, and nowhere else. The operator of that server, usually your organisation or the company that gave you your account, decides how that data is used and is its controller. Their privacy notice applies to it; ask them for it.
Choosing a server and signing in
On first start you enter the address of your server. The app contacts it to find its API and the name it goes by, and keeps both on the phone.
Accounts are not created in the app: the server’s operator creates them. To sign in you enter your email address and password, plus a code from your authenticator app if the account uses two-factor authentication. They are sent over an encrypted connection (HTTPS) to your server only. The app does not keep your password: it keeps only the session the server returns, in the phone’s secure storage (backed by the Android Keystore). Signing out ends the session on the server and deletes it from the phone.
What stays on the phone
The server’s address and name, the session, your language choice, and a note that the app has already asked for permission to show notifications. Your notification preferences are saved with your account on the server.
Everything you see in the app, such as emails and drafts, comments and direct messages, posts and monitoring alerts, is loaded from your server when you open it and held only in the app’s memory while it runs. It is not saved on the phone, and the app is excluded from Android backups. Uninstalling the app deletes everything it stored.
What the app sends to your server
When you approve, edit, send or cancel a reply or a post, pause publishing, or ask the AI to rewrite a draft, the app sends that action and its text to your server. The AI runs on the server, not on the phone; which AI service the server uses is up to its operator.
Notifications
Notifications go through Firebase Cloud Messaging, a service of Google, the only third-party service in the app. If you allow notifications, Firebase gives the phone a device token, and the app sends that token to your server only, so the server can tell you when something waits for you. A notification carries no message content, only a generic notice; the app then fetches the item from your server over its own signed-in connection.
Google processes the token and delivers the notice, possibly outside the European Union, as described in its privacy policy. Notifications work only if your server is set up to send them; otherwise the app works with them off. Signing out removes the token from your server, and you can switch notifications off in the app or in Android’s settings at any time.
Permissions
The app asks only for internet access and, on Android 13 and later, permission to show notifications. It does not use your location, contacts, camera, microphone or files.
Deleting your account and data
Your account and its data live on your server, so ask its operator to delete them. I hold nothing about you to delete. Uninstalling the app deletes everything it stored on the phone.
Your rights and questions
You can ask the operator of your server to access, correct or erase your data, to restrict its processing or to object to it, and you can lodge a complaint with the data protection authority where you live. For questions about the app itself, write to [email protected].
Changes
If a new version of the app changes anything written here, this page will be updated before that version is released.