This Privacy Policy explains how SweetSpot Healthcare Supplies (Pty) Ltd, trading as Cocoa Health (“Cocoa”, “we”, “us”), collects, uses, and shares information when you use the Cocoa mobile app and our websites, including cocoahealth.co and related pages such as our waitlist and guides.
Cocoa is a diabetes meal-guidance companion. It is not a medical device and does not provide medical advice. If you have questions about your health, please speak with a qualified clinician.
1. Who we are
SweetSpot Healthcare Supplies (Pty) Ltd, 136 Jan Jonker Road, Windhoek, Namibia. Email: [email protected].
2. Information we collect
Depending on how you use Cocoa, we may collect:
- Account information. Name, email address, and password if you create an account with email. If you use Sign in with Google or Sign in with Apple, we receive the identifier, name, email, and (where provided) profile photo associated with that account. Apple may provide a private relay email instead of your real address.
- Health and meal information you give us. During onboarding you enter, or speak and we transcribe on your device, details such as your goals, diabetes type, treatments, glucose-tracking method, meal frequency and timing, day-to-day realities, and foods you want to avoid. Speech stays on your device. We store the transcript, not the audio.
- Meal photos. When you take or choose a photo to log a meal, we transmit that photo to analyze the meal. We do not keep the image file after the analysis request finishes. If you confirm the meal, we store the meal name, estimated nutrition, and the analysis.
- We may also store glucose readings, medications, and similar health metrics as those features become available.
- Purchase information. Subscription or in-app purchase status and entitlements. Payments are processed by Apple or Google. We use RevenueCat to manage subscriptions. We do not store your full payment card number.
- Website and waitlist information. Name, email, and optional quiz answers if you join the waitlist; email and related details if you request a guide.
- Usage, device, and diagnostics. App and website activity, approximate device type, crash reports, and similar analytics needed to operate and improve Cocoa.
- Advertising and attribution identifiers. On iOS, if you allow app tracking, we collect the device advertising identifier. We also collect an anonymous identifier created by the Meta SDK, the iOS vendor identifier, and IP address. We store these with your RevenueCat customer record so that trial and subscription events can be matched to ads. If you do not allow tracking, we do not collect the iOS advertising identifier.
3. How we use information
We use the information above to:
- Create and authenticate your account
- Provide personalized meal guidance and in-app features
- Analyze meal photos and suggest quests. When you allow it in the app, we send the data described in section 7 to OpenAI for that purpose.
- Process and restore subscriptions
- Send waitlist, guide, and product emails you request
- Understand product usage, fix bugs, and improve Cocoa
- Measure ads that lead people to Cocoa, including app installs, completed registration, trial starts, and paid subscriptions
- Comply with law and protect the service
4. Google user data
If you sign in with Google, we request basic account information (such as your Google account identifier, name, email address, and profile photo) solely to create and sign you into your Cocoa account and to provide the Cocoa service.
We do not sell Google user data. We use the name and email from a Google account to create and sign you into Cocoa. We also send that email address to RevenueCat. When our Meta ads integration is enabled, RevenueCat hashes the email and sends it to Meta so Meta can match a subscription or trial to an ad. We do not send Meta health or meal information from a Google account. We do not use Google user data to build advertising audiences from that health or meal information. Apart from this, we share Google user data with service providers that help us operate Cocoa, and only as needed to provide the service.
5. Apple Sign in
If you use Sign in with Apple, Apple may share a unique identifier and, depending on your settings, your name and email or a Hide My Email relay address. We use this only to create and maintain your Cocoa account.
6. Health information
Meal logs, photos, glucose readings, medications, and similar content are sensitive. We treat them as confidential, use them to provide and improve Cocoa, and do not sell them. Cocoa is not intended to diagnose, treat, or replace professional medical care. This policy is not a claim of HIPAA coverage.
We do not send meal photos, meal logs, diabetes type, treatments, glucose information, or other health details to Meta for advertising.
7. How we share information
We share information with:
- Apple and Google for sign-in and in-app purchases
- RevenueCat, to manage in-app subscriptions and entitlements, and to send subscription events to Meta. Those events include trial start and paid subscription, together with the advertising and attribution identifiers in section 2 and a hashed email address where we have one.
- Hosting and infrastructure providers that store app and website data
- Email providers (including Resend) to send waitlist, guide, and account messages
- Plausible for privacy-focused website analytics
- Meta, in two ways. On our website, the Meta Pixel measures ads and conversions. In the Cocoa iOS app, the Meta SDK records app installs, app opens, completed registration, and App Store purchases. We do not send Meta the health or meal details described in section 6. Meta’s use of the information it receives is covered by Meta’s own terms.
- Clerk, to create and sign you into your account.
- PostHog, for in-app product analytics.
- OpenAI, only after you allow it in the app, as described below.
Sharing with OpenAI
Before the first meal photo is sent, the app asks you to allow sharing with OpenAI. If you do not allow it, we do not send that data and meal scanning stays unavailable. If you allow it, we send OpenAI your meal photo and these meal details: goals, diabetes type, meal frequency, realities, and foods to avoid. After you confirm a meal, we also send that meal’s name, estimated calories and macros, and the analysis, so OpenAI can suggest quests. We do not send your name, email, phone number, or account ID. OpenAI processes this through the OpenAI API in the United States. OpenAI does not use API data to train its models. OpenAI, and every other third party we share data with, must protect that data to the same or equal standard described in this policy.
We may also disclose information if required by law, to protect rights and safety, or in connection with a merger, acquisition, or similar transaction.
8. Retention
We keep account and app data for as long as your account is active and as needed to provide the service. Waitlist and guide emails are kept while we operate those programs or until you ask us to remove them. We may retain limited records as required by law or for legitimate business purposes such as accounting and security.
9. Security and international processing
We use reasonable technical and organizational measures to protect information. No method of transmission or storage is completely secure. We are based in Namibia and may use processors in other countries, including the United States and the European Union. By using Cocoa you understand that your information may be processed outside Namibia.
10. Children
Cocoa is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe we have, please contact us and we will delete it.
11. Your choices and rights
You can access, update, or delete certain information in the app where those controls are available. You may also email [email protected] to request access, correction, or deletion of your personal information, including your account. We will respond as required under applicable Namibian law and any other law that applies to you. To stop new meal data being sent to OpenAI, email [email protected]. You can also delete your account in the app.
You can stop using the app, uninstall it, or unsubscribe from marketing emails using the link in those emails.
On iOS, you can refuse tracking, or turn it off later, in Settings, Privacy & Security, Tracking. If you refuse, we do not collect the iOS advertising identifier. On Android, you can reset or limit the advertising identifier in your device settings.
12. Changes
We may update this Privacy Policy from time to time. We will post the updated version on this page and change the “Last updated” date. Continued use of Cocoa after an update means you accept the revised policy.