Data boundaries you can inspect.
Agentic Income uses minimal first-party events to understand which public routes are useful. Access requests are handled according to the runtime state shown below.
Access requests
When an intake webhook is configured, the email address and source are sent to that configured service. When a concierge address is configured, the site can prepare a mail message for you to send. When neither exists, the site does not retain the address and says so in the interface.
Analytics
Interaction events can include the page, route, offer, source label, and an opaque request ID. Raw email addresses are not placed in analytics events. Page views and these interaction events are measured with Vercel Web Analytics, which does not use third-party cookies: Vercel counts visitors with a hash of the incoming request that it discards after 24 hours, and reports only aggregated statistics. Interaction events sent to Vercel carry at most two labels (for example the tool and source) and never the destination URL, request ID, or email address. Speed Insights measures page performance under Vercel's own terms.
External destinations
GitHub repositories, tool providers, and future payment providers operate under their own privacy terms. A disclosed affiliate route may identify Agentic Income as the referrer; the recommendation standard remains available on the Trust page.
Current runtime state
The no-secret readiness page shows whether intake, paid checkout, and analytics forwarding are configured without exposing credentials.