← Back to APP’nSAVE
PRIVATE BETA · PILOT GOVERNANCE

Privacy notice

How APP’nSAVE handles information during the private pilot.

Short version

No account is required for the pilot. Guest data stays on your device unless you choose to sign in and synchronise supported data to your account. If you choose to sign in, APP’nSAVE stores the email address used for authentication and synchronises supported planning data to your account so it can persist across devices. APP’nSAVE also collects pilot usage analytics and optional feedback so MadLabz can evaluate reliability and improve the pilot.

1. Who operates the pilot

APP’nSAVE is an independent concept prototype operated by MadLabz in New Zealand. It is not affiliated with or endorsed by Foodstuffs or PAK’nSAVE.

2. Guest and account data

APP’nSAVE stores meal plans, Household Food entries, saved recipes, watchlist items, store-specific carts, settings and notification preferences in your browser or installed web app storage so the app can continue to work as a guest and tolerate temporary connection loss.

If you choose to sign in, supported planning data is also synchronised to your APP’nSAVE account in Supabase. This lets it persist when you return on another device. Signing in is optional and uses your email address for passwordless authentication.

3. Information sent to the pilot service

APP’nSAVE may send pseudonymous device/session analytics such as the selected pilot store, searches, recipe or product interactions, basket completion, anonymous campaign/entry-point information and technical error events. For guests these records use a pseudonymous device identifier. If you sign in, account identity can be linked to your current and previously collected device analytics so activity across sessions/devices can be understood as one account rather than several unrelated devices.

If you use Something looks wrong?, the report can include the selected store, relevant product or recipe context, page/app version and the optional note you type. A name or email address is not required.

4. What APP’nSAVE does not need for this pilot

The private beta does not require an APP’nSAVE account, payment card details or a retailer loyalty login. If you choose account persistence, an email address is required for sign-in. APP’nSAVE does not intentionally ask for precise GPS location. You select the pilot store you want to use.

5. Why the information is used

Pilot information is used to operate the service, measure whether recipe and basket decisions work, investigate wrong or missing catalogue matches, improve reliability, understand pilot adoption and prepare aggregate retailer-level pilot reporting.

APP’nSAVE does not sell pilot usage or feedback data to advertisers.

6. Service providers

MadLabz uses hosted infrastructure to run the pilot, including Vercel for application hosting and Supabase for pilot analytics/feedback storage. Those infrastructure providers may process ordinary technical information such as IP address, request metadata and security logs as part of operating their services.

Live product searches also use retailer catalogue services to retrieve current product, price and availability information for the selected store.

7. Retention

On-device data: retained on your device until you clear it or the browser/app removes it. Account data: retained while the account is used for the pilot or until an applicable deletion request is completed, subject to reasonable security, backup and legal requirements.

Pilot analytics and feedback: retained only for operating and evaluating the private pilot. MadLabz’s pilot retention target is to delete or aggregate raw pilot analytics and feedback within 90 days after the pilot evaluation period ends, except where information is reasonably required for security, resolving a reported issue, or a legal obligation.

8. Your choices

You can use the pilot as a guest without creating an account, sign out at any time, remove locally stored plans/items using the app controls, clear browser/app storage, decline browser notifications, and choose whether to submit optional feedback.

For an access, correction or deletion request relating to pilot information, use Something looks wrong? in APP’nSAVE, choose the general issue option and write “privacy request” in the note. For guest-only records, MadLabz may need the relevant device/session or report context to locate a record. For account data, the account email can help identify the relevant records.

9. Changes to this notice

The pilot is evolving. If information handling materially changes, this page will be updated before or alongside that change.

Private pilot notice · Updated 26 September 2026

Pilot terms APP’nSAVE