Privacy Policy

Last updated: October 31, 2026

We built Potluck Coordinator. This policy explains what data Potluck Coordinator collects, why, and how it is handled.

1. What Data We Collect and Why

Event Data (stored in Apple CloudKit): - Event names, dates, and join codes (created by hosts and stored in CloudKit's public database so guests can join) - The host name you enter, and the display name each guest enters when they claim a dish or RSVP - Dish lists (dish names, dietary tags, serving counts, notes, and who claimed each dish) - Photo attachments (optional dish photos added by hosts or guests, stored in CloudKit) - RSVP responses (going, maybe, or can't make it, with an optional party size, stored per event in CloudKit)

Local Device Data: - App preferences and settings (stored locally via UserDefaults) - Subscription status (whether you have Potluck Pro, verified via Apple StoreKit 2 and RevenueCat) - Your profile (name, dietary preferences, and optional US state), used to pre-fill forms - Sign in with Apple (optional, used for the Community Feed): your Apple user identifier, and the name and email Apple shares if you allow it, stored on your device

No Account Required: Potluck Coordinator does not require you to create an account or provide an email address. Hosts and guests are identified by locally generated device identifiers and the names they choose to enter. Sharing events with guests requires being signed in to iCloud on your device.

2. What We Do NOT Collect

- We do not collect email addresses or phone numbers on our servers - On iPhone, we do not use analytics SDKs (no Firebase, Amplitude, Mixpanel, or third-party tracking) or crash reporting services. The Android app uses Google Firebase Analytics and Crashlytics, described in section 5b - We do not use advertising SDKs or the advertising ID on any platform - We do not access your contacts, location, microphone, or camera beyond what you explicitly initiate (photo picker for item photos) - We do not sell or share data with advertisers or data brokers - We do not operate backend servers for core event sync on iPhone; that goes through Apple CloudKit. The Android app reaches the same CloudKit data through our relay (see section 5b), and we operate a server for the optional Community Feed photo feature (see section 4a)

3. CloudKit Shared Event Data

Event data syncs via Apple CloudKit's public database. This means: - Event data is accessible to anyone with the join code - Data is subject to Apple's own privacy practices and retention policies (apple.com/privacy) - We do not have a separate copy of your event data on our own servers

Do not include sensitive personal information (SSNs, financial data, passwords) in event names, item names, or notes.

4. Photos

Photo attachments are uploaded to Apple CloudKit only when a user explicitly selects and attaches a photo to an item. Photos are stored in CloudKit and visible to all participants in the event. We do not access your photo library beyond the image you explicitly select via the iOS photo picker.

4a. Community Feed Photos

Potluck Coordinator includes a Community Feed that displays dish photos shared by users across the app. When you add a photo to a potluck event, the "Share to Community feed" toggle is on by default. You can turn it off per-photo at upload time, or disable Community Feed sharing entirely in Settings.

When a photo is shared to the Community Feed:

- The photo, your first name, and any caption you provide are stored on our servers (hosted infrastructure in the United States) and may be displayed publicly within the app to all Potluck Coordinator users. - Community Feed photos are moderated by our team before they appear in the feed. We may remove any photo that violates our content standards. - By submitting a photo to the Community Feed, you grant Potluck Coordinator a non-exclusive license to display that photo within the Potluck Coordinator app. - To opt out of future submissions: open Settings and turn off "Share my potluck photos to Community." - To request removal of a previously submitted photo: email support@potluckcoordinator.com with a description of the photo and approximately when it was submitted. - Do not submit photos containing people's faces, personally identifying information, or content you do not have the right to share.

5. Third-Party Services

- Apple CloudKit: real-time event sync. Apple's privacy policy applies: apple.com/privacy - Apple StoreKit 2 and RevenueCat: in-app purchase processing for the Potluck Pro subscription. Apple handles all payment data. RevenueCat receives anonymized purchase receipts to verify and manage subscription entitlements. RevenueCat's privacy policy: revenuecat.com/privacy - Apple Push Notification service (via CloudKit): when an event you host or joined changes, Apple sends a silent signal that wakes the app; the notification you see (for example, a new claim or RSVP) is written on your device. - Apple UserNotifications: local reminders for your events and the dishes you claimed.

The iPhone app does not integrate any third-party analytics, advertising, or tracking libraries. The Android app uses Firebase Analytics and Crashlytics only (section 5b) and no advertising libraries.

5b. Android App

This section applies to the Android version of Potluck Coordinator. Everything above applies on Android too, except where this section says otherwise. Android does not use Apple services, so CloudKit access, StoreKit, Sign in with Apple and Apple Push Notification service work as described here instead.

Event data and our relay: The Android app sends event requests to a small relay server we operate. The relay reads and writes the same CloudKit public database records the iPhone app uses, so iPhone and Android hosts and guests can share one potluck by join code. What passes through the relay: event names, dates, locations, themes, host notes, join codes, the host name and guest display names you enter, dish lists with dietary tags, who claimed each dish, and RSVP responses with party size. The relay does not keep its own copy of event data. The data lives in CloudKit and is visible to anyone with the join code, as described in section 3. The Android app does not upload photos.

Identifiers kept on your phone: The app creates a random device ID, a host token for each event you host (so only you can edit or delete it), and a record ID for each event you join or host. These are sent to the relay so it can find and update the right event. Your profile (name and dietary preferences, used to pre-fill forms), your lists of hosted and joined potlucks, and your settings are stored in the app's private storage on your phone.

Google sign-in (optional): If you choose Sign in with Google, Google shares your Google account ID, name and email address with the app. These are stored on your phone only. Your Google account ID and email are kept out of your Android backup (see below). The Google account ID is also sent to RevenueCat as your app user ID so your Potluck Pro subscription follows you to a new phone. We do not send your name or email to our servers. Guests never need an account.

Subscriptions: Potluck Pro on Android is billed by Google Play. RevenueCat receives purchase information from Google Play, plus your app user ID (a random ID, or your Google account ID if you signed in), to verify and restore your subscription. We never see your payment details. Manage or cancel in the Play Store: Payments and subscriptions > Subscriptions. Google's privacy policy: policies.google.com/privacy

Notifications: If you allow notifications, the app schedules reminders on your phone (the evening before an event, for hosts and for dishes you claimed). Hosts can also get alerts about new claims and RSVPs: about every 15 minutes the app checks the relay for changes to events you host and writes the notification on your phone. The same 15-minute check also covers the potlucks you joined, not only the ones you host, to keep your dish reminders current. We do not use Firebase Cloud Messaging.

Feature votes and ideas: If you vote in "Vote on What's Next" or send a feature idea, the app sends the feature ID (or your idea text, up to 300 characters) and your random device ID to our server at didyu.app.

Location, contacts, camera: The Android app does not request location, contacts, camera or photo access. Tapping an event location opens your maps app with the address text.

Android backup: Android Auto Backup is limited to the app's preferences file (host tokens, hosted and joined lists, profile, device ID and the guest names you entered), so a host keeps control of their events on a new phone. Your Google account ID and email are not in the backup: the app keeps them in a separate file (account.xml) that is excluded from it. The backup is kept in your Google account under Google's terms, only if you have Android backup turned on. Event data is not in the backup.

In-app review: The app may ask Google Play to show its in-app review prompt. Google Play handles any rating; the app does not learn what you answer.

Usage analytics and crash reports (Google Firebase): The Android app uses Firebase Analytics to count how the app is used (app opens, screens, and actions such as creating an event, joining one, claiming a dish or viewing the Pro offer, with counts like the number of dishes) and Firebase Crashlytics to send a report when the app crashes or a server request fails. These reports include a random app instance ID, device model, Android version, app version, approximate region derived from the IP address, and crash details. They never include event names, dish names, notes, join codes, the names you enter, or your email. We use them only to fix bugs and improve the app; we do not use them for advertising and do not use the advertising ID. Google processes this data as our service provider: firebase.google.com/support/privacy

Deleting your data on Android: - Delete one event: open it, tap Delete, confirm. This removes it from CloudKit through the relay. - Delete everything tied to you: Settings > Account > Delete Account (shown when signed in with Google). This deletes the potlucks you host, releases the dishes you claimed, removes your RSVPs, signs you out and clears the app's data on your phone. - Not signed in, or already uninstalled: follow the steps at https://potluckcoordinator.com/delete-account - Uninstalling removes local data. Purchase records stay with Google Play and RevenueCat; email support@potluckcoordinator.com to request their erasure.

Browser Invite Page

Names, dishes, dietary tags, and RSVPs entered on the browser invite page are stored in the host’s potluck the same way as from the apps. We keep your name in your browser storage only to remember it. The page also keeps a random RSVP identifier in browser storage so you can update your response. The browser invite page has no ads or tracking cookies. To limit abuse, the page passes your IP address to our relay with each request so it can apply rate limits; the relay does not store it.

6. Children's Data

Potluck Coordinator is not directed at children under 13. We do not knowingly collect personal information from anyone under 13. Contact support@potluckcoordinator.com if you believe a minor has used the app.

7. Data Retention and Deletion

- Local data: deleted when you uninstall the app - CloudKit event data: persists until the host archives or deletes the event within the app, or until Apple's CloudKit retention policies apply - Subscription records: managed by Apple

To remove event data: open the event, tap Archive or Delete, then confirm. Events you did not create can only be deleted by the host.

8. Security

Local data is protected by iOS sandboxing. CloudKit data is protected by Apple's infrastructure and access controls. Join codes act as access tokens; keep your event join codes private if your event is intended for a limited guest list.

9. Changes to This Policy

Material changes will be communicated via in-app notice. Continued use constitutes acceptance.

10. Contact

Potluck Coordinator support@potluckcoordinator.com United States

────────────────────────────────────────

GDPR: Your Rights (EU/EEA Users)

Last updated: October 31, 2026

1. Data Controller

Potluck Coordinator is the data controller for personal data processed through Potluck Coordinator. Contact: support@potluckcoordinator.com

2. Legal Basis for Processing

- Contractual necessity (Art. 6(1)(b)): Event sync via CloudKit is required to provide the core service of real-time potluck coordination. - Consent (Art. 6(1)(a)): Photo uploads and optional features require explicit user action.

3. Your Rights Under GDPR

Right of Access (Art. 15): Event and item data you created is visible within the app. Contact support@potluckcoordinator.com for any records. Right to Rectification (Art. 16): Edit or update item information directly in the app. Right to Erasure (Art. 17): Delete events and items within the app. Uninstall to remove local data. Right to Restriction (Art. 18): Revoke CloudKit access by uninstalling the app. Right to Data Portability (Art. 20): Contact support@potluckcoordinator.com for assistance. Right to Object (Art. 21): Uninstall the app to stop all processing.

4. How to Exercise Your Rights

Email: support@potluckcoordinator.com. We respond within 30 days.

5. Supervisory Authority

You may lodge a complaint with your local EU/EEA data protection authority.

6. International Data Transfers

Event data is stored in Apple CloudKit under Apple's GDPR commitments and Standard Contractual Clauses. Community Feed photo data is stored on our servers in the United States. By sharing a photo to the Community Feed, you consent to this transfer.

7. Contact

support@potluckcoordinator.com | Potluck Coordinator | United States

────────────────────────────────────────

CCPA/CPRA: Your Rights (California Residents)

Last updated: October 31, 2026

1. Categories of Personal Information We Collect

- Device identifiers (for StoreKit transaction verification, handled by Apple) - Names you enter (host and guest display names) and event content (dish names, dietary tags, RSVPs) stored in Apple CloudKit - Community Feed photos you choose to share, with your first name and optional US state - App preferences stored locally on your device

We do NOT collect: email addresses or phone numbers on our servers, precise location, financial data, biometric data, or sensitive personal information as defined by CPRA.

2. Do We Sell or Share Personal Information?

No. We do not sell or share personal information with third parties for advertising.

3. Your CCPA/CPRA Rights

Right to Know: All event data is visible in the app. We do not maintain server-side user profiles. Right to Delete: Delete events in the app or uninstall to remove local data. Email support@potluckcoordinator.com for any records we hold. Right to Correct: Edit item and event information directly in the app. Right to Opt-Out of Sale/Sharing: We do not sell or share, so no action is required. Right to Non-Discrimination: We will not discriminate against you for exercising CCPA/CPRA rights.

4. Contact

support@potluckcoordinator.com | Potluck Coordinator | United States