Privacy Policy

Data Controller and Contact Information

UnitedLines Ltd is the data controller responsible for processing your personal data. The platform operates at UnitedLines.co.uk and UnitedLines.uk. For privacy inquiries, data subject access requests, or to exercise your privacy rights, contact methods will be provided inside the platform only.

What Personal Data We Collect

We collect the following personal data only to the extent necessary to provide the Service: (a) Account Information: username, email address, optional password hash, profile picture, bio, and expertise claims; (b) Authentication Data: session tokens, login timestamps, and devices where you access the Service; (c) Content You Create: posts, comments, messages, file uploads, reactions, and other content you author; (d) Communication Data: direct message content (encrypted end-to-end and unreadable by us), recipient identity, and message timestamps; (e) Community Participation: communities you join, roles you hold, and moderation actions you take as a moderator; (f) Explicit Preferences: notification settings, privacy settings, follow/block relationships, and content filters you configure; (g) Verification Data: if you voluntarily claim expertise, we may request supporting credentials (certificates, publications, institutional affiliations); (h) Technical Information: browser type, device model, operating system version, and application version (collected passively only as necessary for support and security).

What Personal Data We Do NOT Collect

UnitedLines explicitly does not collect: (a) IP Addresses: we do not log, store, or process IP addresses for profiling or tracking purposes; (b) Device Fingerprints: we do not generate or store unique device identifiers, device fingerprints, or hardware serial numbers for tracking users across sessions; (c) Behavioral Tracking: we do not track page views, link clicks, time spent on features, scroll depth, or mouse movement patterns; (d) Referrer Data: we do not collect or store HTTP referrer information to understand where users came from; (e) Cookies for Tracking: we only use session cookies for authentication (one secure httpOnly cookie); we do not use third-party tracking cookies or pixels; (f) Search History: we do not retain records of searches you perform on the Service; (g) Contact Lists: we do not access, upload, or process your phone contacts, email contacts, or social media connections; (h) Biometric Data: we do not collect facial recognition, fingerprints, iris scans, or other biometric identifiers; (i) Location Data: we do not collect GPS coordinates, cell tower location, or IP-based geolocation; (j) Ad Profiling: we do not build advertising profiles, behavioral interest categories, or predictive segments based on your activity; (k) Encrypted Message Content: end-to-end encrypted messages are stored encrypted; we have no technical capacity to read or process plaintext content.

End-to-End Encryption and Server Blindness

Direct messages in encrypted threads use Signal Protocol encryption. Encryption keys are generated on your device using your password and are never transmitted to or stored on UnitedLines servers. This creates server blindness: UnitedLines servers receive encrypted message blobs but cannot decrypt them without your encryption key. Even if UnitedLines servers were hacked, law enforcement accessed our infrastructure, or a data breach occurred, encrypted message content would remain inaccessible because the keys are not stored anywhere we control. Your encryption key is derived from your password; if you lose your password and do not have a backup, the key is lost and messages cannot be recovered even by us.

Encrypted File Transfer Architecture

File transfers in encrypted threads use zero-knowledge architecture: you select a file, your device generates an AES-256 encryption key, encrypts the file locally, and uploads the encrypted blob to cloud storage. The encryption key is transmitted only to the intended recipient via encrypted direct message. UnitedLines servers store only encrypted file blobs and metadata (file name, size, MIME type, upload timestamp, recipient identity). We have no capability to decrypt files and cannot access file content even if requested by law enforcement. Users are responsible for managing encryption keys; if a key is lost, the file cannot be decrypted.

How We Use Your Personal Data

We use personal data only for these purposes: (a) Service Provision: to store your account, display your profile, deliver your messages, and provide core platform functionality; (b) Authentication and Security: to verify your identity, prevent account takeover, detect and prevent abuse or unauthorized access; (c) Communications: to send administrative messages (password reset, account verification, policy updates) and respond to your support inquiries; (d) Moderation and Enforcement: to detect policy violations, enforce our Terms of Service, and maintain community standards; (e) Legal Compliance: to comply with applicable law, respond to lawful legal process, and prevent illegal activity; (f) Service Improvement: to fix bugs, optimize performance, and develop new features (only using aggregated, anonymized usage patterns where possible); (g) Transparency Logging: to record moderation actions in our public transparency log for accountability and auditing.

We explicitly do NOT use your data for: (a) advertising targeting; (b) behavioral profiling; (c) predictive analytics about your preferences; (d) selling or licensing your data to third parties; (e) training machine learning models on your personal data; (f) creating shadow profiles for advertising purposes.

Lawful Basis for Processing (GDPR)

Under GDPR Article 6, we process personal data under these lawful bases: (a) Contract (Article 6(1)(b)): processing necessary to perform our contract with you to provide the Service; (b) Legal Obligation (Article 6(1)(c)): processing required by law (e.g., fraud prevention, child safety, law enforcement cooperation); (c) Legitimate Interests (Article 6(1)(f)): protecting platform security, preventing abuse, and maintaining service integrity where such interests are not overridden by your privacy interests; (d) Consent (Article 6(1)(a)): for optional features like expertise verification or analytics opt-in (you may withdraw consent at any time).

Data Retention Periods

We retain personal data for the minimum duration necessary: (a) Account Data: retained for the duration of your account; deleted within 90 days of account deletion; (b) Message Content: retained as long as the conversation thread exists; deleted when you delete messages or archive threads; (c) Moderation Log Entries: retained for 7 years to prevent re-offense and for legal compliance; (d) Session Tokens: automatically expire after 30 days of inactivity; (e) Temporary Data: rate limit counters, CSRF tokens, and password reset links expire after 24 hours; (f) Legal Holds: if we receive a lawful legal hold or preservation notice, we retain data for the duration specified by law.

Your Privacy Rights and Choices

Under GDPR and UK Data Protection Act, you have the right to: (a) Access: request a copy of all personal data we hold about you in a portable, machine-readable format (right to data portability). We respond within 30 days; (b) Rectification: correct inaccurate or incomplete personal data. You can edit account information directly in settings or contact us for assistance; (c) Erasure (Right to be Forgotten): request deletion of your personal data, subject to legal retention requirements. Deletion is automatic upon account deletion; (d) Restriction: request that we limit processing of your data (e.g., suspend processing pending resolution of a dispute); (e) Objection: object to processing of your data for direct marketing (we do not do direct marketing). Object to processing on legitimate interests grounds; (f) Withdrawal of Consent: if processing is based on consent, you may withdraw consent at any time in account settings.

To exercise any right, use the contact methods provided inside the platform only. We will respond to all requests within 30 days. We do not charge fees for reasonable requests. If you believe your privacy rights have been violated, you have the right to lodge a complaint with your national data protection authority.

International Data Transfers

UnitedLines Ltd is incorporated in the United Kingdom. Personal data is primarily stored in UK and EU data centers. If we transfer data to countries outside the UK or EU (e.g., for cloud infrastructure), we ensure appropriate legal mechanisms are in place, including data processing agreements containing Standard Contractual Clauses or your explicit consent. We conduct Data Protection Impact Assessments before any international transfers. You have the right to request details of any international transfers of your data.

Third Party Data Processors

UnitedLines uses third-party service providers only where necessary: (a) Cloud Infrastructure: Amazon Web Services, Google Cloud, or equivalent for data storage and compute (all processors are bound by data processing agreements); (b) Email Delivery: SendGrid or equivalent for transactional emails (password resets, notifications); (c) Monitoring: Sentry or equivalent for error logging and performance monitoring (we do not send personal data to these services); (d) Payment Processing: Stripe for subscription processing (PCI-DSS compliant); (e) Analytics: Plausible Analytics or Fathom Analytics for aggregate, privacy-respecting usage statistics (no personal data is sent; these services do not use cookies for tracking). All subprocessors are contractually bound to equivalent privacy and security requirements. You have the right to request a complete list of subprocessors.

Security and Data Protection Measures

UnitedLines implements comprehensive security controls: (a) Encryption in Transit: all data transmitted to/from the Service uses TLS 1.3 encryption; (b) Encryption at Rest: sensitive data (passwords, session tokens) are encrypted using AES-256 at rest in the database; (c) Access Controls: internal database access is restricted by role-based access control; (d) Authentication: employees require multi-factor authentication for infrastructure access; (e) Monitoring: continuous security monitoring, intrusion detection, and anomaly alerting; (f) Penetration Testing: annual security audits and penetration testing by third-party security firms; (g) Vulnerability Disclosure: responsible disclosure program; security researchers can report vulnerabilities through platform contact methods; (h) Incident Response: in the event of a data breach, we will notify affected users and relevant authorities within legally required timeframes.

Cookies and Tracking Technologies

UnitedLines uses only essential cookies: (a) Session Cookie (ul_session): secure, httpOnly, SameSite=Strict cookie containing your session token. This cookie is deleted automatically upon logout or 30 days of inactivity; (b) CSRF Protection: temporary tokens prevent cross-site request forgery attacks; (c) No Third-Party Tracking: we do not use Google Analytics, Facebook Pixel, or other third-party tracking services; (d) No Advertising Pixels: we do not embed tracking pixels from ad networks; (e) Privacy-First Analytics: we use only privacy-respecting analytics (Plausible or Fathom) which do not use cookies, do not require consent, and do not track individuals.

Child Safety and Minimum Age

The Service is intended for users age 13 and above. We do not knowingly collect personal data from children under 13. If we discover we have collected data from a child under 13, we delete that account and data immediately. Users age 13-15 may use the Service but are subject to parental consent requirements under applicable law. We implement age-appropriate content protections and do not process user data for advertising targeting of minors under 16. If you are aware of a child under 13 using the Service, please report it through platform contact methods.

Public Transparency Log and Privacy Implications

UnitedLines publishes a public transparency log of all moderation actions. The log contains: moderator identity, timestamp, reason for action, and justification. To protect individual privacy, the log does NOT include: personal information identifying the target of moderation beyond an account ID necessary for appeals. The log is designed for aggregate auditing and bias detection rather than individual surveillance. Users can opt to have their appeals processed privately; private appeals remain confidential. The transparency log serves to protect privacy by preventing secret surveillance and creating accountability in moderation.

Data Retention and Deletion

You can delete your UnitedLines account at any time from account settings. Upon deletion: (a) your username becomes available for reuse; (b) your profile is removed from search and browsing; (c) your personal data is deleted within 90 days; (d) encrypted messages remain stored but are not associated with your account; (e) public posts remain on the platform but are attributed to a deleted account; (f) data required for legal compliance (fraud prevention, abuse investigation) may be retained in anonymized form. You can request a complete data export before deletion using platform contact methods.

No Data Sales or Advertising Profiles

UnitedLines will never sell, trade, share, or license personal data to advertisers, brokers, or any third party for commercial purposes. We do not build advertising profiles, behavioral interest segments, or predictive models of your preferences. Our business model does not depend on monetizing user data. Revenue comes from premium features, enterprise licensing, and optional subscriptions. This commitment is irrevocable and applies regardless of future ownership changes or corporate restructuring.

Changes to This Privacy Policy

We may update this Privacy Policy periodically to reflect changes in our practices, technology, or legal requirements. Material changes (e.g., new data collection, broader use of data, weaker protections) will be communicated to you via email at least 30 days in advance, with your opportunity to review and withdraw consent if necessary. Continued use of the Service after updates constitutes acceptance of the updated Privacy Policy.

Contact and Privacy Questions

Questions about this Privacy Policy or your privacy rights should be directed through platform contact methods. Formal requests should include: your account name, the nature of your request, and any supporting details. For data subject access requests, include sufficient information for us to locate your data. We will respond to all inquiries within 30 days.