Privacy, in plain language.

We keep account identity and contact information, profile preferences, saved recipes, collections, synchronized drafts, submissions, uploaded source cards, moderation history, membership status, and essential security and abuse-prevention records. Community-cookbook pilot applications also include the applicant's contact details, organization, collection description, rights status, and preservation goals. If you use Google sign-in, Google provides the basic identity information needed to create your account.

Information is used to authenticate members, synchronize recipe boxes, review and preserve submissions, respond to requests, administer memberships, secure the service, diagnose failures, and comply with legal obligations. We do not sell personal information or use it for behavioral advertising.

If you participate in story discussions or cooking reviews, your chosen public display name, optional sanitized profile photograph, comment or review, rating, and posting date may be public. Your Google profile and account email are not published automatically. Reports, moderation history, restrictions, and original edit history remain private to administrators.

Vercel hosts the public application, Supabase provides authentication, database, and file storage, Google supports optional sign-in, and Stripe or PayPal processes subscriptions. These providers receive information only as needed to perform their services. Payment details are submitted directly to the selected payment provider and are not stored by Our Midwest Recipe Box; we retain subscription status and related identifiers needed to provide access and support.

Essential cookies keep members signed in and protect account sessions. Vercel provides privacy-conscious traffic and performance measurements that help us understand site reliability.

Google Analytics is optional and remains unloaded unless you select “Accept analytics.” After consent, it may use cookies and collect usage information such as pages visited, approximate location, device and browser details, scrolling, downloads, outbound-link clicks, and site-search activity. Event data is retained for 14 months. Advertising personalization, Google Signals, and enhanced user-provided data are disabled. We do not send Google Analytics account email addresses, recipe submissions, or other user-provided personal content.

You may decline without losing access to the site or change your choice later with the “Analytics choices” control in the footer. Reasonable technical and organizational safeguards are used, but no online service can guarantee absolute security.

Private account information is retained while an account is active and as reasonably needed for security, backup, dispute, or legal purposes. Account deletion removes private recipe-box data through the account security page. Published contributions may be detached from the deleted account and retained as part of the editorial record; removal or attribution changes are reviewed separately.

Community-cookbook applications and administrator working notes are private and used to evaluate preservation fit, rights readiness, scope, and next steps. Contact details and unpublished collection descriptions are not made public. Applying does not authorize publication; accepted organizations complete a separate agreement before any cookbook material becomes public.

Members may download an account export or permanently delete a non-administrator account from Account Security. You may also request access, correction, removal, or help using the contact address below. The “Analytics choices” control in the footer lets you accept or decline optional Google Analytics at any time. Browser settings can limit cookies, although essential account features may stop working.

The service is not directed to children under 13, and we do not knowingly collect their personal information. Material policy changes will be posted here with a new effective date; when appropriate, signed-in members will receive additional notice.