Seenly

Welcome to Seenly Social

Explore privacy-first short form clips, trending videos, and secure messaging.

Top Creators

Trending Clips

Platform Documentation & Architecture

🛡️ Seenly Social — Privacy Charter & Policy


Seenly Social is engineered around a fundamental commitment: Privacy by Design.
---

1. What We Never Do


- ❌ No Advertising Profiles: We do not track your activity across the web or build behavioural ad profiles. - ❌ No Chat Scanning: Private 1:1 messages are end-to-end encrypted. We cannot read your conversations even if compelled. - ❌ No Data Selling: We will never sell, rent, or monetize your personal information to third-party data brokers. - ❌ No Unnecessary Location Tracking: We do not harvest real-time GPS coordinates.
---

2. Data We Collect & Why


We only collect minimal operational data necessary to deliver the service:
| Category | Data Points | Purpose | | :--- | :--- | :--- | | Account Info | Username, Display Name, Email/Phone | Account identification and authentication | | Public Content | Uploaded Clips, Captions, Comments, Likes | Public discovery and social feed display | | Encrypted Transit | Ephemeral Ciphertext & Public Keys | Routing encrypted messages between recipients | | Operational Metrics| Aggregate view velocity, crash logs | Platform stability and trending calculation |
---

3. User Data Sovereignty & Rights


Every Seenly user possesses total control over their data:
- Data Export: Download a full machine-readable JSON copy of your profile and uploaded content at any time. - Right to Erasure (Account Deletion): Permanently delete your account, posts, clips, and associated metadata from our servers with one click in Settings.
---

4. Lawful Compliance Framework


Seenly complies strictly with applicable privacy laws (GDPR, CCPA) and valid legal processes. Because of our Zero-Knowledge E2EE architecture, we cannot produce plaintext contents of private encrypted messages because we do not possess the decryption keys.

🔐 Seenly Social — End-to-End Encryption (E2EE) Specification


Seenly's messaging subsystem is built with True End-to-End Encryption (E2EE)* using standard, audited cryptographic algorithms via the browser's native *WebCrypto API (`window.crypto.subtle`).
---

1. Cryptographic Principles & Guarantees


- Zero Server Knowledge: Plaintext messages and private encryption keys never touch the Seenly server memory, disk, or logs. - No Backdoors: There are no master keys, admin decryption tokens, or developer escrow mechanisms. - Standardized Cryptography: Zero custom or home-brewed ciphers. All operations utilize standard W3C WebCrypto API primitives.
---

2. Cryptographic Primitives


| Component | Specification | | :--- | :--- | | Asymmetric Key Agreement | ECDH (Elliptic Curve Diffie-Hellman) | | Curve | NIST P-256 (secp256r1) | | Symmetric Cipher | AES-GCM (Galois/Counter Mode) | | Key Length | 256-bit | | Initialization Vector (IV) | 96-bit (12 bytes) cryptographically random per message | | Key Serialization | SPKI (SubjectPublicKeyInfo) Base64 |
---

3. Key Exchange & Message Flow


``` Alice (Device A) Bob (Device B) │ │ ├── 1. Generate ECDH KeyPair (P-256) │ ├── 2. Export Alice Public Key (SPKI) │ │ │ │─────────────── 3. Transmit Public Key ───────────────►│ │ │ │ ├── 4. Generate ECDH KeyPair (P-256) │ ├── 5. Derive Shared AES-256 Key │◄────────────── 6. Transmit Bob Public Key ────────────┤ │ │ ├── 7. Derive Shared AES-256 Key │ │ │ ═══════════════════ SECURE ENCRYPTED CHANNEL ESTABLISHED ═══════════════════ │ │ ├── 8. Encrypt(Plaintext, SharedKey, RandomIV) │ │ │ │────────────── 9. Relay Ciphertext + IV ──────────────►│ │ │ │ ├── 10. Decrypt(Ciphertext, SharedKey, IV) ```
---

4. Key Management & Storage


- Private Keys: Stored exclusively in local device memory or client-side storage (`IndexedDB` / `localStorage`). - Shared Secret Derivation: Both devices independently compute the identical 256-bit AES-GCM key from their respective private key and the peer's public key. - Ciphertext Format: `[12-byte IV] + [AES-GCM Ciphertext + 16-byte Auth Tag]` encoded in standard Base64.
---

5. Public Clip Sharing Architecture


When a user shares a public Clip within an encrypted chat: 1. The client constructs a structured reference card: `[SHARED_POST:{"id":"clip_123","is_reel":true}]`. 2. The reference string is encrypted using the shared AES-GCM key. 3. The recipient decrypts the payload and renders a live interactive card linked to the original Clip ID. 4. Result: Zero video duplicating, preserving bandwidth and cryptographic integrity.

🚨 Seenly Social — Security Policy & Guidelines


Security is foundational to the Seenly ecosystem. We welcome responsible disclosure from security researchers and the open-source community.
---

1. Supported Versions


| Version | Supported | | :--- | :--- | | v1.0.x (Current) | ✅ Supported | | < v1.0 | ❌ End of Life |
---

2. Reporting a Vulnerability


If you discover a security vulnerability within Seenly Social, please follow these steps:
1. Do not create a public GitHub issue. 2. Send a detailed report to our security team at: security@seenly.social (or via GitHub Private Vulnerability Reporting). 3. Include: - Description of the vulnerability. - Proof of Concept (PoC) or reproduction steps. - Potential impact assessment. 4. We acknowledge all reports within 24 hours and will provide regular status updates until resolution.
---

3. Security Hardening Measures


- Content Security Policy (CSP): Strict resource limits preventing unauthorized script injection. - Cross-Site Scripting (XSS): Strict React DOM sanitization and no `eval()` execution. - Cross-Origin Resource Sharing (CORS): Restricted to authorized Seenly domains. - Rate Limiting: Applied to all authentication, upload, and API endpoints. - HTTPS & TLS: Enforced across all web and WebSocket communication channels.

🏛️ Seenly Social — Architecture Specification


This document details the high-level architecture, module decomposition, and data pipelines powering Seenly Social.
---

1. High-Level System Architecture


Seenly employs a decoupled, privacy-first client-server model: - Client Layer: Single Page Application (SPA) built on React 18, Vite 6, and Tailwind CSS. Packaged as a Progressive Web App (PWA) and native Android application via Capacitor 8. - Relay & Backend Layer: Express.js and Go WebSocket relay servers providing zero-knowledge transit for encrypted communication. - Database & Storage Layer: Cloudflare R2 object storage for media CDN, Appwrite for identity & session synchronization, and MongoDB for public indexing.
``` ┌────────────────────────────────────────────────────────────────────────┐ │ SEENLY CLIENT (REACT 18) │ ├─────────────────┬──────────────────┬─────────────────┬─────────────────┤ │ Home & Trending│ Clips Viewer │ E2EE Chat │ Creator Profile│ ├─────────────────┴──────────────────┴─────────────────┴─────────────────┤ │ WebCrypto Security Engine (ECDH) │ ├────────────────────────────────────────────────────────────────────────┤ │ Appwrite & Socket.IO Client │ └──────────────────────────────────┬─────────────────────────────────────┘ │ HTTPS / WSS ▼ ┌────────────────────────────────────────────────────────────────────────┐ │ SEENLY ZERO-KNOWLEDGE RELAY SERVER │ ├──────────────────────────────────┬─────────────────────────────────────┤ │ Zero-Plaintext Message Relay │ Trending Velocity Calculator │ └─────────────────┬────────────────┴──────────────────┬──────────────────┘ │ │ ▼ ▼ ┌───────────────────┐ ┌───────────────────┐ │ Cloudflare R2 │ │ Database Layer │ │ (Fast Media CDN) │ │(Appwrite / Mongo) │ └───────────────────┘ └───────────────────┘ ```
---

2. Core Subsystems


2.1 Trending Clips Engine (24-Hour Velocity)

Trending Clips are calculated dynamically on the server and client using real-time engagement velocity:
$\text{Trending Score} = \frac{(\text{views} \times 1.0) + (\text{likes} \times 2.5) + (\text{comments} \times 3.5) + (\text{shares} \times 5.0)}{(\text{hoursSinceUpload} + 2)^{1.5}}$
- Dynamic Lifespan: Each clip is assigned a `trending_started_at` and `trending_expires_at` (24-hour duration). - No Stories: Ephemeral status updates are deprecated. Ephemeral discovery is powered strictly by trending public Clips.

2.2 End-to-End Encryption (E2EE) Messaging Subsystem

- Key Negotiation: ECDH over curve P-256 via browser `window.crypto.subtle`. - Cipher Suite: AES-GCM with 256-bit key length and unique 12-byte initialization vectors (IV) per message. - Clip Sharing Reference: Clips shared within chats are passed as referenced metadata payloads (`[SHARED_POST:{"id":"..."}]`), eliminating video duplication.

2.3 Media Delivery & Preloading

- Video assets are stored on Cloudflare R2 and distributed over a global edge CDN. - Multi-tier preloading: - Active Clip: 100% full stream buffering with hardware decode. - Next 2 Clips: Metadata and first 3 seconds buffer preload.
---

3. Directory Layout


``` seenly-social/ ├── android/ # Native Android Capacitor workspace ├── public/ # Public assets, sitemap.xml, robots.txt ├── server/ # Express & Node.js backend relay ├── src/ │ ├── assets/ # Brand SVG & HD PNG assets │ ├── components/ # UI components & Views │ │ ├── PixelPerfectSocialApp.jsx # Main App layout & tab router │ │ ├── ReelsViewer.jsx # Vertical video clips viewer │ │ ├── ChatMessenger.jsx # E2EE chat & clip sharing │ │ ├── ProfileDashboard.jsx # Creator profile & grid │ │ ├── SeenlyCreateStudio.jsx # Clip recording & creation │ │ ├── FirebaseLogin.jsx # Authentication module │ │ └── cryptoHelper.js # WebCrypto E2EE library │ ├── hooks/ # Custom React hooks (native, network) │ ├── store/ # Zustand state management │ └── utils/ # Appwrite client, analytics, media resolvers ```

GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007
Copyright (C) 2026 Microbytes / Seenly Social.
This license applies exclusively to the open-source client codebase provided in this repository. It DOES NOT apply to the proprietary backend systems, algorithms, databases, or API infrastructure powering the Seenly Social network.
By using or modifying this client, you agree that: 1. You may freely use, modify, and distribute this client code under the terms of the GPL-3.0. 2. The core backend services, matchmaking algorithms, content delivery networks, and databases are PROPRIETARY and remain the intellectual property of Microbytes. 3. This client is designed to interface exclusively with the official Seenly infrastructure. Unauthorized attempts to reverse-engineer the backend API or use this client to attack the official servers are strictly prohibited.