Privacy Policy
Last updated: 9 July 2026
The short version
Longbox is local-first. There are no accounts and no login. Your collection lives on your device, not on our servers. Photos you capture are sent to an AI service only to read what's on the cover, then discarded — we don't keep them or use them to build a profile of you.
This policy explains what information Longbox ("the app", "we", "us") handles, why, and the choices you have. It applies to the Longbox mobile app and this website.
1. No account, no cloud collection
Longbox has no sign-up, login, or user account. Your collections, wish list, item details, and photos are stored locally on your device. We do not maintain a server-side database of your collection, and we cannot see what you've cataloged.
2. Camera & photos
With your permission, Longbox uses your camera and photo library so you can photograph comics to catalog them. When you capture an item:
- The image is sent to our processing service and an AI vision provider for the sole purpose of identifying the item (title, issue number, publisher, year, condition, and similar fields).
- Images are processed transiently to return that result. We do not retain your photos on our servers after processing, and they are not used to train models or to advertise to you.
- The photos you choose to keep with an item stay in the app's local storage on your device.
3. What we do and don't collect
We aim to collect as little as possible.
- We don't collect: your name, email, contacts, precise location, or a cloud copy of your collection.
- We do process: the image and text needed to identify an item while you're using the capture feature.
- We may collect limited, non-identifying analytics (for example, that a capture happened or a screen was viewed) to understand how the app is used and to fix problems. These are aggregate usage events, not the contents of your collection.
4. Pricing & marketplace lookups
To show estimated values and listings, Longbox may query third-party marketplaces such as eBay using details of an item (for example, a title and issue number). These requests are made to provide the feature you asked for and are subject to those services' own terms and privacy practices.
5. Purchases & subscriptions
If you buy a subscription or in-app purchase, the transaction is handled by the Apple App Store or Google Play and a subscription-management provider (RevenueCat). We receive a purchase/entitlement status so we can unlock features, but we do not receive or store your full payment card details. Billing is governed by the store you purchased through.
6. Third-party services
Longbox relies on a small number of service providers, including:
- An AI vision provider, to identify items from your photos.
- Our own lightweight processing service, which relays requests to those providers and holds no copy of your collection.
- A subscription/purchase provider (RevenueCat) and the app stores.
- Marketplace APIs (e.g. eBay) for pricing and listings.
- A privacy-conscious analytics provider for aggregate usage.
Each processes data only as needed to provide its part of the app and under its own privacy policy.
7. Your control & data rights
- Export: you can export and back up your collection from within the app at any time.
- Deletion: because your collection is stored on your device, deleting the app (or clearing its data) removes your collection. We hold no server-side copy to delete.
- Permissions: you can revoke camera or photo access at any time in your device settings; the identification feature simply stops working without them.
8. Children
Longbox is not directed to children under 13 (or the equivalent minimum age in your region), and we do not knowingly collect personal information from them.
9. Changes to this policy
We may update this policy as the app evolves. Material changes will be reflected here with a new "last updated" date.
10. Contact
Questions about privacy? Email privacy@longbox.cool.
This document is a plain-language template describing how Longbox is designed to work. Review it against your final infrastructure and any legal requirements for your jurisdiction before publishing.