Konbi privacy policy
Last updated: 11 November 2026.
About this policy
Konbi is a shared shopping-list app developed by Wacky Works Digital. This policy explains the app's data handling. It is separate from the general Wacky Works Digital website policy. Contact konbi@wearewacky.com with privacy questions or data requests.
Wacky Works Digital is a trading name of K. Lam Executive Support Ltd, the data controller for Konbi. Registered office: 142-143 Parrock Street, Gravesend, Kent, England, DA12 1EY. We process account and shopping information to provide the service you request, technical information for our legitimate interests in operating and securing it, and information where needed to meet legal obligations. Optional microphone input is initiated by your choice and device permission.
Your account and shared lists
Konbi uses an account for shared lists and synchronisation. Supported sign-in providers include Google, Apple and Microsoft, depending on your app version and provider availability. Provider sign-in creates a Konbi account and provides an account identifier, name, email address and, when available, profile photo. We use these details to sign you in, maintain your profile and identify contributions.
Current versions support email registration with email verification and sign-in to confirmed Konbi accounts using an email address and app-specific password. Our authentication service verifies these credentials. This does not give Konbi access to your email inbox. Password-reset emails are not currently offered.
We store the lists and items you create, including names, quantities, units, order, checked status and added/bought attribution, plus list membership and invite codes. People with access to a shared list can see its contents and contributor names or profile images. Only share codes with people you intend to invite.
Storage and synchronisation
The app keeps account-bound local copies and pending changes so shopping can continue without connectivity. Our isolated Microsoft Azure backend uses self-hosted Supabase and PowerSync to authenticate accounts, store app data and synchronise shared lists. Network infrastructure receives technical information such as IP addresses and request/device information needed to operate and secure the service.
Firebase Cloud Messaging processes installation identifiers and messaging tokens to deliver synchronisation hints on supported devices. Android token registration can occur even if notification permission is declined. These hints prompt the app to fetch permitted data; delivery depends on device and network conditions. Google and Microsoft may process technical information under their own service terms.
On mobile, tapping Add may read text from your clipboard to offer importing several items. If you accept, the imported items become shopping-list data and follow the same storage and sharing rules.
App diagnostics can contain shopping text, account or item identifiers, and incoming links. Service diagnostics can include request metadata and errors. We use diagnostics to operate and troubleshoot Konbi. Device logs and provider logs have different storage and retention; we do not promise a fixed expiry for every log.
Optional voice, app lock and widgets
If you choose voice input, Konbi requests microphone permission and records your command. The recording is held in a temporary file on your device and processed according to your app version. Android version 0.3.15 and later send it through our authenticated Konbi backend to Microsoft Azure Speech for transcription. The transcript is sent to an Azure-hosted language model to extract shopping items. Extracted names, quantities and units are added to your list. Do not include information you do not want sent to these services. You can use manual item entry without microphone permission.
The Azure voice version attempts to remove its temporary recording after success, failure or cancellation. Its backend processes audio and transcripts in memory without writing them to application logs or permanent storage; extracted results may be cached in memory for up to five minutes to handle repeated requests. Azure Speech fast transcription does not retain input audio according to Microsoft's service documentation. Downstream Azure model handling includes applicable abuse monitoring and may involve retention or review. We do not promise universal zero retention.
Earlier app versions send voice recordings to Google's Firebase AI/Vertex AI service for Gemini. Those versions may leave temporary recordings on your device until replaced or cleared by device storage management. Updating to the Azure voice version changes the provider; it does not automatically remove recordings left by an earlier version. Google's generative AI voice route has an under-18 use restriction.
Optional biometric verification uses your device's operating-system authentication. Konbi does not receive or store your fingerprint or face template. Widget appearance settings stay on the device. A home-screen widget may display shopping details to anyone able to view that screen.
Use, providers and your choices
We use app data to provide accounts, shopping, sharing, synchronisation and support, and to protect the service. We do not sell shopping or account data or use it for behavioural advertising. Infrastructure, Google sign-in, messaging and optional voice providers receive the information necessary to perform those functions. This is not a claim that no third party processes data or that all processing happens in one country.
You can edit your profile and shopping items, manage list sharing, revoke microphone access in device settings, and request access, correction or deletion by contacting us. Signing out or uninstalling alone does not delete the account or server-side data.
Depending on applicable law, you may also request portability, restriction of processing or object to processing. Contact us to exercise these rights or raise a concern. You can complain to the UK Information Commissioner's Office.
Retention and account deletion
We keep account and app data while needed to provide your account, shared shopping and support, or for legitimate security and legal purposes. Request account deletion from your profile in current Konbi versions by choosing Request account deletion and confirming the request. You do not need to send a separate email after submitting it in the app. See the dedicated Konbi deletion page for instructions and help if you cannot sign in. Never send passwords or sign-in codes.
After verifying a request, we remove your Konbi account and associated personal data and confirm completion. Deleting a list owner's account also deletes their lists and items. Shared list information owned by another member may remain for other members with your personal attribution removed. Any data retained for security or legal obligations, or awaiting expiry from backups, will be explained as applicable. Copies already held by other people or on an offline device may not disappear immediately. We do not claim instant deletion or an unverified fixed backup-retention period.
Children and updates
The initial Google Play release targets adults aged 18 and over. This does not mean that no personal data is collected from existing younger users. Moving the current voice feature to Azure does not change our initial adult launch audience or complete the requirements for a child-directed service. A parent or guardian should contact us with questions or deletion requests involving a child's data. A store age setting does not itself prevent use in an already-installed app.
We may update this policy when the app or its providers change. The current version and date are shown here.
