Keep business useful. Keep data minimal.
This is an administrative directory, not a place to store sensitive records.
Information you choose to provide
Newsletter requests contain an email address and consent status. Workflow submissions and sponsor applications contain your contact email and the information you enter. Your email is not published in the directory. Do not provide patient information, customer records, account credentials, payment card details, or confidential business data.
How information is used
Requests and applications are stored for operator review. Newsletter activation uses a confirmation token. Confirmation emails and newsletters require approval before dispatch through Resend. An approved sponsor offer may open Stripe-hosted checkout; card details are handled by Stripe, not our form. Neither a submission nor a sponsor application adds you to the newsletter. An operator may explicitly approve copying a sponsor business name, contact email and application review status into the separate AgentOps Hub workspace in HighLevel for CRM tracking. That copy does not enroll the contact in marketing or send a message.
Analytics and operational data
The application supports a small allowlist of aggregate events such as template downloads and successful form submissions. It does not send your search text, form contents, or email to analytics. The application does not set advertising cookies. Where enabled, analytics respects Do Not Track and Global Privacy Control signals. Hosting providers may retain request logs for security and operations. Rate-limit identifiers are hashed; the application does not store raw IP addresses in its analytics records.
Services and storage
This deployment uses Vercel hosting and Neon PostgreSQL, with Resend email, Stripe payments and HighLevel CRM when configured by the operator. Local preview stores data on the operator's computer. Automation research uses public sources and does not need your email. These providers' own privacy terms apply to the data they process.
Control your subscription
Confirmation is required before a subscriber becomes active. Every newsletter includes an unsubscribe link. Unsubscribing prevents future newsletter sends; minimal suppression information may remain to honor that choice. Contact the operator using the originating newsletter reply channel for data access or deletion requests. Until that reply channel is configured, do not use the service to submit sensitive information.
Retention and security
Private contact data is accessible through the protected operator dashboard. The operator is responsible for reviewing queued records, deleting data no longer needed, maintaining backups, and configuring deployment access. No service can promise absolute security. A production operator must provide a working contact channel and finalize retention periods before a public launch.
Policy last updated October 24, 2026. This policy describes the MVP's implemented data flows and must be reviewed when services or business practices change.