Proposed effective date: To be set at launch
1. Information the finished site may collect
Your email, membership level, payment status, saved Plays, reading progress, support messages, and basic security or activity records may be needed to run the service.
2. Why that information may be used
To log members in, open the content they paid for, keep saved items available across devices, improve the library, prevent misuse, answer support requests, follow the law, and explain important account or payment changes.
3. Payments
A future payment provider should process card details directly. The Playbook should retain transaction references and access status. It should not retain full card numbers. Provider terms and subprocessor details must be added before launch.
4. Sharing
Personal information should not be sold. Limited data may be shared with service providers that operate hosting, identity, email, analytics, support, and billing, or when required by law. A finalized list belongs in the production notice.
5. Retention and security
Production records should be retained only as long as needed for service, security, accounting, and legal purposes. Reasonable safeguards reduce risk but no system can promise absolute security.
6. Your choices
Members should be able to update account information, manage communications, cancel renewal, and request access or deletion where applicable. The launch product needs a verified request process.
7. Children and changes
The service is intended for adults and is not designed to collect information from children. Material notice changes should be dated and communicated clearly.
8. Contact
Privacy questions and requests can be routed through the Contact page until a dedicated privacy address is established.