Privacy Policy for JM e-Stories and JM Reader
This Privacy Policy explains how JM e-Stories and JM Reader collect, use, store, protect, and disclose information when you use our website, reader experience, publishing tools, payment features, Android/PWA installation flow, and support routes. It is designed to serve as a public privacy policy page for website visitors, readers, authors, advertisers, and Google Play Store review.
1. Who this policy applies to
This policy applies to users who browse JM e-Stories, sign in to access protected reading features, install JM Reader, purchase stories, submit manuscripts, manage author profiles, advertise content, or contact support through our services.
2. Information we may collect
- Account and sign-in details: email address, optional display name, and verification code flow details used to confirm access.
- Reading and library details: reading progress, saved preferences, offline reading choices, installed web app assets, and related device-side storage needed for reader continuity.
- Purchase and payment details: purchased story identifiers, transaction references, sender names, payment order references, wallet details, payout details, and verification information required to confirm payments and author royalties.
- Publishing and submission details: author names, biographies, emails, manuscript files, cover images, descriptions, categories, pricing details, and other information voluntarily submitted for publication or promotion.
- Advertising and sponsored content details: business or creator contact details, campaign information, creative materials, duration preferences, and related approval notes.
- Technical and usage data: browser type, device type, general diagnostic information, request logs, page routes, and performance information required to keep the service working and secure.
- Support and moderation details: messages you send to support, moderation decisions, fraud review notes, or compliance notes related to account safety, payments, and content handling.
3. How we collect information
We collect information directly from you when you sign in, submit content, complete a purchase, install or use JM Reader, save reading progress, contact support, or otherwise use the service. We may also collect limited technical data automatically through browser requests, caching, storage, security logs, and payment confirmation flows.
4. How we use information
- To create and manage reader access, verify sign-ins, and maintain your library or reading progress.
- To process purchases, confirm payments, prevent fraud, and support author royalty handling or payout workflows.
- To publish, review, moderate, and display stories, author pages, advertising materials, and related content.
- To provide support, answer inquiries, investigate abuse, enforce rules, and resolve technical problems.
- To improve app stability, reader continuity, navigation, and installation experience across browser and Android/PWA contexts.
- To comply with legal obligations, platform rules, payment requirements, and content safety requirements.
5. Legal and operational bases for processing
We process data when it is necessary to provide the services you request, to maintain the security and operation of the platform, to comply with payment and legal obligations, and where applicable on the basis of your consent or your decision to submit content for publication.
6. Payments, purchases, and payout processing
JM e-Stories may support paid stories, payment verification flows, wallet or payout details for authors, and third-party payment pages or payment processors. When you use payment-related features, we may process payment references, order identifiers, payer names, mobile money details, status updates, or related verification information needed to confirm a purchase, release paid access, or process author-side settlement and records.
7. Device storage, cookies, local storage, and offline reading
JM e-Stories and JM Reader may use browser storage, cached files, service workers, or similar web technologies to keep you signed in, remember preferences, store reading progress, support offline reading behaviour, and improve performance. You can clear local browser storage from your device settings, but some reader continuity features may stop working until you sign in again.
8. When we may share information
- Service providers and infrastructure partners: where needed to host the website, run scripts, deliver sign-in or support workflows, or handle payment-related processing.
- Payment and settlement providers: where required to initiate, verify, reconcile, or document payment flows and author payouts.
- Public content display: when you intentionally publish stories, author profiles, adverts, editor listings, or other visible submissions.
- Legal, security, and fraud prevention reasons: when required to investigate misuse, enforce rules, protect users, or comply with lawful requests.
- Business continuity events: if the service structure changes in the future, subject to applicable law and appropriate notice where required.
9. What we do not do
- We do not claim to sell personal data as a product.
- We do not require precise location, microphone, or camera access for basic reading and browsing features.
- We do not publish private payment references, login codes, or support communications as public content.
10. Data retention
We keep information for as long as it is reasonably necessary to operate the service, maintain reader access, document purchases, support published content, resolve disputes, comply with financial or legal obligations, and protect platform security. Some device-side data may remain on your browser or installed web app until you clear it yourself.
11. Security
We use reasonable technical and organisational measures to protect information against unauthorised access, misuse, alteration, or loss. However, no website, online platform, or transmission method can guarantee absolute security, and you should also protect your own device, email account, passwords, and payment instruments.
12. Children and younger users
JM e-Stories is a general audience literary platform. If a child or younger user accesses the service, parents, guardians, and educators should help supervise the use of publishing, payment, and account features where appropriate. If you believe personal information was provided inappropriately, contact us so we can review the request.
13. Your choices and rights
- You may contact us to request access, correction, or deletion of account-related information, subject to legal and operational requirements.
- You may request removal or correction of submitted content that you own, subject to platform review and publication workflow rules.
- You may clear browser storage or remove an installed web app from your device.
- You may stop using the service at any time.
14. Account deletion and data requests
If you want to request deletion of your account data, stored profile data, or reader records that are not required for legal, fraud, payment, or security retention, contact us at [email protected] with enough information to verify your request. We may retain limited records where necessary to document completed purchases, resolve disputes, comply with law, or protect the platform.
15. Third-party links and platform pages
Our pages may link to app entry pages, payment pages, support routes, installation pages, or other third-party destinations. Their privacy practices may be governed by their own policies, and you should review those policies before using those services.
16. Google Play and Android distribution note
This Privacy Policy is intended to support public disclosure for JM Reader and JM e-Stories Android or web app distribution. If our app is distributed through Google Play, this policy should be used alongside the Google Play Data safety section and any in-app disclosures that may be required for permissions, user data, or platform-specific features.
17. Changes to this policy
We may update this Privacy Policy from time to time to reflect product changes, platform requirements, legal obligations, or operational improvements. The updated version will be posted on this page with a revised effective date.
18. Contact us
For privacy questions, data requests, publication concerns, or support matters, contact: [email protected].