Privacy Policy

1. Overview

Kryptode is an offline-first nearby communication application. Its core features are designed to work without requiring a centralized Kryptode account or a central messaging server. Most app data is stored on your device and, when you choose to communicate or publish, information is exchanged directly with compatible Kryptode users nearby.

This policy applies to the Android application published under com.kryptode.app.

2. Information Kryptode Handles

Profile and identity information

Kryptode creates an app identity on your device. Depending on what you enter in the app, your profile may include a display name, avatar selection, career path, role/status, product or service information, an About description, a Kryptode address, and public cryptographic identity information used to verify activity.

Your public profile details are shared with compatible Kryptode users nearby so they can identify and interact with you. Your private identity key is kept on your device and is not intentionally published as part of your public profile.

Messages, calls, files and social activity

• Private messages: stored locally on participating sender and recipient devices.
• Voice activity: voice segments and local call history may be stored on your device so the app can provide call and playback features.
• Files: files you intentionally choose to share are transferred directly between participating devices using Kryptode File Transfer, which creates a temporary nearby device-to-device connection. File names, sizes, MIME types, transfer status, and local save references may be stored in chat history. Received files are saved on the recipient's device.
• Community Board, Marketplace and reviews: content you intentionally publish is designed to be visible to nearby Kryptode users and may be cached on participating devices.
• Friendship, KRY and ranking activity: friendship state, KRY activity, room rank and related verification records are stored locally and exchanged where required for those features.
• Notifications: recent in-app notification records may be stored locally to show unread state and notification history.

Nearby device information

Kryptode detects compatible nearby devices so it can show nearby users and deliver supported app activity. Android may expose temporary wireless identifiers required for connection. Kryptode uses these for nearby functionality and does not use them to build an advertising profile.

3. Device Permissions and Why They Are Used

• Nearby devices / Bluetooth: required for discovering compatible Kryptode users, maintaining nearby connections, and exchanging supported app data.
• Location on Android 12 and below: older Android versions tie Bluetooth and nearby file-transfer operations to Location permission/services. Kryptode requests this only when required by Android for nearby discovery or direct device-to-device file transfer. Kryptode does not use this permission to create a GPS location history.
• Nearby Wi-Fi devices: on newer Android versions, Kryptode may request Nearby Wi-Fi Devices permission when you start or accept a direct file transfer. This is used to establish the temporary phone-to-phone File Transfer connection and is not used for advertising or GPS tracking.
• Microphone: used when you choose voice calling or voice-message functionality. Audio is captured for the communication feature you initiate.
• Camera: used when you choose to scan Kryptode QR codes.
• Notifications: used to alert you to messages, calls, files and other relevant Kryptode activity and to support notification actions where Android allows them.
• Foreground service, wake lock and boot events: used to keep nearby discovery and delivery functioning reliably in the background, subject to Android rules.
• File access: Kryptode uses Android's system file/document picker when you intentionally choose a file or backup. Kryptode does not scan your general file library in the background. For File Transfer, the sender selects the specific file after the recipient accepts the transfer.

4. How Information Is Shared

User-directed sharing

Information is shared when you use features that are inherently social or communicative. For example, a private message is sent to the recipient you choose, while a Community Board post or Marketplace listing is intentionally made visible to nearby users.

Direct Wi-Fi file sharing

File sharing is consent-gated. The sender starts a transfer for a selected Kryptode user and the recipient is asked whether to receive it before Kryptode establishes the temporary File Transfer connection. The connection is used only for that device-to-device transfer.

File bytes are not uploaded to a Kryptode cloud file server. Transfer coordination uses the existing protected nearby Kryptode channel, while file contents are additionally encrypted in transit over the temporary File Transfer connection. The recipient's device saves the file locally, generally in a Kryptode folder under Downloads on supported Android versions.

Private routed delivery

Kryptode can temporarily route protected private packets through participating Kryptode devices when direct delivery is unavailable. Relay devices may temporarily cache encrypted delivery packets solely to help forward them. The current private-route delivery window is limited and expired routed packets are removed automatically. Relay devices are not intended to receive the plaintext content of end-to-end protected private messages.

External services and links

Kryptode may open external services such as Google Play, Telegram or X when you choose those links or platform features. Those services process information under their own privacy terms. Google Play may also process app distribution, installation, security and store information independently of Kryptode.

We do not sell your personal information and we do not share your private communications with advertising companies.

5. Security

Kryptode uses cryptographic protections for supported private communications and file transfers. File Transfer uses a one-time session key coordinated through the protected nearby channel and AES-256-GCM encryption for the file stream, with integrity verification before a received file is accepted. Private identity material is protected using Android device security facilities, and portable migration backups are compressed and protected before being encoded for export.

Direct file transfers are initiated only after user action on both sides. Public content, by design, is not private and may be visible to other participating Kryptode users.

6. Storage and Retention

Most Kryptode information remains on your device until you delete it, clear app storage, or uninstall Kryptode. The app also uses bounded local caches for messages, calls, notifications, public content and delivery state so storage does not grow without limit.

Temporary routed private packets can remain on participating devices only for the app's delivery window before expiring automatically. Data that you intentionally publish or send to another person may remain on that person's device after you remove your own local copy.

Portable Kryptode backup files and files received through File Transfer are under your control. If you save or receive them outside the app, uninstalling Kryptode does not necessarily delete those external files; you must delete them yourself from your device or storage provider.

7. Your Choices and Data Deletion

Kryptode does not require a centralized account for its core nearby communication features. You can remove locally stored app data by using available delete controls, clearing Kryptode's app storage in Android settings, or uninstalling the app.

Where Kryptode provides delete controls for messages, call history, public content or other local records, those controls affect the data available to your device. Information already delivered to another user or published to nearby participants may remain on those devices.

Because the current app does not maintain a central Kryptode account database for these core features, there is no separate server account that must be deleted to remove your locally stored Kryptode identity.

8. Children's Privacy

Kryptode is not designed as a child-directed service. Users should not use Kryptode to share sensitive personal information with people they do not know. If the app's intended audience or age-related features change, this policy will be updated accordingly.

9. Changes to This Policy

We may update this Privacy Policy when Kryptode features, permissions, data practices or legal requirements change. The effective date at the top of this page will be revised when the policy is updated.

10. Contact

For privacy questions, concerns or requests relating to Kryptode, contact the developer using the details below.