UnitedLines White Paper

Executive Summary

UnitedLines is a social platform designed with privacy, user control, and transparent governance as foundational principles. Unlike social networks that monetize user attention through behavioral profiling and targeted advertising, UnitedLines implements zero behavioral tracking, no advertising, and no data resale. The platform combines Signal Protocol encryption for direct messaging, public moderation transparency, expertise verification, and nested discussion threads to enable communication at scale. Built on Next.js, TypeScript, PostgreSQL, and Drizzle ORM, UnitedLines serves users and organizations requiring social communication with privacy and accountability. This white paper describes the platform architecture, design principles, current capabilities, and strategic direction.

Problem Statement and Motivation

Dominant social platforms operate on an attention-harvesting model where user behavior, interactions, and inferred interests are continuously profiled and used for targeted content ranking and advertising. This creates structural incentives misaligned with user interests: platforms succeed when engagement is maximized, not when users benefit. User privacy is treated as a secondary concern, with behavioral data serving as the primary economic asset. Centralized moderation systems lack transparency, making it difficult for users to understand why content was removed or accounts suspended. There is no accessible record of moderation decisions, bias, or appeals outcomes.

UnitedLines addresses these issues through structural design rather than policy promises. Privacy is enforced technically through encryption and data minimization, not merely promised. Moderation is auditable through public logs. Economic incentives align with users: we succeed when users find value, not when we maximize engagement or sell attention. This requires a fundamentally different architecture and business model than incumbent platforms.

Core Principles and Design Philosophy

UnitedLines is built on these principles:

Privacy by Design: Personal data is minimized from the start. The platform does not collect IP addresses, device fingerprints, behavioral tracking, or referrer data. Encryption is the default for sensitive communications. Users control visibility of their follow lists, activity, and profile. These choices are enforced technically, not through policy.

No Tracking, No Advertising: There is no behavioral profiling, no advertising profiles, no predictive modeling of user interests, and no data resale. The platform does not use tracking pixels, third-party analytics, or advertising networks. This is a permanent structural commitment, not a temporary feature.

User Control: Users can delete accounts, request data export, block other users, mute threads, customize notification settings, and control who can message them. Administrative overrides of these controls are minimized and logged.

Transparency in Governance: All moderation actions are logged publicly with moderator identity, reasoning, and timestamps. Appeals are available for all suspensions and content removals. The transparency log enables auditing for bias and abuse.

Open Architecture: Technical specifications are published. API endpoints follow standard REST patterns. Data export is in standard formats. These choices enable third-party auditing and reduce platform lock-in.

Technical Architecture

UnitedLines backend runs on Next.js 13.5 with TypeScript. PostgreSQL serves as the primary datastore with Drizzle ORM providing type-safe database access. Frontend is built with React 18, Radix UI for accessible components, Tailwind CSS for styling, and TweetNaCl.js for client-side cryptography.

Architecture follows strict separation: authentication (JWT via secure cookies), data access authorization (per-user, per-resource validation), encryption key management (entirely client-side), and server-side abuse filtering. All database mutations include session validation and abuse score checking. API endpoints use Zod schemas for request validation.

Database schema includes: users table with account data and flags (admin, moderator, premium, shadow-banned); posts table with content, expertise claims, and scheduling support; comments table with nested reply support; direct message threads with encrypted payloads; file transfers with encrypted blob references; notifications table for mention, reply, reaction, and follow events; transparency logs for all moderation actions; and gamification tables for XP and achievements.

Rate limiting is applied per-user and per-IP based on endpoint sensitivity. Cache is implemented via Redis for session tokens and real-time notifications. Object storage (S3-compatible) is used for encrypted file uploads, user avatars, and post images. File uploads are virus-scanned before storage.

Current Platform Features

The following features are currently implemented and available to users:

User Accounts: Registration via email, username, password, optional profile picture, bio, and expertise claims. Users can set privacy flags for followers list, following list, and age visibility. Multi-factor authentication is available.

Feed and Posts: Users can create posts with text and image attachments. Posts support expertise claims and can be marked as verified. Comments are nested (replies to posts, replies to comments). Reactions are emoji-based. Posts can be scheduled for future publication. Full-screen media viewer with comment overlays for images and videos.

Direct Messaging: End-to-end encrypted direct messages between users. Users can restrict incoming DM threads to friends only. Message history is retained as long as threads exist and can be deleted by users.

Encrypted File Transfers: Users can send encrypted files in DM threads. Files are encrypted client-side before upload. Recipients download and decrypt locally. Files can be deleted or expire automatically.

Communities: Users can create and manage communities around topics. Communities have roles (admin, moderator, member). Community moderation is separate from platform moderation.

Expertise Verification: Users can claim expertise in topics (1-120 characters, user-defined). Expertise claims can be marked as verified by administrators or community moderators. Verified badges display on posts and user profiles.

Gamification: Users earn XP points through platform engagement (posts, comments, community participation). Achievements are awarded based on milestones. Leaderboards show top contributors globally and per-community.

Progressive Web App: UnitedLines can be installed as a PWA on desktop and mobile devices. PWA enables offline fallback using service worker caching of public content. Users can view previously cached posts while offline but cannot create new posts or access encrypted messages offline. The PWA includes install prompts and update notifications.

Notifications: Notifications for mentions, replies, reactions, follows, and comment responses. Users control notification preferences (email, in-app, none).

Privacy Controls: Users can block other users (bidirectional). Users can mute threads or specific users. Users can delete posts, comments, and messages. Users can request data export or account deletion.

Moderation Tools: Administrators and moderators can suspend accounts, remove content, apply shadow bans, adjust abuse scores. All actions are logged in a public transparency log with reasoning and timestamps.

Encryption and Privacy Implementation

Direct messages employ Signal Protocol encryption with the following characteristics: asymmetric Elliptic Curve Diffie-Hellman key exchange combined with AES-256-GCM authenticated encryption. Encryption keys are generated on the client device using user passwords and device-specific material. Keys are never transmitted to or stored on UnitedLines servers. Each message thread maintains unique encryption state, preventing key reuse across conversations.

The server architecture is designed to be communication-blind: encrypted message payloads are stored as-is without UnitedLines servers ever possessing decryption keys. This is a technical limitation, not a policy choice. Even if servers are compromised, law enforcement demands plaintext content, or backup systems are accessed, encrypted messages remain inaccessible because the keys exist only on user devices.

File transfers in encrypted threads use similar architecture: users exchange encryption keys via encrypted message, then upload encrypted file blobs to storage. The server stores encrypted bytes and metadata (file name, size, MIME type, timestamps) only. File content encryption keys never transit through UnitedLines infrastructure.

Metadata minimization is applied across the platform: IP addresses are not logged or profiled; device fingerprints are not generated; browsing history is not retained; referrer data is not collected; temporal access patterns are not analyzed. Public posts and comments are unencrypted but do not require encryption: moderation and spam filtering operate on plaintext, while privacy is protected through data minimization and absence of profiling.

These implementations provide strong privacy against casual surveillance and many sophisticated attacks. However, they do not provide absolute protection against determined adversaries with extreme resources or lawful access. Encryption can be broken through key extraction, side-channel attacks, or compromised endpoints. Users are responsible for securing their devices and passwords. Loss of a password means loss of access to encrypted content.

Progressive Web App Strategy

UnitedLines functions as a Progressive Web App enabling installation on desktop and mobile devices. The PWA uses service workers to enable offline fallback functionality: certain public content (posts, comments, images) is cached locally on user devices for offline viewing. This improves performance and enables access when network connectivity is unavailable.

Offline caching is limited to public content only. While offline, users can view previously cached posts and comments but cannot create new posts, post comments, or access encrypted messages. All writing and encrypted communications require network connectivity. Cache expiration is managed by browser settings and device storage capacity; the platform does not remotely manage or access user caches.

Service worker registration is local and does not communicate tracking data back to UnitedLines servers. Installation prompts and update notifications are displayed to users but do not collect data or enable profiling. Accepting or declining PWA installation and updates is user choice and does not impact privacy.

The PWA does not enable additional behavioral tracking, analytics, or profiling compared to the web experience. Privacy implementation is identical between web and PWA versions.

Moderation and Trust

Every moderation action is logged in a publicly accessible transparency log: account suspensions, content removal, shadow bans, and abuse score adjustments are recorded with moderator identity, reasoning, and timestamps. This enables community members and researchers to audit platform governance and detect bias.

Shadow banning (where posts remain visible only to the posting user) is used for coordinated abuse campaigns. The transparency log notes when a user is shadow banned and provides reasoning. Content removal decisions cite specific policy violations; moderators must provide evidence-based reasoning. Appeals are available for all suspensions and removals.

Abuse scoring is algorithmic and auditable: the platform publishes rules that trigger abuse score increments, enabling users to understand the relationship between actions and consequences. Abuse scores affect content visibility and may trigger account suspension when thresholds are exceeded.

Security Posture

UnitedLines implements security controls designed to protect user data and platform integrity: encryption in transit uses TLS; sensitive data at rest is encrypted using industry-standard methods; internal database access is restricted by role-based access control; employees and administrators require multi-factor authentication for infrastructure access; continuous security monitoring and intrusion detection systems are maintained; periodic security assessments are conducted; and security researchers are encouraged to report concerns through platform contact methods.

In the event of a security breach, UnitedLines will make reasonable efforts to notify affected users and relevant authorities within applicable legal timeframes. However, no system is immune to security risks, and we cannot guarantee absolute protection against all attacks, breaches, or unauthorized access. Users are responsible for securing their passwords and devices.

Business Model and Sustainability

UnitedLines does not monetize through user data exploitation. The revenue model aligns incentives with users: we succeed when users find value in the platform, not when we maximize engagement or sell attention.

Base platform is free for individual users. Premium tier ($8-15/month depending on region) enables: scheduled posting, feed customization, advanced analytics, community creation and management, custom verification workflows, and priority support. Enterprise licensing targets organizations (civic bodies, educational institutions, corporations) requiring self-hosted instances, custom moderation policies, audit trails, and volume discounts.

No personal data is sold, traded, licensed, or shared with advertisers or brokers. Advertising profiles and behavioral targeting are not created. This commitment is structural and permanent, independent of future ownership or financial conditions.

Regulatory Compliance Framework

UnitedLines operates as an independent entity and complies with GDPR, UK Data Protection Act 2018, and equivalent privacy regimes. GDPR compliance is built into platform architecture: user data is minimized by design, encryption prevents profiling, and user rights (access, deletion, portability, objection) are implemented through API endpoints and admin tools. Data subject access requests are fulfilled within 30 days with complete export of personally identifiable data.

Data processing agreements are implemented for enterprise customers. Subprocessors (cloud providers, CDN operators) are disclosed and contractually bound to equivalent privacy requirements. Data is retained for the minimum necessary duration: account deletion triggers purge within 90 days; moderation events are retained for 7 years to prevent re-offense; temporary operational data expires automatically.

End-to-end encryption creates specific technical constraints: UnitedLines does not retain decryption keys, cannot comply with demands for plaintext intercepts, and lacks technical capability to monitor encrypted content. This is disclosed upfront to users, regulators, and law enforcement. We cooperate with lawful legal process on metadata and account information within our technical capability; encrypted content falls outside our ability to provide.

Roadmap and Future Direction

Current Phase: Private beta with core features (messaging, posts, comments, expertise verification, transparency logs, PWA functionality).

Future Development (planned, not committed): Public launch with expanded communities, enterprise licensing, third-party integrations, expertise-weighted feed options allowing users to subscribe to expert-curated rankers, decentralized verification integrations with professional societies and educational institutions, and federation support.

Long-term Vision: Build a social platform where authority derives from voluntary credential verification and community consensus rather than engagement metrics or algorithmic ranking. This requires shifting power from platform operators to communities and enabling competing authority structures to coexist. If successful, this could demonstrate that high-trust, low-manipulation social platforms are economically sustainable and technically feasible.

Strategic Inquiries and Partnerships

Organizations interested in partnerships, enterprise licensing, investment, or acquisition discussions should contact UnitedLines through the in-platform Contact or Support feature or visit /contact. Please include: organization name, contact person, nature of inquiry (partnership, licensing, investment, acquisition, other), and any supporting materials.

No external contact information, email addresses, or phone numbers are published. All communications are directed through the platform for privacy and security.