Privacy Policy

Last updated: September 3, 2026

1. Overview

Intode ("we", "our", "the app") is a mobile SSH IDE that connects to your own servers. We are committed to protecting your privacy. This policy explains what data we collect, how we use it, and your rights.

2. Data We Collect

2.1 Account Information

Intode has no user accounts. There is no sign-up, no sign-in, and no profile. We do not collect your email address, your name, or any other identifier, and we operate no server that could store them.

2.2 Purchase Information

If you subscribe to Intode Pro, the purchase is processed entirely by Google Play or the Apple App Store. Your subscription status (active/expired) is delivered by the store to your device and cached there so the app knows which features to unlock. We never see your payment details, and that status is not sent to us — we run no server that could receive it.

2.3 SSH Connection Data

Your SSH connection details (hostname, port, username, password) are stored locally on your device only. This data is never transmitted to our servers. SSH passwords are stored using the platform's secure storage (Android Keystore / iOS Keychain).

2.4 Crash and Diagnostic Data

Intode uses Firebase Crashlytics, a Google service, on both Android and iOS to learn when the app crashes. This is the only data that leaves your device and reaches us.

If the app crashes, the next time you open it a report is sent containing:

• The stack trace, the exception or signal type, and the names of the functions involved
• Device state at the moment of the crash — device model, operating system version, CPU architecture, available memory and disk space, screen orientation, and whether the device is rooted or jailbroken
• The app version and bundle identifier, and whether the app was in the background
• A randomly generated install identifier (a Crashlytics Installation UUID and a Firebase installation ID) so we can tell one crashing installation apart from another

There is no account attached, because the app has no accounts. Reports do not include your hostnames, usernames, passwords, SSH keys, file contents, or anything typed into or printed by a terminal. The install identifier is random, is not your advertising ID, is not used to track you across other apps or websites, and is discarded when you uninstall the app. We use these reports for one thing: fixing crashes.

Google processes this data on our behalf; see the Firebase privacy documentation and Google's privacy policy. Crashlytics keeps crash traces and the associated identifiers for 90 days and then begins deleting them. Firebase Analytics is not part of this app — we do not record which screens you open, which features you use, or how long you stay.

2.5 Data We Do NOT Collect

• Server file contents, terminal commands, or terminal output
• Hostnames, usernames, passwords, or SSH keys
• Location data
• Advertising IDs, or any identifier usable to track you across apps or websites
• Contacts, photos, or other personal data
• Usage analytics — screen views, feature usage, session length

3. How We Use Your Data

The crash reports described in 2.4 are used to find and fix crashes, and for nothing else. Everything else the app needs stays on your device:

• Unlocking Pro features based on the subscription status your store reports to the device
• Customer support — only what you choose to tell us when you email us

4. Data Sharing

We do not sell or rent your data, and we share nothing for advertising. The parties involved are:

• Google (Firebase Crashlytics) — receives and stores the crash reports described in 2.4, acting as a processor on our behalf.
• Google Play / Apple App Store — handle subscription billing directly, under their own privacy policies. We are not a party to that transaction beyond the resulting entitlement arriving on your device.
• Your own servers — the app connects to hosts you specify. That traffic goes from your device straight to your server and never passes through us.
• Legal requirements — if required by law.

5. Data Storage and Security

Apart from the crash reports in 2.4, all app data lives on your device. SSH credentials are held in the platform's secure storage (Android Keystore / iOS Keychain) and never leave it. SSH sessions are encrypted by the SSH protocol itself, directly between your device and your server. Crash reports are sent to Google over an encrypted connection.

6. Data Retention

Crash reports are retained by Firebase Crashlytics for 90 days and then deleted. We keep nothing else — the rest of your data persists only on your device, for as long as the app is installed.

7. Deleting Your Data

There is no account to delete. Uninstalling the app removes everything on your device — workspaces, SSH credentials, and cached settings are all local and go with it.

Crash reports that were already sent carry no account and no identifier we can connect to a person, so there is nothing for us to look up or erase on request; they are deleted automatically after 90 days.

To manage or cancel a subscription, use your store's subscription settings (Google Play or the App Store); that is where the purchase lives. If you have a question about any of this, email support@mintcinc.com.

8. Children's Privacy

Intode is not intended for children under 13. We do not knowingly collect data from children.

9. Changes to This Policy

We may update this policy from time to time. Changes will be posted on this page with an updated date.

10. Contact

Questions about this privacy policy? Contact us at support@mintcinc.com.