Skip to content

📖 Data and attribution

The bundled catalogue contains public Agent Engineering HQ event information: event titles, venues, published dates, speaker listings with links and talk abstracts, agenda entries, FAQ answers, sponsors and support options, program themes, code of conduct summary, ticket terms and links to registration or recordings. It includes no attendee/member exports, private contact list or proposal submissions.

The software license covers this project's source code and original documentation. It does not grant rights to third-party biographies, talk abstracts, names, logos, photographs or recordings. Such material remains attributed to its public source and subject to any rights held by its owner. Linked videos are not downloaded or redistributed by this project.

Every catalogue record references a public source. An export records its publication time, source revision and content hash. The catalogue is a snapshot: it does not verify live ticket availability, registration approval, cancellation or changes made after export. Consult the linked registration/event page for current details.

Historical events with only a month published retain month precision. Unknown session times and ticket expiry dates are not filled in. Calendar export only uses sessions with published start and end times.

For a correction or removal request, contact events@agentengineering.world with the record and source URL. Maintainers can update the catalogue after checking the source. When updating data, preserve attribution and avoid adding private information or copyrighted assets without authorization.

Privacy

The public catalogue contains published speaker and organizer information, not private attendee/member records. Optional chat processes visitor questions and recent replies. Personal agendas, bookmarks, drafting and private intake are unsupported.

  • No telemetry. The CLI makes no network calls unless you pass --remote URL, which sends only the typed request you ran (for example {"operation":"events","city":"London"}) to that host. It sends an Authorization header only if you set AGENTENG_OPERATOR_TOKEN yourself; only set those for a host you trust.
  • Local files stay local. Optional agenteng code agent logs live in the AgentEng config directory ($AGENTENG_CONFIG_DIR, else $XDG_CONFIG_HOME/agenteng, else ~/.config/agenteng). They are never uploaded. A new config directory and the acp-logs/ folder are created 0700, and log files 0600.
  • agenteng code logs can contain personal text. acp-logs/*.log holds each coding agent's stderr, which may echo your prompts, file paths or account names. Delete the folder any time: rm -rf ~/.config/agenteng/acp-logs. agenteng code does not read or send your files. Prompts go to the coding agent you chose (and its provider), never to AgentEng's server. Talk context comes from the local catalogue, and the attached MCP server is a local agenteng mcp process.
  • Hosted service. The public MCP, A2A and HTTP service reads no client addresses, and no headers apart from Authorization and Origin (for CORS). It keeps no conversations or request bodies. It writes no per-request application log: agenteng serve disables the access log unless you pass --access-log. The hosting platform (Cloud Run) keeps its own standard request log (time, path, status, client address and user agent), which AgentEng does not control.
  • Public chat. When explicitly enabled, the service sends a question, at most six recent messages, and selected public catalogue evidence to the configured model provider. It does not read Supabase, member/attendee exports, private proposals or local bookmarks. Common email/phone identifiers not already in the public catalogue, credential patterns, explicit self-disclosures and requests for private records are refused before a model call. Nonpublic contact identifiers in generated answers cause lookup fallback. These pattern checks cannot detect every personal name, address, obfuscated identifier or sensitive fact; keep personal details out of chat.
  • OpenRouter routing. Public chat sends provider.data_collection=deny and provider.zdr=true, restricting inference to endpoints OpenRouter identifies as not collecting/retaining prompt data. Unavailable eligible endpoints return the static catalogue answer rather than relaxing privacy filters. Provider policy declarations are not an independent audit. OpenRouter gateway prompt logging is an account-level setting; disable it and training opt-ins in the account privacy settings. We cannot verify those account settings or Cloud Run log retention/IAM from the public service.

Tool directory

Tool names and public links are factual metadata attributed to a pinned SuperRadar snapshot. AgentEng supplies its own classifications and normalization; source descriptions, rankings and imagery are not copied. source_listed metadata is not independently verified adoption evidence. Listings retain source aliases and provenance; see directory usage and refresh. Third-party trademarks, assets and software retain their own rights.