Privacy policy
The short version
- Your stack lives on your phone. Your supplements, medications, doses, reminders and dose history are stored only on your device. We never receive them.
- No account, no name, no email. The app signs in with a random anonymous ID so our server can count scans and know whether you have Pro.
- Label photos are read, not kept. When you scan a label, the photo goes through our server to Google Gemini to read the text. We don't store or log the photo.
- Barcodes are looked up at the NIH Dietary Supplement Label Database and Open Food Facts, through our server.
- Recall alerts are checked on your phone. The app downloads the FDA's public recall list and compares it with your stack on the device. Your stack is never uploaded.
- No ads, no analytics, no crash-reporting tools, and we never sell your data.
- Backups are yours. A backup file you make in the app goes only where you save or share it; Android's own backup goes to your Google account. Neither comes to us.
- Delete everything by uninstalling the app, and email us to remove the few records on our server.
1. Who we are
StackSquare™ ("StackSquare", "we", "us") makes the StackSquare app. You can reach us at support@stacksquare.life for any privacy question or request.
2. Data that stays on your phone
Everything you put into your stack is stored only in the app's private storage on your device:
- your supplements and medications, their ingredients and amounts, and your dose schedule;
- your dose log (taken / skipped), reminder settings and app settings;
- a local copy of products you looked up, so a repeat lookup doesn't need the internet;
- for recall alerts: the optional maker, barcode and lot number you add to an item, a copy of the public FDA recall list, and which recall alerts you dismissed or were already notified about.
We do not have a copy, and it is not synced or backed up to our server. Reminders and recall alerts are local notifications created on your phone; we don't send push messages. Exports (CSV, Excel and PDF) are created on your phone. They only leave it if you choose to share or save them somewhere through Android's share sheet, and then the app or service you pick handles them under its own terms.
Backup files. Settings → Backup & restore → Back up now creates one file (.ssq) on your phone containing your stack, schedules, reminder settings, dose history, a few app preferences and your saved products. It doesn't contain your Pro status, your anonymous ID or any sign-in token. The file is not encrypted, so treat it like any other health record: it leaves your phone only where you save or share it (for example your Downloads folder, Google Drive or another app you pick), and that place handles it under its own terms. We never receive it. Restoring reads a file you pick and replaces or merges the data on your phone.
Android backup. If backup is turned on in your phone's settings, Android may also back up the app's database and settings to your Google account and restore them on a new phone. This backup is handled by Google under your Google account, not by us. The app's caches, your Pro status, sign-in tokens and app-integrity tokens are left out or reset on restore, so a new phone gets a new anonymous ID; use Settings → Restore purchases to get Pro back.
3. Data that leaves your phone, and why
3.1 Anonymous ID
The first time the app needs our server, it signs in with Firebase Anonymous Authentication. This creates a random ID (for example kR2…9xQ) that is tied to this installation of the app, not to your name, email or phone number. We use it only to:
- count your label scans and barcode lookups against the Free limits, and
- remember whether this installation has an active StackSquare Pro subscription.
If you uninstall the app or clear its storage, your phone forgets the ID and the app starts over with a new one.
3.2 Label photos (Google Gemini)
When you take or choose a photo of a label (the Supplement Facts panel, the front of a bottle, or a pharmacy label), the app sends that photo over an encrypted connection to our server, which passes it to Google Gemini (Google's AI service) to read the text. We send back only the text that was read (product name, brand, ingredients and amounts, directions).
- We don't store the photo. It is handled in memory for that one request and then discarded. Our server doesn't write it to a database, a file or a log.
- Google processes the photo to provide the Gemini service on our behalf. We use Google's paid Gemini API; under Google's terms for that service, Google does not use your content to train or improve its models. Google may keep request data for a limited time to detect abuse and meet legal obligations. See Google's Gemini API terms.
- For a front-of-bottle lookup, the brand and product name read from the photo are then searched in the NIH database and, if needed, with Gemini's Google Search feature to find the manufacturer's published facts.
- Pharmacy labels can show your name, your pharmacy or your prescriber. The app only needs the medication details, so you may cover or crop out anything else before taking the photo.
- Photos are optional. You can always add an item by name or type it in by hand.
3.3 Barcode and product lookups (NIH and Open Food Facts)
When you scan a barcode, the app sends the barcode number to our server, which looks it up at the U.S. National Institutes of Health Dietary Supplement Label Database (DSLD) and, if not found, at Open Food Facts. These services see a request from our server, not from your phone, and we send them only the barcode or product name, never your ID.
To make lookups faster and cheaper, our server keeps a shared product cache for up to 90 days: the published product facts (name, brand, ingredients), stored under the barcode or the product name. The cache contains product information only. It doesn't record who looked a product up.
The camera is used only while you are scanning. Barcode detection runs on your phone (Google ML Kit, through Google Play services).
3.4 StackSquare Pro subscriptions (Google Play Billing)
Subscriptions are sold and charged by Google Play. We never see your card or payment details. When you subscribe or restore a purchase, the app sends the Google Play purchase token to our server, which checks it with Google Play and saves your subscription status under your anonymous ID: the plan (monthly or yearly), whether it is active, when it renews or ends, and whether auto-renew is on. We also keep the purchase token, so a subscription can be restored on a new phone and so Google Play's renewal and refund notices reach the right record. The app passes your anonymous ID to Google Play with the purchase for the same reason. Google's handling of your payment is covered by the Google Privacy Policy.
3.5 App security (App Check and Play Integrity)
To keep our server from being abused, the app uses Firebase App Check with the Google Play Integrity API. Google Play services check that the request comes from a genuine copy of the app on a genuine device and give the app a short-lived token, which our server verifies. We don't receive device identifiers from this.
3.6 FDA recall alerts
Once a day our server downloads recent drug and dietary-supplement recalls from the U.S. Food and Drug Administration's public enforcement reports (openFDA) and keeps a compact copy of that public list. When you open the app (at most every few hours) and once a day in the background, the app asks our server for the recalls that changed since its last copy. That request carries only the anonymous ID and App Check token every request has (sections 3.1 and 3.5) and the version number of the list the app already has. It doesn't include anything from your stack.
The app then compares the list with your items on your phone, using the brand, product name, maker, barcode and lot number stored there, and shows a banner (and, if you allowed notifications, a notification for serious recalls) when something may match. We don't learn which products you have, whether anything matched, or what you dismissed. Recall alerts are free and don't count toward any limit. You can turn recall notifications off in Settings. A match is a hint to check your label, not a confirmation; talk to your pharmacist or doctor before you stop taking anything.
3.7 Server logs
Like any online service, Google Cloud keeps standard technical logs of requests to our server (for example the time, the function called, whether it succeeded, and the network address it came from). Our own log lines about subscriptions include the anonymous ID and a shortened, scrambled form of the purchase token. Logs are used to keep the service running and secure and are deleted automatically by Google Cloud, normally after 30 days.
4. What our server keeps
| Record | What's in it | Linked to | How long |
|---|---|---|---|
| Anonymous sign-in | Random ID, when it was created and last used | This app installation | Until you ask us to delete it |
| Usage counters | Number of setup scans, scans and barcode lookups this month, the month, last update time | Anonymous ID | Until you ask us to delete it |
| Pro subscription | Plan, active or not, renewal/expiry date, auto-renew, purchase token | Anonymous ID | While you subscribe, and afterwards until you ask us to delete it (Google Play keeps its own records of your purchase) |
| Product cache | Published product facts | Barcode or product name only, not a person | Refreshed after 90 days |
| FDA recall list | Public recall reports copied from openFDA (product, firm, reason, class, lots, dates) | Nobody: public information, not a person | Recalls from the last 2 years, refreshed daily |
| Label photos | Not kept. Read and discarded during the request. | ||
| Your stack, doses, reminders, recall matches, exports, backups | Never sent to us. Only on your phone. | ||
5. Who processes data for us
- Google (Firebase and Google Cloud) runs our server, database, anonymous sign-in and App Check, in the United States (us-central1). Google acts as our processor under the Firebase data processing terms.
- Google Gemini API reads label photos (section 3.2).
- Google Play handles subscriptions, payments and app installs.
- NIH DSLD and Open Food Facts receive product lookups from our server (barcode or product name only).
- U.S. FDA (openFDA): our server downloads the public recall list from it once a day. Nothing about you or your stack is sent.
We don't use any other service providers, and we don't share your data with anyone else except if the law requires it.
6. What we don't do
- We don't sell or rent your data, and we don't share it for advertising.
- The app shows no ads and contains no advertising code or advertising ID.
- The app has no analytics and no crash-reporting tools, and doesn't track you across apps or websites.
- We don't ask for your name, email, phone number, location or contacts.
- This website uses no cookies and no trackers.
7. Security
All traffic between the app, our server and the services above is encrypted (HTTPS/TLS). Our database can only be written by our server; the app can read only its own counters and subscription status. Your on-device data is protected by Android's app sandbox. No system is perfectly secure, so keep your phone locked.
8. Deleting your data
- On your phone: uninstalling StackSquare, or Android Settings → Apps → StackSquare → Storage → Clear storage, deletes everything the app stored on your phone: your stack, dose log, reminders and settings. Exports and backup files you saved elsewhere, and any Android backup in your Google account, aren't affected; delete those where you keep them (you can manage Android backups under Backups in Google One or Google Drive).
- On our server: we hold only the anonymous records in section 4. Email support@stacksquare.life and we'll delete them within 30 days. See Delete your data for how to find your anonymous ID.
- Deleting our records doesn't cancel a subscription. Cancel in Google Play (Play Store → Payments & subscriptions → Subscriptions).
9. Your rights
Depending on where you live (for example under the GDPR in the EU/UK, or California's CCPA), you may have the right to access, correct, delete or get a copy of your personal data, and to object to or limit how it's used. Because the app has no accounts and keeps your stack on your phone, most of your data is already in your hands. For anything on our server, email us and we'll respond within 30 days. You can also complain to your local data protection authority.
Where the GDPR applies, we process data to provide the service you asked for (scans, lookups, subscriptions) and for our legitimate interest in keeping the service secure and within its limits.
10. Children
StackSquare is meant for adults 18 and older and is not directed to children under 13. We don't knowingly collect personal information from children. If you think a child has used the app and you want their data removed, email us.
11. Health information
StackSquare helps you keep track of supplements and medications, which is health-related information. We designed the app so this information stays on your device. The only health-related content that reaches our server is a label photo or barcode you choose to scan, which is used for that request only (plus the shared product facts described in section 3.3). We don't use health information for advertising or share it with data brokers.
12. Changes
If we change this policy, we'll update this page and the effective date. If a change affects what data leaves your phone, we'll also tell you in the app before it takes effect.