Privacy Policy

Last updated: September 8, 2026

This Privacy Policy describes how RgafDev ("we", "us", or "our") handles information when you use the GroCards Grocery Shopping Lists Android application ("GroCards" or the "App"). This policy applies to the Android application with package name com.rgafdev.grocerycards.

Summary: GroCards is a local-first application and does not require an account. Grocery lists and related content are primarily stored on your device. Limited information may leave your device through in-app advertising, analytics, crash reporting, Meta advertising measurement, barcode lookup, speech recognition, Google Play services, Android backup, or features you intentionally use to share information.

1. Information stored on your device

GroCards stores the information needed to provide its grocery-list features locally on your device. This may include:

Grocery-list names and grocery items
Categories, quantities, notes, and item status
Shopping history and purchase-frequency information
Reminders and notification preferences
Application and appearance settings
Custom item photographs or images
Premium-feature status

GroCards does not provide a GroCards cloud account and does not upload your complete grocery lists to a GroCards-operated server.

Android backup

Depending on your device and Android backup settings, some locally stored App data may be included in an Android backup or transferred to another device. These operations are controlled by Android and your Google account settings, not by a GroCards-operated server.

Sharing and importing lists

If you choose to share a list, GroCards creates a shareable file and sends it, together with a list preview and the recipient address you entered, to the email or sharing application you select. That application and its provider process the information according to their own privacy practices.

GroCards imports a list only when you select or open a compatible file and confirm the import.

2. Third-party services

Google AdMob

GroCards uses Google AdMob to display advertising inside the App. The Google Mobile Ads SDK may automatically collect or share information such as:

IP address, which may be used to estimate the device's general location
Advertising ID, App Set ID, and other device or account identifiers when available
App launches, taps, ad impressions, and ad interactions
Device model, operating system, language, and App version
Diagnostic information such as startup time, crashes, hangs, and performance information
Information used to detect advertising fraud and abuse

Depending on your location, device settings, and consent choices, AdMob may display personalized, non-personalized, or limited ads.

We use AdMob to support the App, display advertising, measure advertising performance, and prevent fraud. Google processes AdMob information according to the Google Privacy Policy.

Meta App Events

GroCards uses the Meta Android SDK to measure advertising campaigns that promote GroCards on Meta platforms. This does not mean that Meta ads are displayed inside GroCards.

Automatic Meta App Events may report information such as:

Installation or first activation of the App
App launches or activations
The date and time of an event
App package, version, and platform information
Device, operating-system, language, and network information
IP address and approximate location derived from it
Advertising or device identifiers when available and permitted by device settings and applicable law

We use this information for advertising attribution, campaign measurement, campaign optimization, fraud prevention, and understanding whether Meta advertisements result in installations or App launches.

GroCards does not use Facebook Login and does not request access to your Facebook profile, friends, posts, or messages.

Meta processes information it receives according to the Meta Privacy Policy.

Firebase Analytics

GroCards uses Google Firebase Analytics to understand how the App is used and to improve its features. Firebase Analytics may process:

App launches, sessions, and first-use events
App and device identifiers
Device model, operating system, language, and App version
Network information and approximate location derived from IP address
Feature interactions, such as opening a screen, creating a list, adding an item, using the scanner, or changing a setting
Counts such as the number of items or categories in a list
The category associated with certain actions, which may include a user-created category label
Technical information about feature or service failures

Firebase Analytics events are not intended to contain your email address, complete grocery lists, item names, notes, photographs, or audio recordings.

Firebase information is used for aggregated usage analysis, application improvement, performance measurement, and troubleshooting.

Learn more from Firebase Privacy and Security.

Sentry error reporting

GroCards uses Sentry to identify crashes, errors, and reliability problems. When an error occurs, Sentry may receive:

Crash reports, error messages, and stack traces
App version and release information
Device model and operating-system information
Technical diagnostics and limited application context
Network information, which may include an IP address

We use this information to diagnose technical problems, maintain security, and improve application stability. We do not intentionally attach complete grocery lists, custom photographs, email addresses, or audio recordings to Sentry reports.

Learn more in the Sentry Privacy Policy.

Open Food Facts barcode lookup

When you scan a product barcode and request product information, GroCards sends the barcode to Open Food Facts. Open Food Facts also receives standard network-request information, such as your IP address and the GroCards application identifier included in the request.

This information is used to return product names, quantities, categories, and related product information. GroCards does not send your complete grocery list as part of a barcode lookup.

Learn more from the Open Food Facts Privacy Policy.

Speech recognition

If you use voice entry, GroCards requests microphone access and sends the recorded speech to the speech-recognition service configured on your Android device. Depending on your device and service provider, recognition may occur on the device or through the provider's servers.

GroCards receives the recognized text so it can add or modify list items. GroCards does not intentionally retain an audio recording after the recognition request. The speech-recognition provider's privacy policy applies to its processing.

Google Play and Android services

GroCards uses Google Play and Android services for application distribution, purchases, ownership checks, barcode scanning, in-app reviews, backup, and other platform functionality.

If you purchase a premium feature, payment information is processed by Google Play. GroCards may receive a product identifier, purchase status, and purchase token needed to verify or acknowledge the purchase. GroCards does not receive your complete payment-card number.

Contacting us

If you contact us by email, we receive your email address, message, and any information or attachments you choose to provide. We use that information to respond, investigate problems, and maintain reasonable support records.

Privacy-policy hosting

This Privacy Policy is hosted using GitHub Pages. When you visit this page, GitHub may process standard website-request information according to the GitHub General Privacy Statement.

3. Device permissions

GroCards may request the following permissions when needed:

Camera: used to scan barcodes or take custom item photographs. Custom photographs are stored locally unless you choose to share a list containing them.
Microphone: used when you activate voice entry. Speech may be processed by your device's speech-recognition provider.
Notifications: used to display reminders you configure, where required by your Android version.

You can deny or revoke these permissions through Android settings. A related feature may not work without its required permission.

4. How information is used

Information described in this policy is used to:

Provide the features you request
Save and restore application data
Display and measure in-app advertising through AdMob
Process and verify premium purchases
Look up products from scanned barcodes
Convert speech into grocery-list text
Understand application usage and improve features
Diagnose crashes and technical problems
Maintain the security and reliability of the App
Measure and optimize Meta advertising campaigns
Prevent advertising fraud and abuse
Respond to support requests
Comply with applicable legal obligations

5. How information is shared

Information may be shared:

With Google AdMob for in-app advertising and measurement
With Meta for advertising attribution and campaign optimization
With Google Firebase for application analytics
With Sentry for crash and error reporting
With Open Food Facts when you request a barcode lookup
With Google Play or Android providers for platform features
With an email, messaging, or sharing application when you intentionally share a grocery list
When required by law or reasonably necessary to protect users, the App, or our legal rights

We do not sell your grocery-list contents, custom photographs, support emails, or contact information for money. Some privacy laws may classify advertising and advertising-measurement data transfers as sharing or processing for targeted advertising.

6. Retention and data deletion

How to request deletion

GroCards does not use Facebook Login and does not store Facebook profile information. The Meta SDK may process app-install, app-launch, advertising attribution, and, if enabled, purchase-event information.

To delete data stored locally by GroCards, delete your lists, clear the App's storage through Android settings, or uninstall the App.
To request deletion of information under our control, email grocards.studio@gmail.com with the subject GroCards Data Deletion Request.
Include enough information to identify the relevant support request or record. Do not send passwords, payment-card information, or other sensitive information.

We will respond without undue delay and normally within 30 days. Because GroCards does not use user accounts, some anonymous or pseudonymous analytics and advertising records may not be identifiable as belonging to a particular person.

7. Your choices and privacy rights

Depending on your location, you may have the right to:

Request access to personal information about you
Request correction or deletion
Object to or restrict certain processing
Withdraw consent where processing is based on consent
Request a portable copy of applicable information
Appeal the handling of a privacy request
Complain to your local data-protection authority

You can also manage advertising personalization, reset or delete your Android advertising identifier, revoke camera or microphone permissions, avoid optional online features, delete local lists, clear the App's storage, or uninstall the App.

8. Security

We use reasonable safeguards appropriate to the nature of the App. Network requests made directly by GroCards use encrypted HTTPS connections. Third-party services are responsible for securing information processed on their systems.

No method of storage or transmission can be guaranteed to be completely secure.

9. International processing

Google, Meta, Sentry, Open Food Facts, GitHub, and other service providers may process information in countries other than the country where you live. Their privacy policies describe their international data-transfer practices and safeguards.

10. Children's privacy

GroCards is a general grocery-list application and is not directed to children under 13. We do not knowingly request personal information from children. If you believe that a child has provided personal information to us, contact us so we can investigate and take appropriate action.

11. Changes to this policy

We may update this Privacy Policy when GroCards changes, when service providers change, or when legal requirements change. The date at the top identifies the latest revision.

12. Contact

For questions, privacy requests, or concerns about this policy, contact:

Developer: RgafDev
Email: grocards.studio@gmail.com