Sparky Scout collects account and onboarding information such as team name, billing email, Slack workspace identity, plan selection, and setup status.

When a workspace connects Slack, GitHub, Linear, Discord, Otter, or Fireflies, Sparky Scout may process messages, threads, files, issues, pull requests, CI signals, meeting metadata, transcripts, and other project records authorized by the workspace.

We also collect operational logs, audit records, subscription status, and usage counters needed to run and secure the service.

We use data to answer project questions, summarize delivery status, detect blockers, draft reports, maintain setup checklists, route billing, and improve reliability.

Workspace content is not sold. We do not use customer workspace content for advertising.

Sparky Scout stores workspace records in Cloudflare services, including D1, R2, Vectorize, Durable Objects, Workers KV, and queues where applicable.

OAuth tokens and sensitive provider credentials are encrypted before storage. Access is restricted to operators who need it for support, security, or incident response.

We retain workspace data while the workspace is active and for the configured plan memory window. Public pricing currently describes memory windows from 14 days to 1 year depending on plan.

Customers may request workspace deletion or export support through support@sparkyscout.com.

We share data with sub-processors only as needed to operate Sparky Scout, including infrastructure, payments, connected integrations, and AI model routing providers.

Connected tools such as Slack, GitHub, Linear, Discord, Stripe, Otter, and Fireflies process data under their own terms when customers authorize those integrations.

Depending on location, users may request access, correction, deletion, restriction, portability, or objection support.

Because workspace data belongs to the customer organization, we may route some requests to the workspace owner for verification.