This policy describes the MeshLink app and its account, licensing and support services. Store releases and the new account service are being prepared; availability will depend on the released platform and enabled features. Existing manually issued field keys use their established registration flow.
Account and licence information
When you verify your email, the account service processes your email address, a random account identifier, code-verification attempts and an expiring session. Ordinary email sign-in codes are stored as keyed digests, not as readable codes. The configured email provider receives your address and the verification email to deliver it. For a dedicated App Review account, a protected reviewer portal may deliver freshly requested sign-in codes instead of email. Those codes are additionally stored encrypted while valid. They become unavailable after use, expiry, replacement or exhausted attempts, and are removed during verification or cleanup. The same code-verification, expiry and attempt limits apply. This portal does not give reviewers access to other accounts or email inboxes.
For a purchase, we process Store product and transaction identifiers, verification evidence, plan, device-place count, entitlement dates and payment status. Google, Apple or Microsoft handles checkout and payment details. MeshLink’s account service does not receive your full payment-card number. Recoverable registration keys and saved Store verification evidence are encrypted on the service.
Devices and network participation
MeshLink uses a mesh ID, display name, cryptographic public keys, transport availability and routing information to discover and connect devices. Paid registration links a device identity and platform to an account and licence place. The app’s private identity key stays on the device in normal operation.
Presence and routing information is exchanged with connected peers and, when using Internet transport, the relay. In the new room edition, room identifiers and signed membership certificates are used to verify participation and limit admitted traffic to that room. Radio traffic can still expose transport metadata to nearby receivers. The earlier editions remain on a shared network during the transition. Relay and service operators may process connection metadata such as IP address, request time and error information to run and protect the service. New room accounts and registrations are separate from the earlier service.
Messages, contacts, maps and plans
Messages, contacts, route recordings, markers and operational plans are stored on participating devices and sent over selected mesh routes when you use those features. Delivery may involve forwarding devices, radio networks, Internet relays or mobile/satellite carriers. Directed-message encryption does not mean that all network metadata or every content type is hidden from every intermediary. Share only information you are authorised to transmit.
Location features process coordinates for maps, recording, planning and the sharing mode you select. When you share location, routes, markers or plans, the intended peers receive that information. Device permissions control location and background access; you can change permissions in system settings.
Optional device and third-party services
Depending on the platform and feature, MeshLink uses Bluetooth, attached radios or terminals, camera/photo selection, microphone/speech services, notifications, phone numbers and SMS permissions. Declining a permission may prevent its related feature. The app does not need every permission on every platform.
Online maps and elevation can send the requested map area or coordinates and your network address to the selected providers, including OpenStreetMap, Google, Esri/ArcGIS and OpenTopoData. Downloaded maps and cached terrain elevation tiles are stored on the device. Viewshed calculations process selected observer points and heights locally; downloading missing terrain sends the requested tile area and network address to the terrain provider. Speech recognition may use the operating system’s recognition service when on-device recognition is unavailable. Those providers apply their own privacy terms.
Blocking, content filtering and safety reports
Store editions provide a local blocked-user list and a basic text filter. These settings are stored on your device. The filter checks supported text locally and does not upload it for classification. Blocking suppresses the person's content on your device; it is not a network-wide ban and does not stop your device relaying encrypted traffic for other participants.
When you select Report user, the account service receives a report identifier, your verified account identifier, the reported person's MeshLink ID, the reason and the receipt time. A relevant message identifier may also be supplied. Message contents are not included unless you explicitly select Include this message; that option sends at most 2,000 Unicode characters from the selected message. It does not upload your chat history, photos, voice recordings, plans or registration keys automatically. Do not include passwords, security keys or sensitive operational information.
Reports go privately over HTTPS to MeshLink support, not to other mesh participants. Optional message details are encrypted at rest on the account service and can be read by an authorised operator for abuse review. A receipt confirms storage, not a completed review or automatic action against the reported person. Failed submissions are retained in protected app storage for the same verified account to retry or discard. Reports require Internet access; local blocking and filtering do not.
Submitted reports are retained for review and relevant abuse handling. Deleting the reporting account removes its submitted report metadata and optional encrypted content. Protected backups may retain earlier records until their backup retention ends. Contact contact@meshlink.in for safety or privacy concerns.
Website and support
These pages use no advertising trackers, analytics scripts or third-party fonts. Account-deletion authentication is kept only in page memory; this website does not put its session token into browser local storage or cookies. Hosting infrastructure necessarily processes requests and may retain security/access logs. Support email contains the information you choose to send and is handled through the support email provider.
Why information is used and shared
Information is used to operate communications, verify email and payments, recover licences, enforce device limits, prevent abuse and repeated purchase/trial claims, respond to support and comply with applicable requirements. Necessary service providers and the recipients you communicate with receive data for those purposes. This site does not use personal information for advertising.
Deletion and retention
Delete your MeshLink account here after choosing the correct edition and verifying your email. A deletion request affects only that edition’s account service. Deletion removes the account email, sessions, email/device challenges, memberships, submitted safety reports and their optional content, saved Store verification evidence and recoverable keys for licences you own. Owned licences and their devices are revoked, including devices used by other members. If you are a member of another owner’s licence, your device place remains reserved until its previously issued offline authorization ends, then can be released.
Limited pseudonymous account and Store transaction identifiers, licence state and a keyed digest used to prevent repeated free trials remain for licensing, transaction disputes and abuse prevention. These retained records do not include your readable account email or recoverable registration key. They are not automatically erased on a fixed schedule. Device identifiers in deleted Store-account bindings are anonymised. Backups may temporarily contain older records; deletion must be reapplied if a backup is restored.
Separately, the relay keeps a permanent manual-key enrolment record linking a device’s Mesh ID to the manual key’s fingerprint. Switching to a paid licence or deleting the Store account revokes the Store binding but does not remove this relay record or free its manual-key place. The record remains until the relay administrator removes it. These account actions do not themselves revoke existing field-app access under that manual key. Contact support if you want this separate record reviewed.
Deleting your account does not cancel a Store subscription, automatically refund a purchase, erase files on your devices or recall information already delivered to peers. Cancel recurring billing in the relevant Store. Offline devices may keep a previously signed authorization until it expires. Local messages, maps and exports must be removed on the devices that hold them; other recipients control their own copies.
Your choices and contact
You can choose sharing settings, manage permissions, cancel subscriptions, delete your account and contact contact@meshlink.in about access, correction or privacy concerns. Store-held payment information must also be managed with the relevant Store. We may update this policy when the app or service changes; the date above identifies this version.