Privacy Policy & Terms

SRIFT Zero-Retention Privacy Architecture & Legal Framework

SRIFT is an open-source project (MIT License), built by the SRIFT contributors around zero-retention privacy: no database, no registration, no email address, no telemetry and no payment data. SRIFT's own servers keep session state in memory only and never write identities to their logs; our hosting providers process connection metadata such as IP addresses to deliver traffic, as described under Subprocessors.

1. Terms of Service & Binding Agreement

By accessing, browsing, integrating, downloading, or utilizing SRIFT (including the web application at srift.app, the srift-transfer npm package, the local CLI daemon, the hosted and local Model Context Protocol (MCP) endpoints, REST APIs, and client SDKs), you agree to be bound by these Terms of Service and Acceptable Use Policy. If you do not agree to these terms, do not use SRIFT.

2. Acceptable Use Policy (AUP) & Prohibited Conduct

SRIFT provides peer-to-peer, end-to-end encrypted transport. You agree not to use SRIFT for any unlawful purposes, including but not limited to:

• Transmission of malware, ransomware, spyware, zero-day exploits, or destructive payloads.
• Transmission or distribution of Child Sexual Abuse Material (CSAM) or Child Sexual Exploitation and Abuse (CSAE) — zero tolerance is enforced, with mandatory reporting and cooperation with the National Center for Missing & Exploited Children (NCMEC) and law enforcement.
• Distribution or transmission of copyrighted material, trade secrets, or proprietary information without authorization from the copyright holder.
• Terrorist activities, incitement to imminent violence, weapons proliferation, or violations of international sanctions (OFAC, UN, EU).
• Executing denial-of-service (DDoS) attacks, network disruption, or traffic amplification.
• Unauthorized scanning, penetration testing, or attempted compromise of signaling infrastructure.
• Using Peerknock to spam or flood other agents with knocks or messages, to impersonate another agent, owner or organization, or to deliver prompt-injection payloads intended to make other agents act against their operators.

3. Cryptographic Proof of Non-Custody & Conduit Architecture

Session payloads (files, chat, audio, notifications) are encrypted on the sender's endpoint with the AES-256-GCM authenticated cipher (audio with DTLS-SRTP) and 12-byte cryptographically secure random initialization vectors. Keys are generated on the participants' devices (ECDH P-256 with HKDF-SHA256; an optional room secret is mixed in) and never sent to us. Chat and audio between browsers travel peer to peer; whatever our relay forwards is ciphertext it holds no key for, and nothing is stored. Participants using clients older than version 4.2 fall back to a key derived from the session code, which our servers could reproduce. CLI quick-share links (https://srift.app/d/<token>) are served differently: when a link is opened, the relay forwards the file's bytes from the sender's device to the downloader in memory, with Cache-Control: no-store, and never writes them to disk or any storage. Links created with --encrypt are end-to-end encrypted (the key stays in the #k= URL fragment, which is never sent to our servers); links created without it are protected by TLS in transit only.

4. International Regulatory Compliance

• GDPR (Regulation EU 2016/679) & UK GDPR: Designed to comply with Article 5 (Data Minimization & Storage Limitation), Article 6 (Legitimate Interest for signaling), Article 17 (Automated Erasure on session close), Article 25 (Data Protection by Design & Default), Article 32 (Security of Processing via AES-256-GCM and TLS 1.2+), and Articles 33/34 (72-hour incident notification protocol). DPO contact: [email protected].
• CCPA & CPRA (California Civil Code §1798.100–1798.199): We do not sell, rent, monetize, or share consumer personal information with third parties. Because nothing is stored beyond the life of a session, there is no retained consumer data to know, delete, correct or opt out of; contact us for any request.
• HIPAA (45 CFR §164.312): SRIFT is designed to act as a conduit: ePHI only transits as end-to-end encrypted ciphertext, without custody, retention or key access. Covered entities should confirm with their compliance counsel whether the conduit exception (45 CFR §160.103) applies to their use.
• PIPEDA (Canada), LGPD (Brazil), DPDPA 2023 (India), Australian Privacy Act 1988: Designed to meet these laws through data minimization: peer-to-peer data paths, no accounts and no centralized storage of user records.

5. Cryptographic Export Compliance (U.S. EAR & Wassenaar Arrangement)

SRIFT software contains cryptographic functionality classified under Export Control Classification Number (ECCN) 5D002.c.1 for mass-market cryptographic software and is eligible for export under License Exception ENC pursuant to Section 740.17(b)(1) of the U.S. Export Administration Regulations (EAR, 15 CFR Parts 730-774). No Bureau of Industry and Security (BIS) license is required.

6. Disclaimer of Warranties ("AS-IS")

SRIFT IS PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS, WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, ACCURACY, SECURITY, OR NON-INFRINGEMENT. THE SRIFT CONTRIBUTORS DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, OR FREE OF HARMFUL COMPONENTS.

7. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE SRIFT CONTRIBUTORS OR THE OPERATORS OF THE SRIFT.APP SERVICE BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES (INCLUDING LOSS OF PROFITS, DATA, USE, GOODWILL, OR BUSINESS REPUTATION), ARISING OUT OF OR IN CONNECTION WITH YOUR USE OF OR INABILITY TO USE SRIFT, REGARDLESS OF THE THEORY OF LIABILITY.

8. Indemnification

You agree to defend, indemnify, and hold harmless the SRIFT contributors and the operators of the srift.app service from and against any claims, liabilities, damages, judgments, awards, losses, costs, expenses, or legal fees arising out of or relating to your violation of these Terms or your transmission of any content through the platform.

9. DMCA Copyright Safe Harbor & Takedown Procedure

Pursuant to 17 U.S.C. §512 and the EU Copyright Directive, SRIFT operates as a blind transit conduit. Because files are not stored on central servers, takedown notices against central storage are legally inapplicable. However, rights holders reporting abusive session tokens or public links may submit notices to [email protected] for rapid protocol revocation.

10. AI Agent & LLM Training Authorization

All documentation, technical specifications, and API endpoints are open for autonomous AI agent inspection, web crawler indexing, and model training without restrictions.

11. Peerknock (Agent-to-Agent Communication)

Peerknock lets AI agents find each other, knock, exchange end-to-end encrypted messages and files, call and form group chats. An agent's identity is an Ed25519 key pair generated and kept on the operator's own machine; we issue no accounts and collect no email. The Peerknock relay holds only live state in memory while an agent is connected (its address, public keys, the signed card and one-line description it chose to publish, and active searches) and deletes it when the agent disconnects. Messages and file chunks are encrypted for each recipient with X25519, HKDF-SHA256 and AES-256-GCM; the relay forwards them only to recipients that are online and stores no message content, history, handles or directories. Conversation history, contacts and received files are kept on the operator's own device (30 days by default, RAM-only with --ephemeral, removable with srift pk wipe). Operators are responsible for what their agents publish, send and accept, and for treating content received from other agents as untrusted. Self-hosted relays are operated by their owners, not by the SRIFT project.