Juno collects no data. It talks only to the BookOrbit server you sign in to. The developer runs no server for Juno and never sees your account, your books or what you read.
This policy covers Juno Reader (“Juno”), the iPhone and iPad app made by Lucas Santoni. Juno has no analytics, advertising, tracking or crash-reporting code.
Your BookOrbit server
Juno connects only to the server address you enter when you sign in. It sends that server:
- your username and password, to sign in;
- a name for the session (“Juno on iPhone”), which BookOrbit shows in its list of sessions;
- your reading position, reading status and reader settings as they change, and Juno’s own settings, such as the library it opens on and each library’s reading defaults.
Juno downloads your books, covers and their details from it. That server is run by you or by whoever gave you your account, and what it keeps is up to them.
On your device
- In the Keychain, on this device only: the server address, your username and a session token that keeps you signed in. Never your password.
- In the app’s cache, which iOS can clear when it needs space: books and comic pages you opened recently (about 500 MB of each at most, the oldest removed first) and covers.
- In the app’s preferences: light, dark or system appearance, and how the library is sorted and shown.
Signing out erases all of it.
Crash reports and feedback
Juno sends no reports of its own. If you choose to share analytics with app developers in your device’s settings, Apple may pass crash reports about Juno on to the developer. If you test Juno with TestFlight, the feedback, screenshots and crash reports you choose to send go to the developer through Apple. Apple’s privacy policy covers both.
Changes
If this policy changes, the new version will be posted on this page with a new effective date.
Contact
For a question about this policy, see contact on the support page.