01Network ranking
The feed starts with recent posts, prioritises people you follow, then considers useful engagement. Paid promotion receives a bounded boost and is always labelled Promoted. Payment cannot remove blocks, privacy rules or moderation.
02Moderation
Known credential theft, configured unsafe phrases and domains, repeated spam, blocks and member reports are enforced on the server. Human admins decide reports. End-to-end encrypted plaintext cannot be scanned by the server.
03Network encrypted messages
Supported encrypted Network conversations use device-held P-256 User Keys, conversation-specific HKDF-SHA256 keys and AES-GCM. Account and delivery metadata, public keys and ciphertext remain visible. This does not claim that every Ident.ink messaging product is end-to-end encrypted.
04Local infrastructure
Core data, cache, streams and object storage run on Ident.ink-controlled infrastructure. Health, backups, quotas and cleanup jobs are operated locally.
05Legal governance
The Legal Centre versions the contract, acceptable-use rules, partner terms, community standards, refunds, incident handling, moderation appeals and dispute process.
06Request boundary
Authenticated actions are authorised on the server. Inputs are bounded, suspicious request patterns are rejected, sensitive actions have dedicated rate limits and external connections cannot silently become code execution.
07Release and recovery
Production changes use isolated builds, tested backups, route verification and immutable rollback. A passing compile is not treated as proof that customer workflows work.
08Errors and response
Customer errors receive safe messages rather than internal diagnostics. Operators use health checks, structured events and references to investigate. Credible active harm is contained first, but a guaranteed response or resolution time exists only where a written contract says so.