LimeBat app privacy policy

Who to contact

LimeBat, 64 Krum Popov Street, Sofia 1421, Bulgaria. Contact [email protected] or +359 878 870 324 about privacy, access, correction, deletion or concerns.

Local SSH use

You can use local SSH profiles without a LimeBat account. Profiles, saved credentials and trusted host keys stay in secure device storage. SSH connects directly to the server you choose; that server receives your network address and commands and may keep its own logs. LimeBat does not receive your terminal output. Local command suggestions remain on the device and are excluded from cloud synchronization.

Optional accounts and encrypted vaults

Signing in sends your email, password, chosen device name and any required authenticator code over HTTPS. We retain your name, email, account identifier, password hash, authorized device records and account security settings to operate and protect your account. Session tokens expire after 30 days and can be revoked. Recovery codes for account authentication are stored as hashes.

If you enable synchronization, personal server configurations, passwords and notes are encrypted on your device before upload. The service stores encrypted snapshots and revisions. Your vault recovery key is separate from your account password and is not sent to LimeBat. Authorized team members receive encrypted access to shared data. Account passwords cannot recover a lost vault key. Team membership, invitations, roles and subscription status are service metadata.

Direct chats and contact codes

Messages, photos, delivery state and history are encrypted in account-scoped files on your device. They are excluded from the cloud vault. Delivery and history transfer travel directly between devices over encrypted WebRTC data channels, without a server payload relay. Both apps must remain open and online. Direct participants and the configured STUN address-discovery provider can learn network addresses.

The website stores your shareable contact code, consent version and account-level block choices. Regenerating a code permanently retires the old value without an owner. To establish a connection, the service temporarily stores encrypted device identifiers and connection descriptions, including network candidates, for up to 180 seconds; requests and a scheduled cleanup remove expired records. Those descriptions contain no chat messages or photos. Native history transfer to another device of your account requires approval on the source device.

Reports and safety

Text filtering happens on the device and received photos are hidden until you choose to view them. If you explicitly report a user, the app sends account identifiers, the selected reason and the explanation you write to LimeBat support. It does not attach messages, photos or history. Avoid putting private conversations, passwords or unnecessary personal data into the explanation. Reports are encrypted at rest, restricted to site administrators, and used to investigate abuse, respond and enforce our community guidelines. Support notifications may be delivered through our configured email provider. Reports may be retained as needed for investigation, repeat-abuse prevention and legal obligations.

Providers and website visits

Hosting, network protection and email providers process the information needed to deliver the service. Infrastructure may log network addresses, request times, response codes and errors for security and operation. We do not add an advertising or analytics SDK to the native app and do not sell chat content. The public company website may use Google Analytics and optional Cloudflare Turnstile or Google Maps; visiting it in your browser is separate from native local SSH use. This privacy page, app support and community guidelines do not load Analytics.

Optional website team payments use Stripe. Stripe processes payment information under its own privacy policy; LimeBat retains customer/subscription references and status. The native app does not contain an in-app payment form. Providers may process data outside your country under their applicable safeguards.

Retention and deleting your account

Personal cloud vaults and account records remain while the account is active. In the app, open Account → Delete account; the option is also available before unlocking configurations. Confirm with your account password and any required authenticator code. Your account is disabled and sessions are revoked immediately. The support team completes deletion within seven days and emails confirmation. Shared team ownership and subscriptions are reconciled without erasing other members’ data. You do not need to send a separate email to initiate deletion.

After the request is accepted, the app removes this device’s account configurations, recovery key and chat data. Guest profiles are separate. We cannot remotely erase copies already held on offline devices, shared team members’ independent copies or chat recipients’ devices. Payment providers may retain legally required billing records, and restricted backups follow their normal replacement cycle. Confirmation contact details are removed from the deletion request after its email is delivered. Contact us if you need help with residual device data or other information you previously submitted.

Your choices and rights

You may use local SSH without signing in, revoke devices, decline incoming chats, block or report users, delete local conversations and request account deletion. Contact us to request access or correction, object to processing or exercise applicable data-protection rights. You may also raise a concern with the competent data-protection authority. Account and service data are used to provide the requested features, secure the service, respond to reports and satisfy legal obligations; permissions and optional actions remain under your control.

Changes

We will update this page when the service changes. Material changes to chat rules require renewed acceptance in the app. Questions: [email protected].