Server
You decide which machine, network, and hosting provider can run the instance.
Memos privacy
Memos has no hosted account service, product telemetry, or data pipeline for your notes. A self-hosted instance stores everything on infrastructure you control.
Last updated August 2, 2026.
Memos does not report feature usage, behavior, or device profiles back to the project.
Your notes are not copied into a Memos-operated cloud service or analytics pipeline.
The website does not use advertising pixels or analytics scripts to build a profile about you.
Collection
The project does not need a copy of your identity, content, or behavior to provide self-hosted software.
You do not need a Memos-hosted account, subscription, or profile to download and run the software.
Memos stores note text, attachments, and metadata in the database and storage configured for your own instance.
There is no mandatory analytics SDK, behavior profiling, or product telemetry reporting usage to the Memos project.
Memos does not require ad pixels, cross-site trackers, or advertising IDs in the product or on this website.
Your control
Privacy comes from a short, inspectable data path and infrastructure whose rules you set.
You decide which machine, network, and hosting provider can run the instance.
SQLite, PostgreSQL, or MySQL stays in your environment under your access rules.
You decide where backups live, how long they remain, and who can restore them.
Boundaries
Memos can define its own software and website. Other services and instance operators define theirs.
usememos.com does not require an account, contact form, analytics tracker, advertising pixel, or tracking cookie to read its public pages.
GitHub, Discord, the public demo, hosting providers, and other linked services operate under their own privacy terms when you visit them.
If another person or organization operates the Memos instance you use, that operator controls its server, access policy, retention, and backups.
Privacy questions
Memos does not receive your notes or usage. Your instance operator controls the environment where they live.
Inspect the source, review the deployment path, and decide where your data should live.