Privacy in the Android app

This is the privacy policy of CodeKasten for Android (com.codekasten.app). It says what the app keeps, what it sends, and to whom.

What the app keeps on the phone

• Your session for each account you sign in with, sealed with a key kept in Android's keystore. Signing out removes it, and ends that session on the server.
• The workspaces you open: their records, definitions and your own items (Inbox, fleeting notes), so they work offline. Signing out of an account deletes everything kept for it; Settings frees a workspace's space. Nothing of this is backed up to Google or moved to another phone.
• Changes not sent yet, until the server has them.

What the app sends, and to whom

• To the CodeKasten server you sign in to (codekasten.com, or the one your company runs): what you read and change, as the web app does. That server's own policy applies to it.
• Notifications: the server tells Google's Firebase Cloud Messaging to wake the phone. The message carries only identifiers, never the content of an item; the phone then asks the server itself. The app gives Firebase a push token and nothing else: no analytics, no advertising identifier.
• Crash reports go to codekasten.com: where in the app's code the crash happened (with every message taken out before it is sent), the app's version, the Android version and the phone's maker and model. Never your records, your text or your account. Switch them off in Settings. They are kept 90 days.

What the app does not do

No advertising, no analytics, no tracking across apps or sites, no selling or sharing of data. The app asks for the network and, on Android 13 and later, for notifications; nothing else. Pictures you add to a document are picked by you and sent to your server only.

Your data

Records you keep in a workspace belong to that workspace; ask its owners, or the people who run your server, to change or delete them. To have your account on codekasten.com deleted, write to the address given on codekasten.com.