Your information, explained
Privacy policy
NextBasket helps households share grocery lists, review receipts and understand their shopping. This page explains how information is used when you use the Android app.
- Your account and household shopping records use Firebase services.
- Receipt images are processed on your device and are not uploaded by NextBasket to a shared photo service.
- Household members can see shared shopping records according to their access role.
- Deleting your account does not automatically delete records that remain in a shared household.
This policy covers the NextBasket Android app and the Constantine Labs website. Constantine Labs is the developer of NextBasket. For privacy requests, contact support@constantinelabs.dev.
1. Information we handle
Account information. NextBasket uses Firebase Authentication for email/password and Google sign-in. This involves your email address, account identifier and authentication information. Your display name and, when provided by your sign-in provider, profile photo information may also be used.
Household and shopping information. We store household names, memberships, access roles, invitations, stores, lists, item quantities, notes, checked status and contributor identifiers. Receipt records can include store names, purchase dates, items, prices, totals, currencies and review status. These records support synchronization, purchase history, insights and replenishment suggestions.
Receipt images and selected files. With your permission or selection, the app captures photos or imports images and PDFs for receipt recognition. It keeps local receipt images and rendered PDF pages in private app storage. Text recognition runs on the device using Google ML Kit. Parsed receipt details are saved to the household database; new writes do not retain the full raw OCR text. Original files in your photo library or other storage remain separate from the app's private copies.
Technical information. Firebase and Google services process information needed to provide and secure their services, including IP addresses and authentication details. ML Kit also collects device/application information, identifiers and performance or usage metrics as described in its disclosures. On-device image processing does not mean that these SDKs send no technical data.
2. Why information is used
- Sign you in and maintain your account and household access.
- Synchronize shared lists and receipt records, including offline changes when connectivity returns.
- Extract receipt details and calculate spending, observed prices and shopping suggestions.
- Protect household access, resolve support requests and process deletion requests.
The current app does not include advertising, Firebase Analytics or Crashlytics integrations.
3. Sharing and service providers
Members of your household can access shared lists, receipts, shopping history and contributor information. Their role determines which changes they may make. Share invitation codes only with people you intend to invite.
NextBasket uses Google Firebase Authentication and Cloud Firestore for sign-in and cloud records, Google sign-in for an optional authentication method, and Google ML Kit for receipt recognition. Google processes service data under its applicable terms and privacy practices. Information may be processed outside your country.
- Firebase privacy and security
- ML Kit terms and privacy
- ML Kit Android data disclosures
- Google Privacy Policy
If you contact support, the email service used to handle your message also processes the information you send. Please do not include passwords or unnecessary receipt or payment details.
4. Storage and security
Cloud records are subject to household membership and role checks. Network connections use encrypted transport. The app keeps an offline database cache and local receipt images on your device. Android cloud backup and app-data transfer are disabled in the app configuration, although behavior may vary by device. No storage or transmission method guarantees absolute security.
5. Retention and deletion
Account and shopping records are retained while needed for the app's functionality or until deleted using the available controls. Shared household records have no automatic expiry.
Successful account deletion removes your authentication account, app profile and household memberships. A household in which you are the sole member is deleted together with its associated shopping records. Owners of households with other members must transfer ownership before using in-app account deletion.
Shared records remain. Lists, receipts and contributor identifiers in households with other members remain until household editors delete those records or the household is deleted. Deleting your account therefore does not erase all content you contributed to a shared household.
Device copies. The in-app sign-out/deletion flow clears this account's private receipt photos and offline data on that device. Those photos have no cloud copy in NextBasket. A web or email request cannot remotely erase files or offline copies on other devices. Original images/PDFs outside the app are not deleted by account deletion.
Provider retention. Removal from provider backups may take longer than deletion from the active app. Firebase states that Authentication logs IP addresses for a few weeks and removes other authentication data from live and backup systems within 180 days after the associated user is deleted. See Firebase's current retention information.
See account deletion options and retained-data details →
6. Your choices
You can edit available account and shopping details, control camera access through Android settings, choose which files to import, sign out, or delete your account. Revoking camera permission prevents new camera captures; it does not remove existing records. Some edits and deletion actions require an internet connection.
Contact the support address below about privacy questions, access or correction requests, or deletion without access to the app.
7. This website and support email
This website is hosted through Cloudflare. Cloudflare processes connection information, such as IP addresses and request details, to deliver and protect the site. We do not add advertising trackers or analytics scripts to these pages. Cloudflare may use security-related cookies or similar mechanisms. See Cloudflare’s Privacy Policy.
Email sent to our support address is routed through Cloudflare to a Gmail inbox managed by Constantine Labs. Your address, message and attachments are processed to respond and verify requests. Please send only the information needed for your request.
8. Changes to this policy
This page will be updated when NextBasket's data practices change. The date at the top identifies the latest version. Material changes will be communicated where required.
9. Contact
NextBasket privacy and support: support@constantinelabs.dev