Security design · development status
Protection you can reason about.
Neluora’s implemented private-Moment path encrypts media on the sender’s iPhone and decrypts it only on authorized recipient devices. The development service stores ciphertext, opaque identity and the minimum audience, delivery, timing and quota metadata needed to operate that path.
Implemented private media boundary
The iOS client normalizes image orientation, removes unintended metadata, creates bounded renditions and encrypts every rendition before upload. Publication uses one canonical Moment, a publication-time immutable audience and one authenticated content-key envelope per authorized device. Download authorization rechecks account, device, snapshot, envelope, block and availability state.
Identity and sessions
Accounts and devices use random opaque identifiers. Access credentials are short-lived; refresh credentials rotate and detect replay. Long-lived device authentication and envelope keys are device-only Keychain items. An owner-chosen Display name is presentation data and never replaces those identifiers in authorization or cryptography.
Deletion and honest limits
Deleting a Moment revokes hosted access, distributes tombstones and queues physical ciphertext deletion. Removing or blocking someone prevents future delivery and hosted retrieval where enforceable. Neither operation can erase a screenshot, export or plaintext a recipient already obtained.
Not yet approved for private beta
Conversation encryption still needs a pinned, reviewed OpenMLS engine and rollback-safe state boundary. Private phone discovery needs an independently reviewed VOPRF construction. Recovery, two-physical-device destructive tests, broader hostile-media coverage, production isolation and external mobile/backend/cryptographic review remain release gates.
Verification discipline
- Wrong-audience, outsider and revoked-device authorization tests
- Metadata stripping, tamper rejection and ciphertext-only storage inspection
- Idempotent upload, publication, tombstone and deletion tests
- Payload-denying logs and secret/dependency scanning
Report a vulnerability
A coordinated-disclosure address and safe-harbor policy will be published before external testing. Do not send private content to an unverified contact route.