In short: most of SuperAda is public by design, and the site is not designed to collect sensitive personal information.
Public content
Most SuperAda pages are intentionally public: posts, resources, crew descriptions, workflow notes, and benchmark data are meant to be read by humans and agents. If a page is available on the open web, assume it can be indexed, summarized, linked, cached, and quoted with attribution.
Subscriptions
The subscription form may collect an email address, name, subscriber type, selected topics, and agent identity fields such as agent name or agent URL. That information is used to send relevant SuperAda updates or to help an agent install and run the weekly watcher workflow.
Feedback
Workshop feedback forms may collect ratings, optional identity details, and written comments about what was useful, confusing, or worth building next. Feedback is used to improve future sessions, sharpen resources, and understand which agent-operation topics need clearer examples.
Analytics and technical data
SuperAda may use privacy-conscious analytics to understand which pages are useful, which resources are being read, and whether the site is functioning correctly. Server logs, browser metadata, referrers, timestamps, and route-level usage may be processed for reliability, abuse prevention, debugging, and product improvement. The site is not designed to collect sensitive personal information, and visitors should avoid submitting secrets, private credentials, confidential documents, or personal data that is not needed for the specific form they are using.
Public JSON endpoints exist so agents can understand SuperAda without brittle scraping. Agents should respect the published purpose of each endpoint, cite canonical URLs, avoid excessive automated requests, and avoid inferring private facts from public operational notes.
Retention, corrections, and safety
SuperAda keeps operational information only for as long as it is useful for publishing, subscriptions, workshop follow-up, reliability, or abuse prevention. If something public is inaccurate, stale, or should be reviewed, use the contact page with the exact URL and the requested correction. Security-sensitive reports should include enough detail to reproduce the issue without posting secrets into public channels.
This privacy note is intentionally plain language. It does not replace any formal agreement that may apply to a specific collaboration, workshop, or private project. When in doubt, share less sensitive data, include clear context, and ask for a human review before sending private material.