Effective date: November 4, 2026. Operator: ItemRecall.
This policy describes our iPhone app, browser version, and supporting ItemRecall services. If you have questions or wish to request access or deletion, use the contact information below.
We use Supabase for account and item records and legacy photo storage, and Modal to host our API, and Google Gemini API for photo analysis. For unpaid Gemini API services, Google's terms permit use of submitted content and generated responses to improve products; human reviewers may inspect them. Users should not submit sensitive, confidential, or personal information through unpaid services. Paid API data-use terms differ. Do not submit sensitive or confidential photos using unpaid API services. Those service providers process information to operate ItemRecall under applicable contractual and privacy protections. We do not sell personal data, run ads, or use personal photos for advertising. We do not intentionally use submitted photos to train our own AI models. See the providers' own notices: Supabase privacy and Modal privacy, Gemini API terms, and Google privacy.
Adult use and service availability: Google's Gemini API terms restrict use of API clients by people under 18. Before enabling Autolabel, users must confirm they are at least 18 and agree to the described AI data transfer. ItemRecall's manual photo and labeling functions do not send photos to Google Gemini. Google also restricts unpaid API use for end users in the European Economic Area, Switzerland, and the United Kingdom; the developer must configure distribution and AI service availability accordingly.
The camera stays off when you open or sign in to ItemRecall, even if you previously allowed access. To take pictures, users explicitly choose Continue before the first system camera permission request. When access has previously been allowed, they select Start camera. Users can decline access and still use their saved items and photos. Selecting an optional reference photo uses the device's system photo picker; the current iPhone workflow does not require access to the whole photo library. You can deny or revoke camera access in iOS Settings. In ItemRecall's Camera section, turn Autolabel off to stop sending future captured photos for AI processing. Existing local photos remain accessible and can be labeled by hand. Review your privacy choices.
Local iPhone photos remain in ItemRecall's documents folder until you manually remove them, an enabled auto-delete rule removes them, you delete the current account's folder, or you uninstall the app. A protected photo is excluded from automatic deletion. Your phone's backup settings may include app documents; copies in device backups or other devices are controlled separately. We do not provide an automatic ItemRecall cloud-photo backup for the new installed iPhone workflow.
For old cloud photos, the app transfers each one to the iPhone, verifies the transferred bytes, and then deletes its cloud original; if verification fails, the cloud original is retained. Data on a different phone will not be automatically deleted by deleting files from this phone.
You can delete individual photos and items inside ItemRecall. You may also permanently delete your account from Settings → Delete account without completing a survey. Account deletion initiates removal of account records, item records, known legacy cloud photo data, and that account's local folder on the current device. It does not automatically erase copies in other devices or independent device backups. Limited security logs and service backups may be retained for their configured retention periods or where legally required.
We use HTTPS for network connections, access controls for account data, and server-side password hashing. No system is completely secure. For questions, requests to access or erase information, concerns about a cloud photo copy, or questions about retention, Contact us at joannasun1999@gmail.com.
ItemRecall is a general-purpose item-memory tool and is not designed or directed specifically to children under 13. We may update this policy as features or providers change. The new effective date will appear on this page.