YOUR READING. YOUR INFORMATION.

Privacy policy.

A clear account of what stays on your iPad, what our services process, and the choices you have.

Effective · Current iPad beta & product website

Merrow’s illustrated red-cap bookmark

Your saved reading library and notes stay in the app’s local storage. Optional GitHub access uses a backend that retains account/session information and limited security records. We do not sell customer data or use it for advertising or AI-model training.

This policy covers the current Merrow iPad beta, its optional GitHub connection and the product website. For privacy questions or requests, email support@merrowreader.app.

1. Your reading library

Merrow stores saved documents, reading positions, bookmarks, highlights, typed notes and Apple Pencil notes in your device’s local reader storage. The current app does not upload this reading library or these notes to a Merrow storage service, and does not synchronize notes between devices.

You can remove documents and associated local marks in Merrow. Deleting the app or clearing its storage can remove saved information. Device backups and your Files or cloud-storage providers have their own behavior and policies. Keep original copies of important documents.

Documents can contain links or external images. Opening those resources may contact their hosts and disclose technical information such as your IP address. Uncached resources can require a network connection.

2. Connecting GitHub

You can read local documents and public GitHub repositories without signing in. If you connect GitHub, the Merrow backend retains your GitHub numeric account identifier, username and encrypted authentication/session information to provide the connection. It does not retain your GitHub email address, first name, last name or full profile name as account fields. GitHub’s account response may contain additional profile fields during authentication; Merrow selects only the account ID and username for the retained account record.

The backend processes repository information and source files you request, subject to your account’s access and the repositories authorized for the Merrow GitHub App. Merrow accepts only Contents read and Metadata read App grants, rechecks private repository access for each request and does not edit repository files. The backend does not maintain a server-side reading library or store document bodies in its security activity records.

GitHub access and refresh tokens are encrypted in server session records. The iPad stores an opaque Merrow session identifier in Apple Keychain; GitHub tokens are not passed to the app’s JavaScript reader. Some database indexes, including the GitHub account ID used to find sessions, are not encrypted application payloads. Encryption is a safeguard, not a claim that the server processes or retains no account data.

New GitHub source content is retrieved when requested, including an explicit refresh. Cached reading and annotations remain on your device. These source-refresh operations do not synchronize your notes between devices. Private offline copies cannot be remotely revoked while a device is disconnected.

3. Security records & retention

Merrow retains security records for completed sign-ins, sign-outs, disconnects, repository discovery/reads and API request denials or errors. These records contain a time, fixed action/result, transport category, HTTP result status and a numeric GitHub account or repository identifier when verified. They exclude document text, notes, names, email addresses, repository names, file paths, IP addresses, user agents, cookies, OAuth codes and tokens. These records support access protection and incident investigation; they are not reading-behavior analytics.

Security record payloads are encrypted. Records expire after 30 days. Cleanup runs at startup, during API activity and every minute while the backend runs. A 25,000-record limit may remove older entries sooner. Security records remain subject to this policy after disconnect, even though authentication sessions are removed. The activity history is bounded and may have gaps if recording fails.

Sign-in sessions become invalid after 30 minutes of inactivity or 12 hours from creation. Login transactions last at most 10 minutes and native authorization handoffs at most one minute. Expired database entries are cleaned on the same startup/request/background schedule. Removing an application record does not guarantee immediate physical erasure from storage journals or provider systems.

The hosting provider’s technical/edge logs are separate and may contain IP addresses, user agents, hostnames, request paths, response status and timing. Our current hosting service makes technical logs available for 30 days; provider storage and recovery practices are not a promise of physical deletion at that deadline. Merrow emits generic security/error event names rather than intentionally logging request bodies or credentials. Providers may retain infrastructure copies under their own policies. We will reassess this disclosure if application backup practices change.

4. Your controls

You can sign out, disconnect GitHub, remove saved local copies and revoke Merrow through GitHub settings. Sign-out removes the current server session. Disconnect attempts to revoke the GitHub grant and removes the user’s Merrow server sessions and pending native grants. If GitHub cannot confirm revocation, Merrow shows instructions for revoking it directly. Security records follow their separate 30-day expiry policy.

Removing local GitHub copies also removes their associated local annotations and cached assets when you choose that option. These controls do not delete your GitHub account or source repository. Contact support@merrowreader.app about Merrow-related information or deletion requests. Do not send passwords, access tokens or private repository contents.

5. Providers & disclosure

We do not sell customer data, use it for advertising or AI-model training, or voluntarily share customer logs with unrelated parties. Providing Merrow requires service providers to process information:

  • GitHub handles authorization and repository requests.
  • Our hosting provider operates the backend and processes technical request information.
  • Our email provider handles support messages.
  • Our website hosting and network providers handle product website and domain traffic.
  • Apple provides distribution, TestFlight and device services.

Each provider also operates under its own terms and privacy practices. External resources you choose to open contact their hosts. Visiting the product website sends technical request information to its hosting/network providers, even though the website does not require GitHub sign-in.

We may disclose information when you direct us to, or when legally required. This policy does not promise that no provider or other party ever processes data needed to deliver the service.

6. Support & beta testing

When you email support, our email provider and the operator receive the sender address and the information you choose to send, which may include your name or a screenshot. Those messages are separate from GitHub account fields and are not part of the automatic 30-day security-log expiry. They remain in the support mailbox while needed to handle the issue and related follow-up; you can request deletion, subject to applicable retention obligations. Please avoid sending sensitive content.

Apple’s TestFlight service can provide beta feedback, screenshots and crash information according to its own disclosures. The current beta has no Merrow purchase flow and no third-party advertising or analytics SDK added to the app. The public product website is separate from the native reader and has its own hosting/network processing.

7. Updates & contact

Changes will be published here with an updated effective date. For privacy questions or requests, contact support@merrowreader.app.

Visit Merrow support