← Back to Home

Product Privacy Policy

Effective Date: October 17, 2026 • Published by: Cymbidium Labs LLC • Version 1.1 (Zero-Data Privacy Architecture)

1. Fundamental Architecture & Core Philosophy

Meridami is built upon a simple principle: what we do not collect, we cannot lose, leak, or sell. We operate under a strict Zero-Data-Collection privacy model. Unlike traditional social platforms that centralize and monetize your contact networks, Meridami uses client-side End-to-End Encryption (E2EE) and hardware-backed local device storage.

2. Data We Do NOT Collect

The cloud relay (api.meridami.com) does not store:

  • No Plaintext Friend Lists: Your friends and contacts are encrypted with your device vault key before any multi-device sync message is transmitted.
  • No Real Names or Personal Notes: Real names, Discord handles, and personal notes are never sent in plaintext to our servers.
  • No Location Coordinates or GPS Tracking: Meridami operates purely on general IANA timezone identifiers (e.g., Asia/Tokyo) to compute relative hours, never raw GPS or IP geolocation tracking.
  • No Voice or Chat Content: Meridami does not record, intercept, or monitor any voice channel audio or Discord message content.
  • No Persistent Browser Storage: In browser and Web Document PiP environments, session keys and decrypted friend cards reside strictly in volatile RAM memory and are never persisted to unencrypted browser localStorage.

3. Data We Process Operatively & How It Is Protected

A. Client-Side Cryptographic Vaults

Your personal cards and settings are encrypted using AES-256-GCM AEAD with keys derived locally on your device via PBKDF2 or Curve25519/X25519 key agreements. In native mobile environments, keys are secured in hardware-isolated secure storage (Apple Keychain on iOS/macOS and Android KeyStore).

B. Encrypted Cloud Sync Blobs

If you choose to enable multi-device sync or remote backups, our servers store strictly scrambled, opaque binary ciphertext blobs. Decryption keys never touch our servers, making it mathematically impossible for Cymbidium Labs LLC or any third party to decrypt your vault data.

C. Technical & Operational Metadata

To deliver voice notifications and synchronize presence between your desktop and mobile devices, our relay processes minimal technical metadata:

  • Opaque Push Tokens: Ephemeral APNs (Apple) or FCM (Google) device tokens used strictly to deliver wake triggers. Push payloads contain only opaque slot IDs with zero names or cities.
  • Hashed Discord Identifiers: One-way SHA-256 snowflake hashes used for blind indexing of presence routes.
  • Ephemeral Presence Heartbeats: Desktop activity pings valid for 180 seconds to suppress mobile notifications while you are active at your computer.
  • Standard Edge Server Logs: Standard HTTP connection logs (IP address, user agent, timestamps) collected by Cloudflare and Google Cloud Run strictly for DDoS mitigation, rate limiting, and security compliance.

D. Native Mobile Contacts Import

When using our optional native contacts import feature on iOS (CNContactStore) or Android (ContactsContract), contact records are parsed and mapped 100% on-device into your local private vault. Zero names, phone numbers, email addresses, or postal addresses are ever transmitted to any remote server or cloud relay.

E. Automatic Silence with Strangers

When participating in public or shared voice channels, Meridami automatically checks participant IDs against your local decrypted vault. If no friends from your list are active in the channel, the HUD automatically remains hidden and collapsed to zero pixels, preventing any exposure of strangers' names or presence.

F. Privacy-Preserving Diagnostic & Reliability Telemetry (Opt-Out)

To monitor system health, detect relay regressions, and calculate the desktop push notification suppression efficiency ratio (minimizing redundant phone battery drain while at your PC), Meridami collects minimal, strictly anonymized operational telemetry under rigorous architectural guardrails:

  • Strict Whitelist of Permitted Parameters: Outbound telemetry is restricted to an immutable client-side whitelist (ALLOWED_TELEMETRY_KEYS) covering non-identifying operational counters and performance flags (such as suppressionRatio, desktopActive, pushDispatched, isNative, mode, status, and errorCode). Any unwhitelisted parameters are dropped on-device before transmission.
  • Zero Social Graph Invariant: The telemetry pipeline never collects, stores, or logs Discord usernames, 17–20 digit Discord snowflakes, voice channel IDs, guild names, friend lists, private notes, or birthdays.
  • Automated On-Device Redaction: Before any telemetry packet escapes the device, an automated privacy sanitizer runs cryptographic entropy and regex scans to strip 64-character hex private keys, API secrets, and sensitive URL query tokens.
  • Local Delta Throttling: Identical operational status snapshots are fingerprinted and throttled on-device, eliminating redundant network pings and reporting only meaningful state changes.
  • Complete User Opt-Out Control: Telemetry is optional. Users can disable all operational diagnostics at any time in application settings (setting isTelemetryEnabled = false). When toggled off, all client telemetry dispatches, local event buffers, and diagnostic metrics are completely halted.

4. Data Retention & Automatic Expiration

Temporary relay drops and single-use invite links stored in our cloud relay are automatically and permanently purged upon expiration (72 hours for temporary drops; 7 days for claim invites).

5. User Rights, Data Control & Deletion (GDPR & CCPA)

Because all personal records are stored strictly on-device in your local encrypted vault:

  • Full Data Erasure: Clearing app data on your device or clicking "Reset Vault" in settings instantly and permanently deletes your encryption keys and all friend records.
  • Remote Sync Purge: You may request the immediate deletion of your blind snapshot blob from the cloud ledger at any time via in-app settings.
  • Statutory Rights: Users in the European Economic Area (EEA), United Kingdom, and California enjoy rights of access, portability, and deletion under GDPR, CCPA, and CPRA. Since we store zero plaintext personal identifiers, requests are fulfilled via your client vault credentials.

6. Children's Privacy Protection (COPPA)

Meridami is not directed at or designed for children under the age of 13. We do not knowingly collect or solicit personal information from children under 13. If you believe a child has provided us with personal data, please contact us immediately.

7. Contact & Corporate Information

Meridami is developed, maintained, and operated by:

Cymbidium Labs LLC
A subsidiary of Cymbidium Holdings LLC (Wyoming Filing ID: 2026-002068368)
30 N Gould St, Ste N, Sheridan, WY 82801
Developer Inquiries: developer@cymbidiumlabs.com
Administrative Inquiries: admin@cymbidiumlabs.com