ReadShoreReadShore Privacy Policy
How ReadShore uses your articles, account and AI-processing data, and the choices you have.
Who this policy covers
AIthentic LLC operates ReadShore. This policy covers the ReadShore iPhone app and its cloud services, including TestFlight versions. It is separate from the company website privacy notice. Contact us at steven@aithentic.tw about this policy or your data.
Reading on your device
You can save and read articles without an account. Your device stores saved addresses, titles, source text, captured images, reading controls, preferences, and any locally retained summaries, analyses, or Tidi conversations. Opening an original article or retrieving a page or preview contacts its publisher or content host, which can receive ordinary network information such as your IP address. Device backups are also subject to your Apple and device settings.
Signing in with Apple
Cloud features use Sign in with Apple and Supabase authentication. We process an account identifier, authentication information, the email address Apple supplies (which may be a private relay address), and your cloud-processing permission. Signing in alone does not enable automatic Summary & Analysis processing.
Summary, Analysis, and source retrieval
If you enable Summary & Analysis, eligible articles already saved and those you save later can be processed in the cloud. We send the source address and the normalized text and metadata needed to retrieve the source and generate an explanation. Our backend stores the associated content, requests, generated results, and execution records to deliver and recover this work. Raw share captures and locally captured source images are not sent to the AI model. You can turn this permission off in Settings; this stops new work governed by that permission and cancels unresolved handoffs, but does not delete results already retained.
Tidi conversations
Opening Tidi or writing a draft does not send a model request. When you press Send while signed in, we process your message, the selected readable source text, relevant conversation context, and page context needed for the answer, including the Saved search query when applicable. Only the bounded context for that turn is sent, rather than an unrestricted copy of your library. Tidi Send is a separate user action and is not controlled by the Summary & Analysis permission. Conversations are retained locally; our backend retains the payloads and records needed to execute and recover admitted turns.
Service providers and purposes
We use Apple for sign-in and TestFlight distribution, Supabase for authentication and backend storage, and Google Cloud for backend execution. AI requests go through OpenRouter to OpenAI-model endpoints. Model requests are configured to deny provider data collection and require zero-data-retention endpoints; this does not mean our own backend keeps no content or that operational metadata is never retained. Source retrieval may send public article or post addresses to Firecrawl, Jina Reader, ScrapeCreators, or SociaVault, depending on the source and enabled service. Providers process the information needed to supply these services; we require protection consistent with this policy. See OpenRouter’s data handling and model retention controls.
Operations and testing
We process account and request identifiers, timestamps, error categories, usage, and cost records to authenticate requests, protect the service, enforce limits, and diagnose failures. Routine application diagnostics exclude article text and free-form AI output. TestFlight may provide Apple-collected crash, usage, and feedback information. If you contact us or send feedback, we receive what you choose to include and use it to respond and investigate. Do not include passwords or other secrets in feedback. We do not sell personal information or use your reading content for advertising.
Retention and deletion
Saved articles remain until you remove them. Moving an article to Recently Deleted preserves it for restoration for 365 days, unless you choose Delete Permanently sooner; after the deadline, removal occurs when the relevant storage can next process it. Permanent deletion removes associated source content and AI artifacts, while minimal content-free deletion records may remain to prevent stale replay. Deleting a Tidi conversation removes its local conversation and queues removal of its hosted payloads; it does not delete the saved articles. Network-dependent deletion can require a connection and retry. Turning off processing, signing out, or uninstalling the app does not by itself delete your cloud account.
Deleting your account and exercising your choices
Use Settings → Account → Delete account to request deletion. Once the server confirms deletion of your cloud account and associated user content, this device clears its library and credentials. Other devices can clear their cache after reconnecting; we cannot remotely erase an offline device or copies you control. Content-free infrastructure billing records may remain for the rolling 24-hour accounting window; expired records are pruned by subsequent operations rather than a guaranteed wall-clock erase. Service-provider backups and operational logs follow their applicable retention cycles. Contact steven@aithentic.tw to request access, correction, or deletion, or ask about retained information. We may need to verify that you own the account.
Security, international processing, and changes
We use encrypted network connections, authenticated access, and account-scoped controls to protect cloud data. Service providers may process information outside your country, including in the United States and other locations where they operate. No storage or transmission method eliminates every risk. We update this page when our practices change and will provide additional notice or seek permission where required before materially changing how your information is used.
Last updated: October 9, 2026