Strong password storage
Passwords are never stored as plain text; they are kept with industry-standard strong hashing.
- Hash-based storage
- Session renewal after login
- Password change flow
MDNote.dev
Markdown workspace
Security
MDNote.dev runs with an architecture that separates user notes from each other and protects the workspace with modern security standards.
Passwords are never stored as plain text; they are kept with industry-standard strong hashing.
Failed login attempts are tracked and accounts are protected against unauthorized attempts.
Each user only sees and edits their own notes; total data privacy is ensured.
Session
Registration and login processes work with fundamental security practices like password hashing, active session checks, and session renewal. Suspicious attempts are monitored to keep accounts secure at the highest level.
Data boundary
In the MDNote workspace, each user's notes and folders are strictly independent. Database-level ownership verification prevents any cross-account data leaking or unauthorized access.
Your data is protected on the server side with secure sessions and isolated access controls.
Security practice
Account hygiene is as important as application security in protecting your notes.
Choose a hard-to-guess password not used on other services.
Log out when you are done on shared computers.
Follow your organization's policy when writing secrets, passwords, or customer data in notes.
Report suspicious account behavior through the contact channel.
FAQ
Your notes are protected with secure server sessions, strong password hashing, and account-level data isolation.
No. Every user's workspace is strictly isolated. Through robust authorization checks, no user can view another user's notes or folders.
Yes. The security infrastructure records failed attempts and shields accounts from brute-force attacks.