Privacy Policy

1.1 Information You Provide (Required)

• Account information: iCloud account identifier, and subscription status.
• User content: recipes you save or import, cooking notes, ratings, tags, grocery lists, meal plans, and cooking history.
• Support communications: messages or feedback you send to us.

1.2 Subscription & Payments

• Subscriptions are processed by Apple’s App Store.
• We do not collect or store full payment or credit-card information.

1.3 Automatically Collected Information

• Device information: device type, operating system version, app version.
• Usage data: feature-usage and interaction events, only when optional first-party analytics are enabled for your build (see 1.4). We do not collect crash logs, performance traces, or other diagnostic data.

Usage data is collected only to improve the App. This data is not used for advertising or cross-app tracking.

1.4 First-party analytics (optional)

When enabled in a build, the App sends first-party analytics events to our secure HTTPS API at api.marinaid.app, hosted on Amazon Web Services (AWS) in the United States. We do not embed third-party advertising or cross-app analytics SDKs for this purpose.

To authenticate the App with our API we first perform a short challenge/response exchange that sends your pseudonymous CloudKit user record name and a client-side challenge response over HTTPS, and receive a short-lived access token in return. No password, email, or Apple ID is transmitted.

Every event carries:

• A random event id (UUID) and an ISO-8601 timestamp
• The event type (one of the categories below)
• Your account pseudonym — a stable identifier derived from your iCloud / CloudKit user record name (it is not your Apple ID email)

The full list of event types we currently send, and the additional fields each event carries:

• app_opened — UTC calendar date (sent at most once per day)
• recipe_imported — the recipe's source URL, a hash of the recipe id, the recipe title, the canonical recipe page URL, and the recipe image URL
• recipe_cooked — recipe id hash, recipe title, page URL, image URL
• recipe_meal_planned — recipe id hash, recipe title, page URL, image URL, and the UTC date the meal is planned for
• recipe_share_link_created — recipe id hash, recipe title, page URL, image URL, total share count
• recipe_favorited — recipe id hash, favorite on/off
• recipe_rated — recipe id hash, your 1–5 rating (0 if cleared)
• recipe_viewed_engaged — recipe id hash and how many milliseconds it was visible
• collection_created / recipe_added_to_collection — a SHA-256 hash of the folder id
• grocery_items_added_from_recipe / grocery_synced_to_reminders / grocery_sent_to_instacart — item count only (no item names)
• household_membership — your role (owner / member / none) and the number of other members
• subscription_changed — whether the resulting state is Pro

Several events therefore include recipe titles, source URLs, and recipe image URLs (clearly identifiable user content). They do not include the full recipe body, your free-text notes, or your grocery item names. Cooking voice transcripts and on-device OCR results never leave the device.

Aggregate recipe snapshots: we maintain a separate database of information keyed only by recipe id hash (without your account id on those snapshot records) to power community-wide metrics and enrichment. Our servers may occasionally fetch public web pages (for example, the same recipe URL used for import) to fill in missing titles or preview images for those aggregates—subject to reasonable limits and only for operational purposes, not for advertising profiles.

If analytics are not configured for your build, or the App cannot obtain a short-lived access token, events remain on your device and are not transmitted.

1.5 Feedback you submit

When you tap a Send-feedback control inside the App, the message is delivered to the same api.marinaid.app service. The exact payload depends on the form:

• Import-quality feedback — recipe id, recipe title, source URL, video URL (if any), one or more issue tags (ingredients / steps / times & servings / other), a severity level, and your free-text comment (up to 2,000 characters). Each submission also includes basic device info (app version, build number, iOS version, device model) so we can reproduce parsing problems.
• Import-failure reports — the URL that failed to import (HTTPS only), the error message, and an error type label.
• General app feedback — your free-text comment (up to 2,000 characters) and an optional context string.

Free-text comments may include any information you choose to type. Please do not include sensitive personal data.

1.6 Information We Do Not Collect

• Precise location data
• Contact lists
• Photos or media outside content you explicitly import
• Health-profile fields you enter to personalize nutritional goals (age, sex, height, weight, activity level, goal). These are stored only in your private Apple CloudKit container and on your device. They are never sent to our servers, included in analytics events, or shared with third parties.
• Cooking voice transcripts — speech recognition runs on-device and audio is not retained
• OCR text from photos you scan — text extraction runs on-device

Marinaid is an iCloud-based service and requires an Apple ID with iCloud enabled.

Your data is stored in your private Apple iCloud account via CloudKit and is associated with your Apple ID. A local database on your device provides offline access and is synced automatically with iCloud.

Optional analytics events and aggregate snapshot data may be stored in AWS (for example, DynamoDB) in the United States, separately from your iCloud recipe library. Raw analytics events are associated with your pseudonymous analytics subject id; aggregate snapshot rows keyed by recipe id hash are designed not to include that subject id.

Data is used solely for:

• Core App functionality
• Cross-device sync via iCloud
• Backup and recovery
• Subscription entitlement verification

Your data is private, stored in your personal iCloud container, and not visible to other users.

Marinaid integrates the following third-party services:

• Apple iCloud (CloudKit) — cloud sync and storage of your recipes, grocery lists, meal plans, cooking history, and profile. Data is stored in your private iCloud container (or, for shared households, a shared CloudKit zone) and governed by Apple's Privacy Policy.
• Amazon Web Services (AWS) — hosts our marketing site, static recipe-site catalog, and optional first-party analytics + feedback API infrastructure (United States). Data processed on AWS is covered by this policy and AWS's role as a processor under our configuration.
• RevenueCat — subscription management and purchase verification (United States). Receives your anonymous user identifier and App Store subscription transaction data. We do not send custom user attributes. Governed by RevenueCat's Privacy Policy.
• Instacart — when you tap "Send to Instacart" from a grocery list, we POST your item names, quantities, and units to Instacart's product-link API so they can build a shopping cart for you. We do not send your name, account id, or any other recipe context. Governed by Instacart's Privacy Policy.
• Google Favicons API — retrieves website icons for display alongside recipe sources. Only the source website's hostname is sent; standard HTTP request data (your IP address, user agent) reaches Google. No account or recipe identifiers are sent.
• Recipe source websites — when you import a recipe from a URL, the App fetches that public web page directly from its host (for example, NYT Cooking, an Instagram post, a TikTok video URL). Standard HTTP request data (your IP address, user agent) reaches that site; we do not send your account information.

We do not use third-party in-app analytics SDKs, crash-reporting SDKs, or advertising frameworks. Optional analytics are sent to our own API, not to a separate ad-tech network.

Third-party services are not permitted to use your data for advertising or their own independent purposes.

Marinaid includes opt-in social features that let you publish content to a public Marinaid profile so other users can discover and follow you. This content is stored in Apple's public CloudKit database (separate from your private library). Publishing is per-item and requires an explicit action; nothing is published by default.

If you choose to publish, the following may appear in the public database:

• Profile: handle, optional bio, optional profile photo (downsized)
• Recipes: title, ingredients, steps, source URL, video URL, up to four images, author, cuisine, category, and a compressed full-recipe payload
• Folders: folder name and the list of recipe ids it contains
• Meal plans: weekly plan entries
• Cook logs: which recipe you cooked, when, and your rating
• Follow graph: who you follow and who follows you

You can stop publishing any item, or wipe your entire public profile and social graph, from Account → Privacy → Delete my public data. See "Data Retention & Deletion" below for details.

European Economic Area (GDPR)

If you are located in the EEA, you have the right to:

• Access your personal data
• Correct inaccurate data
• Request deletion of your data ("right to be forgotten")
• Restrict or object to processing
• Request data portability

California (CCPA / CPRA)

California residents have the right to:

• Know what personal information is collected
• Request deletion of personal information
• Opt out of the sale or sharing of personal information

Marinaid does not sell or share personal information for cross-context behavioral advertising.

You may exercise your rights by contacting us.

For App Store transparency purposes, Marinaid may collect:

• Identifiers: pseudonymous account id derived from your iCloud user record name (linked to user; shared with RevenueCat for subscription management).
• User Content: recipe titles, source URLs, and image URLs in analytics events; free-text comments in feedback submissions; grocery item names, quantities, and units when you send a list to Instacart; whatever you choose to publish via opt-in social features (linked to user).
• Purchase History: subscription transactions (managed via App Store and RevenueCat).
• Diagnostics: app version, build number, iOS version, device model, and event counts / dwell times in analytics (linked to user).
• Usage Data: app interaction events from first-party analytics (linked to user; not used for advertising or cross-app tracking).

Health & Fitness data is not collected by the developer. The age, sex, height, weight, activity level, and goal you optionally enter to personalize nutrition targets are stored only in your private Apple CloudKit container and never reach our servers.

Data is used strictly for App functionality, analytics, and subscription management and is not used for advertising or tracking across apps or websites.