Your table is private. Your information deserves the same care.

Information Foodies collects

Waitlist and contact information

When you join the waitlist or contact Foodies, we receive the email address and message you provide, the time of consent, and basic delivery or response records. The public waitlist also uses a one-way request fingerprint for abuse control; the raw IP address is not stored in the waitlist record.

Account and profile information

Foodies stores your sign-in email and may store a name, profile photograph, handle, bio, city, food interests, profile visibility choice, and authentication records. If a third-party sign-in option is offered and you choose it, that provider supplies the account details shown during sign-in.

Club and gathering information

Information you or other members add may include club names, mottos, crests, member roles, invitation tokens, rhythms, gathering dates and locations, themes, notes, RSVPs, votes, contributions, traditions, recaps, photographs, and host handoffs. Club members may be able to see this information according to their role and the feature involved.

Generated content and uploaded files

When you request an AI-assisted crest, gathering cover, clubhouse skin, or writing suggestion, Foodies processes the direction you provide, generation status, output, and related cost or support records. Uploaded profile and gathering images are also stored.

Payments and notifications

If you buy an offered credit pack, Foodies stores purchase references, amount, status, and credit balance. Payment-card details are handled by the payment provider rather than stored by Foodies. If you enable native notifications, Foodies stores a device token and delivery environment so notifications can be sent or disabled.

Usage and device information

Public pages and the app use Google Analytics to understand visits and a small set of product actions. This may include page, referrer, browser, device, approximate region, campaign, and interaction data. Advertising storage and ad personalization signals are disabled. Operational logs may include request, error, security, and performance information.

Why Foodies uses information

• Provide sign-in, membership, invitation, gathering, contribution, recap, profile, generation, payment, and notification features.
• Send requested sign-in links, gathering updates, operational messages, and consented waitlist or launch email.
• Protect accounts and the public waitlist, prevent abuse, investigate errors, and maintain service reliability.
• Measure public-page and product flows using events designed not to contain personal or private-club fields.
• Respond to support, privacy, legal, correction, and security requests.

Service providers and disclosures

Foodies uses providers that process information only for the relevant service. Current categories include:

• Hosting and file storage: Vercel and Vercel Blob.
• Database infrastructure: Neon.
• Email and authentication delivery: Resend and any sign-in provider you choose when offered.
• Payments: Stripe.
• Analytics: Google Analytics.
• Requested AI features: OpenAI and Anthropic, depending on the feature.

These providers may process information in Canada, the United States, or other jurisdictions where they operate, where local authorities may lawfully access it. Foodies may also disclose information when required by law, to protect rights or safety, or as part of a business transfer subject to appropriate notice and safeguards.

Privacy inside a club

Foodies is private by default, but it is collaborative. Members of the same club can see information needed to participate. Anyone who receives a live invitation capability link may see the limited club preview attached to that link. Founders can rotate invitation links. A member may separately choose a link-accessible profile where that option is available.

Do not add another person’s sensitive information, private address, dietary or health details, or photograph unless you have permission and a legitimate reason to share it with the club.

Your choices

• Email: use the unsubscribe mechanism in a marketing email. Operational messages needed to provide the service may still be sent.
• Profile: update available profile fields and visibility settings in Foodies.
• Notifications: disable notifications in your device settings; Foodies also supports disabling registered device tokens.
• Analytics: browser controls and content-blocking tools can limit cookies or analytics requests.
• Access, correction, deletion, or consent withdrawal: use the controls in Foodies or contact Foodies using the route below. Identity verification may be required, and some records may be retained where legally required or necessary for security, transaction integrity, or resolving disputes.

Deleting a Foodies account

A signed-in member can open Account & privacy from the account menu and choose Permanently delete my account. Foodies requires the member’s verified email, the confirmation word shown in the app, and the current password when that account has one.

Founders must first transfer each club to another member or deliberately delete that club, so no private clubhouse is left without an owner. Completed deletion removes the profile, linked sign-in identities, password credential, active sessions, device tokens, credit records, and memberships. If Sign in with Apple is linked, Foodies also requests revocation of that Apple authorization before local deletion completes.

Past membership numbers are retired and never reassigned. Shared club history may keep neutral “Former member” references so remaining members’ recaps, results, and honours stay coherent. A privacy-safe deletion audit keeps no name, email, provider token, or club content. Protected backups and essential security or legal records may expire on a separate limited schedule.

Retention and security

Foodies keeps information while it is needed to provide the service, maintain transaction and security records, meet legal obligations, or resolve disputes. Retention depends on the record and may continue in protected backups for a limited period after deletion from active systems.

Foodies uses access controls, server-side data access, encrypted network connections, protected secrets, one-way abuse fingerprints, and private membership checks. No internet service can guarantee absolute security; report a suspected issue promptly without accessing other people’s information.

Children

Foodies is not directed to children under 13 and does not knowingly ask them to create accounts. If you believe a child has provided personal information without appropriate consent, contact Foodies.

Changes to this notice

Foodies will update the effective date and this page when practices materially change. If a change requires new consent or direct notice, Foodies will provide it through an appropriate channel.