Privacy Policy

Effective July 28, 2026. Applies to Swippr on iPhone and Android.

Your photo library

Swippr asks for access to your photo library because reviewing photos is the entire purpose of the app. Everything it does with them happens on your device: browsing, grouping by month, finding similar shots, reading file sizes, and playing videos. No photo, video, thumbnail, filename, or piece of image data is ever uploaded anywhere.

Swippr needs access to your whole library because it is a tool for going through your whole library. A one-time picker cannot do that job: the app's core feature is remembering every photo you have already decided on, across sessions, so you can clean a large library a few minutes at a time. You can still grant access to only selected photos if you prefer, and Swippr will simply work with the smaller set and say so.

On Android, Swippr requests READ_MEDIA_IMAGES and READ_MEDIA_VIDEO to read your library, and ACCESS_MEDIA_LOCATION so that photos keep their original location data during the delete operation. On iPhone it uses the standard photo library permission. Location information read from a photo is used only on your device, and is never sent anywhere.

Deletion is always yours to confirm

Swippr never deletes anything on its own. Photos you swipe away are staged in a review bin and can be pulled back out. Nothing is removed until you confirm, and the final confirmation is your operating system's own dialog, not ours.

Deleted items are recoverable for about 30 days on both platforms: in Recently Deleted in the Photos app on iPhone, and in your gallery app's Trash on Android, where Swippr uses the system trash rather than a permanent delete.

Data stored on your device

Swippr keeps a small database on your device so it can remember which photos you have already reviewed, your daily streak, and your lifetime cleaning totals. It also caches technical details it has worked out about your library, such as video file sizes, a short numeric fingerprint used to spot near-duplicate shots, and photo coordinates where your photos carry them.

All of it stays on your device and is removed when you uninstall the app. None of it is ever transmitted.

Place names for trip groups come from a small list of cities built into the app itself. Swippr deliberately does not use the Apple or Google geocoding services, because doing so would send your photo coordinates to them.

What does go online, and when

Nothing about your photos is ever sent anywhere, in any build. That is a narrower promise than "works offline", and the difference is worth stating plainly. If you use iCloud Photos with Optimize iPhone Storage, the full-size original of an older photo lives in iCloud rather than on your phone, so simply showing it to you means iOS fetching it back. That is your own photo arriving from your own iCloud account, not anything of yours going out, but it does mean Swippr makes no offline claim. Deciding, staging, and deleting work with no connection. Seeing a photo that is not on the device does not.

Beyond that, only two things cause a network request of Swippr's own, and neither one involves your photos.

Test builds: anonymous usage counts

Builds distributed for testing through TestFlight or Google Play testing send a small amount of anonymous usage data so we can find and fix problems:

• A random install identifier: a generated number, not tied to you, your Apple Account, your Google Account, your email, or any device serial or advertising id.
• Basic feature events such as "app opened", "deck started", and "cleaning confirmed", with counts and byte totals.
• Error reports, meaning the error message and technical stack trace, when something breaks.

This data contains no photos, no filenames, no location, and no personal identifiers. It is stored with our infrastructure provider, Supabase, and the app's access is write-only: it can report its own events but can never read anyone's data back. It exists only to make the app stable, and it is never sold, shared, or used for advertising.

Swippr tells you this inside the app as well. The privacy screen you see when you first open a test build states plainly that the build sends anonymous usage counts and never photos.

Purchases

If you buy anything in Swippr, that purchase is handled by the App Store or Google Play, and is recorded through RevenueCat, which tells the app what you are entitled to. RevenueCat receives your purchase history and an anonymous customer identifier generated for your install. It is configured so that it does not collect device or advertising identifiers.

Swippr has no accounts, so there is nothing to sign into and no profile attached to a purchase. Your payment details are handled entirely by Apple or Google and are never seen by us. Builds without in-app purchases enabled make no such request at all.

What Swippr never does

• No ads and no advertising SDKs of any kind.
• No analytics or attribution SDKs, no data brokers, no third-party trackers.
• No accounts, sign-ups, or email collection.
• No uploading, backing up, or syncing of your photos or anything derived from them.
• No downloading of your full-size originals from cloud storage to measure them, because that would consume your data allowance to produce a number.
• No selling or sharing of any information with anyone.

Third parties

Two services can be involved, both described above and neither with access to your photos: Supabase, which stores anonymous telemetry from test builds only, and RevenueCat, which records purchases in builds where purchases are available. There are no others.

Children

Swippr is not directed at children and does not knowingly collect personal information from anyone, including children. There are no accounts and no way to submit personal information through the app.

Your choices

• You can revoke photo access at any time in your device settings. Swippr will show what it can still see and will not fight your choice.
• You can uninstall the app at any time, which removes its local database along with it.
• Inside the app you can reset your review memory whenever you like. This never touches your photos.
• If you used a test build and want the anonymous telemetry from your install deleted, email us and we will remove it. Include nothing more than a note that you are asking, since we have no way to identify you and will simply remove data on request as described below.
• To request deletion of purchase data held by RevenueCat, email us and we will pass the request on.

Changes to this policy

If this policy changes, the new version will be posted on this page with an updated effective date.

Contact

Questions about privacy, or a data request? Email privacy@swippr.app.