Dinner preferences should stay low-stakes and private.

What an invite contains

A short invite stores the creator’s first name, dinner options, creator votes, deck context, and creation time. Anyone with the invite link can open that deck, so treat the link like a private message.

When the guest finishes swiping, their first name and votes are written back to the invite record so the creator can see the outcome of the round they started. That result is stored alongside the invite, is covered by the same 30-day expiry, and is only reachable by someone holding the invite ID. Sharing the final verdict uses the device share sheet or clipboard.

Guest results are recorded once per invite. A round that has already been submitted cannot be overwritten.

How long invites last

A short invite stores the creator’s first name, their dinner options, their votes, the deck context, and—once the guest finishes—the guest’s first name and votes. All of it is kept for up to 30 days from creation, and the link stops working at that point.

A scheduled job runs once a day and permanently deletes every invite past its 30-day expiry, including the guest’s recorded round. Expired invites also stop being readable immediately at expiry, so a record is unreachable well before the job removes it.

If short-link storage is unavailable, SamePlate creates a longer portable link instead. That link carries the creator’s deck and votes inside the URL and is not stored by SamePlate.

Location

Nearby restaurant discovery is optional. The browser rounds latitude and longitude to three decimal places—roughly a neighborhood—before sending them to SamePlate’s server. The server uses that approximate location to request nearby OpenStreetMap listings.

Location is not added to invite links or invite records. The hosting provider may retain ordinary request logs containing the approximate area under its own operational policies.

Services involved

• Vercel hosts the beta application and server functions.
• Supabase stores short invite records when configured.
• OpenStreetMap and Overpass provide nearby restaurant data.
• TheMealDB provides sourced recipe data and images.

SamePlate does not currently use advertising trackers, analytics cookies, or user accounts.

SamePlate does keep operational error logs so failures can be diagnosed. Those logs record what went wrong, not who it happened to: invite IDs, approximate coordinates, and API credentials are stripped before anything is written, and invite contents, names, and votes are never logged.

Attribution

Nearby restaurant data comes from OpenStreetMap contributors, queried through Overpass. OpenStreetMap data is licensed under the Open Database License.

Sourced recipes and their images come from TheMealDB. Each sourced card credits TheMealDB and links to the original publisher where one is provided. Recipes written by SamePlate are shown as original content.

Safe beta use

Do not put sensitive personal information into names or invite links. SamePlate is for lightweight dinner preferences, not confidential or emergency information.