Privacy Policy

This Privacy Policy applies to:

• the SpinFreeze mobile application;
• user accounts and authentication flows;
• public recipe and community features;
• premium subscription features;
• customer support interactions related to the app;
• related infrastructure and service providers used to operate SpinFreeze.

We collect information directly from you, automatically through your use of the service, and from service providers that help us operate SpinFreeze.

Account & Authentication

We may collect your email address, password credentials, internal account ID, authentication provider details (Google Sign-In, Sign in with Apple), password reset or verification requests, and session and sign-in timestamps.

When you sign in with Google or Apple, the provider may transmit additional profile metadata as part of the OAuth flow (such as name, profile photo URL, or locale). We do not request, display, or use this metadata within SpinFreeze, but it may be stored temporarily by our authentication provider (Supabase) as part of standard processing.

Profile Information

We may collect your username, display name, bio, settings and preferences, accent color settings, and premium entitlement status.

SpinFreeze is designed so user profiles do not contain photos, real names, email addresses, or location data.

Content You Create

We may collect recipes, drafts, recipe titles, descriptions, ingredients, notes, steps, nutrition information, photos and uploaded images, collection names and cover images, ingredient submissions, freezer and spin tracking data, and appliance model information if you choose to provide it.

Recipe Share Cards

If you save a recipe share card, SpinFreeze generates an image and, with your permission, saves it to your device's photo library. That saved image file is stored locally on your device; we do not receive or store a copy of it. Separately, if you publish a recipe, SpinFreeze may generate its own promotional images or share cards from that recipe's public elements to feature it on our official channels, as described in our Terms of Service.

Community & Interaction

If you use community features, we may collect follows, saves, likes, and engagement actions; public profile visits and recipe interactions; reports, blocks, hides, and other safety controls; and moderation status, appeals, and enforcement metadata.

Search & Discovery

We may collect search queries, search filters, and indexed public recipe, ingredient, and tag data used to return results.

Notifications

If you enable notifications, we may collect or store notification permission state, reminder scheduling outcomes, notification tap events, recipe identifiers for deep linking, scheduled reminder times (stored on your device), and device timezone information. SpinFreeze currently uses device-local notifications for operational reminders.

Analytics & Diagnostics

We may collect screen views and navigation events, feature usage and funnel events, search and engagement events, subscription and paywall-related events, app version, platform, device type, language and timestamps, internal or pseudonymous identifiers, and crash reports, error messages, exception details, stack traces, and breadcrumbs.

Feedback & Bug Reports

If you submit feedback or a bug report from within the app, we may collect your message, feedback category and type, the screen or area of the app you were using, app version and build number, platform, associated Sentry crash or feedback identifiers, and up to three screenshots you choose to attach.

Subscriptions & Billing

If you view, purchase, or restore premium features, we may collect internal account identifiers, product and package identifiers, entitlement status, purchase and restore metadata, renewal or expiration status, and limited troubleshooting metadata.

We do not receive your full payment card number directly. Payment information is handled by the Apple App Store or Google Play.

AI Analysis Requests

When you use AI features (such as Recipe Importer), we log analysis requests for rate limiting and service quality purposes. These logs contain request metadata and are not stored long-term.

Technical & Infrastructure

We and our service providers may receive IP address, approximate location inferred from IP, device or platform headers, request timestamps, and service logs needed to secure and operate the platform.

Website Fonts

Our public website loads typefaces from Google Fonts and Fontshare. When your browser requests those files, those providers receive your IP address, browser and device information, and request metadata needed to deliver the font files. We use these providers only to render the website and do not use them to identify you.

If you enable health-platform sync, SpinFreeze may write one nutrition entry per logged spin to Google Health Connect on Android or HealthKit / Apple Health on iOS.

The entry may include calories, protein, carbs, fat, and timestamp. SpinFreeze writes this information only after the user logs a spin in SpinFreeze and only when the Sync to Health Connect / HealthKit toggle is on. SpinFreeze does not sync nutrition entries in the background.

We never read data from Health Connect, HealthKit, or Apple Health. We also never write workouts, weight, sleep, or non-nutrition data.

You can revoke access at any time in the Health Connect app on Android, or in Apple Health or iOS Settings under Privacy & Security > Health. Revoking access may not delete entries that were already written because Health Connect and HealthKit own that data after it is saved.

Compatible third-party macro-tracking apps may read these entries when you grant them permission in your Health Connect or HealthKit settings. Those apps' own privacy policies govern how they handle entries after import.

We use information to create and secure accounts; authenticate users and manage sessions; operate, store, and display recipes, collections, and media; power search, feeds, discovery, and public profiles; enable community interactions; send operational notifications and reminders; manage subscriptions, restores, and premium entitlements; moderate content and maintain community safety; run analytics, diagnose crashes, and improve the app; detect abuse, fraud, and security incidents; and comply with legal obligations and resolve disputes.

Certain information may be visible to other users when you use public features, including your username, display name, bio, published recipes (titles, descriptions, ingredients, notes, photos, and tags), public collections, and counts or indicators related to follows, likes, saves, or similar engagement.

Published content may appear in search results, feeds, recommendations, creator profile pages, and other discovery surfaces. Even after you edit or delete content, limited copies may persist temporarily in caches, backups, reports, moderation records, or abuse-prevention systems.

When you publish a recipe, it and the related public profile information described above may be displayed on a publicly accessible web page hosted at spinfreeze.com (for example, a shareable recipe page at a /recipe address). These pages do not require a SpinFreeze account or the SpinFreeze app to view and can be opened by anyone with the link.

Because these pages are public, they are designed to be found on the open web and may be crawled, indexed, cached, summarized, and displayed by third parties we do not control, including search engines, AI and large language model systems, and social or messaging platforms that show link previews. These pages may include structured recipe data (such as schema.org metadata) that third parties can read. We cannot control or delete copies that search engines, AI systems, or other third parties retain. Unpublishing or deleting a recipe stops us from serving its public page going forward but does not guarantee removal from third-party indexes or caches.

SpinFreeze uses artificial intelligence to support certain features.

Recipe Tagging

When you publish a recipe, we may send your recipe title and ingredient list to Google Gemini so SpinFreeze can generate flavor-oriented or related discovery metadata.

Ingredient Name Formatting

When you add or edit ingredients in a recipe, we may send the ingredient name and brand name to Google Gemini to generate a shorter, friendlier display label (for example, dropping a brand prefix when the generic name is unambiguous). Only the ingredient name and brand are sent; no account identifiers are included.

Nutrition-Label Extraction

When you use nutrition-label extraction, we may send a photo of the nutrition label, barcode, product name, and brand name (if provided). You remain responsible for reviewing and correcting extracted values before relying on them.

Ingredient Photo Recognition

When you use the ingredient photo recognition feature, SpinFreeze may send a photo you take or upload to Google Gemini to identify the food products and ingredients visible in the image. The image is first checked by OpenAI's moderation systems before being processed by Gemini. The identified ingredient names, brands, and categories returned by Gemini may be used to help populate a recipe.

Recipe Importer

Recipe Importer turns a URL or screenshot into a spin-ready recipe. When you import from a URL, SpinFreeze fetches the recipe page content. When you import from a screenshot, SpinFreeze sends the image you upload. In either case, the content is processed by Google Gemini via Cloudflare Workers to extract recipe ingredients, quantities, nutrition values, and container size.

Data sent for Recipe Importer: For URL imports, the fetched page content. For screenshot imports, the image you uploaded. We do not intentionally include direct account identifiers. Third-party processing is subject to the provider's own terms and policies.

Recipe Importer has a small number of free trial imports per account. Beyond that, continued use requires a Premium subscription with monthly quota limits.

Recipe Importer outputs are generated by SpinFreeze using third-party AI. They are not sourced from, endorsed by, or approved by Ninja, SharkNinja, the original recipe author, or any appliance manufacturer. "Ninja" and "Creami" are trademarks of SharkNinja Operating LLC.

Your choices:

• You may choose not to use Recipe Importer. Manual recipe entry is always available.
• You remain responsible for reviewing the imported recipe before saving.
• If you delete your account, your import history is deleted.
• For other questions about how your data is handled, contact us at support@spinfreeze.com.

What We Do Not Intentionally Send

For AI features, we do not intentionally send your password, billing details, or precise device location.

AI Output

AI-generated tags, extracted values, and Recipe Importer outputs may be stored with the related recipe or ingredient record. They are assistive and provided without warranty.

To keep SpinFreeze safe, we may process content using automated systems and, where appropriate, human review. This may include recipe titles, descriptions, ingredients, and notes; uploaded images; display names and bios; reports and report reasons; appeal justifications; and moderation logs and enforcement history.

We use this information to identify prohibited content, investigate reports, review appeals, maintain audit trails, detect repeat abuse, and meet legal, platform, or safety obligations. Some initial moderation decisions may be automated. Where applicable, users may request human review through the appeals process.

Uploaded images — including recipe photos and support screenshots — are automatically scanned for sexual content and other prohibited material as part of our safety workflow. If we obtain actual knowledge of illegal content, such as child sexual abuse material (CSAM), we will report it to appropriate authorities (including the NCMEC CyberTipline as required by law) and may preserve and disclose related account information to law enforcement.

Separately from safety screening, automated systems may also check whether a published recipe's text and photos, and newly uploaded photos, are topically relevant to SpinFreeze (for example, whether they actually relate to frozen treats or the Ninja Creami). This relevance check uses the same third-party AI systems described under "AI & Moderation Providers" in the section below.

We may share information with service providers and partners that operate SpinFreeze:

Core Service Providers

Supabase for authentication, database, and API services; Cloudflare for workers, storage, delivery, and infrastructure; Typesense for search indexing and query processing; and Google Fonts and Fontshare for public-website font delivery.

Authentication Providers

Google and Apple for federated sign-in. On Android, Google Play Integrity is also used to verify that requests originate from a genuine, licensed build of SpinFreeze; an encrypted integrity token generated by Google Play on your device is sent to Google's Play Integrity API for this purpose. On iOS, Apple App Attest is used in the same way; the iOS system contacts Apple's App Attest service to issue a device-bound cryptographic certificate, which SpinFreeze's server verifies locally to confirm the request originates from a genuine, unmodified build. Apple's processing of App Attest requests is subject to Apple's own privacy practices. On devices where neither native attestation method is available — such as older devices or environments without Google Play Services — a Cloudflare Turnstile challenge may be used as a fallback to verify that the request originates from a legitimate client; the challenge response is verified server-side against Cloudflare's Turnstile verification service, which may receive your IP address as part of that verification.

AI & Moderation Providers

Google Gemini for AI-assisted tagging, nutrition-label extraction, ingredient name formatting, ingredient photo recognition, and Recipe Importer parsing; OpenAI for automated text and image safety moderation and for automated content-relevance classification (assessing whether recipe text and photos are on-topic for frozen treats); Slack for human moderation review of flagged content and moderation appeals, and for routing in-app feedback and bug reports to our team — when content is flagged or an appeal is filed, recipe data (title, description, ingredients, notes, and image references) and moderation metadata may be sent to operators via Slack; when you submit feedback or a bug report, your message, feedback category and type, screen context, app version and build number, platform, associated Sentry crash or feedback identifiers, and any screenshots you attach may be sent to operators via Slack; Cloudflare-hosted infrastructure for moderation and safety workflows.

Analytics & Diagnostics

PostHog and Sentry.

Subscription & Billing

RevenueCat, Apple App Store, and Google Play.

Nutrition & Ingredient Data

Open Food Facts for product nutrition data lookups. When you scan a barcode or search for a product by name, the app may query the Open Food Facts API to retrieve ingredient and nutrition information for that product. Open Food Facts receives the barcode or search query along with standard request metadata (such as IP address) inherent in any network request.

Public Web Pages & Search Engines

Recipes you publish may be served as public web pages that search engines, AI crawlers, and social or messaging platforms can access, index, cache, and display in results or link previews. This sharing happens because the pages are public, not because we send your data to those parties. See the "When Information Is Public" section above for details.

Legal & Safety Disclosures

We may disclose information when reasonably necessary to comply with law or legal process; protect the rights, safety, or property of SpinFreeze, users, or the public; investigate fraud, abuse, or security incidents; or support a merger, acquisition, financing, or business transfer.

We retain information for as long as reasonably necessary to provide the service, secure the platform, comply with legal obligations, resolve disputes, and enforce our Terms. Account and operational records are retained as needed to operate and secure the service. Public and community data may be retained for moderation, safety, backups, and dispute resolution. Analytics and diagnostics data may be retained to measure quality and plan improvements. De-identified or aggregated analytics may be retained longer. Subscription and billing records may be retained for accounting, tax, fraud prevention, and disputes. Encrypted backups may retain limited data according to rotation practices.

You can request account deletion from within the SpinFreeze app.

Deletion Process

1. You request deletion in-app.
2. You are immediately signed out.
3. A 30-day grace period begins.
4. If you sign back in during that period, the deletion request is canceled.
5. After the grace period, permanent deletion is processed.

Information Deleted

After the grace period, we delete or de-identify user-facing account data, including profile data, recipes and drafts, collections, social and usage records, uploaded media, and authentication associations.

Information That May Be Retained

Limited records may be retained for security, fraud or abuse prevention, disputes, tax and accounting, legal compliance, deletion workflow records, backup integrity, and de-identified analytics.

Deleting an account does not automatically cancel app-store subscriptions.

Depending on your location, you may have rights regarding your personal information, including rights to access, correct, delete, object, restrict, request portability, and appeal certain decisions where required by law.

You may also be able to:

• manage public content visibility by editing or deleting content;
• block users or hide content;
• report content;
• manage notification permissions through device settings;
• exercise any analytics-related consent or opt-out controls we make available.

To submit a privacy request, contact support@spinfreeze.com.

If laws such as GDPR or UK GDPR apply, we may rely on the following legal bases:

• Contract — to provide accounts, authentication, premium features, and core functionality.
• Legitimate interests — to secure the service, moderate content, prevent abuse, run analytics, diagnose failures, and improve the product.
• Consent — where required for notifications, non-essential analytics, or similar processing.
• Legal obligation — where we must retain or disclose information to comply with law.

SpinFreeze and its service providers may process information in countries other than the one where you live. If required by applicable law, we will use appropriate safeguards for cross-border transfers, which may include contractual protections or other recognized transfer mechanisms.

SpinFreeze is not directed to children under 13, and we do not knowingly collect personal information from children below that age in violation of applicable law.

If you believe a child has provided personal information in violation of this policy, contact us at support@spinfreeze.com.

We use reasonable administrative, technical, and organizational measures to protect personal information. No system is perfectly secure, and we cannot guarantee absolute security.

We may update this Privacy Policy from time to time. If we make material changes, we may provide notice through the app, by email, by posting an updated policy, or through another appropriate method.

If you have questions, requests, or concerns about this Privacy Policy, contact:

support@spinfreeze.com

SpinFreeze LLC
5900 Balcones Drive Ste 100, Austin, TX 78731