Privacy
What MacCrab Rave collects (and doesn't). On-device by default, no download counts, no per-user tracking.
MacCrab Rave follows the same posture as MacCrab itself: on-device by default, no account required, nothing phones home that doesn’t have to. This page is the honest account of what the catalog does and doesn’t collect.
Browsing the catalog
Browsing rave.maccrab.com and installing plugins needs no account and sets no tracking cookies. The catalog is static signed JSON; your MacCrab app fetches it, verifies the Ed25519 signatures against the key bundled in the app, and never reports back what you looked at or installed.
Download counts
The site shows no download or install counts. Your MacCrab sends no telemetry when you install a plugin. Fetching the catalog and a plugin’s archive are ordinary requests to rave.maccrab.com, so they pass through Cloudflare like every other request (see Third parties).
Signing in (only for submitting)
You sign in to Rave, with GitHub OAuth, only to submit a plugin or see your submissions. Commenting does not use a Rave sign-in (see Comments). If you sign in, we store the minimum: your GitHub numeric id, login, and avatar URL, plus the submissions and moderation records tied to your account. We never store an email or any GitHub data beyond that. Admin access is a fixed list of GitHub ids in the site’s code; there is no role you can be granted by using the site.
Comments
Comment threads are GitHub Discussions in the public repository peterhanily/maccrab-rave-comments, shown through giscus. Comments load automatically from giscus.app and GitHub when you open a plugin or kit page with JavaScript enabled. These third parties receive the requests needed to display the widget, comments and avatars; no sign-in is needed to read them. To post, you sign in to giscus with GitHub: comments are posted through the giscus GitHub App as you. When you come back from signing in, giscus puts a session token in the page’s address. That request reaches rave.maccrab.com through Cloudflare (see Third parties), and your browser may keep the address in its history. Rave’s script then removes the token from the address, keeps it in that tab’s session storage (never localStorage) if the discussion previously loaded in that tab, and sends it only to giscus.app. The comment text and author identities live in GitHub, under GitHub’s privacy terms; Rave’s own servers store nothing about comments. Turning comments off changes nothing about the catalog or its trust chain.
Retention and deletion
If you signed in to Rave, you can delete your account. Deletion is a single atomic operation (POST /api/account/delete) that requires you to type your own login to confirm. We do not hard-delete every row — some data is anonymized, and one identifier is retained with justification, because parts of the catalog are an append-only accountability log and others are Ed25519-signed bytes we cannot rewrite from a web request. We are honest about that here rather than claiming a clean wipe.
Per-table, what happens on deletion:
| Data | On deletion |
|---|---|
Your user row (users) | Pseudonymized, not fully anonymized. login, avatar_url, the reputation snapshot, and any ban_reason are scrubbed; trust_state is set to deleted. Your GitHub numeric id is retained — see the justification below. |
Your submissions (submissions) | The denormalized submitter login is scrubbed to [deleted]. Any open / in-flight submission is withdrawn. Submissions that already reached a published/terminal state are left in place (their byline may be in signed catalog bytes — see the limit below). The submitter id link is retained. |
Media you uploaded (media) | Free-text captions are erased. Approved/published screenshot bytes that are part of a live listing are kept; the uploader link points only at your now-pseudonymized row. |
Reports you filed (reports) | Your reporter identity is anonymized, but the report body is kept — a resolved safety/abuse report must remain legible for anti-abuse purposes. |
Moderation log (moderation_events) | Mentions of your login in submission log entries are not yet removed when you delete your account; only the maintainer can see them. The actor id is retained (audit anchor, below). A single terminal account_deleted marker row is written as proof of erasure. |
Why we retain your GitHub numeric id. Your github_id is the foreign-key anchor for the submission, moderation, media and report rows above, and it is the only stable handle that lets us enforce a ban or trace abuse if a bad actor deletes and re-creates. We keep it under legitimate interest (audit / anti-abuse), not under your consent, and the row it belongs to is otherwise pseudonymized. This is why we describe the result as pseudonymized-with-justified-retention, not “fully anonymized”.
Published-author limit (partial erasure). If a submission of yours was already merged into the signed catalog, your byline may be baked into bytes that are protected by an Ed25519 signature. We cannot rewrite signed bytes from this endpoint. On explicit request, we can enqueue an offline re-sign of the catalog to drop the byline.
Retention. The pseudonymized rows and the retained github_id anchor are kept only as long as needed for audit and anti-abuse (legitimate interest), and are minimized and removed once that need lapses.
What we never have
- Your installs, scans, or any forensic output — that stays on your Mac.
- The catalog signing key. It never touches this site’s servers or CI; it is kept in the macOS keychain on the maintainer’s Mac.
- Any cross-site tracker, ad network, or analytics-by-default.
Third parties
- giscus.app and GitHub, for comments: the giscus widget, comments and their authors’ avatars load automatically on plugin and kit pages with JavaScript enabled.
- GitHub, when you sign in to Rave (GitHub OAuth), and when a submission becomes a pull request in a GitHub repository; the pull request names your GitHub login.
- avatars.githubusercontent.com: if you sign in to Rave, the page header shows your GitHub avatar from GitHub’s image server.
- Cloudflare hosts the site and runs its functions. It handles every request and keeps edge logs and the functions’ logs. The functions count requests per IP address there to rate-limit them, and your browser may send Cloudflare Network Error Logging reports.
Who runs Rave
Rave is run by MacCrab’s maintainer, peterhanily on GitHub. Write to maccrab@peterhanily.com about anything on this page.
Security disclosure
Found a problem with a plugin or the catalog? Email maccrab@peterhanily.com. Don’t post security issues in a public comment thread. See the verification docs for the trust model.