Privacy Policy

Personal Gazette for Android · last updated 11 August 2026

The short version. Personal Gazette has no accounts, no analytics, no advertising and no server of its own. It does not collect your personal data, and the developer never receives it. Your feeds, your editions and your settings stay on your phone. The app contacts the websites you point it at, and — only if you switch it on — a language model at an address you choose.

Who this is from

Personal Gazette is published by WilliansCode, Brazil. Questions about this policy can go to wives@outlook.com.

What the app stores, and where

Everything below is kept in the app's private storage on your device. None of it is transmitted to the developer, and it is all removed when you uninstall the app.

Your sources — the feed addresses you add or import, their names, and your starring and per-feed options.
Your editions — the papers the app has built, as HTML, PDF and EPUB files, with the article text and pictures they contain.
Your settings — every option in the Settings screen, stored as a single file.
Any API key you enter for a language model. It is stored on the device in the same settings file, in plain text, and is sent only to the endpoint you configured. It is never sent anywhere else and never to the developer.
Cached pictures from the articles in your editions.
Links you share into the app, until the next edition is built.
A crash file naming the last error, if the app has ever crashed. It stays on the device and is not uploaded; nothing sends it anywhere.
Website cookies, set by the pages the app opens in the browser engine — see below.

You can delete all of it at any time by uninstalling the app, or by clearing the app's storage in Android's Settings.

What leaves your device

Goes to	What is sent	When
The websites and feeds you choose	An ordinary web request: the address, and a browser-style user-agent string. No identifier for you or your device is added.	Whenever an edition is built.
A language model, at an address you enter	Headlines and passages from the articles in that edition, plus your API key for that service.	Only if you set the model option to a server. Off by default.

The optional model

The app can use a language model for four small jobs: ordering the stories, writing a one-line editor's note, choosing pull-quotes, and curating the exploration pages. Every one of them has a non-AI fallback, so the paper is built whether or not a model is used. There are two choices, and the default is no model at all.

No model. Nothing is sent anywhere beyond your feeds.
A server. Any OpenAI-compatible endpoint that you enter: a hosted service such as OpenRouter, or a model running on your own network. Article text and your API key are sent to that address and to no other. What the operator of that endpoint does with it is governed by their policy, not this one — if it is your own machine, it never leaves your network.

The app contains no advertising, analytics or telemetry library of any kind, so there is no third-party component reporting on your use of it.

Opening pages in the browser engine

Some websites build their article text in the browser rather than sending it, so an ordinary fetch returns a page with no words in it. When a plain fetch comes back that way, the app renders the page using Android's system WebView, as a browser would. This is on by default, for every source, and can be switched off entirely — or limited to the sources you mark individually — in Settings.

Those sites may then set cookies, which Android stores for the app. Turning the option off, or clearing the app's storage, disposes of them. The app does not read your device's browser history, and has no access to any other app's cookies. The pages fetched this way are the ones your own feeds link to, and nothing about you is added to the request.

What the app does not do

No account, sign-in, email address or profile.
No analytics, tracking, advertising or advertising identifier.
No location, contacts, camera, microphone, photo library or file access beyond files you explicitly pick or save.
No server operated by the developer — there is nowhere for your data to be collected to.
Nothing is sold or shared with third parties.

Permissions, and why

INTERNET and ACCESS_NETWORK_STATE — to fetch the feeds and articles you asked for.
POST_NOTIFICATIONS — to tell you a scheduled edition is ready. Optional, and Android asks you first.
RECEIVE_BOOT_COMPLETED, WAKE_LOCK, FOREGROUND_SERVICE — so a scheduled daily edition survives a restart and can finish building. Added by Android's own WorkManager.

Children

The app is not directed at children and collects nothing from anyone. The content it displays comes from the feeds you choose, and is not reviewed by the developer.

Your rights

Because no personal data ever reaches the developer, there is nothing held about you to access, correct, export or erase. All data the app holds is on your own device and under your control. This position is intended to satisfy the LGPD (Brazil), the GDPR (EU/EEA/UK) and comparable laws by not collecting anything in the first place.

Changes

If this policy changes, the date at the top changes with it, and a material change will be noted in the app's release notes.