Privacy policy

Who we are

Readastic is operated by Reostack Technologies, Nigeria. Reostack Technologies is responsible for the personal data it processes through Readastic and this website. Contact us at support@readastic.com for support or privacy requests.

No Readastic account is required. We do not sell personal data or use it for targeted advertising.

Your library and local narration

Imported articles, pasted text, documents, recognized text, generated local audio, listening history and app preferences are stored on your device. We do not operate a server that receives or stores your library. Phonon 40M narration and its Spencer voice are bundled with the iPhone app for iOS 18 or later. Local narration runs on your device without a model download or text upload.

Backups you create and operating-system backups may contain library data. Their location and access depend on where you save them and your Apple or Google backup settings. Deleting the app does not necessarily delete copies you saved elsewhere.

Services you connect to

• Articles and feeds. When you add a link or refresh a followed feed, your device contacts its publisher. The publisher may receive your IP address, request information and the requested URL. Images in articles and feeds load from the hosts they name, often an image service rather than the publisher, which receive the same request information. Public X links are retrieved through FxTwitter, which receives the post’s URL, your IP address and request information.
• Cloud narration in 1.0.11 and earlier. Readastic 1.0.11 and earlier offer optional cloud narration with Gemini, OpenAI or ElevenLabs. If you turn it on in those versions, the text you narrate is sent directly to that provider with your API key, and the provider processes it under its own terms and privacy practices. Saving a key also sends it to that provider to check it. Your key stays in your device’s secure storage and is never sent to us. Readastic 1.0.12 and later narrate only on your device and delete saved provider keys.
• App updates. Each time it opens, Readastic checks Expo’s update service for app updates. Expo receives your IP address, a random installation identifier and technical details such as the app build and platform.
• In-app browser. Pages you open in the in-app browser load directly from their sites. Anything you type there that doesn’t start with http:// or https:// is sent to Google as a search.
• Notifications. Local reminders are scheduled on your device. If you enable Readastic announcements, Firebase Cloud Messaging and Apple/Google push services process an installation registration token, push token and device/app information to deliver messages. You can disable announcements in Readastic or revoke notification permission in system settings.
• Image recognition. Recognition happens on the device. On Android, Google’s ML Kit may download recognition components and process associated technical diagnostics; imported images and recognized text are not sent to our server.

Provider information: Gemini API terms, OpenAI privacy, ElevenLabs privacy, Firebase privacy, Expo privacy, Cloudflare privacy.

App usage and crash reports

During onboarding, Readastic asks you to accept the Terms and Privacy Policy. Google Analytics for Firebase and Firebase Crashlytics remain disabled until that acceptance is saved on your device. Usage and diagnostics is on by default after that saved acceptance, which enables both services. You can turn it off at any time in Settings → App → Usage and diagnostics and turn it on again there. Google Analytics receives app interactions and screen names to help us understand which features work well. Firebase Crashlytics receives technical crash information and sanitized failure categories to help us fix problems. These services may process installation identifiers, app/device/OS information, timestamps and diagnostic state. Analytics also derives a general location from masked IP addresses. Readastic does not request device location access. We do not describe these records as completely anonymous.

Our custom events and failure messages exclude article content, titles, publisher URLs and API keys. Advertising-ID collection and advertising consent are disabled in our app configuration. Turning off Usage and diagnostics stops future app usage events and app-reported failures, disables the SDK collection settings, resets local Analytics data and requests deletion of unsent crash reports. Native SDK cleanup is asynchronous and may not remove every active-session report. This control cannot recall uploads already in progress or erase records already received by these services. Your library, local narration and local Usage statistics continue to work. Restoring a library snapshot keeps Usage and diagnostics off if it was off on this device or in that snapshot. Uninstalling does not by itself erase records already received by these services. Contact support@readastic.com for privacy requests.

This website uses Cloudflare Web Analytics to count visits and measure page speed. It sets no cookies and doesn’t follow you across other sites. Cloudflare receives your IP address, browser details and the pages you view to provide it. If you ask the download card to email you the App Store link, Cloudflare Email Service sends that one message to the address you enter; we don’t store the address or use it for anything else. Cloudflare processes connection information to host and secure it. If you email us, we receive your address, message and any attachments; please avoid sending API keys or sensitive article content.

Retention and deletion

Your library stays on your device until you delete it or the app’s local data. Archiving keeps an article; it does not delete it. Delete exported and operating-system backups separately if you want those copies removed.

Firebase applies service-specific retention and deletion schedules to Crashlytics records. Google Analytics event data is retained for 2 months and user data for 14 months. The user-data retention period resets with new activity. Aggregated reports may remain longer. We retain support correspondence only as needed to resolve requests, maintain necessary support records or meet legal obligations. Publishers, and cloud providers used with earlier versions, apply their own retention policies.

To request access, correction or deletion of personal data we hold, email support@readastic.com. We may need information to verify your request or locate a record. We do not receive your local library and cannot retrieve or erase it remotely. Avoid including your article text or API keys in a request.

Your choices and rights

You can turn off Usage and diagnostics in Settings → App, disable announcements and manage operating-system permissions. Where consent is the basis for processing, you may withdraw it; this does not affect prior lawful processing. We also process information needed to provide requested services, respond to support requests, maintain security and meet applicable legal requirements.

Depending on applicable law, you may request access, correction, deletion, restriction or portability of personal data, object to processing, and complain to a relevant data protection authority. In Nigeria, this includes the Nigeria Data Protection Commission. Contact us first if you would like help with a concern.

Google, Cloudflare and cloud providers used with earlier versions may process data outside Nigeria. Processing is subject to applicable transfer requirements and the relevant providers’ data-protection arrangements. Readastic is not directed at children; if you believe a child has sent us personal information, contact us.

We may update this policy as the app changes. The effective date and revision identify the version you accepted in the app; the copy-updated date marks later wording changes. Material changes to optional collection will be explained where you make that choice.