Natty Privacy Policy

This policy explains how Vailgrid handles data for the Natty mobile app. It supplements the shared Vailgrid Privacy Policy. Natty is a developer terminal designed around an encrypted local vault. Core terminal and Remote Files (SFTP) use works without a Natty account.

Data Natty Handles on Your Device

Natty can store hostnames, usernames, connection settings, known-host decisions, credentials, software private keys, public-key metadata, snippets, command-palette history, explicit session bookmarks, workspace state, file paths, and transfer state. Natty encrypts its local database and separately encrypts sensitive vault records. Device-bound and physical-security-key private material remains in the device secure hardware or external authenticator.

Terminal output and prompts are not sent to Vailgrid. Natty does not include advertising SDKs, analytics SDKs, or automatic crash uploads. Remote clipboard writes are blocked by default, and terminal content enters a bookmark only after you explicitly select it.

Connections You Direct

When you connect to a host, Natty sends the connection and authentication data required by the protocol to the host or jump hosts you selected. SFTP uploads and downloads move files only between your device, OS-selected destinations, and remote systems you direct. Telnet is unencrypted, disabled by default, and requires per-host opt-in.

Optional Account and End-to-End Encrypted Sync

GitHub OAuth or email OTP can create an optional Natty account. Creating an account does not enable sync. The authentication service can process your email address, OAuth subject, Natty account identifier, and a random Natty sync-device identifier to provide account, authorization, device transfer, revocation, and deletion features.

If you separately enable sync and confirm a recovery code, Natty encrypts each versioned entity on your device before uploading it to the dedicated Supabase service. Synced entity content can include profile metadata, commands, snippets, preferences, and explicit bookmarks, but remains ciphertext to Vailgrid and Supabase. Routing metadata is bounded and authenticated. Supabase and GitHub process account or service data only to provide the features you request; Natty does not use it for advertising or tracking.

Retention and Deletion

Local data remains on your device until you delete it, clear app data, restore replacing records from an encrypted backup, or uninstall Natty. Completed download-cache files have bounded local retention. Data on remote hosts remains subject to the operator of those hosts.

You can delete an optional account and its server-side account data and ciphertext from Natty's Sync settings. If you cannot access the app, follow the public account-deletion instructions. Deleting an account does not erase the encrypted local vault on your devices. Data already decrypted on a revoked or offline device cannot be recalled remotely.

Diagnostics, Support, and Platform Data

Natty does not automatically upload diagnostics. If you contact support, send only the minimum information needed and do not send passwords, private keys, tokens, recovery codes, terminal content, host addresses, file paths, or encrypted backup files. Apple, Google, GitHub, and Supabase may process store, authentication, or service data according to their own policies and your choices.

Contact

For privacy questions, contact [email protected]. For product help, use Natty Support.