Home/Privacy Policy
PRIVACY ARCHITECTURE

Privacy Policy

Our architectural commitment to minimal metadata and zero central chat archives.

Last Updated: August 2026

At Jarvis Connect, privacy is not a marketing checkbox or an optional setting. It is the fundamental technical blueprint of everything we build.

1. No Phone Numbers or Identity Tracking

Jarvis Connect does not collect, request, or store your phone number, contacts list, or government ID. You operate solely with a chosen username and your device authentication credentials.

2. Local On-Device Storage

Your conversation history is stored strictly on your physical device, protected by hardware-level AES-256 GCM encryption. No master copies or chat transcripts exist on our servers.

3. Ephemeral Delivery Queue & 7-Day Limit

When you send a message, our servers coordinate delivery with strict retention limits:

  • Online Delivery: When the recipient is actively connected, the encrypted payload is delivered instantly and no copy is kept on the server.
  • Offline Delivery: When the recipient is offline, the encrypted payload waits in a temporary queue for up to 7 days.
  • Immediate Eradication: The millisecond the recipient confirms receipt, the temporary server copy is permanently destroyed.
  • Automatic Expiry: Any message undelivered after 7 days is permanently purged from our database.

4. User Safety and UGC Controls

In compliance with App Store UGC safety standards, you have the right to block any user and report harmful messages. Reports forward only the specific message payload for review without exposing any other conversations.

5. Contact and Support

If you have questions regarding our architecture or privacy standards, reach out directly to our engineering support desk.

Architectural Guarantee

Jarvis Connect operates with zero permanent centralized message archives. Any undelivered message payload remaining on the temporary delivery queue after 7 days is automatically purged and destroyed.