Privacy Policy
Last updated: June 16, 2026
SwiftAlerts ("SwiftAlerts", "we", "us") provides a market-intelligence data endpoint that AI agents can query. This policy explains what information we collect, why, and how we handle it. We keep this deliberately short and plain.
Information we collect
- Account email. When you sign in with Google, we receive your email address and basic profile (name, avatar) to identify your account and gate access.
- Access token. We generate and store an MCP API token tied to your account so your agent can authenticate to the endpoint.
- Things you submit. Access requests and any analyst handles you suggest for coverage.
- Technical logs. Standard request metadata (IP address, user agent, timestamps) processed by our hosting provider for security, abuse prevention, and reliability.
The market, financial, and infrastructure data served through the endpoint is aggregated from public and third-party sources and is not personal information about you.
How we use it
- To authenticate you and operate the service.
- To secure the endpoint, enforce rate limits, and prevent abuse.
- To review access requests and respond to messages you send us.
We do not sell your personal information, and we do not use it for third-party advertising or cross-site tracking.
Service providers
We rely on a small number of processors to run the service:
- Google — authentication / sign-in.
- Cloudflare — hosting, CDN, and request security.
- Turso — the database that stores account and application data.
These providers process data on our behalf under their own terms and security practices.
Storage in your browser
The dashboard stores a sign-in session and your access token in your browser so you stay logged in. Clearing your browser storage signs you out.
Retention & your choices
We retain account data while your account is active. You can ask us to delete your account and associated data, or to access a copy of it, by emailing the address on our contact page. Revoking or regenerating your token immediately invalidates the old one.
Security
Access is invite-gated and tokens are stored hashed. No system is perfectly secure, but we limit what we collect and restrict who can reach it.
Changes
We may update this policy as the service evolves. Material changes will be reflected by the "last updated" date above.
Contact
Questions about privacy? Reach us via the contact page.