Marketplace privacy

The contract

• No IP addresses logged. Your address is used for one thing: our server counts how many requests come from it in the last few minutes, so nobody can flood the endpoint. That count lives in memory for a few minutes and then it is gone. Your address is never saved, never written to a log, and never passed to anyone else.
• No user identifiers — only random per-install UUIDs (one per install, not per user).
• No package contents transmitted.
• Anonymous and opt-in. Off until you turn it on, and genuinely anonymous when you do. DorkOS shows a first-run notice explaining it, and you can turn it back off any time.
• Aggregate counts only displayed publicly on marketplace pages.
• Full event data accessible only to the DorkOS team for debugging.

What we collect

• The package name and marketplace it came from.
• The package type (agent, plugin, skill-pack, adapter).
• The install outcome (success, failure, cancelled).
• How long the install took (for performance debugging).
• An error code on failure (so we can fix what is breaking).
• A random install ID generated locally per install.
• The DorkOS version (so we can spot version-specific install regressions).

How to turn it off

Install counts are off until you turn them on, and always anonymous. Turn them on or back off any time: run dorkos telemetry enable or dorkos telemetry disable, or use the Privacy and Data tab in DorkOS settings. Setting the environment variable DO_NOT_TRACK=1 keeps everything off no matter what the settings say.

Open source pipeline

Both the client-side reporter and the receiving Edge Function live in the public DorkOS repo. You can audit exactly what gets sent.