01 · Privacy policy
Who is responsible. ai-memory.net is the product site for Mnemosyne OS, operated by Guangdong Xinshiming Industrial Co., Ltd. (广东鑫室铭实业有限公司). For any question, request or complaint about this policy, use the contact page — it reaches the maintainer directly, which is a shorter path than any form letter.
This site has two halves, and they handle data differently. It is worth being precise about which half you are using.
- The landing page and the documentation are static. Reading them creates no account, sets no cookie, and stores nothing in your browser beyond your theme and language choice. Nothing is submitted to us.
- The hosted console needs an account. If you sign in — with GitHub or with an emailed one-time code — we store the email address you authenticate with, a password hash if you set a password, an avatar if you upload one, the API keys you create, and the memories you choose to save. That is the whole list.
- Passwords are never stored in a recoverable form. They are hashed with PBKDF2-SHA256, 200,000 rounds, with a random per-account salt. We cannot read your password, and neither can anyone who takes a copy of the database.
Third-party components and where they run
- GitHub OAuth — the optional sign-in path. If you use it, GitHub authenticates you and tells us your GitHub identity; GitHub's own privacy statement governs that step.
- WorkBuddy Cloud SDK — an optional managed backend used for end-user authentication
and managed Postgres. It is only functional on its registered release domain
(
mnemosyne-os.app.workbuddy.host). On ai-memory.net the SDK is present in the page but cannot establish a session; the UI says so rather than pretending otherwise. - Google Fonts and other CDNs are deliberately absent. Fonts are self-hosted so that loading this site does not leak your IP address to a font host — which is also why the page still renders correctly on networks where those hosts are unreachable.
Where the data physically is
The web server is hosted in a Google Cloud region in the United States. If you are in the European Union, the United Kingdom, or mainland China, using the hosted console therefore involves a cross-border transfer of the data you put into it. The engine itself is local-first — it writes to a SQLite file on your own machine and transfers nothing — so the usual answer is to run it yourself and keep the data local. That is not a workaround; it is the intended design.
Children
This site is a developer tool and is not directed at children. We do not knowingly hold personal data from anyone under 16. If you believe we do, write to us and we will delete it.
02 · What the server records, and for how long
Caddy writes a JSON access log for this domain. It is the only record of your visit, and it is the reason we can describe it here precisely instead of with adjectives.
- Fields recorded: timestamp, IP address, request line, HTTP status code, response size,
response duration,
User-Agent, and — when your browser sends one — theReferer. - Retention: the log rotates at 10 MiB, keeps five files, and nothing older than 30 days is retained. When the oldest file ages out it is gone.
- Purpose: two things only — aggregate visitor figures on the password-protected
dashboard at
/stats/, and security work: spotting scanners, breaking up brute-force attempts and rate-limiting abuse. - Never written to the log:
Authorizationheaders,CookieandSet-Cookieheaders, and request bodies. Session tokens and passwords cannot appear in the log because they are never written to it. - Not used for: profiling, advertising, cross-site tracking, or training a model.
Server-side requests from the machine itself and from private address ranges are excluded from the visitor figures, so the numbers on that dashboard describe other people rather than our own health checks. Where a figure is derived from the log rather than observed directly, we would rather say so than let it read as something it is not.
03 · Cookies and local storage
- No tracking cookies. This site sets none — for advertising, analytics, or anything else. There is no cookie banner because there is nothing to consent to.
- One strictly necessary session cookie. If you sign in to the console, a cookie named
mn_sidcarries your session. It isHttpOnly(unreadable from JavaScript),SameSite=Lax, andSecureover HTTPS. It expires after 30 days of inactivity, and signing out clears it immediately. - HTTP Basic authentication on
/stats/. The visitor dashboard is protected with the browser's built-in Basic auth. Your browser may offer to remember those credentials; that is a browser feature, not a cookie we set. - Local storage, preferences only. Two keys —
mn-theme(dark or light) andmn-lang(English or Chinese). They stay in your browser, are never sent to the server, and are not readable across other websites. - Clearing everything is done from your browser's own settings. No request to us is needed, and nothing breaks if you do it.
04 · Your rights over your data
If you hold an account, you can export what the console stores about you from the dashboard, and you can revoke any API key yourself at any time. For a formal request under the GDPR, PIPL or a comparable regime, write through the contact page — we answer the request rather than redirecting you to a form.
- Access and portability — export from the console, or ask us for a copy.
- Rectification — edit any memory in the console; correct your profile in place.
- Erasure — ask, and the account and its memories are deleted. This is a real deletion: memories live in a single SQLite file, and removing it removes them. Copies held in encrypted backups expire on the normal backup cycle.
- Objection and restriction — name the processing you object to and we stop it.
- Complaint — you may also complain to your local data protection authority. We would rather you told us first, but the right is yours either way.
05 · Terms of service
By using this site you agree to the following. If you do not agree, the software is still yours under the MIT licence — take the repository and run it yourself.
- The software is MIT-licensed. The engine is free to use, modify and redistribute under the terms in the repository. That licence, not this page, governs the code.
- This site is provided as is. No warranty of availability, fitness for purpose or accuracy. Features, benchmarks and roadmap items may change without notice.
- Numbers on the site are measurements, not promises. Benchmarks are reproducible from the repository; your latency will differ with your hardware.
- Accounts are personal. Keep your credentials to yourself. You are responsible for what is done with your API keys, so revoke any key you no longer control.
- The hosted console is a courtesy, not a contract. There is no SLA. Rate limits apply and may be tightened to keep the service available to everyone.
- Suspension. Accounts that abuse the service may be limited or closed, with notice where the law requires it.
- Liability is limited to the extent permitted by law. The system is free, and the service is provided without charge; in no event are we liable for indirect or consequential loss.
- Governing law. These terms are governed by the laws of the People's Republic of China. Disputes are subject to the jurisdiction of the courts of Guangdong.
06 · Acceptable use
- Do not attempt to access accounts, data or systems that are not yours.
- Do not run automated scans, fuzzing or load tests against this site without asking first. Ask, and the answer is often yes — the point is that we would like to be able to tell you when something breaks.
- Rate limits and the web application firewall exist to keep the service available for everyone. Circumventing them is a breach of these terms, not a challenge.
- Do not use the memory API to store other people's personal data without a lawful basis to do so.
- Security research is welcome. Report it privately through GitHub security advisories rather than in a public issue, and give us a reasonable window to fix it.
07 · Changes and contact
Material changes are dated at the top of this page and noted in the release notes. Continuing to use the site after a change means you accept it; if you do not, stop using the site and delete your account.
Security contacts, disclosure policy and scope are published in machine-readable form at
/.well-known/security.txt.
Nothing on this page is legal advice, and no page can be. If you need a data processing agreement, a self-hosted deployment review, or a compliance mapping for a regulated environment, use the contact page — the answers exist, they are simply too specific for marketing copy.