Stored to operate the service
Operational records stay intentionally narrow.
NexFade stores encrypted payloads, encrypted metadata envelopes, workspace ownership, expiration details, billing state, and lifecycle records needed to operate the service.
Intentionally not stored in readable form
The service is designed to stay out of the readable content path.
Readable notes, file contents, and the decryption fragment are not stored as part of normal service operation. That boundary is part of the product design itself.
Providers and support
A small vendor set supports the product.
Providers such as Stripe, PocketBase, Cloudflare, Fastmail, and Sentry may process the limited payment, infrastructure, mail, and error data needed to operate NexFade. Support and billing questions are handled through support@nexfade.com. Security reports can be sent to security@nexfade.com.
Optional Muse connector
Muse receives limited link information.
If you connect NexFade to Muse, Auth0 handles the connector sign-in and Meta processes what you enter in Muse. NexFade uses the verified OAuth identity and scoped tool calls to return only link IDs, limited lifecycle status, and browser handoff URLs. Complete share links, readable content, recipient details, and decryption keys stay in your NexFade browser flow. Do not enter them into Muse.
Operational logging
Logs and abuse controls stay measured.
Application logs are kept limited and redacted. Abuse controls lean on validation, rate limiting, and hashed request signals rather than broad raw activity storage.