DATASTAM STARWELL

Privacy Policy

LAST UPDATED: JULY 2026

Starwell is built by Datastam (Blue Green Yellow Inc., Toronto, Canada). Starwell serves public official statistics; the service itself is designed to need very little of your data. This page states exactly what we collect and why.

What we collect

• Waitlist and update signups: your email address and, if you choose to provide them, a short note about what you are building and what data you need. Used to grant access, send occasional product updates, and prioritize the connector queue. Never sold or shared for advertising.
• API and MCP usage metadata: for each request we log the endpoint or tool called, the data source and series requested, response latency, an API key identifier when a key is used, and a one-way hashed network identifier for anonymous rate limiting and abuse prevention. We do not log request contents beyond this, and we do not build advertising profiles.
• Questions sent to the answer endpoint: the question text is processed to compute the answer and may be cached (with its computed result) so repeated questions are served faster. Do not include personal or confidential information in questions.
• API keys: stored only as cryptographic hashes. We cannot recover a lost key; we issue a new one.

What we do not collect

• No personal data beyond the above. Starwell serves aggregate official statistics and never handles microdata about individuals.
• No third-party advertising or analytics trackers on this site.
• No sale of any user data, to anyone, ever.

Processors we rely on

Infrastructure providers process data on our behalf: hosting (Railway), database and storage (Supabase), model inference for the answer endpoint (Anthropic), and email delivery (Resend). Each receives only what is needed to provide its function.

Retention

Waitlist entries are kept until you ask to be removed. Usage metadata is kept in aggregate for capacity planning and the connector demand map; request-level records are pruned on a rolling basis. Cached answers expire automatically when the underlying official data is revised or on a fixed schedule.

Your choices

Email hello@datastam.com to unsubscribe from updates, delete your waitlist entry, revoke an API key, or ask what we hold about your email address. We respond within 30 days.

Changes

We will update this page when practices change and adjust the date above. Material changes affecting API users are announced through the update list.