ReadEase – AI Text Reader
Last Updated: October 3, 2026
ReadEase processes scanning, PDF extraction and reading aloud on your device. AI features send the text needed for the requested action to our service and Google Gemini. This policy describes both those flows.
You can scan with the camera, choose a photo or import a PDF; version 1.5 and later lets you select PDF pages. Apple Vision performs OCR on your device, and PDF text extraction runs locally. ReadEase does not upload scanned images, selected photos or PDF files to the AI service. Text extracted from them is sent only when an AI action processes that text.
Reading sessions and accepted writing results are saved locally using SwiftData. Your current writing draft and preferences are saved in local app storage. Opening a different writing entry can save the current draft to History. ReadEase does not operate cloud synchronization of this history.
You can delete individual History entries and clear the current draft in Write. Removing the app removes its local app data from that installation; device backups or copies you exported are managed separately by you and your backup provider.
ReadEase uses Apple's system speech synthesis and word highlighting. It does not send the text to our AI service for reading aloud.
Before the first AI request, the app asks you to allow text processing by our service and Google Gemini. If you decline, it does not send that request. Your choice applies to later AI requests on that installation; you can turn off AI sharing in Settings at any time. You can continue using non-AI reading and writing features without allowing AI sharing.
Simplification, summaries, sentence explanations, spelling checks, polishing, tone adjustment and translation send text through our Cloudflare Worker to Google Gemini. A sentence explanation includes nearby context; for a selected section, the request contains that section. The service may also send the source and candidate result to Gemini to check whether the result preserves the source meaning.
Requests use encrypted HTTPS. Our service does not persist source text, drafts, prompts or AI outputs in its database or service logs. Text and results are processed in memory while fulfilling a request. Developer-visible logging of Gemini GenerateContent requests is disabled for our ReadEase project. Separately, Google says it retains prompts, context and generated results for 55 days to detect and prevent abuse, including limited review of flagged content. Cloudflare and Google process data under their own applicable terms.
See the Gemini API abuse-monitoring policy, Gemini API Terms and Cloudflare Privacy Policy for current provider practices. Avoid submitting information that you do not want these providers to process.
Apple handles purchases and restoration through StoreKit. ReadEase receives signed transaction information, not your payment-card details. The secured AI service validates signed purchase information with Apple to determine current Pro access, expiry and revocation.
The secured AI service uses Apple App Attest to verify an installation and bind requests to it. Service metadata includes a pseudonymous installation identifier, public verification key, request counters, short-lived challenge/session records, quota day and usage, and hashes used to authorize automatic summaries. Those hashes are not stored copies of your text. A registration time zone determines the daily quota reset. Request processing checks purchase status when a signed purchase is provided.
Cloudflare processes network information such as an IP address to deliver and protect the service. Our diagnostic events contain the task, prompt/model version, latency, input size, token counts and success or failure; they do not include your submitted text. ReadEase does not integrate Firebase Analytics or advertising SDKs, and we do not sell your data.
Short-lived sessions expire after ten minutes and challenges after one minute. Daily quota and verification records support service access and abuse prevention. Contact us to request deletion of service metadata associated with your installation; local history and exported copies are managed separately.
You can use local import, layout settings and reading aloud without requesting AI processing. You control which text you submit and can remove local History entries or start a new writing draft. For questions or requests about service data, email admin@flipior.com.
We update this policy when data handling changes. Installation verification and server-side purchase/quota checks apply as the security update is rolled out; older app versions may use the previous request authentication flow.