Audio by arcologies
< RETURN TO TERMINAL

NVSBL - Terms of Service

Last Updated: August 18, 2026

1. What NVSBL Is

NVSBL is a privacy-first communications terminal built for people who want more control over identity, communication, local data, and what happens when a secure relationship ends.

Instead of requiring another person to know your phone number, email address, or public social profile, NVSBL lets users establish private relationships through pseudonymous Mesh IDs. Within that relationship, NVSBL provides encrypted messaging, protected file transfer, voice/video communication, local Vault storage, and optional data-destruction controls.

NVSBL is built around a simple idea: privacy should not end when a message is encrypted in transit. Users should also have meaningful control over identity exposure, local storage, sensitive files, compromised contacts, lost devices, and unwanted persistence.

2. Mesh Identity & Secure Relationships

Ordinary NVSBL use does not require a conventional account built around a real name, phone number, or email address. The application uses a pseudonymous Mesh identity and an anonymous backend authentication identity to operate network features.

  • Mesh IDs: A Mesh ID is the identifier another NVSBL user can use to establish a secure relationship with your terminal.
  • Operator Alias: Users may assign aliases to make private contacts recognizable locally. Aliases are not verified real-world identities.
  • Public-key exchange: Secure relationships are established deliberately rather than through public discovery, follower systems, or random stranger matching.

3. Local Credentials & Recovery

NVSBL uses local credentials to protect the encrypted terminal.

  • Quick Access PIN: A convenience credential used for ordinary local unlocking.
  • 12-word Master Phrase: A stronger recovery credential intended to remain under the user's control.
  • No guaranteed recovery: If required credentials and cryptographic material are lost or permanently destroyed, NVSBL may be unable to recover locally encrypted data.

4. Privacy Controls & Intentional Data Destruction

NVSBL includes optional features designed for situations in which the user no longer wants sensitive data, a relationship, or an entire terminal identity to persist.

  • Incinerator: Applies a short retention lifecycle to qualifying messages.
  • Dead Drop: Provides a one-time protected transfer path for supported payloads.
  • Deep Lock: Removes ordinary quick-access behavior and forces the stronger recovery path configured by the user.
  • RipWire: An optional dead-man's-switch style control that may initiate the destructive terminal workflow when its configured conditions are met.
  • Ghost Wipe / Terminal Decommission: A deliberate full wipe is designed to remove the initiating terminal's NVSBL identity, associated backend records, and locally stored NVSBL application data and cryptographic material accessible to the app.
  • Contact severing: A protected sever instruction may remove a shared NVSBL relationship, conversation data, and session material on participating terminals.
  • Decoy controls: Configured decoy interface elements may intentionally trigger a destructive security action.

These features are powerful by design and may cause irreversible data loss. NVSBL does not claim that an application can forensically erase every operating-system cache, physical storage location, backup, provider log, or memory location outside its control.

5. Communications Features

NVSBL supports encrypted private communications between established Mesh contacts.

  • Messaging: Ordinary message content is encrypted before protected server delivery.
  • Attachments: Supported files are encrypted locally and delivered through restricted storage workflows.
  • Vault: Sensitive files may be stored locally inside the encrypted NVSBL environment.
  • Voice and video: Calls use encrypted WebRTC transport and supported native iOS call behavior.

6. User Safety, Reporting & Blocking

NVSBL is designed for private communication, not public broadcasting or random stranger matching. Users can block Mesh identities and may deliberately submit selected evidence through REPORT & BLOCK.

A user-initiated report is an intentional exception to ordinary message confidentiality. The reporting user may choose to disclose the selected message or report evidence to NVSBL for moderation, safety, abuse-prevention, and enforcement.

7. Acceptable Use

NVSBL is intended for lawful private communication. You agree not to use the service to:

  • Violate applicable law.
  • Transmit unlawful, exploitative, non-consensual, or abusive material.
  • Distribute malware or intentionally exploit NVSBL infrastructure.
  • Automate spam, denial-of-service activity, credential attacks, or abusive traffic.
  • Bypass security, moderation, purchase, rate-limit, or access-control systems.

8. Purchases & Network Entitlements

Certain digital NVSBL features or periods of network access may be offered through Apple In-App Purchase on iOS. RevenueCat is used to assist with purchase and entitlement management.

  • Apple billing: Apple processes iOS payments under Apple's billing, tax, refund, and App Store policies.
  • RevenueCat: RevenueCat may process a pseudonymous NVSBL account identifier, product identifiers, transaction information, and entitlement status needed to provide purchase functionality.
  • No full card storage: NVSBL does not receive or store the user's complete payment-card number from Apple.

9. Third-Party Infrastructure

NVSBL depends on third-party providers to deliver an internet-connected mobile communications service.

  • Supabase: Pseudonymous authentication, database/realtime operations, protected server functions, signaling, and selected storage workflows.
  • OneSignal: Push-notification delivery using device tokens and pseudonymous notification identifiers.
  • Apple / RevenueCat: iOS purchases and entitlement management.
  • WebRTC connectivity services: STUN, TURN, or similar connectivity infrastructure may process IP addresses and connection metadata when establishing calls.

10. Security Boundaries

NVSBL uses modern cryptographic and access-control techniques intended to reduce privacy and security risk. No software can guarantee complete security, uninterrupted service, anonymity against every adversary, or protection from a fully compromised device.

A malicious recipient can still copy content they legitimately receive. Network metadata may exist even when message content is encrypted. A compromised or jailbroken operating system may undermine application-level protections.

11. Availability & Changes

Features may change, be improved, be suspended, or be removed to address security, reliability, compatibility, provider, or legal requirements. Network services can also be affected by maintenance, third-party outages, operating-system behavior, or connectivity conditions.

12. Limitation of Liability

To the maximum extent permitted by applicable law, NVSBL and its independent creators are not liable for indirect, incidental, special, consequential, or punitive damages arising from use of or inability to use the service, including loss of encrypted data, loss of access, destructive security actions, service interruption, device compromise, or third-party infrastructure failures.

Nothing in these Terms excludes rights or remedies that cannot lawfully be excluded.

13. Privacy

Use of NVSBL is also governed by the NVSBL Privacy Policy, which explains what information NVSBL and its service providers process, how end-to-end encrypted content is handled, how reporting works, and how permanent Mesh / terminal deletion operates.

14. Contact

Questions about these Terms, safety, or NVSBL may be sent to:
support@nvsbl.app