iOS app privacy policy
How eReader Relay handles information when you use its iPhone and iPad app.
Prepared: 15 October 2026
Scope and contact
eReader Relay is operated by Nodular Pty Ltd (Australia). In this policy, “we” and “us” refer to Nodular Pty Ltd.
This policy describes the eReader Relay app for iPhone and iPad, including its share sheet extensions, and the service operations it requests: signing in, listing your destinations, saving a web page to a reading list, and generating or delivering an EPUB. For privacy questions, access or correction requests, deletion requests, or complaints, email [email protected].
The app uses your eReader Relay account. Installing or deleting the app does not create or delete that account. Other features, such as newsletter inboxes and website billing, also process data; see Privacy and data for additional context.
Information used by the app
- Account and authentication information. Sign-in happens on the eReader Relay website in a browser sheet; the app does not receive your password. The website returns an access token, which the app stores in the iOS Keychain with your display name and email address. A copy of the token is kept in the Keychain group the app shares with its share sheet extensions, so they can send links. Authenticated requests send the token to eReader Relay.
- Links you send. When you tap Send it, or choose eReader Relay in a share sheet, the app submits that page's URL and title, your chosen destination, and request information to eReader Relay. The app does not read your browsing history, other apps' content, or pages you do not send.
- Reading lists and devices. The app retrieves your reading-list names and identifiers, and device names, types, and identifiers, and your plan's limits. It remembers your default destination on the phone. The service resolves device identifiers to the delivery addresses configured in your account.
- Recently sent. The app keeps the last five links sent from the phone, with their titles, destinations, and delivery status, in the Keychain. It asks eReader Relay for the status of queued EPUBs while it is open.
- Content and delivery records. The service fetches the submitted public URL to extract article content and images. Depending on your destination, it stores the capture with your reading list or creates an EPUB and delivery job.
The app contains no advertising, analytics, or crash-reporting software, and does not track you across apps or websites.
Why information is processed
Information is used to authenticate requests, show your destinations, remember your choices, save requested pages, generate and deliver EPUBs, apply account permissions and plan limits, show delivery status, and respond to support and privacy requests.
Service providers and recipients
The production API is hosted at ereaderrelay.com. Cloudflare supplies hosting, processing,
storage, and delivery infrastructure. Content and delivery addresses are passed to the email or
device service involved in a delivery you request, such as Amazon's Send to Kindle service. The
source website receives the service's request when it fetches your submitted URL. Apple delivers
the app and its updates.
These providers may process information outside your country. Contact support for information about current processing locations and provider arrangements. Device providers and source websites apply their own policies to the operations they control.
Storage, retention, and your choices
Signing out removes the session, the share sheet's copy of it, your remembered destination, and Recently sent from the phone. Deleting the app removes its local data. App sessions are configured to expire after 30 days.
Stored reading content is retained for the duration of your active account, subject to the content-management controls you use. Deleting the app does not delete those service records or copies already delivered to a device. Contact support to request deletion or current retention information; a request may need identity verification.
Security and complaints
Production API requests use HTTPS. The service verifies account authorization for reading-list and device operations. The Keychain protects the stored session; no storage or transmission method is risk-free.
Send privacy concerns to [email protected] with enough information for us to investigate, without sending account secrets. You may also have rights to contact a privacy regulator in your jurisdiction.
Changes
This page will be updated when the app's data practices change. Review the page date and contact support if you need an explanation of a change.