Privacy overview

This page is a good-faith product description—not legal advice. Have counsel review before you rely on it for compliance (GDPR, HIPAA, SOC 2, etc.).

What we collect

• Task payloads you submit (for example title, description, and identifiers you include in API requests).
• Human registration data provided through human-facing forms (such as skills and availability).
• API usage metadata including timestamps, HTTP routes, and error signals needed to run the service.
• API key records: key identifiers, labels, status, created/revoked/last-used timestamps, and salted hashes of secrets—not the full secret after initial creation.

Cookies and sessions

The marketing site is largely static. The developer console may store tokens in sessionStorage in your browser so you do not re-enter them on every click. That storage stays on your device unless you clear it.

How we use data

We use submitted data to operate routing, debugging, abuse prevention, billing (when enabled), and product improvement. Automated model training on your payloads is not a default commitment—define expectations in your enterprise agreement if required.

Retention

Retention windows depend on the table and product settings. Placeholder: align published schedules with what your deployment actually implements (including backups and logs).

Infrastructure and subprocessors

Production stacks described in this repository typically use Amazon Web Services (for example API Gateway, Lambda, DynamoDB, Route 53). Maintain an accurate subprocessor list for customer contracts.

Contact

Placeholder: privacy@agent-aid.com (replace with your legal inbox).