Version 1.0 — Effective May 17, 2026
Compliance: CAN-SPAM, CCPA, applicable state privacy laws
myrecipecard.kitchen ("we," "us") is committed to protecting the privacy of our users. This Privacy Policy explains how we collect, use, store, and share personal information when you use our Cook's Card generator and food cost analytics platform.
| Data Type | Purpose | Required? |
|---|---|---|
| Name | Card personalization, lead identification | Yes |
| Card delivery, rate limiting, email sequence | Yes | |
| Cuisine type | Service customization, segmentation | Yes |
| Recipe data (name, portions, ingredients, instructions, notes) | Cook's Card generation | Recipe name required; others optional |
| Data Type | Purpose | Required? |
|---|---|---|
| All free-tier data | Carried forward from signup | Yes |
| Business name & address | Service configuration, invoicing | Yes |
| Payment information | Subscription billing (processed by Stripe — we never see your full card number) | Yes |
| POS data exports | Food cost analysis, contribution margin ranking, menu engineering | Yes |
| Phone number | Account support, walkthrough scheduling | Optional |
| Data Type | Purpose |
|---|---|
| IP address | Rate limiting, security |
| Browser/device type | Site compatibility |
| Page views | Analytics (PostHog, self-hosted) |
| Email open/click rates | Email sequence optimization |
| Use Case | Data Used | Legal Basis |
|---|---|---|
| Generate Cook's Cards | Recipe data, email | Service delivery |
| Deliver food cost reports | POS data, business info | Contract performance |
| Send email sequence | Email, name, cuisine | Consent (opt-in at signup) |
| Process payments | Payment info via Stripe | Contract performance |
| Rate limiting | Email, IP address | Legitimate interest (abuse prevention) |
| Improve the Service | Aggregated, anonymized usage data | Legitimate interest |
| Respond to support requests | Account/contact data | Contract performance |
We do NOT sell, rent, or trade your personal information. Period.
We share data only with:
| Third Party | Purpose | Data Shared |
|---|---|---|
| Stripe | Payment processing | Name, email, payment method (PCI-DSS compliant) |
| Resend | Email delivery | Email address, name |
| PostHog (self-hosted) | Analytics | Anonymized usage events |
We will disclose information if required by law, court order, or to protect our rights.
Your POS data (sales mix, item counts, revenue figures) is the most sensitive data we handle:
| Data Type | Retention Period |
|---|---|
| Free-tier lead data (name, email) | Until unsubscribe + 30 days |
| Cook's Cards generated | 1 year; your downloaded copies are yours forever |
| POS data (paid subscribers) | Duration of subscription + 90 days |
| Financial reports generated | Duration of subscription + 90 days |
| Payment records | As required by tax law (typically 7 years) |
| Email engagement data | 1 year |
To exercise any right, email joe@myrecipecard.kitchen with "Privacy Request" in the subject line. We respond within 30 days.
California residents (CCPA): You have additional rights under the California Consumer Privacy Act, including the right to know what data is collected and the right to opt out of data sales. We do not sell personal information.
When you subscribe to our newsletter or submit the Cook's Card form, you will receive email communications. Every email includes:
We honor unsubscribe requests within 2 business days.
No system is 100% secure. If we discover a breach affecting your data, we will notify you via email within 72 hours.
myrecipecard.kitchen is not directed at individuals under 18. We do not knowingly collect data from minors.
We may update this Privacy Policy from time to time. Material changes will be communicated via email at least 30 days before taking effect.
Privacy questions or data requests: