Fiyyi · Beta guide
Your information in the beta.
A practical overview of the information used by the current Fiyyi app. Updated 12 September 2026.
Browsing and local use
The demonstration on the home page uses fictional profiles and does not save your choices. When you use the app without an account, profiles and history are stored in your browser. Clearing browser storage can remove that local information.
Product lookups still contact online services. Local profiles do not mean all app processing happens offline.
When you sign in
Fiyyi uses Supabase for email authentication and cloud features. Your account can be associated with saved profiles, dietary selections, history, favourites and Plus access. Session information is kept so the app can recognise your signed-in account.
Photos and product requests
Photos you submit are sent for packaging analysis. Product requests may include the barcode and selected dietary constraints needed to evaluate or search for alternatives. Upload only information you intend to provide for that product.
Contributions can be held for review before public product data is updated. Product information and contributions may be retained to improve the catalogue. Do not upload sensitive personal information in packaging photos.
Service providers
The current app uses Sites hosting, Supabase authentication and database services, and external product-data services. Payment checkout, when enabled, is handled through Stripe. Fiyyi does not ask you to enter card details into its own beta-code form.
Your controls
You can edit profile selections, clear history and sign out in the app. Clearing local browser data does not by itself delete an account or cloud records. For account-data questions or deletion requests during this beta, contact the person who provided your beta invitation using your existing contact channel.
Do not send passwords, sign-in codes, beta codes or payment details when requesting help.
