FoxPlot Privacy

Privacy Policy

This draft explains how FoxPlot should handle account data, reading activity, creator submissions, advertiser campaigns, safety settings, privacy requests, and future platform analytics.

Draft policy notice: this page is a planning draft and should be reviewed by qualified legal counsel before public launch, mobile app submission, or global availability.

Open Privacy Requests Back to Home

Information FoxPlot may collect

FoxPlot may need to collect information required to operate accounts, libraries, creator portals, advertiser portals, moderation workflows, safety settings, payments, and support.

Account details such as name, email, login provider, role, and settings.
Reader activity such as saved books, Listen progress, Watch activity, favorites, and content preferences.
Author details such as profile information, submissions, payout status, moderation history, and content metadata.
Advertiser details such as business identity, campaign submissions, billing status, placement preferences, and ad performance.
Safety and compliance information such as age profile, content warnings, reports, appeals, privacy requests, and admin decisions.

How information may be used

FoxPlot should use information only for platform operation, safety, personalization, payments, moderation, analytics, support, legal compliance, and user-requested actions.

To provide reading, listening, watching, library, author, and advertiser features.
To enforce content ratings, age gates, youth-safety rules, ad restrictions, and moderation decisions.
To process subscriptions, campaign billing, author payouts, refunds, and financial records through approved providers.
To respond to reports, appeals, privacy requests, support requests, and legal requests.
To improve performance, reliability, recommendations, accessibility, and platform safety.

Ads and affiliate tracking

FoxPlot may support sponsored placements, advertiser campaigns, affiliate links, and campaign analytics. Ads should be clearly labeled and should not appear inside the digital book reading experience.

Ads may appear in Listen and Watch experiences when allowed by policy.
Affiliate links and sponsored content should be labeled clearly.
Authors should control which approved ad opportunities they activate on eligible content.
Ad personalization and ad-free subscription options should be handled through account settings.

Children and younger audiences

FoxPlot must protect younger audiences by enforcing ratings, maturity restrictions, content warnings, guardian controls, and backend age-safety checks before production launch.

Youth profiles should not be able to access mature or adult-only content.
Age-gated content should be blocked server-side, not only hidden on the frontend.
Parents or guardians should have a way to request child safety and privacy review.
Mature content, adult content, and sensitive content should be tagged and reviewed before distribution.

Privacy requests and account deletion

Users should be able to request data export, account deletion, data correction, ad preference review, content history deletion, or child safety/privacy review.

Identity verification may be required before fulfilling sensitive requests.
Some records may need to be retained for payment, tax, fraud-prevention, dispute, safety, legal, or audit reasons.
Deletion workflows should be logged and handled carefully before production.
Users should receive confirmation and status updates for privacy requests.

Fox Plot

Loading your story world...

Preparing your books, author library, reader portal, marketplace, and creator tools.

This draft explains how FoxPlot should handle account data, reading activity, creator submissions, advertiser campaigns, safety settings, privacy requests, and future platform analytics.

Draft policy notice: this page is a planning draft and should be reviewed by qualified legal counsel before public launch, mobile app submission, or global availability.

Information FoxPlot may collect

FoxPlot may need to collect information required to operate accounts, libraries, creator portals, advertiser portals, moderation workflows, safety settings, payments, and support.

Account details such as name, email, login provider, role, and settings.

Reader activity such as saved books, Listen progress, Watch activity, favorites, and content preferences.

Author details such as profile information, submissions, payout status, moderation history, and content metadata.

Advertiser details such as business identity, campaign submissions, billing status, placement preferences, and ad performance.

Safety and compliance information such as age profile, content warnings, reports, appeals, privacy requests, and admin decisions.

How information may be used

FoxPlot should use information only for platform operation, safety, personalization, payments, moderation, analytics, support, legal compliance, and user-requested actions.

To provide reading, listening, watching, library, author, and advertiser features.

To enforce content ratings, age gates, youth-safety rules, ad restrictions, and moderation decisions.

To process subscriptions, campaign billing, author payouts, refunds, and financial records through approved providers.

To respond to reports, appeals, privacy requests, support requests, and legal requests.

To improve performance, reliability, recommendations, accessibility, and platform safety.

Ads and affiliate tracking

Ads may appear in Listen and Watch experiences when allowed by policy.

Affiliate links and sponsored content should be labeled clearly.

Authors should control which approved ad opportunities they activate on eligible content.

Ad personalization and ad-free subscription options should be handled through account settings.

Children and younger audiences

FoxPlot must protect younger audiences by enforcing ratings, maturity restrictions, content warnings, guardian controls, and backend age-safety checks before production launch.

Youth profiles should not be able to access mature or adult-only content.

Age-gated content should be blocked server-side, not only hidden on the frontend.

Parents or guardians should have a way to request child safety and privacy review.

Mature content, adult content, and sensitive content should be tagged and reviewed before distribution.

Privacy requests and account deletion

Users should be able to request data export, account deletion, data correction, ad preference review, content history deletion, or child safety/privacy review.

Identity verification may be required before fulfilling sensitive requests.

Some records may need to be retained for payment, tax, fraud-prevention, dispute, safety, legal, or audit reasons.

Deletion workflows should be logged and handled carefully before production.

Users should receive confirmation and status updates for privacy requests.