Website
mdbase.dev is a public static documentation website. It has no account system or advertising trackers. The hosting provider may retain ordinary request logs for security and service operation.
Connect accounts
Public signup uses an email address to deliver a one-time verification link. Connect retains the verified address, account name, accepted terms and privacy-policy versions, identity-provider links you add, and security and audit metadata needed to operate the account. Passwords are stored as password hashes, not readable passwords. Abuse controls retain keyed digests and bounded counters for email addresses and source networks.
Connect also retains registered devices and their public keys, application declarations, collection identifiers and display names, collection members and their roles, exact grants, tokens, audit metadata, and routing metadata needed to operate the service. If you use an encryption password for Private collections, Connect stores your account key locked with that password. Connect never receives the password or the unlocked key.
Connect uses these records, never collection contents, to produce aggregate operator reports: how many accounts complete setup, how often authorization and pairing requests are approved, denied, or left unfinished, and which applications are connected and in use. Direct use on the same computer is visible only as per-account counts reported by the desktop app. Connect does not use third-party analytics. Expired tokens, unfinished authorization and pairing requests, and protocol usage counts are deleted about 13 months after they expire or were last updated.
Collection data
For a synced collection, each change is encrypted on your device before it is uploaded. Connect stores the encrypted changes, snapshots, and attachments. It can see the collection’s members, devices, and app grants, the number, padded sizes, and timing of changes, and connection metadata such as IP addresses.
For a Cloud copy collection, Connect also holds the collection key and keeps a readable copy, which the hosted service uses to execute authorized mdbase operations. For these collections, the hosted service acts as a trusted data processor.
For a Private collection, Connect holds no collection key and cannot read record contents, paths, field names, or attachments.
For a collection with sync off, record contents and paths stay on your devices. Applications reach it through an encrypted relay session with the computer that holds it. The relay sees routing metadata, timing, and sizes.
If an application schedules reminders, Connect stores each reminder’s time and a random identifier. For Private collections and collections with sync off, it stores no reminder content.
When an account moves to the new sync system, mdbase keeps the old system’s copy of each collection for 90 days after it moves, for recovery.
Connect uses your verified address for account email: verification and other messages about your account that the service needs to send. Beta accounts may also receive a short welcome and setup message.
Occasionally, we may email account holders about a significant change to mdbase Connect or a new mdbase application. These announcements are infrequent and include an unsubscribe link. We do not send regular product updates or marketing email unless you opt in, and we do not sell or share your address for others' marketing.
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. For the mdbase Reader browser extension, see its extension privacy page.
Contact
Email support@mdbase.dev about a privacy concern. Report security issues as described on the security page.