Rotorfolio
Watches before they are yours.
Last updated: 18 September 2026
Rotorfolio is an app for keeping a private record of a watch collection. It was built so that this policy could be short.
Rotorfolio collects nothing. There is no account, no analytics, no advertising, no tracking, and no server holding a copy of anything you enter. Everything you put into the app stays on your device.
Everything you enter — watches, references, notes, prices, currencies, serial numbers, boutiques, salespeople, dates, accuracy readings and the photographs you take or choose — is written to the app’s own private storage on your device.
None of it is transmitted anywhere. It is included in your device’s iCloud or computer backup if you have backups switched on, in which case it is covered by Apple’s terms and not by anything the developer controls.
You can export all of it at any time as a JSON file to a location you choose in the Files app. That export is yours; the app does not upload it.
The widgets show a small summary — watch names, references and how long you have been waiting, never prices or serial numbers. That summary is stored in the app’s own shared container on your iPhone. It does not pass through any server.
Only when you choose to photograph a watch, or to read a reference number off a warranty card or caseback. Photographs are saved into the app’s own storage. Reading a reference happens entirely on the device; the image is not kept and not sent anywhere.
When you choose a picture for a watch, the system photo picker runs outside the app and hands over only the image you selected. The app cannot see the rest of your library.
Only if you set a check-in reminder for a watch you are waiting on. Reminders are scheduled locally on the device. Nothing is sent through any server, including Apple’s push service.
Only if you switch on the app lock. The check is performed by iOS; the app learns whether it succeeded and never sees any biometric data.
Each permission is requested at the moment you first use the feature that needs it, and refusing one disables only that feature.
Nothing you enter is ever sent anywhere. The app does make a few requests for public data, each of them either started by you or a plain download of a public file. None carries an identifier, an account, or any device information beyond what any HTTPS request necessarily carries, and the developer receives no record of any of them.
Once a day, if the device is online, the app downloads the current reference catalogue — a public file on this website — so that references added since your version shipped can be found. The request asks for the file and nothing else.
When you look up a reference that is not in the catalogue, that reference — and nothing else — is sent to The Watch Info to retrieve specification data. Their handling of that request is governed by their own policy.
If you paste a link from a manufacturer’s website, the app fetches that page to read the specifications from it. Where the catalogue knows the manufacturer’s own product photograph for a reference, the app loads that image from the manufacturer’s servers when the watch is shown. Those servers see an ordinary image request from your device, as a web browser would make.
When you use Set to time, the app asks a public time server (Apple’s, or the NTP pool) for the current time. The request contains no data.
The Today tab reads the public feeds of a handful of watch publications and lists their headlines. When the tab is refreshed, the app requests one file from each of these publishers, as a news reader would: Hodinkee, Fratello, Monochrome, SJX, Time+Tide, Revolution, Worn & Wound and aBlogtoWatch. Each request asks for the feed and carries nothing about you or your collection; each publisher’s handling of it is governed by their own policy. The list of publishers is a public file on this website, downloaded once a day like the catalogue, so a publisher can be added or removed without an update to the app. You can switch any publisher off in the tab. Which headlines are about your own watches is worked out on your device by comparing them with your references; that comparison never leaves the phone. Opening an article shows the publisher’s page in Safari inside the app, exactly as Safari would.
Every other part of the app works with the device offline.
Nothing, unless you write. There is no analytics SDK, no crash reporting service, no advertising framework, and no third-party code that transmits anything. The developer has no way of knowing what is in your collection, or that you use the app at all.
The one exception is a message you choose to send from the app’s feedback menu. It goes by ordinary email to the address below, from your own mail account, and its last lines list the app version, the iOS version, the phone model, the language, how many watches you have, and whether iCloud sync and Apple Intelligence are switched on. You can read those lines and delete any of them before sending. Nothing about the watches themselves is included.
Apple provides the developer with aggregate, anonymous App Store statistics — download counts and similar — which are produced by Apple and contain no information about you.
The app is rated 4+ and is suitable for all ages. It collects no personal data from anyone, children included.
Under the Swiss Federal Act on Data Protection and the GDPR you have rights of access, correction, deletion and portability over personal data a controller holds about you. The developer holds none, so there is nothing to request.
The data on your device is under your control: edit or delete any of it in the app, export it from the collection menu, and remove all of it by deleting the app.
If a future version of the app changes what is described here, this policy will be updated before that version ships, and the date at the top will change with it.
Questions about this policy go to that address, or through the support page.