A small amount of data, for a small nightly ritual.

What the app collects

• An installation ID. Nightly creates a random identifier and secret token for this installation. The server stores the identifier and a one-way hash of the token.
• Reading activity. When you finish a piece, Nightly stores its reading date, type, and completion time. This powers your reading log and streak.
• Your time zone. The app sends the device time-zone name so the correct local-noon issue is shown.
• Connection and diagnostic information. Cloudflare processes your IP address and request metadata to deliver and protect the service. Operational logs can contain request URLs, response status, timing, approximate network location, and error details. These are used to investigate failures and keep Nightly working, not to target advertising.

Nightly does not store your Google name, email or profile photo. Signing in processes a Google identity token to verify your identity; it is not retained. Nightly does not collect contacts, precise location, microphone recordings, photos, advertising ID, or payment details. The app contains no advertising or third-party analytics SDK.

What stays on your device

Tonight’s text, dictionary data, reading position, and active reading state are stored on your device. Once the text has downloaded, you can read it offline. Narration streams from Nightly’s servers and may be temporarily buffered on your device; a complete offline audio download is not currently guaranteed. Clearing Nightly’s storage or uninstalling the app removes the local reading cache.

Optional Google sign-in

Reading does not require an account. If you choose Google sign-in, Google authenticates you and sends an identity token to Nightly. We verify the token and keep Google’s stable account identifier, a random Nightly account ID and the account creation time. We do not request access to Gmail, Drive, contacts or your password.

Nightly stores only a one-way hash of its account session token on the server, linked to the installation. Your device keeps its session in secure storage. Sessions expire after 30 days; sign-in challenges expire after five minutes. Expired credentials are removed by a daily cleanup, up to 24 hours after expiry.

Signing out removes this device’s local account session and attempts to revoke the server session. Offline revocation may not complete; the server session still expires automatically. Signing out preserves local reading history. Account sign-in does not yet provide cross-device history backup.

About Nightly → Account → Delete account removes the Google identifier, Nightly account and all its server account sessions after a recent sign-in. Installation history remains separate; use Request data deletion to remove that too. You can also request account deletion at the support address below; we will verify ownership before removing it. Google handles its sign-in service under its own privacy policy.

Optional usage sharing

In supported builds, About Nightly → Share usage lets you choose whether to share which readings you open and which audio readings start playing. This is off by default and does not require an account. We store the installation ID, reading date, piece ID, signal type and receipt time. Repeat starts of the same piece count once per reading date. These signals do not tell us how long you listened or whether you paid attention.

We use aggregate reports to improve Nightly. We do not collect your reading text, dictionary searches, email or Google account identifier through usage sharing. Pending signals are stored temporarily on the device while offline. Server signals expire after 30 days and are removed by a daily cleanup, which can take up to another 24 hours. No permanent usage aggregates are retained.

Turning sharing off stops collection, clears unsent signals and requests deletion of this installation’s server usage records. If you are offline, that deletion retries when you next open the app online. It does not remove your reading history or streak.

Why the data is used

The installation ID authenticates reading-history requests. Reading activity provides the history and streak features. The time zone determines which issue belongs to the current reading night. Nightly does not use this information for advertising, cross-app tracking, or personalized content.

Service providers and sharing

Cloudflare hosts Nightly’s API, database, and audio files and processes requests on Nightly’s behalf. Google Play distributes the Android app. Nightly does not sell personal data or share it with advertising companies.

Pilot signups

The website no longer asks for or stores new signup email addresses. Earlier pilot signup addresses and their status remain stored for managing test access, not newsletters or advertising.

To join the beta, follow the website’s link to Google Groups. Google manages group membership and Play test opt-ins. The group owner can see member details to manage test access; members cannot see the member list or post messages. You can leave the group through Google Groups.

Retention and deletion

Request account or data deletion. Deleted database records may remain in Cloudflare recovery backups for up to 30 days.

Installation and reading-history records are retained while Nightly provides the service or until deletion is requested. Pilot signup records are retained for the pilot and release process. Cloudflare Workers operational logs expire automatically within seven days under the service’s current retention limits; provider security records are handled under Cloudflare’s applicable policies.

To request deletion, email houdrizvee@gmail.com and write “Nightly data deletion.” In the app, About Nightly → Request data deletion opens an email draft with your installation ID. We use this ID to locate the installation and verify the request before deleting its identifier, authentication record and reading-history records. Include your signup email if you also want the pilot signup removed. A request does not erase the app’s local cache; clear app storage to remove that copy. Google Groups membership is managed separately through Google.

If you contact support, we receive the email address and information you choose to send. Do not send passwords or your installation’s secret token. Support correspondence is used to resolve your request, not for marketing.

Security

Nightly uses HTTPS in transit. Installation secrets are stored in Android’s secure storage, and the server stores only a hash of the secret token. No system can be guaranteed perfectly secure, but Nightly limits the information it keeps.

Children

Nightly is not directed to children under 16. The nightly catalogue may include historical themes intended for older readers.

Changes

This page will be updated when Nightly’s data practices change. The effective date above shows the latest revision.