Privacy

Website

mdbase.dev is a public static documentation website. It has no account system or advertising trackers. When you join the beta waitlist, mdbase Connect retains the submitted email address and request time so the request can be reviewed and an invitation can be sent. Rate-limit records use keyed digests of the email and network address; the access-request record does not store the network address. The hosting provider may also retain ordinary request logs for security and service operation.

Connect

Connect account services retain identity, computer pairing, application declarations, collection identifiers and display names, exact grants, tokens, audit metadata, and routing metadata needed to operate the service.

Local collection paths and record payloads stay at the connector. Encrypted relay traffic exposes routing metadata, operation names, timing, and sizes. Request and response bodies remain encrypted between the application and local connector.

Hosted collection records are encrypted at rest by the hosted provider. The provider decrypts them to execute authorized mdbase operations and acts as a trusted data processor.

Application providers

Applications connected through mdbase receive data under the grants users approve. Each application provider is independently responsible for its own handling of authorized data.

Contact

Report a privacy or security concern through the appropriate repository in the mdbase GitHub organization.