Cookies & device storage
Pilot version · Feature description updated 19 October 2026. Operator details, a complete retention schedule and international-transfer arrangements still need completing.
2026-10-19-pilot-7
1. Technologies currently used
Current app code uses browser localStorage or native AsyncStorage for login sessions, authentication verification information, interface language, user listing drafts, pending image-cleanup records and push-device state. Mobile upload previews may be copied temporarily into app storage; the local demo additionally stores fictional test data. Device-storage rules may apply even where the technology is not a cookie.
2. Purposes, clearing and limits
Session and authentication information maintains sign-in and helps prevent authentication-request substitution. Language stores your display choice and drafts let you resume listing. Signing out ends app sign-in but does not guarantee clearing all drafts, language or other local data. Browser site-data settings or operating-system app-data controls can clear these; doing so may sign you out and lose unpublished drafts.
No advertising-tracking or analytics SDK is configured in the inspected app code. This does not cover cloud-service logs or third-party sign-in pages. Before adding non-essential analytics, advertising or cross-site tracking, disclose purposes, providers and durations and provide rejection and withdrawal choices under applicable rules. No current universal consent button manages every third-party cookie.
3. Device permissions
Camera access is requested when you choose to take a photo; you select photos through the system picker. Refusing permission affects the corresponding feature, not unrelated features. Device push requires a suitable build, configuration and your permission. Manage permissions in system settings; capabilities can differ between web, Expo previews and standalone builds.