1. What we collect

Account data: email address, hashed authentication credentials, display name, and the workspace(s) you create or join.

Provider data: league rosters, schedules, transactions, matchups, draft results, settings, and public player identifiers fetched through a supported connection. Yahoo is the primary web-beta provider; Sleeper is conditional beta; Fantrax requests are reviewed separately and are not a public connector. We pull only what is required for the surfaces you use.

Usage data: pageviews, feature interactions, decision events, and errors may be recorded in application logs, the product database, or an environment-configured analytics service. We do not sell these events or use them for third-party advertising.

Billing data: paid-plan reservations during beta do not require card details. Vandly is the intended processor, pending acceptance and integration checks. If checkout becomes commercially live, hosted payment fields will be handled by the named processor and card details will not be stored by Pick Pilot.

2. How we use it

To run the Service: compute analytics, generate projections, drive AI features, deliver email, render the UI, and bill paid subscriptions.

To improve the Service: aggregated, de-identified usage metrics inform roadmap priorities (for example: which surfaces are visited most, which features are abandoned, which queries time out).

We do not sell personal data. We do not use your data to train third-party models. AI-backed features should pass only task-relevant league context to the configured provider and exclude provider credentials. Provider retention and training terms must be verified operationally before GA; contact us for the current subprocessors for a specific beta cohort.

3. Third-party processors

Pick Pilot uses application infrastructure and contracted processors that can vary by environment. The current or intended categories include:

· Vandly (intended payment processing and subscription billing, not active until acceptance). · Resend (transactional and digest email delivery). · Yahoo and Sleeper (provider connections you authorize or request); Fantrax only for an accepted private-beta method. · OpenAI (configured AI surfaces). · Hosting, database, cache, error-reporting, and product-analytics vendors enabled for the target environment.

We require appropriate processor terms before GA. Optional integrations remain disabled when their production configuration is empty. We do not use third-party advertising trackers. Material processor changes will be reflected here.

4. Retention

Account deletion: requesting deletion revokes sessions immediately and starts a seven-day cancellation window. After that window, the purge worker scrubs readable account identifiers and marks the account deleted. Some relational rows remain pseudonymized to preserve security and referential audit integrity; this is not a 90-day recovery promise.

Aggregated analytics: retained indefinitely in de-identified form. These records cannot be linked back to an individual user.

Operational logs: 30-day target. AI event metadata: 90-day target before deletion or aggregation. Automated enforcement and production evidence for these targets are GA gates.

Backups: encrypted 30-day rotation target, subject to operational verification. Security, deletion-request, and future billing audit records may be retained for up to 24 months or longer where law requires, with identifiers minimized. You can request export or deletion from Settings → Data & Account.

5. Children

The Service is not directed to children under 13. We do not knowingly collect personal information from users under 13. If you believe a child has provided us personal information, contact privacy@pick-pilot.com and we will delete it.

6. Your rights

Depending on where you live, you may have rights to access, correct, port, restrict, or delete your personal data, and to object to certain processing. To exercise any of these rights, email privacy@pick-pilot.com from the address on file. We will respond within 30 days and may verify your identity before fulfilling a request.

Residents of the EEA, UK, or Switzerland: our lawful bases for processing are contract performance (running the Service you signed up for) and legitimate interests (improving the Service and preventing abuse).

7. International transfers

Beta data may be processed in the United States and in locations used by our contracted processors. Where legally required, international transfers must use an approved transfer mechanism such as Standard Contractual Clauses; processor and residency review is a GA gate.

8. Security

Data is encrypted in transit (TLS 1.2+) and at rest. Provider OAuth tokens are encrypted at the application layer using libsodium sealed boxes; refresh tokens are rotated automatically. Authentication sessions are short-lived and rotated on privilege change. We follow the principle of least privilege for internal access and log all admin operations. Report vulnerabilities responsibly: security@pick-pilot.com.

9. Changes

We may update this Policy. Material changes will be announced in-app at least 14 days before taking effect, and the effective date at the top of this page will be updated. Continued use of the Service after the new effective date constitutes acceptance.

10. Contact

Privacy questions: privacy@pick-pilot.com. General questions: hello@pick-pilot.com.