Again — Privacy Policy
Effective date: 3 November 2026
Who we are
Again is provided by Görkem Ege, an individual developer trading as Remsys Studio. This policy explains how the iOS app handles information.
Your diary stays with you
No account is required. Again has no ads, advertising tracking or separate behavioral analytics SDK. Your food diary, goals, recipes, saved foods, corrections and settings are stored locally on your device, not on a diary server operated by us. Purchase-related processing is described below; “local diary” does not mean that the app never connects to the internet.
Files and device backups
JSON backups and CSV exports are files you choose to create and save or share through the iOS share sheet. Again does not automatically upload these exports. The destination you select may be a cloud or third-party service. iOS device backups may also include app data, depending on your Apple settings. Deleting the app can remove local data; separately saved exports and system backups must be managed separately.
Barcode lookup
For an uncached barcode, Again requests product information over HTTPS from world.openfoodfacts.org (Open Food Facts). The request includes the barcode number, requested product fields and an app-identifying User-Agent header. The service also receives connection information such as your IP address. Your diary, goals and meal history are not sent. Camera images are processed on the device for barcode detection and are not uploaded by Again. You can enter the barcode manually instead of granting camera access. Results are cached locally.
Apple purchases and RevenueCat
Apple processes payments. Again uses RevenueCat to check and restore Pro access, with an SDK-generated anonymous app user ID rather than an Again account. RevenueCat processes purchase receipts, transaction history and entitlement status, plus technical context such as device/OS, app/SDK version, locale and currency. It receives network information; its documentation says it derives country from IP when needed and then discards the IP. Connections can record first/last-seen times even without a purchase. This supports purchase functionality, fraud prevention and purchase reporting/analytics. Again does not send diary data, your name or email, or payment card details to RevenueCat, and does not enable advertising identifier collection or attribution integrations in its code. The SDK also reads and sends the iOS App Tracking Transparency permission status without asking for tracking permission.
Reminders, Siri and Shortcuts
The optional reminder is off by default. If enabled with notification permission, iOS schedules it locally; no remote push service is used. Again’s Shortcuts actions and their pending commands are handled locally and open Again to finish logging. Apple controls Siri voice processing, which may use Apple servers depending on the device and settings. Again does not upload voice recordings.
Your choices and questions
You can edit or delete diary entries, manage camera and notification permissions in iOS Settings, and keep your own exports. For privacy questions or requests about purchase-related data, contact us at remsysstudio@icloud.com. If you email us, we receive your address and the information you choose to include, and use it to answer your request. Third-party processing and retention follow the linked policies. We will update this page and its effective date when this policy changes.
RevenueCat — SDK Attributes · RevenueCat — Privacy · RevenueCat — App Privacy · RevenueCat — Customer Profile · Open Food Facts — Privacy · Apple — Privacy · Siri — Privacy