Soiree

Privacy Policy

Last updated September 2026. Soiree is currently a small friends-and-family soft launch. This policy describes what the site actually does today — it has not been reviewed by a lawyer, and should be before any wider public launch.

Information we collect

  • Account information: your email address and a username, collected when you sign up. Authentication is handled by Supabase, which sends you a confirmation email when you register.
  • Content you create: recipes (including any photos you upload), star ratings, and comments. Recipes you mark private are visible only to you; recipes you mark public are visible to anyone who visits the site.
  • Profile information: a display name, bio, location, and photo, all optional and all shown on your public profile page. This page is visible to anyone, including logged-out visitors and search engines — don't put anything here you wouldn't want publicly indexed.
  • Usage data: we use Google Analytics (GA4) and Vercel Analytics to see how the site is used — pages visited, general location and device type, and similar aggregate usage patterns. We don't use this to identify you individually.
  • Error monitoring: if the site encounters a technical error while you're using it, we send a report to Sentry, a third-party error-tracking service, so we can find and fix the problem. That report includes technical details — the error message, a stack trace, the page URL, and your browser/device type — and your account ID if you're logged in. It never includes your email address, display name, or the contents of any recipe (including private ones), and any search terms or form data are stripped before the report is sent. Error reports are production-only; nothing is sent while the site is in development.
  • Private messages: direct messages between users are stored, including any recipe attached to a message. Sharing one of your private recipes into a message gives its recipient standing access to that recipe — separate from its public/private setting — for as long as the message exists. Unsending the message or deleting the recipe ends that access going forward, but can't undo anything the recipient already viewed or saved before then.
  • Recipe view tracking: when you view a public recipe, we record a hashed identifier — derived from your account if you're logged in, or from your IP address and browser if you're not — so we can avoid double-counting repeat views from the same visitor and rank recipes by popularity. The identifier is hashed with a secret salt before storage, so it isn't stored in plaintext; we do not store your IP address in our database. (Note: our hosting provider, Vercel, may separately log your IP address as a normal part of serving any website — that's outside this app's control, same as any hosted site.)

Cookies and tracking

Supabase sets a cookie to keep you logged in. Google Analytics sets cookies to distinguish visitors and sessions. Vercel Analytics does not use cookies. We don't currently run ads or affiliate links; if that changes, this policy — and likely a cookie-consent notice — will be updated first.

How we use your information

To operate the site: creating your account, showing your private and public recipes, running ratings and comments, and understanding overall usage so we can improve the site. We do not sell your information.

Where your data is stored

Application data (accounts, recipes, ratings, comments, photos) is stored with Supabase. The site itself is hosted on Vercel. Both are third-party infrastructure providers, not affiliated with Soiree beyond hosting it.

Your choices

You can edit or delete your own recipes and comments at any time from within the app, and unsend a message you've sent or hide a message from your own view of a conversation. There is currently no self-service way to delete your entire account — to request deletion of your account and associated data, contact us (below) directly. If your account is deleted, messages you sent remain visible to their recipients, attributed to a removed account rather than erased — direct messages aren't deleted along with the sender.

Children's privacy

Soiree is not directed at children under 13, and we don't knowingly collect information from them.

Changes to this policy

As the site grows past this soft launch, this policy will be revised — including a proper legal review before any public launch, and an update if ads, affiliate links, or a cookie-consent flow are added.

Contact

Questions or requests about your data: jaketiberghien@gmail.com or hello@join-soiree.com