Readpod / iOS
Privacy policy
How information is used, retained, and protected, and how to exercise your privacy choices.
Last updated: November 5, 2026 Effective date: November 5, 2026
This Policy covers Readpod for iOS and this official support website. The account, advertising, analytics and attribution disclosures apply across the Service where the described features are enabled. Platform-specific sections identify Apple and Google services and controls; a feature available on one platform is not necessarily available on the other.
Readpod is a fiction-reading application for iOS. This Privacy Policy explains how Readpod ("Readpod," "we," "us," or "our") collects, uses, discloses, retains, and protects information when you use the Readpod application and its related services (collectively, the "Service").
1. Who Is Responsible for Your Information
Readpod operates this service.
Contact Readpod through Settings > Help & Feedback in the app or the official Support Center.
2. Information We Collect
Readpod provides a guest reader account without requiring an email address, phone number or password to start reading. You can choose a supported third-party sign-in option, such as Google, Apple or Facebook, when offered in your version.
2.1 Account, sign-in and service identifiers
We process your reader account ID, guest status, installation and service identifiers, access and refresh credentials, and the profile information associated with your account. Profile information can include a display name, email address, avatar and email-verification status. Purchase-account identifiers and purchase credentials associate transactions with the correct reader account.
When you choose a supported third-party sign-in provider, the provider and Firebase Authentication process authorization credentials and identity information. Readpod receives and processes provider identifiers, a Firebase user identifier and ID token, and the email address, name and avatar made available by the provider. We send the relevant information to our servers to authenticate you, create or access your reader account, maintain your profile and support account recovery. Signing in can change the active reader account; it is not merely a temporary identity check. We do not receive your provider password.
We may associate an AppsFlyer installation identifier with guest registration or sign-in and use a Readpod account identifier in analytics and attribution as described in Section 5. A guest account and its identifiers are not necessarily anonymous personal data merely because no email address is required.
2.2 Reading and library activity
We process information needed to provide the reading experience, including:
stories added to or removed from your Library;
reading position, reading history, and recently read stories;
chapter access and unlock status;
reading preferences such as appearance, text size, and reader controls; and
genre preferences and reading activity used for personalized recommendations when that option is enabled.
Search terms are sent to return results. Readpod also stores up to eight recent searches locally by content language. You can clear them from the search page. Search and interaction events may also be processed as described in Section 5.
2.3 Purchases, subscriptions, Coins, and chapter unlocks
On iOS, purchases are processed by Apple through the App Store and StoreKit. On Android, Google Play purchases are processed by Google through Google Play Billing. We do not receive your full payment-card number or Apple/Google account password.
To verify a purchase, deliver Coins, prevent duplicate delivery, maintain your balance, and resolve purchase issues, we may process:
the App Store or Google Play product identifier;
Apple transaction identifiers, signed transaction information and storefront information; Google Play order identifiers, purchase tokens and purchase/acknowledgment status; and purchase dates and transaction status supplied by the applicable store;
the number of Coins purchased or used;
your Coin balance and Coin activity; and
the story, chapter, Coin price, and time associated with a chapter unlock.
In app versions and store regions that offer subscriptions, we may also process original and renewal transaction identifiers, subscription product and period, renewal and expiration information, offer eligibility or use, refund/revocation and billing status, and the subscription entitlement associated with your reader account, as made available by Apple or Google Play. We use this information to verify, provide and restore subscription access, reconcile renewals and refunds, prevent duplicate delivery or fraud, and handle support requests. This conditional disclosure does not mean subscriptions are available in every version or region; versions without subscriptions do not create subscription records merely because this Policy describes them. Relevant subscription transaction records follow the purchase-record retention rules in Section 9.
Where offered, tasks and rewarded ads grant only the benefit and amount shown after eligibility and completion are verified. An ad starting or closing alone does not guarantee a reward. Rewards are not cash and cannot be transferred or redeemed for cash. Long-book chapter unlocks and short-book whole-book access follow the displayed offer. Native-store or web checkout availability depends on version and region; the checkout identifies the payment provider, currency, price and renewal conditions. Returning from checkout does not itself prove payment: verification may still be pending. Do not pay again solely because verification is delayed; contact support with the transaction reference.
2.4 Notifications
Readpod uses Firebase Cloud Messaging (FCM) for push messaging, including on iOS through Apple Push Notification service (APNs). We process installation tokens and notification delivery and interaction information. Notification permission can be managed in device settings.
2.5 Feedback and diagnostic information
If you submit feedback, we process the message, the support category, and any context you choose to provide. Do not include payment-card details, passwords, or other unnecessary sensitive information in feedback.
We process technical errors and service events for reliability. Local diagnostic records may be kept with credential filtering, and diagnostic tools may let you copy or export records you choose to send to support. Error events may be reported through the analytics and service systems described in Section 5; this is separate from sharing a local diagnostic file.
2.6 Network and technical information
When the app communicates with our servers, the servers may process technical information such as IP address, request time, app version, operating-system version, device and network characteristics, requested endpoint, response status, and security events. We use this information only as needed to operate, secure, troubleshoot, and protect the Service. Routine operational logs are retained for up to 90 days. Records isolated for a confirmed security, fraud, or abuse investigation may be retained for up to 24 months, or longer when required by law or an active dispute.
When you post reviews, chapter or paragraph comments, replies or likes, we process the content, account identifier, nickname, avatar, related book or chapter and interaction information. Published content and your displayed profile can be visible to other readers. Blocking, hiding and reporting actions are processed to apply your choices or review abuse; hiding content does not necessarily delete it for everyone.
3. How We Use Information
We use the information described above to:
create, authenticate, recover, and protect your guest or signed-in reader account, and complete a supported third-party sign-in when you request it;
provide Discover, Library, search, reading, chapter access, and reading-history features;
synchronize reading progress, Library state, unlock entitlements, Coin balance, and purchase records;
verify App Store or Google Play transactions and deliver purchased Coins only once;
provide recommendations and, when enabled, personalize story discovery;
send notifications you have allowed;
answer feedback and troubleshoot technical or purchase problems;
detect abuse, fraud, unauthorized access, duplicate transactions, and violations of our Terms of Service;
measure app use, reading and purchase interactions, advertising performance and campaign attribution as described in Section 5;
maintain the reliability and security of the Service; and
comply with legal, accounting, tax, consumer-protection, and regulatory obligations.
Where applicable law requires a legal basis, we rely on performance of our agreement with you, compliance with legal obligations, our legitimate interests in operating and securing the Service, and your consent where consent is required. You may withdraw consent for optional processing at any time, without affecting processing that occurred before withdrawal.
4. Personalized Recommendations
Recommendations may use reading and interaction information as described in this Policy. Available advertising consent and system privacy controls apply to their stated purposes; they do not automatically erase reading records or disable all service measurement. Contact support for applicable privacy requests.
5. Advertising, Analytics, and Tracking
5.1 Google Analytics for Firebase / BeiDou and app-event measurement
Readpod uses Google Analytics for Firebase and our service-side event measurement to understand use of the app, maintain reliability and improve reading, purchases and advertising. Information can include app-instance and installation identifiers, a Readpod user ID, device and app characteristics, session information, user properties, and automatic and custom events. Custom events can describe sign-in outcomes, screen and search interactions, story and chapter interactions, reading progress and duration, Library actions, purchase flows, advertising requests, impressions, clicks and revenue, and operational errors. Event details can include content/product identifiers, transaction status, amounts, currency, timestamps and technical context relevant to the event.
We may set a Readpod user ID and user properties in Firebase Analytics. Measurement data can therefore be linked to an account and must not be treated as anonymous statistics. Event routing and available events depend on the enabled features; not every event is sent to every provider. See Google's privacy policy and Firebase privacy information.
5.2 AppsFlyer attribution and campaign links
We use AppsFlyer to measure installations, sessions, acquisition campaigns and relevant in-app events, and to open content from campaign links. AppsFlyer may process its installation identifier, a Readpod customer user ID, IP address, device and operating-system information, campaign/referrer and deep-link information, and custom event details such as interactions, conversions, purchases or revenue where those events are configured. Attribution information can be associated with account and event information to evaluate acquisition and campaign performance.
Platform identifiers may include the Android advertising ID (AAID/GAID) on Android and IDFV on iOS. IDFA on iOS is available only with the required Apple tracking authorization. Advertising identifiers are subject to device privacy controls and applicable consent requirements. See AppsFlyer's Services Privacy Policy and customer-data processing information.
5.3 Advertising and mediation partners
Readpod displays third-party advertising in enabled placements, which can include banners, native ads, interstitials and rewarded ads. We use advertising and mediation services including Google AdMob, AppLovin MAX and TopOn. Depending on the active mediation configuration, participating networks can include AppLovin, Liftoff Monetize (Vungle), Digital Turbine (Fyber), Meta Audience Network, Unity Ads, Mintegral and InMobi. Availability varies by version, region and advertising configuration.
These services may process advertising and app-installation identifiers, IP address and approximate location derived from it, device and app information, consent choices, ad requests, impressions, clicks, rewards and revenue information. We use this information to deliver and measure ads, award eligible rewards, limit repeat ads, prevent fraud and, where permitted and with any required consent, personalize advertising. Identifiers used by an advertising or mediation service may include a service-specific user or installation identifier. Advertising partners receive data necessary for these purposes; data use is subject to applicable law and your available privacy choices.
For provider details, see Google advertising information, AppLovin's privacy policy and TopOn's privacy policy. The applicable advertising consent message identifies participating vendors and choices where required.
5.4 Platform permissions and privacy choices
iOS: Apple's App Tracking Transparency permission controls tracking that requires that authorization, including access to IDFA. You can change it in iOS Settings. Refusing permission does not prevent core reading or purchasing, and does not by itself disable all analytics, contextual advertising or attribution processing that does not require that permission.
Android: Android does not use Apple's ATT prompt or IDFA. You can manage the advertising ID and available advertising privacy controls in your device's Google or privacy settings; available controls vary by Android version. Removing or restricting an advertising ID does not itself delete account data or stop all analytics and contextual advertising.
Recommendations may use reading and interaction information as described in this Policy. Available advertising consent and system privacy controls apply to their stated purposes; they do not automatically erase reading records or disable all service measurement. Contact support for applicable privacy requests.
5.5 The official website
Our static website pages do not embed Firebase, AppsFlyer, cookies, analytics scripts, advertising pixels, external fonts, or third-party scripts. Website hosting and content-delivery providers may process IP addresses, request times and browser/network information to deliver and secure the pages. Opening an external provider, refund or support link takes you to a separate service governed by its own policies. Your language preference is saved only in this browser’s local storage.
6. When We Disclose Information
We do not sell your personal information for money. We disclose information to analytics, attribution and advertising partners for the purposes described in Section 5. Where applicable privacy law treats a disclosure for personalized advertising as sharing or a sale, we provide the choices required by that law; contact Readpod support to exercise applicable rights.
We may disclose information only in the following circumstances:
Service providers. To hosting, infrastructure, security, customer-support, or other processors that need the information to provide services to us and are subject to appropriate confidentiality and data-protection obligations.
Google and Firebase. For Firebase Analytics, supported sign-in and Firebase Authentication, Android push delivery through FCM, Google Play purchases, and Google advertising services as described above.
AppsFlyer and advertising partners. For attribution, campaign links, event measurement and advertising as described in Section 5.
Other sign-in providers. To the provider you choose, such as Facebook, for authorization and account identity. See Meta's privacy policy.
Legal and safety reasons. When reasonably necessary to comply with law, regulation, legal process, or a valid government request; to enforce our agreements; or to protect the rights, safety, and security of users, the public, Readpod, or others.
Business transfers. In connection with a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, subject to applicable law and appropriate notice or safeguards.
At your direction. When you ask us to disclose information, such as the feedback text you submit to support.
We review service providers before granting access and limit their processing to the services they provide to us. Material changes to the categories of recipients will be reflected in this Policy.
7. On-Device Storage and Platform Recovery
Readpod uses app-local SQLite databases, preferences, cache files and secure credential storage, including iOS Keychain. Cached chapters, reading and listening positions, searches, settings and optional downloaded voice models support the app. Clearing caches may require content or voice files to be downloaded again. Reading and listening positions can be recorded separately. We do not promise iCloud Keychain synchronization, permanent offline access or account recovery after reinstalling.
8. International Data Transfers
Readpod is operated from Hong Kong. Our infrastructure and service providers may process information in Hong Kong and in other countries or regions where they operate. Those locations may have data-protection laws different from those where you live. Where required, we use contractual, organizational, or other legally recognized safeguards for international transfers.
9. Retention
We retain information only for as long as necessary for the purposes described in this Policy, including to provide the Service, maintain security and transaction integrity, resolve disputes, and comply with law. Our standard retention periods are:
Account and reading data: Reader identifiers, Library state, reading progress, reading history, recommendation preferences, Coin balance, and active chapter entitlements are kept while the account remains active. Following a completed account-deletion request, these records are deleted or de-identified from active systems within 30 days.
Purchase and financial records: App Store or Google Play transaction, Coin delivery, Coin activity, and paid chapter-unlock records needed for accounting, tax, charge, refund, and fraud review are retained for seven years from the relevant transaction, or longer if required by law or an active dispute.
Push notifications: An APNs or FCM token is kept until it becomes invalid, notification delivery is disabled for the device, or the account is deleted. Obsolete tokens are removed from active systems within 30 days after we identify them as obsolete.
Feedback and support: Feedback and its support context are kept for up to 24 months after the support matter is closed, unless a longer period is needed for a dispute, safety issue, or legal obligation.
Operational logs: Routine request and security logs are kept for up to 90 days. Records isolated for a confirmed security, fraud, or abuse investigation may be kept for up to 24 months or for the duration of a related proceeding.
Backups: Deleted information may remain in protected backups for up to 90 days before being overwritten, unless a longer period is required by law. Backup data is not restored to ordinary use after an account-deletion request.
Identity and measurement providers: Authentication, analytics, attribution and advertising records are retained according to the applicable processing purpose, configured retention and legal obligations. Account deletion includes requesting deletion of associated personal data processed on our behalf by service providers, subject to legitimate retention exceptions. Data that has been irreversibly anonymized is no longer associated with an identifiable account.
Hong Kong business and transaction records are retained for at least seven years where required. Other personal information is not kept longer than necessary for the purpose for which it was collected. At the end of the applicable period, information is deleted or de-identified unless continued retention is legally required.
10. Account Deletion
Account deletion is available in the app. A submitted request is not completed deletion; completed deletion is permanent.
Open Readpod → Me → Settings → Account & privacy. Choose Delete account, review the consequences, and confirm the request. A Deletion requested result means processing is pending. Follow the processing timeframe and completion information shown in the app.
If you cannot access the app, consult the official Support Center for account deletion assistance. Provide your Readpod ID and describe the access issue. We may need to verify account ownership.
Completed deletion removes the reader account and the account data we are not legally required to retain. It also clears account-related local data, including locally cached reading progress, Library entries, chapter entitlements, and credentials. Deletion permanently gives up remaining Coins, unlocked-chapter access, reading history, and other account state. Deleted accounts cannot be restored.
If an App Store or Google Play transaction is still pending or has been verified on the device but not yet delivered to the account, Readpod may require that transaction to finish before account deletion; contact support if it remains pending. This protects against losing a paid transaction or delivering it to a different account.
Some transaction, security, fraud-prevention, tax, accounting, or legal records may be retained as described in Section 9. Account deletion does not itself submit a refund request. App Store refunds follow Apple's process; Google Play refunds follow Google Play's process and applicable law.
Deleting your Readpod account or uninstalling the app does not itself cancel an App Store or Google Play subscription. Cancel through the store that bills you: Apple subscriptions or Google Play subscriptions. Restoring an eligible paid entitlement does not restore deleted account data. See the subscription terms.
Deleting Readpod does not delete your underlying Apple, Google or other provider account. We handle deletion of associated personal data held by us and request deletion by providers processing it on our behalf, subject to the retention exceptions above. You may separately manage connected-app authorizations in your provider account settings. Contact Readpod support for assistance; do not send passwords or authentication tokens.
11. Your Privacy Rights
Depending on where you live, you may have rights to:
request access to personal information associated with your account;
request correction of inaccurate information;
request deletion of information;
object to or restrict certain processing;
withdraw consent for optional processing;
request a portable copy of eligible information;
appeal a decision regarding a privacy request; and
complain to a data-protection authority.
Recommendations may use reading and interaction information as described in this Policy. Available advertising consent and system privacy controls apply to their stated purposes; they do not automatically erase reading records or disable all service measurement. Contact support for applicable privacy requests.
We will not discriminate against you for exercising a privacy right. These rights may be limited where an exception under applicable law applies.
12. Security
We use administrative, technical, and organizational measures designed to protect information, including encrypted network transport, access controls, platform security features, and transaction verification. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
If you believe your account or information has been accessed without authorization, contact Readpod support.
13. Children
Readpod is not directed to children under 13, or a higher minimum age where required by local law. We do not knowingly collect personal information from a child below the applicable minimum age. If you believe a child has provided information to Readpod contrary to this section, contact Readpod support so that we can investigate and take appropriate action.
Users who have not reached the age of legal majority where they live must have permission from a parent or legal guardian to use paid features.
14. Changes to This Policy
We may update this Policy to reflect changes in the Service, law, or our data practices. We will update the date at the top and provide additional notice when required. If a change materially affects optional processing based on consent, we will request consent again where required.
15. Contact Us
Contact Readpod through Settings > Help & Feedback in the app or the official Support Center.