ByGrams — Privacy Policy

Last updated 22 August 2026

ByGrams collects no personal data. There are no accounts, no analytics, no advertising, and no tracking of any kind. Nothing you do in the app is reported to the developer or to anyone else.

What the app stores

Everything ByGrams saves stays on your device and is removed when you uninstall it:

• The recipe repository you choose — the owner/repo name and branch you enter, plus your gram-display preference.
• A cache of recipe files already downloaded, so recipes stay readable without a network connection.

None of it is transmitted anywhere.

Network connections

ByGrams makes network requests to one place: GitHub, to download the public recipe files from the repository you pointed it at. Specifically api.github.com and raw.githubusercontent.com.

As with any request to any website, GitHub can see your device's IP address and which files were requested. That information goes to GitHub, not to ByGrams, and is handled under GitHub's privacy statement. The app sends no identifier of its own, and no account or credential is involved — only public files are read.

Tapping a link on the About screen opens your browser at the ByGrams project page. What happens after that is between you and your browser.

What the app never does

• No user accounts, sign-in, or profiles
• No analytics, telemetry, or crash reporting
• No advertising, and no advertising identifiers
• No location, contacts, camera, microphone, or file access
• No selling or sharing of data, because none is collected
• No writing to your repository — ByGrams only ever reads

The app requests a single Android permission, INTERNET, used solely to fetch the recipe files described above.

Children

ByGrams is not directed at children and collects no data from anyone, including children under 13.

Verifying this

You do not have to take our word for it. ByGrams is open source under the MIT licence, so the network code and everything it stores can be read in full at github.com/walnutgeek/bygrams.

Changes

If this policy changes, the revised version will be published at this address with an updated date above. The history of every change is in the repository.

Contact

Questions or concerns: open an issue on the project repository.