1. What Cute Magick Is
Cute Magick is a personal web runtime — software you install and run on your own device. It is not a hosted service. It does not run in our cloud. We make the software. You operate it.
Plain language. Short because we respect your time.
These documents are written in plain language on purpose. Cute Magick is software you can run yourself. You own your data. We try not to hold more of it than we have to. Questions? Email me@diana.nu.
Cute Magick is a personal web runtime — software you install and run on your own device. It is not a hosted service. It does not run in our cloud. We make the software. You operate it.
Anyone. Cute Magick is open source under the MIT License. Use it for personal projects, professional work, experiments, weird art, quiet tools — everything in between. No account required to run it locally.
The source code is released under the MIT License. You may read it, fork it, modify it, and redistribute it. The full license is included with every release. Commercial use is allowed.
Cute Magick Hosted is an optional managed service. Billing is through Stripe. You can cancel at any time. Your content is always yours — export your full site and Git history at any moment. Cancellation gives you a 30-day export window before anything is removed.
We are a one-person operation on a single server. We are not pretending otherwise.
99.5% per calendar month — honest for a single-server setup. ~3.5 hrs max unplanned downtime/month.
At least 24 hours advance notice via status page and email. Scheduled windows don't count against uptime.
Status updates posted when something goes wrong. Post-mortems for any outage over 2 hours.
Email at me@diana.nu, pay-what-you-want. $0 is completely fine — same quality either way. Response target: 2 business days.
No service credits for downtime. Instead: transparency, public incident reports, and a genuine effort to do better. PWYW: after each resolved ticket you'll get one optional follow-up email with a payment link. No pressure, no minimum.
Very little. Don't use Cute Magick to harm people, distribute illegal content, misrepresent its origin, or imply official endorsement without permission. That's it. We assume you're here to build something you care about.
Everything you create belongs to you. We have no claim over it. Your site is a folder on your machine. Your history is a Git repository you control. We are not a party to what's inside.
Cute Magick is provided as-is. Software has bugs. We make no warranties about fitness for any particular purpose. We genuinely try to make it reliable — if something breaks, we want to know. But we cannot accept legal liability for software we don't host.
To the maximum extent permitted by law, the creators of Cute Magick won't be liable for indirect, incidental, or consequential damages — including data loss or downtime. Keep your own backups. Git makes this easy: push to a remote.
We'll publish changes in release notes and on the website. Continuing to use Cute Magick after a change means you agree to the updated terms. We won't make changes silently or against your interests.
These terms are governed by the laws of the State of California, United States. If any provision is unenforceable, the rest continue in full force.
Questions about these terms? Email Diana at me@diana.nu. Cute Magick is a one-person project and that goes directly to her.
Cute Magick is self-hosted software. The architecture is itself a privacy decision.
The short version
Cute Magick does not collect your personal data. It cannot. The software runs on your machine and your data never leaves it unless you explicitly push it somewhere yourself. There is no Cute Magick server receiving your content, your files, or your behavior.
Nothing, by default. No telemetry, no analytics, no crash reporters, no session recording, no fingerprinting, no tracking pixels. The source code is open — if you ever find data being transmitted without your knowledge, that's a serious bug and we want to hear about it.
Standard web server logs (IPs, requests, referrers). Email addresses if you opt in to release notifications. Payment info if you subscribe — handled entirely by Stripe (stripe.com/privacy), we don't store card numbers. We don't sell or share any of this.
Your site's content lives entirely on the machine you're running Cute Magick on. We can't read your drafts, see your commit messages, or access your database. We are not in the room. Self-hosting is a privacy guarantee, not just a feature.
For hosted customers we hold: your site files and media, your SQLite database, your full Git history, your account email, and billing info (via Stripe). We use it only to operate your site. We don't read, analyze, or train models on your content. We access it only when you explicitly invite us for support, or for automated operational tasks like backups.
You can export everything — files, database, full Git history — at any time. Export is a first-class feature. If you cancel, your data is retained for 30 days for export, then permanently deleted. We'll remind you before that happens.
Cute Magick software may use session cookies for your local admin panel — these never leave your machine. The website may use cookies for session management. No third-party tracking cookies.
Cute Magick integrates with third parties only at your request — if you push to GitHub, your commits go to GitHub; if you embed third-party scripts, those operate under their terms. We're not responsible for services you connect to voluntarily.
We don't knowingly collect information from children under 13. If you believe a child has shared information with us through the website, email us and we'll address it promptly.
Website logs rotate within 30–90 days. Email subscriptions are retained until you unsubscribe. Hosted customer data has a 30-day retention window after cancellation, then is permanently deleted.
Depending on where you live, you may have rights under GDPR, CCPA, or similar laws. Because we hold very little data by design, most requests will be simple. Email me@diana.nu and Diana will respond within 30 days.
We take reasonable steps to protect data we hold. Your local installation's security is your responsibility — use strong passwords, keep your server updated, push to a remote for backups. Found a vulnerability? Please report it responsibly before public disclosure.
Material changes will appear in release notes and on the website. We won't reduce your privacy protections without notice. Questions: me@diana.nu.
Most legal documents are written to protect the company from the user. We tried to write ours differently.
The best protection we can offer you is a system where we simply don't have your data in the first place. That's not a compromise — it's the point.
Your site is yours. Your work is yours. Your history is yours.
We're just here to make the tools.
— Diana
© who cares, really ¯\(ツ)/¯
Terms & Privacy