Information collected
We process your name, email, username, optional profile image and coaching bio, primary sport, time zone, communication preferences, sign-in identity, login timestamps, subscription state, organization membership, saved plays, formations, playbooks, scouting records, and call sheets. Profile images are stored in private object storage and served only to the authenticated account. If password access is enabled, we store only a salted password hash plus short-lived, hashed reset and session records; plaintext passwords and reset tokens are never stored. Community submissions keep the uploader identity private for safety enforcement even when the public post is anonymous; public contact details appear only when the uploader chooses contact mode. Stripe processes website payment details; Playbook by AYCD does not store full card numbers. The initial Apple and Google Play releases do not offer Stripe checkout or direct customers to an external subscription purchase from inside the app.
When you use roster and organization features, we also store participant names, positions, optional height and weight, biographies, team and staff relationships, private organization messages and attachments, grade reports and eligibility information, player agreements and acknowledgements, scholarship award and renewal details, fundraiser goals and amounts raised, organization account records, and itineraries. These records are linked to the account or organization that manages them and, where supplied, the named participant. Uploaded film, photos, profile images, and organization files are stored or processed by the service providers needed to provide those features. Support requests, reports, and feedback include the information you choose to submit.
Runtime diagnostics can include the signed-in account email, platform, app version, page path, user agent, error message, and stack trace. We use these reports to investigate failures and maintain the app. Sideline Notes in the iOS app are stored on your device and are not sent to Playbook servers.
If you join the Playbook product mailing list, we store the email address you submit and the signup source so we can send product and development updates. Joining the mailing list is optional and does not create a coaching account.
Privacy-preserving product analytics records an allowlisted event name, page path, timestamp, and—when signed in—account email. When a visitor arrives from a marketing campaign, we may also store limited first-party attribution information such as UTM campaign parameters, a Meta click identifier, the landing path, and timestamps so a later trial or purchase can be connected to its original campaign. On selected public marketing and sign-in pages, the Meta Pixel may send PageView measurement and browser identifiers to Meta for campaign measurement. The Apple and Google Play apps do not load the Meta Pixel or capture advertising attribution. First-party feature usage events and runtime diagnostics may still be collected in those apps. The Meta Pixel is not loaded inside the private coaching workspace, and Playbook by AYCD suppresses browser Pixel loading when a supported Global Privacy Control signal is present. Playbook by AYCD does not expose payment-card details to advertising platforms.
How information is used
Information is used to authenticate users, provide private coaching workspaces, enforce subscription and staff limits, process billing events, prevent abuse, recover data, improve reliability, measure the effectiveness of marketing campaigns, and respond to support, refund, or legal requests. If server-side advertising measurement is enabled, limited conversion signals may be sent to the applicable advertising platform. Customer email is cryptographically hashed before use in Meta server-side event matching, and Stripe remains the source of truth for whether a paid purchase occurred. Community titles, descriptions, diagrams, and embedded metadata are automatically screened for unsafe language, sensitive data, and image references; held submissions may be reviewed by authorized administrators. When you block a Community uploader, we store the private relationship between your account and the uploader so all current and future approved submissions from that coach remain hidden from you. Neither account's email is exposed through the block control.
Sharing, retention, and security
Information is shared only with infrastructure, payment, communications, and advertising measurement providers needed to operate and measure the service, with approved members of your organization as you direct, or when required by law. Advertising measurement is limited to campaign and conversion attribution; full payment-card information is never shared by Playbook by AYCD. Access decisions and ownership checks are enforced on the server.
Records are retained while an account is active and as needed for billing, attribution, fraud prevention, disputes, and legal obligations. Before completing an account or organization erasure, Playbook creates and verifies a deletion-scoped application-data snapshot inside its protected database. That snapshot cannot be downloaded or restored and has a purge deadline exactly 30 × 24 hours after the erasure completes. An hourly control removes it at or after that deadline and records durable hash-and-time evidence only; an outage can delay, but never advance, that verified purge. Authentication secrets and provider media bytes are excluded from this snapshot and are removed through their own governed deletion paths. Existing database backups that may contain the erased scope are restore-suppressed and scheduled for verified object-storage purge no later than that deadline.
Your choices
You can report objectionable Community content and block its uploader inside the app. Blocking hides that coach's current and future Community uploads from your account without notifying the coach or revealing an anonymous identity. You can use the in-app and public Delete Account page to permanently remove your coaching account and associated coaching content. You can also request correction, deletion support, a refund review, or an investigation through the report form. The 30-day deletion snapshot is a non-restorable safety record, not an undo period. Limited billing, attribution, fraud-prevention, security, and legal records may be retained separately when required. In particular, a signed organization-contract acknowledgement and its acknowledger identity may remain as legal evidence for the applicable obligation or dispute period; it cannot restore account access.
Playbook product mailing-list messages will include a way to unsubscribe. You may also ask the site administrator to remove your mailing-list email.