arrow_back

Privacy Policy

info

For Entertainment Purposes Only

Ripely is a personal food-tracking tool provided for convenience and entertainment. It is not a food-safety authority and is not a substitute for professional guidance.

Effective date: April 2, 2026  ·  Last updated: April 3, 2026

1. Who We Are

Ripely ("we," "us," or "our") is a household food-inventory application operated for personal, non-commercial use. We are based in California, United States. If you have questions about this policy you may contact us at privacy@ripely.app.

2. Information We Collect

We collect only what is necessary to provide the service:

  • Email address: Used solely to send your magic sign-in link and to identify your account. We do not send marketing emails.
  • Food inventory data: Item names, categories, quantities, purchase dates, and expiration dates that you voluntarily enter.
  • Household data: Your household name and an invite code you generate. Member relationships are stored to share inventory within a household.
  • Push notification subscription data: If you opt in to web push notifications, we store your push subscription endpoint URL and encryption keys in order to deliver expiry alerts to your browser.
  • Email notification preferences: Your preference for receiving daily digest emails about expiring items, including delivery frequency and opt-out status.
  • Feedback & feature requests: If you submit a bug report or feature request through the app, we store the content of your submission along with your user ID and timestamp. This data is used solely to improve Ripely.
  • Usage data: Standard server logs (IP address, browser type, pages visited) retained for up to 30 days for security and debugging.

We do not collect payment information, government IDs, health data, or any sensitive personal information.

3. How We Use Your Information

We use your information exclusively to:

  • Authenticate you and maintain your session
  • Display, store, and sync your household's food inventory
  • Send expiration alerts you configure within the app
  • Send daily digest emails about expiring items (if enabled in Settings)
  • Deliver web push notifications for expiry alerts (if you grant browser permission)
  • Provide food intelligence via API to third-party developers and AI assistants (planned feature — not yet active)
  • Diagnose technical errors and maintain security

Email Notifications

If you have items expiring soon, we may send daily digest emails via Resend, a third-party email provider. These emails contain item names, expiry dates, storage tips, and recipe suggestions. You can disable email notifications at any time from Settings. Resend's own privacy policy governs their handling of email addresses.

Push Notifications

Ripely supports web push notifications via the VAPID protocol for expiry alerts. Browser permission is required — this is strictly opt-in. Your push subscription data (endpoint URL and encryption keys) is stored in Supabase. No food data is stored by push notification intermediaries; only encrypted payloads are transmitted.

We do notsell, rent, trade, or share your personal information with third parties for advertising purposes. We may share aggregate, de-identified trend data with commercial partners (see Section 4 & 6 for details). This aggregated data cannot identify you or your household.

4. MCP API & Developer Access

Ripely is building an MCP (Model Context Protocol) API that will provide food intelligence tools to third-party developers and AI assistants. This feature is not yet active. When launched, the following data practices will apply:

  • Free-tier tools: Tools such as lookup_food, get_freshness, get_storage_tips, and parse_grocery_list process food names and dates only. No personal data is sent or stored through these endpoints.
  • Pro-tier tools: Tools such as check_expiring_items may access household inventory data. This requires an API key and explicit user opt-in from the household admin.
  • Developer responsibility: Developers accessing the API are responsible for their own privacy compliance when handling data returned by the API.
  • API logging: API usage is logged (endpoint called, timestamp, API key prefix) for rate limiting and abuse prevention. These logs are retained for 90 days.
  • Anonymized data: Aggregate, anonymized food trend data (e.g., popular items, seasonal demand patterns, common waste categories) may be used to improve the food intelligence database and may be shared with or sold to commercial partners such as restaurants, grocery retailers, and food brands. This data is always de-identified and aggregated — it can never be traced back to an individual user or household.

5. Third-Party Services

Ripely relies on the following third-party services to operate:

  • Supabase: Database, authentication, and realtime sync — SOC 2 Type II certified, US-hosted.
  • Vercel: Hosting and serverless functions — SOC 2 Type II certified.
  • Resend: Transactional email delivery for daily digest emails and authentication emails.

We do not use advertising networks, analytics trackers, or social media pixels.

6. Data Sharing & Commercial Use

Ripely shares data in two ways:

  • PRO API household access: If a household is connected via the PRO API, inventory data may be accessible to the developer who holds the API key. This requires explicit opt-in from the household admin. Users can revoke API access at any time from Settings.
  • Aggregate trend data: We may share or sell aggregate, de-identified data — such as popular food categories, seasonal demand patterns, common waste items, and regional freshness trends — to commercial partners including restaurants, grocery retailers, and food brands. This data helps partners reduce their own food waste and optimize inventory. It is always stripped of personal identifiers and aggregated across many households so that no individual user or household can be identified.
  • What we never share: We never sell, rent, or share your personal information (email, household name, specific inventory lists) with any third party. Commercial data sharing is limited exclusively to anonymized, aggregate insights.

Developers accessing the PRO API must agree to Ripely's API Terms of Service before receiving any data.

7. Data Storage & Security

Your data is stored on Supabase (PostgreSQL, hosted in the United States). Supabase is SOC 2 Type II certified. All data is encrypted in transit (TLS 1.2+) and at rest. Access is restricted by Row-Level Security policies so you can only see your own household's data.

Despite these measures, no system is perfectly secure. You use Ripely at your own risk.

8. California Privacy Rights (CCPA)

If you are a California resident, you have the following rights under the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA):

  • Right to Know – You may request a summary of the personal information we hold about you.
  • Right to Delete – You may request deletion of your account and all associated data. To do so, email us or delete your account from the Settings page.
  • Right to Correct – You may update inaccurate information directly within the app.
  • Right to Opt-Out of Sale – We do not sell personal information. We may share aggregate, de-identified data that cannot identify you (see Section 6). Under CCPA, de-identified data is not considered "personal information."
  • Right to Non-Discrimination – We will not discriminate against you for exercising any of these rights.

To exercise your rights, email privacy@ripely.app. We will respond within 45 days.

9. GDPR Rights (EEA/UK Residents)

If you are located in the European Economic Area or the United Kingdom, you have the following rights under the General Data Protection Regulation (GDPR):

  • Right of Access – You may request a copy of the personal data we hold about you.
  • Right to Rectification – You may request correction of inaccurate or incomplete data.
  • Right to Erasure – You may request deletion of your personal data.
  • Right to Data Portability – You may request your data in a structured, machine-readable format.
  • Right to Restrict Processing – You may request that we limit how we process your data.
  • Right to Object – You may object to processing based on legitimate interest.

Legal basis for processing: contract performance (providing the service) and legitimate interest (security and debugging). We do not engage in automated decision-making or profiling.

International data transfers: Your data is stored in the United States via Supabase, and emails are sent via Resend. Both services maintain appropriate safeguards for international transfers.

To exercise your rights, email privacy@ripely.app. We will respond within 30 days. You also have the right to lodge a complaint with your local supervisory authority.

10. Cookies & Local Storage

We use strictly necessary cookies and browser local storage to maintain your login session. We do not use tracking cookies, advertising cookies, or third-party analytics cookies.

11. Data Retention

Your account data is retained for as long as your account is active. If you delete your account, all personal data is permanently removed within 30 days. Server logs are purged within 30 days. API usage logs are retained for 90 days. Push notification subscription data is deleted immediately when you unsubscribe or revoke browser permission.

12. Entertainment Use Only — No Liability

Ripely is provided for personal entertainment and convenience purposes only. It is not a certified food-safety system and must not be relied upon as one.

Expiration dates, freshness indicators, and alerts displayed by Ripely are based solely on information you manually enter. Ripely does not inspect, test, smell, or evaluate any physical food item.

To the fullest extent permitted by applicable law, Ripely, its operators, and contributors disclaim all liability for any illness, injury, property damage, financial loss, or any other harm arising from:

  • Consuming food based on Ripely expiration guidance
  • Incorrect dates or information entered by you or household members
  • Food spoilage, contamination, or unsafe storage conditions
  • App downtime, data loss, or technical errors
  • Any reliance on information displayed in the app

Always use your own judgment regarding food safety. When in doubt, throw it out.

13. Children's Privacy

Ripely is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, please contact us so we can delete it.

14. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the effective date above. Continued use of Ripely after changes constitutes acceptance of the revised policy.