Stockd

Support, Privacy Policy, and Terms of Service for the Stockd iOS app.

View the Project on GitHub Kynera-Studios/stockd-pages

Stockd Privacy Policy

Last updated: 2026-07-03 (All sections final; legal-review items (a) analytics-no-opt-out sentence + (b) controller address applied same day. Cross-checked against App Store Connect nutrition labels per docs/privacy/data-inventory.md.)

Effective: July 3, 2026

Stockd is built and operated by Kynera Studios LLC (“Stockd,” “we,” “us,” or “our”). This Privacy Policy explains what we collect, why, where it goes, and what you control.

If you have questions, email info@kynerastudios.com.

Plain-English summary (also legally binding):

  • We collect what’s needed to run a household pantry app: your account identifier, the food items you track, your grocery list, your meal plans, and (if you subscribe) your subscription status.
  • We do not sell your data, do not track you across other apps, do not use advertising, and do not access your photos library, contacts, or location.
  • We use Google Firebase to store your data, Google’s Gemini and Imagen AI to generate recipe text and images, RevenueCat to manage subscriptions, and Open Food Facts to look up barcode product info.
  • You can delete your account at any time from Settings → Delete account. Deletion is a cascade — your data is removed from our systems. (Apple subscriptions, if any, must be cancelled separately in your Apple ID Settings.)

1. What we collect

1.1 Account identifier

When you sign in, we receive an account identifier from your chosen provider:

Firebase Auth assigns a stable internal user ID (UID) that we use to associate your data with your account. Your UID is visible in-app at Settings → User ID.

1.2 What you put into Stockd

1.3 What gets generated for you

1.4 Subscription info

If you subscribe to Stockd Pro, Apple charges your Apple ID and notifies RevenueCat (our subscription middleware), which sends us a webhook event. We never see your credit card, and we store no payment details.

The complete record we keep per subscription transaction is: the transaction identifier, your account identifier, your household identifier, the subscription product ID, the entitlements it grants, the subscription tier, whether the subscription is currently active, the purchase timestamp, the renewal/expiration timestamp, a cancellation timestamp (if you cancel), and the type and time of the most recent billing event — plus whether the transaction came from Apple’s live or test (sandbox) environment.

Our RevenueCat integration is configured for privacy minimalism: the app identifies you to RevenueCat only by your account identifier. We do not use RevenueCat’s advertising-attribution or audience features, do not attach custom customer attributes, and do not collect device advertising identifiers.

1.5 Diagnostics

1.6 Analytics

Stockd v1.0 collects three specific events to validate critical design assumptions:

All three events are sent to Firebase Analytics and are linked to your UID. We do not use this data for advertising or sell it. These events are essential to validating v1.0’s design and cannot be disabled in this version; a settings toggle is on the v1.1 roadmap. The full event taxonomy stays minimal in v1.0; future versions may add events, and this section will be updated accordingly.

1.7 What we do NOT collect

We do not collect: your location, your photos library, your contacts, health data, financial information (Apple handles payment), browsing history, search history across sessions, or sensitive personal data as defined by Apple. We do not use the AppTrackingTransparency framework — Stockd does not track you across other apps or websites.


2. Why we collect it (purposes)

We do not use any of this data for advertising, profiling, or sale.


3. Where it goes (third-party processors)

Provider Purpose What they see
Google Firebase (Auth, Firestore, Cloud Functions, Storage, Analytics) Storage, auth, server compute, analytics Everything in §1 except payment details
Google Gemini API AI text generation Your prompt + pantry item names (no UID, no email)
Google Imagen API AI image generation Recipe name strings only
Apple StoreKit Payment processing Your Apple ID payment info (we never see card data)
RevenueCat Subscription middleware Apple StoreKit transaction events; our UID-to-subscription mapping
Open Food Facts Barcode lookup Barcode digits only
Apple SIWA relay Private email forwarding (only if you chose Hide My Email) Your real email (we never see it)

We have agreements with these providers consistent with our handling of your data. We do not sell or share your data outside this list.


4. Sharing within Stockd (household members)

If you invite other people to share a pantry, those people can view and modify the shared pantry’s items, grocery list, and meal plan entries. Their visibility is to the shared pantry, not to your other accounts or unrelated data.

Removing a household member revokes their access immediately for future reads.


5. Your rights and choices

5.1 EU / UK residents (GDPR)

If you are a resident of the European Union or the United Kingdom, you have additional rights under GDPR / UK GDPR: access, rectification, erasure, restriction of processing, data portability, and objection. To exercise these rights, email info@kynerastudios.com. We respond within 30 days.

The legal basis for our processing is performance of a contract (running the service you signed up for) under Article 6(1)(b) GDPR. For diagnostic and analytics purposes, our legal basis is legitimate interest (Article 6(1)(f) GDPR) — improving the service we provide you.

5.2 California residents (CCPA / CPRA)

If you are a California resident, you have the right to know what personal information we collect, to delete it, to correct it, and to opt out of any “sale” or “sharing” — Stockd does not sell or share your data, so the opt-out is automatic and there is no link to provide. Contact info@kynerastudios.com to exercise other rights.


6. Children

Stockd is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact info@kynerastudios.com and we will delete it.


7. Security

We use industry-standard security practices: encrypted connections (HTTPS / TLS), Firebase security rules enforcing per-user access controls, no plaintext password storage (we use OAuth — there are no passwords for us to store), webhook signature verification for subscription events, and an audit log for account deletions and entitlement changes.

No system is perfectly secure. If we discover a breach affecting your data, we will notify you in accordance with applicable law.


8. Changes to this policy

We may update this Privacy Policy. Material changes will be announced in-app or by email before they take effect. The “Last updated” date at the top reflects the most recent revision.


9. Contact

Privacy questions, data requests, or concerns: info@kynerastudios.com

Stockd is operated by Kynera Studios LLC (the data controller), 7901 4th St N, Ste 300, St. Petersburg, FL 33702, USA.


Kynera Studios LLC · © 2026


Document status note (for the spec / pass-two reviewers): FINALIZED 2026-07-03. (a) OD-b4 SIWA relay-address handling — finalized in §1.1; (b) RevenueCat data set — §1.4 finalized against the shipped 4.0b/4.0c code: per-transaction field set enumerated from rcWebhookHandler.ts (uid, orgId, environment, rcProductId, rcEntitlementIds, tier, isActive, purchasedAt, renewsAt, canceledAt, anonymizedOwnerAt, lastEventAt, lastEventType — no payment data), and attribution-off confirmed from RevenueCatBootstrap.swift (Purchases.configure(withAPIKey:appUserID:) only; no setAttributes, no attribution collection, no device ad identifiers) — data-inventory.md pending-section B closes; (c) Crashlytics — enabled per OD-b5, finalized text at §1.5. Factual basis at docs/privacy/data-inventory.md. The page is publicly live at https://kynera-studios.github.io/stockd-pages/privacy/. Standard caveat: this is a legal document; neither Cece nor Sarah is a lawyer; a second set of eyes is strongly recommended before submission for a product taking payments — see the v1-launch-checklist §6 “second-set-of-eyes legal review” row.