NTsocial Privacy Policy
日本語 · 繁體中文版 · Terms & Legal Notices · Community Standards · Terms of Use
1. Scope and Controller
This Privacy Policy explains how LiberaNt LLC ("LiberaNt," "we," "us") handles information in the NTsocial mobile application, related companion features, Internet services, and the official websites at ntsocial.app and www.liber-ant.com (collectively, the "Services"). LiberaNt LLC is the controller of information it processes through its Internet services, support, safety reports, and websites. Nearby users independently receive content that you choose to transmit to them.
LiberaNt LLC30 N Gould St, Ste N
Sheridan, WY 82801, USA
Email: contact@liber-ant.com
2. Summary
- Internet and nearby communication: NTsocial uses a locally generated identity. Internet is on by default and uses Cloudflare; nearby BLE communication can work without internet.
- Your data has distinct destinations: your device keeps identity, settings, and history; online features also process data through Cloudflare, while participating peers receive and may relay eligible content.
- No advertising or cross-app tracking: the App does not add advertising or behavioral-tracking SDKs, and we do not sell personal information.
- Your choices: manage Internet in Profile, publish only intended public fields, and control optional integrations, support reports, and feedback separately. See sections 16 and 17 for Cloud and People details.
3. Information the App Handles
Depending on the platform, version, permissions, and features you use, the App may create or store the following on your device:
- a locally generated peer identity, fingerprint, cryptographic material, nickname, avatar, profile text, and optional profile location text or website;
- joined channels, channel keys, trusted or blocked peers, gateway and radio bindings, preferences, and permission state;
- public, channel, and private messages; replies; delivery receipts; images; recorded voice; files; map objects; and user-created GPX or offline-map data;
- ATaK locations and map state when you use those features;
- routing queues, fragments, retry state, attachment-transfer state, and other temporary operational records needed for mesh delivery; and
- local diagnostic and crash logs. Diagnostic bundles leave the device only when you deliberately export or share them.
Closing the App does not necessarily delete message history, attachments, keys, settings, location history, or diagnostics.
4. Peer-to-Peer Sharing
When you publish a profile, send content, join a channel, share a location, or enable a gateway, the relevant information is transmitted to nearby devices, intended recipients, channel members, or connected companion/radio systems. Other participating devices may temporarily relay packets even when their users are not the final recipients.
- Public content is public. Channel content is shared with eligible participants and should be handled according to the channel’s protection and membership settings.
- Peer identifiers, fingerprints, nicknames, profile fields, presence, and approximate radio signal information can be visible to nearby peers.
- Recipients can save, copy, screenshot, export, or forward what they receive. LiberaNt cannot remotely erase copies on other devices.
Public posts and published profile fields can be seen by Internet users beyond nearby peers. Encrypted channel content is readable by eligible members who hold the required key. Turning off Internet on one device does not recall copies held by others.
5. Private-Message Protection
- Automatic DM2: private text and images can use end-to-end protection with per-message AES-GCM keys, RSA-OAEP key wrapping, and P-256 signatures. Public identity keys are obtained through verified nearby exchanges or an authenticated Cloud directory, with first-key-wins trust. First contact does not verify someone’s real-world identity.
- Manual shared-secret E2EE: both participants may configure the same secret, using PBKDF2-HMAC-SHA256 and AES-GCM. Exchange and verify the secret through a trusted channel.
- Changed identity: a change to a pinned automatic identity blocks sending and Basic1 downgrade.
- Legacy Basic1: this nearby compatibility mode uses an app-embedded key and is not end-to-end encryption, sender authentication, or forward secrecy. Cloud private-message admission accepts automatic DM2 or manual E2EE, not Basic1.
Password-protected channels use their channel encryption. Public content remains public regardless of transport encryption. Higher-quality images use separately encrypted objects and existing message descriptors. Encryption does not prevent recipients from saving or redisclosing content.
6. Location, Bluetooth, Camera, Microphone, and Network Permissions
The App requests system permissions only for features that need them. Availability and wording vary by platform.
- Bluetooth / nearby devices: discovers peers, advertises the local mesh service, exchanges messages, and connects to supported radios or gateways.
- Local network / Wi-Fi: supports authenticated nearby high-speed history or file transfer when the feature, hardware, OS, and entitlement are available.
- Location: iOS accesses current location when you choose to update a local ATaK point. Android can periodically share location to selected ATaK channels when you enable reporting, and can use location for the optional UTFind feature described below. Location shared to a channel may be retained by its members.
- Microphone: records voice messages and push-to-talk audio when you activate those controls.
- Camera and user-selected files: scans channel QR codes and imports the images, recordings, map files, or attachments you choose.
You can deny or revoke permissions in system settings, but the related feature may stop working.
7. Safety Reports and Support
Where available, the App can prepare a safety report containing the selected reason, message ID, sender nickname and fingerprint, conversation scope, timestamp, a limited excerpt of reported content, and context you add. The report remains on the device until you review it and send it through your mail or sharing app. Sending it discloses the report and your email account information to LiberaNt and the email providers involved.
We use reports and support communications to respond to you, investigate abuse or defects, improve safety, enforce our Community Standards, protect users and the Services, and meet legal obligations.
8. Optional Integrations and Third Parties
- UTFind (Android, opt-in): In builds that include this feature, it is off by default and requires separate consent and a service key. While NTsocial is on duty, it can scan nearby FT/UT Bluetooth tags and send the tag identifier (Bluetooth MAC address), the phone's latitude and longitude, timestamp, and service credential over HTTPS to UTFind/UTTEC. Failed records are encrypted locally, limited to 5,000 records, and retried later. Turning the feature off stops new scans and deletes pending, not-yet-uploaded UTFind records. UTTEC independently controls information it receives.
- MeshLink, Meshtastic, LoRa, Wi-Fi, and LAN: If you connect a companion app, radio, hotspot, or LAN peer, content and technical routing data are provided to those selected systems and nearby participants as needed to perform the command.
- Apple and Google: App stores and operating-system services may process download, purchase, device, diagnostic, or crash information under their own terms and your platform settings. The current App does not add its own advertising or behavioral analytics SDK.
Cloudflare: provides Internet messaging, encrypted message and image storage, and Global People processing as described in sections 16 and 17.
9. Website Information
The official website stores your selected language in browser localStorage. It does not currently use advertising pixels or behavioral analytics. The website and its hosting provider necessarily receive ordinary connection information such as IP address, browser/user-agent, requested URL, time, and security logs.
If you submit the optional feedback form, we receive the fields you choose to provide, which may include product, name or nickname, email, device and OS version, App version, network state, test scenario, reproduction steps, issue description, severity, test group, contact preference, submission timestamp, and one JPG/PNG screenshot. The form sends these items through Google Apps Script to an internal Google Sheet; an attached image may be stored in Google Drive. Do not include secrets or information about another person unless authorized.
The website loads Google Fonts and links to external services such as Google Play. Those providers receive network information when their resources or pages are requested and process it under their own privacy policies.
10. Purposes and Legal Bases
Where applicable law requires a legal basis, we process information: to provide features or respond to a request; with consent for optional location, UTFind, reporting, or feedback features; for legitimate interests in security, abuse prevention, support, and product reliability; and to comply with law or protect vital rights. You may withdraw consent by disabling the feature, revoking permission, or contacting us, without affecting prior lawful processing.
11. Retention and Deletion
- On-device App data: remains until you delete individual content, use available in-App reset or panic-wipe controls, clear App storage, or uninstall. Some operating-system backups and copies held by peers may remain outside LiberaNt's control.
- Temporary mesh state: is bounded and removed as sessions end, entries expire, transfers finish, or capacity limits are reached; exact timing depends on the data type and platform.
- Pending UTFind data: follows the limits described above and is deleted from the App after confirmed upload or when you disable and purge the feature. Server-side retention is determined by UTTEC.
- Feedback, reports, and support records: are kept only while reasonably needed to resolve the request, investigate safety or security issues, prevent repeated abuse, maintain necessary business records, or satisfy legal obligations. We periodically review them and delete or de-identify them when those purposes no longer require identifiable data. A legal hold or dispute may require longer retention.
- Website language choice: remains in your browser until you clear site data.
Cloud and People: message payloads, image ciphertext, and the media index use a 30-day lifetime. People registrations are temporary memory-only records. Public identity keys and trust records are separate; see sections 16 and 17.
12. Your Choices and Privacy Rights
You may control App permissions, disable optional features, delete locally stored data using available App or operating-system controls, avoid submitting optional website fields, and ask us to access, correct, delete, restrict, or provide a copy of personal information that LiberaNt actually holds. Depending on your location, you may also have rights to object, withdraw consent, appeal a decision, or complain to a supervisory authority.
We do not sell personal information or share it for cross-context behavioral advertising. Cloud records and copies on devices have separate retention and deletion rules. We generally cannot retrieve or delete content stored only on your device or another participant’s device. Send requests to contact@liber-ant.com; we may need proportionate information to verify the request.
13. International Processing and Security
LiberaNt is based in the United States. Cloudflare, Google, email providers, UTTEC, platform providers, and people participating in a mesh may process information in other countries. Their laws may differ from yours. We use reasonable technical and organizational safeguards for information under our control, but peer-to-peer radio, the internet, third-party systems, and recipient devices cannot be guaranteed secure.
14. Children
The Services are not directed to children under 13, and we do not knowingly solicit personal information from them. If you believe a child has submitted personal information to LiberaNt, contact us so we can review and delete it as required. Users who have not reached the age required to consent in their country should use the Services only with authorization from a parent or guardian.
15. Changes and Contact
We may update this Policy as the Services or law change. We will change the date above and provide additional notice when required. Questions, safety concerns, and privacy requests may be sent to contact@liber-ant.com.
16. Internet Communication and Cloudflare
Internet is enabled by default. In Profile, you can turn it off independently of nearby Wi-Fi sync; the choice survives restart. It connects Public, eligible joined channels, private messages, and images to the Cloudflare service. Switching it off stops this device’s Cloud requests, online registration, and Internet file links, while preserving local history and existing pending Cloud jobs. Those jobs can resume when you turn it on again. Posts created while the setting is off are not automatically bulk-uploaded afterward. Other participants may retain or relay content they already received.
Cloudflare processes authenticated sessions, routing identifiers, subscriptions, receipts, synchronization cursors, and encrypted message envelopes. Message payloads, image ciphertext, and the related media index have a configured 30-day lifetime. Public identity bundles and key-pinning records are separate from temporary online presence; going offline does not delete them or reset trust.
Internet file transfers, where available and enabled, use consented WebRTC streams, optionally through TURN, instead of uploading file bodies to R2 storage. Signaling, connection metadata, and temporary relay credentials are needed. Network providers process connection information; a direct connection can expose a participant’s network address to the other participant.
Local history and downloaded files may remain after Cloud expiry. Hiding or deleting a message on your device does not delete every service record or other recipients’ copies. Infrastructure request and diagnostic logs are separate from the message and People retention described here.
17. Global People and Public Profiles
With Internet enabled, an authenticated connection registers your peer ID and public profile in Global People. Published fields can include nickname, tagline, bio, website, email, GitHub, Twitter, Instagram, text location, and avatar identifiers. Only publish information you want online users to see. Text location is entered by you, not automatic GPS reporting; avatar identifiers are not public image URLs.
The service keeps current online registrations and public profile projections in memory. It does not write People records or online history to SQL, KV, R2, or WebSocket attachments. A heartbeat is sent approximately every 60 seconds while the App can run; registration expires by 120 seconds after the last valid heartbeat or earlier when its session expires. A closed connection is removed when the service observes it. Suspended or disconnected apps may therefore remain listed briefly. Background execution is not guaranteed.
Clients keep Internet People snapshots in memory, remove expired Internet labels, and do not save these snapshots to disk. Opening a conversation or explicitly saving a contact uses separate local contact and history controls. Nearby BLE and Internet labels remain distinct. Online presence is not real-world identity verification or file-transfer consent.
People does not automatically upload GPS coordinates, scan results, Bluetooth MAC addresses, private notes, messages, private keys, or credentials. Individual People heartbeats and profile bodies are not logged by this feature; infrastructure logs and other service records are separate. Expiry is logical removal, not a guarantee of physical memory erasure at an exact instant.