Security
Playbook treats the security of its users, archive, and systems as an ongoing responsibility.
Last reviewed: 4 September 2026
Security Notice: Fraud & Impersonation
Playbook takes fraud, impersonation, deceptive communication, phishing attempts, and malicious lookalike activity seriously. We are committed to protecting users from behavior intended to mislead, deceive, or falsely represent Playbook.
Playbook will never request sensitive information such as passwords, payment details, authentication credentials, or account access through unsolicited and unverified messages.
Official communications from Playbook are conducted only through the following channels:
- our verified email address: hello@playbook.cam;
- our official Playbook.cam Contact page;
- the official Playbook application distributed through the Apple App Store and Google Play Store;
- our official social media channels recorded below:
- Instagram: @heyplaybook
- Facebook: Playbook
- YouTube: Playbookcam
- X / Twitter: @playbookcam
While these are Playbook's official channels, users should remain cautious of accounts using similar names, misspellings, slight variations, copied branding, or automated spam accounts designed to appear affiliated with Playbook. We denounce impersonation, spam, deceptive lookalike accounts, and any behavior intended to mislead users, misrepresent Playbook, or falsely act on our behalf.
Any communication claiming to represent Playbook outside the official channels listed above should be treated as unverified. Do not provide passwords, payment information, authentication codes, account access, or other sensitive information in response to suspicious communication.
If you receive suspicious communication or believe someone is attempting to impersonate Playbook, do not engage. Contact us directly through our official Contact page and include any relevant details or evidence that may help us review the matter. We take these reports seriously and may take appropriate action, including investigation and reporting the activity to relevant platforms or authorities where necessary.
Playbook is not responsible for third-party impersonation, phishing attempts, or fraudulent activity conducted outside our official platforms. For your safety, do not provide financial information, account access, or sensitive credentials through third-party applications or unofficial channels when asked to proceed on Playbook's behalf.
1. Our Approach
Playbook is designed to reduce unnecessary exposure of user data and administrative access while preserving the availability and integrity of the Service.
Our security approach includes, where applicable:
- authenticated access to protected features;
- access controls for database, storage, and administrative functions;
- encrypted network transport through HTTPS/TLS;
- restricted handling of service credentials and secrets;
- separation between public content and protected operational data;
- logging, abuse prevention, and moderation controls used to detect or respond to misuse;
- dependency, infrastructure, and service updates as the platform evolves.
No internet service can guarantee perfect security. Playbook reviews its systems and practices as the product, infrastructure, and threat environment change.
2. Account Security
Users are responsible for protecting their account credentials and devices.
We recommend using a strong, unique password, keeping devices and software updated, and never sharing authentication credentials with another person.
If you believe your Playbook account has been compromised, contact us as soon as reasonably possible.
3. Reporting a Security Issue
If you believe you have discovered a security vulnerability affecting Playbook, please report it privately to:
Subject:
Security Report
A useful report should include, where possible:
- the affected page, feature, endpoint, or system;
- a clear description of the suspected vulnerability;
- steps that allow us to understand or reproduce the issue;
- the potential security impact;
- any screenshots, logs, or supporting evidence that can be shared safely;
- a way to contact you if clarification is needed.
Please do not include passwords, authentication tokens, private keys, or unrelated personal data in a report.
4. Responsible Testing
Good-faith security research should avoid causing harm to Playbook, its users, or third parties.
Please do not:
- access, alter, download, or disclose another person's data without authorization;
- disrupt the availability of the Service;
- perform denial-of-service or destructive testing;
- use social engineering, phishing, or physical intrusion;
- introduce malware or intentionally persistent access;
- continue testing after you have confirmed a vulnerability in a way that could increase harm.
If testing could affect real users or data, stop and report the issue instead.
5. Third-Party Infrastructure
Playbook relies on third-party infrastructure and service providers for parts of its operation. Those providers maintain their own security programs and controls.
Playbook remains responsible for configuring and using those services appropriately within the parts of the Service we control.
6. Security and Privacy
Security and privacy are related but distinct.
For information about how Playbook handles personal data, retention, user rights, and privacy requests, see the Privacy Policy.
For platform rules, prohibited behavior, moderation, and abuse handling, see the Community Standards and the Trust Center.
Contact
Security questions and vulnerability reports may be sent to:
Subject:
Security Report
Playbook
An Artist's Archive