What MEMIX keeps, and why.
A plain account of what data is collected from browsers, uploaders, and API users, and what it's used for.
Last updated: draft — insert date on publish · this is a starting draft, not legal advice. Have counsel review before you rely on it.
Browsing the library
Searching and downloading from the public library doesn't require an account. No name, email, or personal identifier is collected from a browser. Standard technical logs (IP address, timestamp) are kept briefly for rate-limiting and abuse prevention — not profiling.
IP addresses are hashed before storage, never kept in plain form.
Wallet connection
Connecting a wallet uses SIWE (Sign-In with Ethereum). MEMIX stores the public wallet address used to sign in — nothing more. No private key, seed phrase, or balance is ever collected. Signing in never triggers a payment or an on-chain transaction.
Uploads & ownership declarations
The ownership/authorization declaration made at upload time (including the uploading wallet address, a timestamp, and a hashed IP) is stored permanently as a legal record — even if the asset itself is later removed.
API keys & usage
An API key is tied to the wallet address that generated it. Call volume and which endpoints are used are logged for billing and rate-limiting. Query contents are retained only as long as needed for abuse detection, then discarded.
Takedown records
Every takedown request and its resolution is recorded permanently in an append-only log. See /takedown.
What is never sold
MEMIX never sells wallet addresses, upload history, or query logs to third parties.
What is sold is access to the structured catalogue data, via the API.
Contact & jurisdiction
Not filled in yet: a data controller contact address and applicable jurisdiction. Both are required before this page goes live.
MEMIX · catalogue of record
librarian@memix:~$▊