Vault Reader
§ 00 · Colophon
Privacy

A very shortprivacy policy.

Last updatedApril 20, 2026
i

TL;DR

Vault Reader collects nothing. There are no servers to store your data on, no analytics, and no third-party SDKs. Everything the app does happens on your iPhone or directly between your iPhone and GitHub.

ii

What data the app handles

When you sign in with GitHub, a personal access token is issued to your device and stored in the iOS Keychain. The token never leaves your device except when the app calls GitHub directly on your behalf.

Markdown content from the repositories you connect is cached locally via SwiftData. Sync happens between your iPhone and GitHub's API; no intermediary server sees the content.

iii

What we collect

Nothing. Minner Labs operates no backend for Vault Reader. We do not receive or store usage data, IP addresses, device identifiers, account information, or content from your repositories.

iv

Third parties

Vault Reader integrates with exactly one third party: GitHub, to sign you in and sync files you ask it to. GitHub's handling of your data is governed by GitHub's privacy policy.

There are no analytics SDKs, crash reporters, ad networks, or marketing pixels in the app.

v

AI features

Summaries, explanations, and vault-wide Q&A run entirely on-device using Apple Foundation Models. Your prompts and the AI's responses never leave your iPhone. There is no cloud inference.

vi

Children's privacy

Vault Reader is rated 4+ and is not directed to children under 13. Because we collect no data, the app does not knowingly collect information from any user, including children.

vii

Changes to this policy

If this policy changes, the effective date at the top of this page will update, and material changes will be noted in the app's App Store release notes.

viii

Contact

Questions or concerns? Use the support form, or email support@minnerlabs.com.