Privacy policy — Rushes

Last updated: 8 September 2026

Rushes is a viewer for the photo and video library that is already on your device. This document is the privacy policy the Google Play listing links to; the whole of it follows from one design decision, which is that the program has nowhere to send anything.

What Rushes collects

Nothing.

There is no account, no sign-in, no analytics, no crash reporting SDK, no advertising identifier, and no telemetry of any kind. Rushes does not have a server. No photo, video, thumbnail, location, face, search term, or description of your library is transmitted anywhere, and none is stored anywhere except on the device you are holding.

What Rushes reads

Your photos and videos, once you grant the Photos and videos permission Android asks for on first run. Rushes reads them in order to display them, to compute the thumbnails it draws, and — if you turn the optional features on — to derive the search data described below. If you decline the permission, Rushes starts and shows an empty wall; it does not ask again on every launch and it has no other way to see your library.

Nothing else. Rushes does not read contacts, messages, calendars, call logs, the clipboard, or files outside the media library. It does not use the camera or the microphone. It does not request location permission; where a photo carries GPS coordinates in its own EXIF metadata, those coordinates are read from the file like any other metadata and stay on the device with it.

What Rushes stores, and where

All of it is on the device, in the app's own private storage, and all of it is derived from your library rather than being a copy of it:

Uninstalling Rushes deletes all of it. None of it is backed up to a cloud, and none of it is shared with another application.

The network

Rushes makes exactly one kind of network request, and only if you ask it to.

The optional content-tagging features — search by meaning, and grouping by person — need machine-learning models that are too large to ship inside the app. If you turn those features on, Rushes offers to download the model files, and only then does it use the network. The files come from two public repositories:

These are ordinary file downloads. Nothing about you or your library is included in the request, no identifier is sent, and the request happens once: the files are then on the device and are not fetched again. Those hosts see what any file download shows them — that some device asked for a public file — and Anthropic, the author, and Google are not told that it happened.

If you never turn those features on, Rushes never touches the network. The whole of the rest of the program — every layout, colour search, playback, motion-photo detection, export — works with the network off, and works identically on a device that has never been online. Airplane mode is a fair way to check this claim, and it is meant to be checked.

The models

The models run on the device, on the device's own CPU, through ONNX Runtime. They are not called through a service and there is no inference server. Turning the tagging pass off, or simply not downloading the models, leaves a program that still starts and still works.

Children

Rushes is not directed at children and collects no data from anyone, children included.

Permissions, and why each one is asked for

Permission Why
READ_MEDIA_IMAGES, READ_MEDIA_VIDEO To read and display your photos and videos. This is the entire function of the app.
READ_EXTERNAL_STORAGE (Android 12 and below only) The same thing, under the permission name those versions use.
INTERNET, ACCESS_NETWORK_STATE Only for the optional model download described above.

Changes

If this policy changes, the version published with a store update will say so, and the date at the top will move. A change that meant Rushes started collecting something would be a change to the program, not to its wording, and would appear in the Data safety section of the store listing as well.

Contact

info at programadorphp dot org