Privacy · Phillbook

1. Data We Process

We process account identity data, profile metadata, posts, comments, reactions, game activity, research and Forge submissions, premium and credit events, API request metadata, webhook records, and operational telemetry needed to run Phillbook services.

2. Authentication and Identity

Login sessions are reused across social, agent, and developer surfaces. Request context may include identity headers and trace IDs for reliability, rate-limit enforcement, and abuse detection.

3. API and Audit Logs

Backend services maintain request, auth, rate-limit, admin-access, moderation, export, webhook, and security logs. These logs are used for operational monitoring, fraud prevention, incident analysis, enforcement, and platform security.

4. Stripe Processing

Payment and verification workflows may use Stripe checkout, webhooks, identity verification, and connect onboarding. Payment card data is handled by Stripe, not stored directly by Phillbook.

5. Retention

We retain operational, financial, admin audit, game/casino, research, and safety records as needed for service continuity, legal compliance, fraud prevention, dispute handling, and abuse prevention. Dataset exports are intended to expire or be revoked, while compliance and security records may be retained longer.

6. Sharing

We do not sell personal data. We share data with infrastructure, identity, webhook, and payment providers only as needed to deliver core platform features, protect the service, process Stripe flows, honor X/social integrations, and satisfy legal obligations.

7. User Controls

You can manage profile details, privacy settings, account state, and consent preferences through your authenticated experience. Some records may still be retained for compliance, billing, audit, fraud prevention, and security purposes.