ReliableReader Privacy Policy

Effective Date: June 27, 2026
Applies to: ReliableReader for iOS, version 0.1 beta

ReliableReader is an iOS app for importing long-form text and generating speech audio for listening. This policy describes the data handling behavior of the current beta version, including the optional in-app feedback system.

ReliableReader is operated by Awaiting Aesthetic Living Arts (Shenyang) Co., Ltd. (坐等唯美艺术生活（沈阳）有限公司).

For privacy questions, contact: reliablereader-privacy@jiripple.com
For support questions, contact: reliablereader-support@jiripple.com

Information You Provide

ReliableReader may process text that you import, paste, type, or share into the app. This can include article titles, article body text, URLs shared from other apps, and text passed through Shortcuts.

When you tap to generate speech, ReliableReader sends the text you ask the app to read directly to the Microsoft Azure Speech endpoint you configure in the app. Microsoft Azure Speech is a third-party service and is not operated by ReliableReader. You are responsible for the Azure region, endpoint, account, key, quota, charges, and Azure-side data settings you choose. ReliableReader does not proxy these Azure Speech requests through its own servers and does not receive or store your Azure Speech key, article text, or Azure-generated audio on developer-operated servers. Azure Speech is subject to Microsoft Azure's applicable terms, privacy, and data processing practices. Do not generate speech unless you want the current text to be sent to the Azure Speech endpoint you configured.

ReliableReader does not include a shared server-side Azure key in the current beta. You provide your own Azure Speech key, region, and endpoint in the app settings.

If you actively submit feedback in the app, the feedback message you write is sent to the ReliableReader feedback backend and stored as support/feedback content. The developer may view that message and may reply through the feedback system. ReliableReader does not collect optional email, phone number, or name fields in this version.

Online in-app feedback is a best-effort support convenience and does not require an account. If online feedback is unavailable, you can use the manual fallback support channels listed in this policy.

Azure Speech Configuration

The current beta stores your Azure Speech configuration locally on your device:

Azure Speech requests are sent directly from the app to the endpoint you configure. ReliableReader does not use a developer-operated server to receive, proxy, or store your Azure Speech key, article text, or Azure-generated audio.

Local Storage

The current beta may store the following information locally on your device:

Local drafts, settings, and audio cache are stored in the app sandbox. Depending on iOS backup settings and app implementation, some local app data may be included in device backups. ReliableReader does not intentionally sync Azure Speech keys, article drafts, or audio cache through iCloud. You can use the in-app cache clearing controls to remove cached audio from the device.

The app includes local controls for clearing saved drafts, clearing the local audio cache, and deleting the saved Azure key. Clearing local drafts or cached audio does not delete data that may already have been sent to Azure Speech for generation, and it does not delete feedback already submitted to the ReliableReader feedback backend.

Diagnostics and Feedback

ReliableReader includes optional diagnostics to help troubleshoot import, generation, playback, text cleaning, and feedback issues.

Copied diagnostics are intended to be redacted where possible, including key-like strings, tokens, authorization values, cookies, URLs, SSML, local file paths, request or response body fields, and long text snippets. This redaction is a safety measure and is not guaranteed to remove every sensitive value.

The separate cleaned reading text view may include article content. Do not share cleaned reading text unless you choose to provide that content.

In-app feedback is submitted only when you choose to send it. A feedback submission may include:

The in-app feedback system does not automatically attach or upload article body text, cleaned reading text, Azure keys, Bark tokens, authorization headers, cookies, raw request or response bodies, SSML, full URLs, complete webpage contents, clipboard contents, or local file paths. However, if you choose to paste or type such content into the feedback message, it will be submitted and stored as part of that message. Server-side validation is intended to reject protected structured fields if they are included accidentally.

When feedback is submitted, the backend stores feedback session metadata, the user feedback message, developer replies, status events, and optional safe diagnostics summaries. In the current backend model, feedback records are normally retained for up to 7 days. Standard server logs and backups may have different retention periods.

The feedback system uses a sessionId and a high-entropy sessionToken so the app can check for replies without an account. The app stores the sessionToken in Keychain. The backend stores only a hash of the session token. The session token is not shown in the app UI and is not included in developer notifications.

Developer replies may be visible in the app when you refresh the feedback status. ReliableReader does not promise real-time support or that every feedback report will receive a reply.

ReliableReader may use Bark or a Bark-compatible service as a server-side developer notification channel for new feedback. The app does not contain a Bark token. Notification content is limited to low-sensitivity routing and triage fields, such as a session id prefix, category, state, timestamp, app version, build number, or an access-controlled developer link that does not contain a sessionToken or user content. Bark notifications do not include your feedback message, article text, cleaned reading text, session token, Azure key, or raw diagnostics.

If you send feedback through email, screenshots, screen recordings, copied diagnostics, or other manual channels, the information you include will be handled through that feedback channel. Do not paste Azure keys, secrets, request headers, request bodies, private article text, cleaned reading text, or other sensitive content into feedback unless you choose to share it.

Server Logs and Service Operations

When you submit or refresh in-app feedback, the feedback backend and its infrastructure providers may process standard server logs, such as IP address, request time, request path, HTTP status code, User-Agent, error information, and security or rate-limiting records. These logs are used for security, abuse prevention, troubleshooting, and service operations. They may be retained according to infrastructure provider defaults and operational needs, including longer retention where needed to investigate abuse, security incidents, or legal obligations.

TestFlight

If you install or test ReliableReader through TestFlight, Apple may process beta-testing information under its TestFlight privacy practices, such as tester name, email address, invitation information, device and operating system information, crash logs, usage information, and feedback you submit through TestFlight. The ReliableReader developer may access testing, crash, and feedback information made available through Apple's TestFlight tools for testing, troubleshooting, and support.

App Capabilities and Permissions

ReliableReader uses network access to reach the Azure Speech endpoint you configure. It also uses background audio playback so generated audio can continue playing according to iOS audio behavior.

The app can receive content through the iOS share sheet, Shortcuts, URL scheme or app handoff, and clipboard import. ReliableReader does not continuously monitor the clipboard in the background. Clipboard import happens only after you tap the import action in the app. Shared URLs are imported as URL text in the current beta.

Based on the current app configuration, ReliableReader does not request access to the microphone, location, contacts, or photo library.

Services Not Included in the Current Beta

The current beta does not include:

The current beta does include a developer-operated backend only for feedback that you actively submit. It is not used for account login, cloud sync, advertising, analytics, tracking, hosted TTS, or storing Azure keys.

ReliableReader does not sell personal information, does not share personal information for cross-app or cross-site targeted advertising, and does not use feedback messages, article text, or diagnostics for advertising profiles or data brokerage.

International Processing

ReliableReader's feedback backend and developer notification infrastructure may be located outside your country or region. The Azure Speech region is chosen by you, and text is sent to the Azure endpoint you configure. Data protection laws may differ by country or region.

Children

ReliableReader is intended for a general audience and is not directed specifically to children. We do not knowingly collect children's personal information through the in-app feedback system. If you are a minor, use the app with the consent and guidance of a parent or guardian and do not submit sensitive personal information in feedback.

Your Choices and Rights

For beta testing, use non-sensitive text when possible. You control whether to configure Azure Speech, what text to import, when to generate speech audio, and what feedback or diagnostics to share.

You can remove local data using the controls in the app settings. Local deletion controls do not delete feedback already submitted to the feedback backend.

Depending on the laws that apply where you live, you may have rights to request access, correction, deletion, restriction of processing, or withdrawal of consent. You can submit privacy requests at reliablereader-privacy@jiripple.com. Because ReliableReader currently has no account system, we may need enough information to locate your feedback record, such as feedback sessionId, submission time, or feedback category. Do not email Azure keys, sessionTokens, or private article text. For data already sent to your configured Azure Speech service, use your Azure account and Microsoft Azure tools.

Changes to This Policy

This policy may be updated as ReliableReader changes. We will update the effective date when the policy changes. If our data handling practices change materially, we will provide notice as required by applicable law.