Privacy by Design: Zero-Knowledge Privacy Policy

SECTION 1 PHILOSOPHY NexifyUp was engineered on an uncompromising principle: private communication is a fundamental human right. Unlike traditional cloud communication platforms that retain message archives on centralized servers to train machine-learning models or profile users for targeted advertising, NexifyUp is built on a Zero-Knowledge Architecture. This Privacy Policy applies to the NexifyUp Web application, Android native client, Unified Video Conferencing Studio, Instant Guest Calling protocol, Awake routine automation, Twin Chat, Playvertize in-call experiences, and NexifyPay/MyChama financial ledger coordination. Core Guarantee: If we are subpoenaed, audited, or physically seized, we cannot disclose your communications, video streams, or contacts because we do not possess the keys or plaintext records to read them.

SECTION 2 DATA INTEGRITY To guarantee total transparency, here is an explicit list of sensitive data categories that NexifyUp never logs, stores, transmits, or extracts: No Plaintext Messages Chats and in-call messages are encrypted before leaving your handset. No Call Recordings WebRTC audio and video streams flow directly peer-to-peer or via blind memory relays. No Private Encryption Keys Identity and prekeys reside strictly in your device's secure hardware keystore. No Ad Trackers or SDKs No Google Analytics, Meta Pixel, Adjust, or third-party behavioral profiling code.

SECTION 3 TECHNICAL TELEMETRY To route encrypted messages and initiate WebRTC handshakes between peers who may reside behind strict corporate NATs or cellular firewalls, our infrastructure briefly processes transient signaling packets: Playvertize game data: When you use Playvertize games, campaign and game identifiers, a player identifier and display name, submitted score, and submission timestamp may be sent to Playvertize for gameplay, result processing, and leaderboards. Playvertize processes this data under its own applicable privacy notice. Do not submit personal information as a game name or other optional game field unless you intend it to be shared with the game provider. WebRTC Signaling SDP & ICE Candidates: Ephemeral session descriptors exchanged via secure WebSocket/HTTP long-polling solely to negotiate direct media channels. These are erased from memory buffers immediately once connection is established. Push Notification Tokens: Anonymous FCM/APNS device tokens used solely to wake your phone when an encrypted message or Awake alarm arrives. The notification payload itself contains zero plaintext. Transient Routing Metadata: IP addresses and timestamp headers necessary for TCP/UDP packet routing. These headers are purged in rolling memory cycles and never correlated with your contact graph.

SECTION 4 VIDEO CONFERENCING & GUESTS NexifyUp's Unified Video Conferencing Studio allows instant joining via disposable call links (/join/[room_code]) without account creation or credential harvesting. Peer-to-Peer Encryption Video and audio media packets are encrypted using DTLS-SRTP. Media streams flow directly between participants whenever network topology permits. When STUN/TURN traversal is required, the TURN relay forwards raw encrypted bytes without decoding capability. Screen Sharing & Presentation Stage Screen capture display streams are transmitted solely to current room members. No recordings, frame snapshots, or optical character recognition (OCR) scans are performed on server infrastructure. In-Call Chat & Playvertize Gaming Messages exchanged in the in-call side drawer and moves made in multiplayer games (Tic-Tac-Toe, Chess, Word Quest, Brandopoly) are stored in client memory and purged instantly when the call ends.

SECTION 5 CRYPTOGRAPHY All direct communications utilize the industry-standard Double Ratchet Algorithm combined with Curve25519, AES-256-GCM, and HMAC-SHA256: Perfect Forward Secrecy: Ephemeral root and message keys cycle after every single exchanged packet. Even if a future key were ever compromised, past messages cannot be decrypted. Break-in Recovery: Compromising a single ratchet state allows the ratcheting mechanism to restore security with the subsequent Diffie-Hellman exchange. Hardware Keystore Isolation: In Android handsets, private keys reside in hardware TEE / StrongBox. In browsers, keys are handled via WebCrypto APIs and IndexedDB without plain export.

SECTION 6 NEXIFYPAY & PAYMENT PRIVACY NexifyPay provides payment initiation and transaction coordination. NexifyUp does not hold or custody funds; payments are processed by the selected mobile-money operator or other payment provider. Payment provider data: The payment provider may receive the transaction details needed to authorize, process, and settle your payment, and handles that information under its own privacy terms. Credentials: Do not share your mobile-wallet PIN, CVV, or banking credentials with NexifyUp or in chat. Enter payment credentials only in the trusted payment provider's secure prompt. Transaction records: NexifyUp may retain limited transaction references and status information to display receipts and service history. Provider transaction records remain subject to the provider's retention and privacy terms.

SECTION 7 MYCHAMA DATA & PRIVACY MyChama provides group and member services for community savings circles. MyChama is a separate provider from NexifyPay and the payment provider. Data shared with MyChama: When a user creates a circle and gives the required third-party disclosure consent, the circle name, creator/member names and phone numbers, contribution amount, and membership details needed to provision the circle may be sent to MyChama. NexifyUp also stores circle and member records in Pulse to provide the feature. Group visibility: Circle members may see group details, contribution status, and payout schedules needed to participate. Group information is available to authorized circle participants. Provider privacy terms: MyChama handles information it receives under its own applicable privacy notice. This NexifyUp Policy describes NexifyUp's handling and does not replace MyChama's notice.

SECTION 8 ROUTINES & ALARMS Awake accountability alarms and Twin Chat shared spaces are designed to bridge physical distance without infringing on behavioral privacy: Local Alarm Execution: Alarm schedules and physical wake-up audio triggers execute via native device alarm managers (Android AlarmManager / Web Audio APIs). Zero Sleep Tracking: We do not monitor your sleep patterns, biometric sensors, or bedside ambient noise. Twin Chat Vaults: Shared files and memories within Twin Chat spaces are stored with split-key encryption accessible solely by the two paired accounts.

SECTION 9 GUARDIAN PROTECTION For underage family members utilizing ChildUse mode, privacy is preserved through cryptographic parental governance rather than third-party surveillance: Emergency SOS beacons and location check-ins are encrypted directly with the designated parent/guardian node's public key. NexifyUp engineers, ISP relays, and law enforcement cannot decipher ChildUse locations or contact permissions without the parent device key. Child accounts are immune to external search indexing, public room discovery, and unapproved contact requests.

SECTION 10 DATA RETENTION NexifyUp enforces deterministic ephemeral lifecycles across transient features: Feature Category Retention Policy Foots (Stories & Status) Purged at exactly 24:00:00 mark In-Call Video & Chat 0 server storage • Erased at call termination Undelivered Messages Purged after 14 days maximum queue WebRTC Session Tokens Erased within 300 seconds of close

SECTION 11 CLIENT STORAGE NexifyUp does not use advertising cookies or cross-site tracking identifiers. We utilize local browser storage strictly for essential platform functionality: IndexedDB / LocalStorage: Used to store your encrypted message history, contact cache, room preferences, and identity key fragments locally on your device. Theme & Audio Settings: Caches whether your system prefers dark/light mode and selected microphone/speaker devices. Zero Third-Party Cookies: No ad networks, social media widgets, or tracking pixels are ever embedded into NexifyUp web pages or applications.

SECTION 12 GLOBAL COMPLIANCE Regardless of your citizenship or geographic location, NexifyUp affords all users the highest standard of international data protection rights: Right to Erasure (Forget Me) Clear your local cryptographic keys or request server routing token purging with one click. Right to Portability Export your local encrypted message vault anytime to an offline backup archive. Kenya Data Protection Act 2019 Compliant with Office of the Data Protection Commissioner (ODPC) data minimization principles. EU GDPR & California CCPA Zero personal data sale, strict purpose limitation, and absolute user consent sovereignty.

SECTION 13 SECURITY & CONTACT NexifyUp welcomes independent cryptographic verification, penetration testing, and ethical security inquiries. If you have questions regarding our zero-knowledge implementation or wish to submit an audit report: Data Protection Officer: [email protected] Copy Email Response SLA: Within 48 business hours for all cryptographic & privacy inquiries. Last Revised: October 20, {{ "now"|date("Y") }} • Version 4.0 • Canonical Zero-Knowledge Security Policy