Privacy Policy

Effective November 2, 2026

The short version

Rtro does not collect your data. There is no account to create, no server to send it to, no analytics, no advertising, and no third-party SDKs. Everything the app does to a photograph happens on your iPhone.

What stays on your device

Photos you develop are read through the iOS photo picker: only the photo you hand to Rtro is available to it, and nothing else in your library is read or listed.

Development runs entirely on-device. A finished photo is written to your library only when you tap SAVE, and only through iOS's add-only photo access.

Your settings — film, grain, exposure, language, theme — live in the app's local preferences and disappear when you delete the app.

Permissions

• Photo library, add only. Requested when you save, for one purpose: writing the developed photo. You can deny it; the rest of the app still works.
• Photo picker. System UI, outside the app. Rtro receives only the single photo you choose.

Rtro does not request access to the camera, microphone, location, contacts, or notifications, and it contains no advertising identifier.

Network

Rtro does not make network requests. The only pages it can open are this policy and the Terms of Use, from Settings. Loading them is an ordinary request for a static page: no cookies are set, no identifiers are attached, and nothing about you or your photos is sent with it.

Data sharing

There is nothing to share, sell, or disclose. The developer never receives your photos, your usage, or any identifier from your device.

Retention and deletion

No data is retained off your device. Deleting the app removes its local settings and caches. Photos you have saved remain in your library, under your control.

Children

Rtro collects no data from anyone, of any age.

Your rights

Privacy laws such as the GDPR and the CCPA give you rights over personal data held about you. Rtro holds none. If you believe otherwise, write to the address below and it will be looked into.

Changes

If the app's data practices ever change, this page will be updated and the effective date above revised. Given the architecture described here — on-device only — that is not expected.

Contact

Lisheng Chang · csee@live.com