Privacy Policy

Last updated: 15 May 2026

What we collect

Miriaview collects the minimum data needed to operate the Service and improve it.

• Account data — your Apple App Transaction ID, a stable identifier issued by Apple’s StoreKit that lets us associate your subscription with our service. We do not collect your email, name, or any other personally identifying information through the app.
• Subscription data — current plan, status, and renewal date as reported by Apple. We do not see your card or payment details.
• Published content — markdown documents and sites you choose to publish are stored on our servers and made available at the public URLs you receive.
• Usage analytics — anonymous events (e.g. "publish_clicked", "paywall_shown") sent to Google Analytics 4. No file content, file names, or personal identifiers are collected. You can opt out in Settings → Privacy.
• Page view data on published pages — anonymous session cookie, referrer, country (from IP), user agent. Used for aggregate analytics on your published pages.

What we do NOT collect

• The content of files you read or edit locally;
• The content of folders you have not explicitly published;
• SSH server credentials, hosts, or remote file contents;
• Browsing history or activity outside Miriaview;
• Any data that we sell or share with advertisers.

How we use the data

• To operate the Service (publish, subscriptions, accounts);
• To improve product features (which features are used, where users get stuck);
• To respond to support requests and abuse reports;
• To prevent abuse and protect the Service.

Storage and retention

Account and subscription data are retained while your account is active. Published content is retained until you unpublish. Usage analytics are retained per Google Analytics defaults (up to 14 months). Abuse reports are retained for moderation purposes.

Your choices

• Opt out of usage analytics: Settings → Privacy → Share usage data toggle off;
• Unpublish content: in Miriaview app, Reader → Unpublish, or contact support;
• Delete account: contact support@miriaview.com.

Cloud SSH Sync (optional, Pro)

When you enable Cloud Sync for an SSH workspace, Miriaview keeps a read-only connection to your server so your published Markdown updates automatically when files change there.

• What we store on our server: the SSH host (hostname/IP, port, username), the workspace root path you chose to expose, the SHA-256 fingerprint of your server’s host key, and a per-enrollment Ed25519 private key generated on your Mac. The private key is encrypted at rest with a server-side master key (KEK) held in an isolated service.
• What the connection is allowed to do: read only. The Cloud Sync key is intended to be installed under a chrooted, read-only SFTP scope on your server. We probe this on activation and refuse enrollment if writing succeeds.
• What we read from your server: only the specific files you publish. We compare modification time and size to detect changes, then read the new contents and re-render the public version. We do not list directories, crawl, or read any files outside the ones you publish.
• Data retention: the encrypted private key and metadata stay until you disable Cloud Sync. Disabling removes them server-side and stops polling. We retain a minimal audit log (connections, syncs, errors) for 90 days for diagnostics.
• Your control: you can rotate the Cloud Sync key at any time, disable Cloud Sync from the Settings or the workspace context menu, or remove the line we added to your server’s authorized_keys manually. Disabling from Miriaview removes that line for you.

Third-party services

• Apple — handles all subscription billing and provides the App Transaction ID we use as your identity. See Apple Privacy.
• Google Analytics 4 — anonymous usage analytics.

Contact

Privacy questions: privacy@miriaview.com.