Platform trust / Data ownership
Your data, always yours: data ownership and portability on Publish360.
How Publish360 gives publisher teams direct access to reader, purchase, content, entitlement and engagement data in standard, usable formats.
Scope and review note
This guide describes Publish360 data-access and export capabilities. It is not legal advice and does not replace review of data-controller roles, retention, security, contractual terms or transition arrangements for a specific deployment.
01 / The guide
01
No lock-in. No surprises.
A publisher platform should help a team build a direct reader relationship, not make that relationship difficult to inspect, reuse or move. Publish360 is designed so that the data and content a publisher brings to the platform remain accessible to the publisher’s authorised team. The aim is simple: make routine access ordinary, not a negotiation that only begins at contract renewal or exit.
- Reader accounts, including names, email addresses, registration dates and communication preferences.
- Purchase history, including titles, dates, amounts and promotional codes used.
- Subscription records, including tier, start date, renewal history and current status.
- Reading and listening progress, completion status, last position and time spent per title.
- Ingested content files, including EPUB, PDF and audiobook assets as supplied.
- Usage analytics, including monthly active users, sessions, device breakdown and engagement measures.
- Entitlement records showing which reader can access which content through purchase, subscription, gift or institutional access.
02
Access the information your team needs, directly.
Authorised publisher users can access the relevant information from the Publish360 admin dashboard. The working model is designed for self-service access: teams should not need to raise a support ticket or wait for a particular contract event to retrieve operational data that they need to serve readers, analyse performance or connect their own systems.
- Export reader and subscriber lists to CSV.
- Filter transaction and subscription reports by date range, title or tier before downloading.
- Export reading and listening engagement data at an aggregate or individual-reader level.
- Download content files from the content library.
- Export current entitlement records by reader and access basis.
- Retrieve historical analytics by month, quarter or a custom reporting range.
03
Use formats that travel.
Portability is not merely being able to see data on a screen. It means receiving information in formats a publisher can actually use in its own CRM, analytics environment, reporting workflow or a future platform. Publish360 exports operational data in standard, machine-readable formats and preserves original content assets for reuse within the publisher’s rights and agreements.
- CSV and JSON exports for operational, reader, transaction, entitlement and analytics data.
- EPUB, PDF and audio files retained in their supplied publishing formats.
- Exports designed to be usable without proprietary conversion tools or special software.
- A practical foundation for reporting, system integration and transition planning.
04
If the operating model changes, take the information with you.
A technology decision should remain reversible. If a publisher moves to another platform, it should be able to take the necessary data and content with it rather than discover a technical or commercial lock-in at the point of change. Publish360’s transition approach includes reasonable technical assistance, documentation of available data structures and support for the receiving technical team, so that reader continuity can be planned rather than improvised.
- Keep an up-to-date export and data-structure record as part of normal platform governance.
- Define ownership, data-controller roles, security and retention responsibilities in the deployment agreement.
- Test a representative export before it is urgently needed.
- Plan reader communication, entitlement continuity and receiving-platform responsibilities before any transition date.
02 / Take this to the meeting
Data portability review checklist
Use this as a working agenda with decision owners, not a box-ticking exercise.
- 01Authorised publisher users can identify where reader, purchase, subscription, engagement, entitlement and content information is accessed in the admin dashboard.
- 02The publisher has tested representative CSV and JSON exports using the teams and systems that will rely on them.
- 03Content assets, metadata and format records are documented alongside the publisher’s own source files and rights information.
- 04The publisher has confirmed its own data-controller, retention, security and access responsibilities for the deployment.
- 05The transition plan identifies reader communications, entitlement continuity, data transfer ownership and the receiving platform’s technical requirements.
- 06Data structures, support routes and reasonable transition-assistance arrangements are recorded in the relevant agreement and operational documentation.
03 / Questions
09 Questions publishers ask
Publish360 provides access to reader and subscriber lists, transaction and subscription records, engagement data, entitlement records, analytics and ingested content files. The exact fields and permissions should be confirmed for the publisher’s deployment and authorised users.
The platform is designed for authorised publisher users to access routine data through the admin dashboard, including exports for reader lists, transactions, subscriptions, engagement, entitlements, analytics and content assets.
Operational data is available in standard formats such as CSV and JSON. Ingested content remains available in its supplied publishing format, such as EPUB, PDF or audio, subject to the publisher’s rights and deployment arrangements.
The portability approach is designed to make transition planning straightforward: retain usable exports and content assets, document data structures, and plan entitlement continuity with the receiving platform. Eden provides reasonable technical assistance during a transition, as set out in the relevant arrangements.
More questions? Answers arranged by role — finance, IT, editorial, marketing, operations.
04 / Sources and next reading
