Privacy and secret safety
The public privacy page explains email updates, anonymous visit measurement, signup analytics, metadata-only inbox records, and private handling of missing-data reports. Authenticated API responses use no-store headers.
Complete inbox records for email sent to an @aicdapi.com address keep bounded delivery metadata: the provider event and message IDs, delivery time, sender and recipient addresses, subject, and attachment metadata such as provider IDs, names, file types, content disposition (such as inline or attached), and content IDs. They also keep a SHA-256 digest of the signed webhook payload.
If bounded delivery metadata is invalid or over its limit, AICD API keeps a smaller omitted-metadata quarantine record. It keeps the provider event and message IDs, delivery time, one matched @aicdapi.com recipient, reason codes, safe recipient and attachment counts when known, and a SHA-256 digest of the signed webhook payload. In this record, the sender, full recipient lists, subject, and attachment metadata are empty.
AICD API does not store message bodies or attachment files during this first stage. Resend receives the full message so it can deliver and forward it. Do not send passwords, API keys, payment card details, or other secrets by email.
Support will not ask for an API key, password, wallet seed phrase, private key, authorization header, or signed payment payload.
Known data limits
- Government publishers can change pages, fields, schedules, and history without notice.
- A research-catalog entry does not prove a source is active in the live feed.
- An empty result can mean no match, incomplete coverage, publication delay, or source trouble.
- A classification helps discovery. Read the underlying agenda text and government source before acting.
- Keep proposed actions separate from adopted actions. A meeting agenda does not prove final approval.
Report bad data or a bug
- Email hello@aicdapi.com.
- State whether this is bad data, missing data, access trouble, or a software bug.
- Include the public government source URL, AICD API page or route, approximate time, and safe error code.
- Remove keys, authorization headers, personal data, and wallet secrets before you send it.
Service status and changes
A public status page and a public release-note feed are not available. Source status shows health only for the featured Dallas-Fort Worth meeting sources. This Help Center documents current public limits.