Privacy policy · Effective October 25, 2026

How ClipCart Grocery handles your information.

This policy covers the invitation-only ClipCart iPhone beta and the ClipCart Grocery website, including its email waitlist.

Two separate experiences

The iPhone app is an invitation-only beta for iOS 26 or later. It lets you sign in to your Smith’s account in an embedded browser, review coupon information, and start clipping yourself. Clipping does not run on a schedule or start on its own.

The website has an optional email waitlist. The website’s pricing, signup, dashboard, and account features describe a separate web service and are not part of this iPhone beta. The iPhone beta does not require a paid subscription.

Information on your device

When you sign in, you enter your retailer credentials directly into the embedded Smith’s sign-in page. ClipCart does not ask you to type those credentials into a ClipCart form. The retailer’s sign-in page and its own privacy practices apply to that sign-in.

The app keeps retailer web session data and app records on your device. These can include a local account link, coupon inventory, clipping run history, and records used to track clipping actions and unresolved results. The retailer session snapshot is stored in the iOS Keychain as device-only data and is not configured to sync through iCloud. ClipCart may not be able to remove every app record just because you disconnect or delete the app; iOS backup, Keychain, and app removal behavior can affect what remains on a device.

The app has no advertising or third-party analytics SDK integration. Apple’s TestFlight may collect beta feedback, crash reports, or usage information under Apple’s settings and policies.

Information you choose to send

You can review and explicitly send a bug report from the app. A report may include app version and build, source version, device model, iOS version, simulator status, run and connection states, fixed failure categories, coupon and processing counts, and limited timing or progress information. It does not include retailer credentials, cookies, or your retailer account identifier in its automatic diagnostic fields.

You may add a note of up to 2,000 characters. Notes are free text and could contain personal information, so leave out passwords, verification codes, account details, and other sensitive information. The report is sent over HTTPS to our report service at reports.clipcartgrocery.com. Sending is optional and requires your action.

The invitation code is stored in a device-only Keychain entry and sent to the report service only to authorize a submission. The service stores a digest of each code in its invitation records and associates submissions with an internal invitation reference. This groups reports submitted with the same invitation; it does not verify a person, retailer account, or device identity. Anyone who has your code may be able to submit reports with it. Contact us if a code is lost or shared.

Reports are stored privately by the service operator and may be reviewed using OpenAI-powered tools to help triage issues. Relevant technical summaries may be added to confidential GitLab issue tracking. User notes and private model reasoning are not published as issue text. Report submission does not automatically create an issue or mean that a report has been confirmed.

Email waitlist and site operations

If you join the waitlist, the site sends your email address, a source label for the signup page, and the submission time to a Google-backed waitlist service. The email is used to manage the waitlist and contact you about ClipCart. Joining is optional. Contact us to ask for your waitlist entry to be removed.

Website hosting and the report-service connection use Cloudflare infrastructure. Those providers may process technical request information, such as IP address and request details, to deliver, protect, and operate their services under their own policies. We do not promise that network providers never process or retain such information.

Why information is used

We use information to operate the beta and waitlist, provide features you request, receive and investigate reports, protect service availability, and respond to support requests. We do not use beta information for advertising.

We share information with service providers that host or support the website, waitlist, report intake, beta distribution, or issue review, and when needed to protect rights, safety, or the service or to comply with law. A recipient’s own privacy policy and practices also apply to information it receives.

Relevant third-party information: Apple Privacy, Kroger Privacy Policy, Cloudflare Privacy Policy, Google Privacy Policy, OpenAI Privacy Policy, and GitLab Privacy Statement.

Keeping and deleting information

App records are stored locally on your device. Some records, including unresolved action records, may be retained to avoid losing track of an uncertain retailer action. Disconnecting or deleting the app does not promise that every local record is erased; iOS backup, Keychain, and app removal behavior can affect what remains.

Bug report originals and their private triage records have no automatic deletion schedule and remain stored until the operator deletes them. If the report service reaches its storage limit, it rejects new submissions; stored reports are not automatically deleted to make room. You may ask us to locate and delete a report by providing its report ID, if available. Backups and copies made by service providers may take additional time to expire, and a deletion request may not remove information that must be kept for security, legal, or operational reasons.

Waitlist information is kept while it is useful for the waitlist and related communications. The waitlist currently has no published fixed deletion period. You can request removal using the contact below.

You can stop using the app at any time and choose not to send reports or join the waitlist. To request deletion or ask a privacy question, email support@clipcartgrocery.com. Include a report ID for a report deletion request; do not send passwords or retailer credentials.

Safeguards and policy updates

We use safeguards appropriate to the beta’s operation, including device-only Keychain storage for retailer session snapshots and HTTPS for report submissions. No method of storage or transmission can be guaranteed completely secure.

The app is not designed for children. We do not knowingly seek personal information from children through the beta or waitlist.

We may update this policy as the service changes. The effective date above shows when this version took effect.