Privacy planning for readers, creators, royalty splits, payouts, and audiobook access.

Information we may collect

Account details, contact information, reader library activity, listening progress, bookmarks, purchases, reviews, creator profile details, payout setup status, and admin support history may be collected when the platform is fully built.

Reader data

Reader accounts may store purchased audiobooks, listening progress, bookmarks, saved titles, reviews, cart activity, order history, membership status, and support requests.

Creator data

Author, narrator, publisher, and rights holder accounts may store public profile details, uploaded title metadata, royalty split participation, payout readiness, referral links, dashboard activity, and support history.

Royalty and payout data

Royalty-splitting requires records for sales, refund status, payout eligibility, payout holds, participant approvals, tax or verification status, and payout provider references. Sensitive payout details should be handled by secure third-party providers and server-side systems.

Payment data

Real payment processing should be handled by a secure payment provider. Sapphyre Dominion should not store raw credit card details in frontend code or unsecured databases.

Audio and usage data

The platform may track listening progress, playback position, device resume state, chapter progress, streaming access checks, and download eligibility when those features are enabled.

Support and contact data

Messages sent through support or contact pages may include name, email, account type, order details, title references, rights questions, payout questions, and technical issue reports.

Cookies and analytics

The production site may use cookies, session storage, local storage, analytics, fraud prevention, and authentication tokens. Optional analytics should be clearly disclosed before launch.

How information may be used

Information may be used to operate accounts, deliver purchased audiobooks, process orders, calculate royalty lines, support payouts, prevent fraud, resolve support tickets, improve the platform, and comply with legal obligations.

How information may be shared

Information may be shared with service providers needed for hosting, payments, payout onboarding, email delivery, analytics, fraud prevention, storage, support, and legal compliance. Creator royalty reports may show relevant participant and title-level payout information.

Retention

Some records may need to be retained for accounting, tax, fraud prevention, royalty audits, rights disputes, refunds, and legal compliance. The final policy should define retention periods by data type.

User choices

Users should be able to manage account details, communication preferences, public profile information, and certain privacy settings. Data deletion requests may be limited by royalty, tax, accounting, dispute, or legal retention requirements.

Readers

Privacy focus: library activity, purchases, listening progress, bookmarks, reviews, and support history.

Authors

Privacy focus: public profile details, title ownership, royalty participation, sales reporting, payout readiness, and referral attribution.

Narrators

Privacy focus: voice samples, narration credits, royalty-share agreements, payout readiness, and public profile visibility.

Publishers

Privacy focus: catalog management, rights holder coordination, publisher splits, referral rules, and payout reporting.

Admins

Privacy focus: permission-controlled access to user records, reports, payout holds, refunds, royalty audits, and account reviews.