Privacy

What RsrvX records

You do not need to sign in to use the menu or to book a table.

Booking a table: when a restaurant takes bookings or a waitlist on rsrvx.com, it keeps the name, the email address or mobile number and the note you give (a note can mention an allergy), your party size, the time or your place in line, the table it holds for you, and whether you came, cancelled or missed the booking. If this phone is signed in as a member there, other than through a manager's 12 hour link, the booking is linked to your membership. The restaurant's owners, managers, floor leads and hosts see its bookings on the host stand, past days included. Your booking link is the only way to see, change or cancel the booking online, and anyone who has the link can do so; RsrvX keeps only a scrambled form of it. Your internet address is saved only in a scrambled form made with a secret key, to limit how many bookings come from one place. Nothing is emailed or texted about a booking.

At your table, the menu records:

• A random id saved on this phone the first time you open an RsrvX menu, so the menu knows it is the same phone. The same id is used at every restaurant on RsrvX, and it does not expire.
• The table and visit your phone joined, and when.
• What you open on the menu (sections and dishes, and for how long) and the picks you add or remove.
• Calls to your server with their reasons, and the requests you send to staff.
• The ratings you give dishes and the reasons you choose, and a one-line review if you choose to share one, with your first name and last initial if you add them.
• If you use them: the table's allergy card (which allergens, and whether it is for a child), your notes on how staff can best serve you, and the pace you set for the meal.
• Your internet address, to limit abuse. RsrvX saves only a scrambled form: for 2 days when you use the server's assistant, and for about a day when you join a dining community from its page or change your member name (it can stay longer at a quiet restaurant, until the next one clears it).

How it is used

To run your table: keep your party's phones in step, send your calls and requests to the staff on duty, and show them your allergy card and notes.

To show the restaurant how its menu does: which dishes are opened, picked, ordered and rated, and at what time of day.

To show ratings on the menu: dish scores from guest ratings, and review lines the restaurant approves.

To hold your table when you book, and to run your RsrvX account and profile if you make one.

RsrvX shows no ads and uses no ad trackers.

Dining communities and RsrvX accounts

If you join a restaurant's dining community, the restaurant gets the first name and the email address or mobile number you give, your member number, check-ins, points, rewards and event sign-ups, and which of its kitchen notes and course lessons you mark read and when. It also keeps the perks you use, if it offers perks, your notice settings for its community inbox and, if you use them, the posts you write with their photos and mentions, your member profile choices and your favorite dishes.

Its owners and managers see a profile for each member: visits, what staff recorded as spent, the dishes opened, picked and rated on phones linked to the membership, ratings and comments, the points each member earned and what for, your birthday if you or its staff added it, taste notes from the assistant and, if your chats are saved, the full text of those chats (each time one is opened, that is recorded). They also see each member's event sign-ups, whether they came and when each event reminder reached their inbox, and the perks used today with each member's first name, member number and table. They see counts too: how many members were active, read each kitchen note and course lesson, started or finished each course and chose a digest by email or by text, how many times each perk was used, and how many of the notices sent in the last 30 days were read. A count can cover a single member. They can group members, start automatic follow-ups such as a birthday note or an offer on a dish you picked at the table but did not order, download the contact details of members who agreed to hear from them, and pull a feed of member activity, bookings included, into their own tools. A restaurant can leave a share of members out of a follow-up at random, so it can compare how often members with and without it came back and how much they spent; it sees totals for each group, not who was left out. Turning messages off later does not reach a copy the restaurant already downloaded.

Other members of that community see your first name, your level, your place and points on the leaderboard, the posts and replies you write, and a What I had share once staff approve it, with its dishes, words and photo. If you list yourself in the members directory, they also see your member profile, described below. Points come from visits, dish ratings, events you attend and more, so they hint at how often you take part. At an event, other members see how many seats are taken or left and how many are on the waitlist, never who is going. You can leave the leaderboard at any time; that does not hide your shares or reviews. If the restaurant turns on reviews, a review you write of a visit is public on its community page with your first name and the date, and the restaurant can reply to it.

Member posts: where the restaurant turns them on (they are off unless it does), you can write a post in a category it opens to members, once you reach that category's level. A post has a title, your words, in which links are not allowed, and one photo if you add one. With a photo you confirm that it is yours and that anyone in it agreed to it being shared, and the restaurant keeps that yes and when you gave it for as long as it keeps the photo. RsrvX removes the location, camera and other details stored in the photo file before saving it, but keeps its color profile, which can carry a description of the device. Other members who can open that category see your post with your first name (or Member followed by your member number, if you gave no first name) and level, its likes and replies and the members you mentioned; members who blocked or muted you, and members you blocked, do not see it. In some categories a post waits for the restaurant to review it first, and reports from three members put a live post back in review. A post still waiting after 14 days is hidden and its photo deleted. You can write 3 posts a day, and the restaurant keeps how many you wrote each day, even after you delete one. If a post cannot go out, your browser keeps its title and words in a cookie for 2 minutes so you can send it again. You can delete a post of yours, whatever its state, from the community page wherever it is listed for you: among the newest posts there or on your own list of up to 20 of your posts: those waiting for review or hidden, those in a category the restaurant hid from members or that is now above your level and, while member posts are off, all of them. A live post in a category that is now above your level still shows to members who reach that level. A post no longer listed there, or any post while the restaurant has its community feed off, goes only when you leave the community or your membership is deleted. Deleting a post deletes its photo, likes and mentions and every reply under it, other members' replies included. A notice already sent to a member you mentioned stays in their inbox until it is deleted after 90 days, and it keeps your member number.

The restaurant's owners and managers see the posts waiting for review, the newest posts and replies members wrote and the ones they hid most recently, each with its words, its photo and the member's first name and member number. They can approve a post or a reply, decline or hide one with a reason, restore it, or mark it helpful. Declining or hiding a post deletes its photo. Your inbox tells you when the restaurant first lets a post of yours go live after review and when the restaurant marks a post or reply of yours helpful, and the reason a post was hidden shows next to it on your own list. The restaurant keeps a record of each of these decisions with who made it and the reason, and a record that each post was made and whether it had a photo, never the words; these records stay after the post is deleted.

Mentions: in a post or a reply you can mention a member by writing @ with the first word of their first name, then # and their member number, like @Ana#12, and in a post you can also pick them from a short list. Mentions work in replies under the restaurant's own posts and under What I had shares too, even where member posts and the members directory are off. You can mention only members who list themselves in the members directory while the restaurant has it on, or who already wrote in that conversation as the post's author or in a reply, and who reached the level the conversation needs, never a member you blocked or muted or who blocked you. The mention shows with the post or reply, with their first name and member number. Once the post or reply is live, the member gets a notice in their inbox, unless they muted or blocked you or already had 3 from you that day. The restaurant keeps a record of who was mentioned in which post or reply.

Members directory and profiles: where the restaurant turns on its members directory (it is off unless it does), members can see a list of the members who chose to be in it, search it by first name and open their profiles. You are not in it until you turn on List me in the members directory on your profile page in that community. Once you are, members of that community can find you there, open your profile and mention you, unless they blocked or muted you or you blocked them. Your profile shows your first name and, if you allow each one, your level, points, favorite dishes (up to 12 you pick from the menu), how many visits you made, your badges and up to 5 of your latest posts and shares. Each of these is shown to Members until you set it to Only me; your points show only where your level does, and a badge that would tell a part you hid stays hidden. Your member number is in your profile's web address, and members who can write posts can also see your first name and member number in the short list of members they can mention. Only me hides a part from other members only, and only on your profile and in the directory: your level still shows next to what you post and reply, and if you place on the leaderboard, your level and points show there unless you leave it. These choices are separate from the sharing settings on your RsrvX account. The restaurant keeps your choices and favorite dishes until you change them or your membership is deleted. A favorite dish the restaurant takes off its menu no longer shows to other members, but it stays on your list and in your download, and still counts toward your 12, until you remove it. Its owners and managers see who is listed in the directory, not the other choices you make for your profile.

Signing in on another phone: if you give your email or mobile number at a table on a phone you did not join from, a manager can check a photo ID against the first name on your membership and link that phone to it. A membership with no first name cannot be linked. That phone then stays signed in as you at that restaurant for 12 hours. It shows your member card, perk code, points, level, history and message choices, and it can ask for rewards and post visit reviews as you. It cannot change your name, message choices or birthday, or leave the community. Your member page lists the phones linked in the last 12 hours, and Remove signs one out at once. The restaurant's records show which manager linked a phone and when, and when you removed it.

Rewards: the restaurant keeps your check-ins, your points and what each was for, your progress toward any goals it sets and, only if you or its staff add it, your birthday month and day. Leaving the community deletes them. Where RsrvX has turned it on, a restaurant can give rewards points for each dish you rate at a visit, the same at any star rating. Only dishes served at your table and rated on the phone that checked in to your membership at that visit count, each dish once, up to a number of dishes the restaurant sets (3 unless it picks from 1 to 20). Where rating points are on, a What I had claim can also add a bonus the restaurant sets when the phone that made it rated a dish served at that visit. A review line from a rating that earned rewards points is labeled on the menu as having earned member points, and the label stays after you leave or delete your data. Where RsrvX has turned it on, a visit review earns the same community points at any rating.

Community points, which set your level and your place on the leaderboard, also count the dishes you rate. Wherever a restaurant's community feed is on, each dish you rate at a visit earns 2 points, up to 5 dishes a visit, at any star rating, unless the restaurant changes these numbers. Only dishes served at your table and rated on the phone that checked in to your membership at that visit count, each dish once. Ratings you made before this began count too. A review line from a rating that earned only community points has no label on the menu. Where member posts are on, each like another member gives a post of yours earns 1 point, up to 10 a day. Each post or reply of yours the restaurant marks helpful earns 5 points once, and a reply of yours under one of the restaurant's own posts or under a What I had share can be marked helpful even where member posts are off. The restaurant can change these numbers, and these points count only while the post or reply is live: not while the restaurant has hidden it or it waits for review, and not once it is deleted.

Courses and kitchen notes: when you tap Mark as read on a kitchen note or on a lesson in a course, the restaurant records which one and when. Opening a course or a lesson is not recorded. Your page shows how many lessons of each course you read and when you finish one. Mark as unread deletes the mark. Reading earns no points. No staff screen shows which lessons a member read. Finishing a course adds a badge, which other members see in the members directory and on your member profile if you list yourself in the members directory and let members see your level and badges.

Member events: you can say you are coming on the community page or on its events page. The restaurant records your party size, whether you are going or on the waitlist, when you said so and whether you came, from your check-in or a staff mark. You can cancel only before the event starts. After that, your sign-up stays until your membership is deleted. If you are going, a reminder lands in your community inbox before the event, 24 hours before unless the restaurant picks another time or none, and a notice tells you when a waitlist spot opens for you. Neither comes if you turned notices off, and neither is ever emailed or texted. Add my events to my calendar downloads one file with the events you are going to, and each event can be added on its own. The file has each event's title, time, description, price note and a link, and no name or contact details. RsrvX keeps no copy. Leaving the community or deleting your data does not reach a copy saved on your phone or in a calendar app, and anyone using a browser where you are signed in as a member, other than on a phone a manager linked, can download the file.

Perks are off unless the restaurant turns them on. A perk opens at a level, and most perks are used from your table; a perk for new dishes is not used but shows you the dishes added lately. The restaurant records which perk you used, the day and time, your visit and table, and which staff member confirmed it. Servers and floor leads who can see your table, and the owners and managers, see your first name, member number and table next to the perk you used that day and, for a perk staff confirm, a short code that matches your phone. Using an off-menu perk opens the invite-only menu for everyone at your table, and a record that you opened it stays with the restaurant, under an internal number, after you leave. A perk for new dishes puts a notice in the inbox of members at its level when the restaurant publishes new dishes. A perk use is kept until your membership is deleted.

A birthday perk works once a year in your birthday month, and staff confirm it. It uses the birthday month in that restaurant's rewards, which you can add there and its staff can also set. If there is none there, it uses the birthday month on your RsrvX account, when your account can prove that membership is yours (see Deleting your data) and you share your birthday with Restaurants I've joined, which is the default. Set your birthday to Only me on your account page to stop that. Your birthday has to be on file for a while first (30 days unless the restaurant's rewards set another wait), and on your RsrvX account any change to your profile starts that wait again. When you use the perk, the staff who see it can tell it is your birthday month. Where the restaurant's rewards already give a birthday treat, the perk sends you there instead.

If you tick a box to hear from the restaurant, we record that you agreed, the exact words you agreed to and when. You can turn messages off on your member page, or on your account page if you have an RsrvX account. A restaurant's marketing emails and texts go only to members who ticked its box for that channel: RsrvX checks the box again just before each one goes out, sends at most one every 3 days from the same restaurant on the same channel, and holds automatic follow-ups until between 9 am and 9 pm in the restaurant's time zone. Each marketing email has an unsubscribe link, which turns off that restaurant's marketing emails to that address and leaves other restaurants' alone. Every restaurant's texts and RsrvX's own, other than sign-in codes, come from RsrvX's texting service. Replying stop to one of its texts stops every text it sends to your number and turns off the texts you agreed to get from every restaurant and from RsrvX; your email choices stay as they are. Replying start lets texts through again but turns none of them back on, so tick each box again to get them. RsrvX has not switched on its email or texting service yet, so no marketing email or text is sent.

Community inbox: you get notices there when another member replies to your post or share or mentions you, the restaurant approves your post or marks your post or reply helpful, an event reminder is due, a waitlist spot opens for you, you reach a new level, you finish a course (the notice says a new course is open to you), a perk tells you about new dishes (the notice says a new perk is open to you) or your digest is ready. Notices are on unless you turn them off in your inbox, and the restaurant can turn them off for everyone. Turning them off keeps the notices you already have. A notice stores only what it is about, never anyone's words, except that a mention notice also keeps the member number of the member who mentioned you, which is in your download. The inbox does not name other members, but it shows the title of the post a notice is about, and a member's post has the title that member wrote. A notice about a post by a member you blocked or muted, or who blocked you, or about an event that is over, shows without its title. You get no reply notice from a member you blocked or muted. Notices are deleted after 90 days. Owners and managers do not see your notices or which ones you read. Apart from the counts described above, they see only when each event reminder reached a member's inbox, so they can tell when one did not. Your inbox opens only in a browser where you are signed in as a member, not on a phone a manager linked.

Digest: if the restaurant allows it (it is off unless the restaurant turns it on), you can choose a weekly or monthly digest in your community inbox. It is a short count of new posts, upcoming events, new courses and unread notices, never what anyone wrote. To choose one, you pick email or text, and you can pick only a channel where you ticked the restaurant's box. RsrvX has not switched that sending on, so for now the digest shows only in your inbox, while notices are on there. The digest relies on that box and records no yes of its own. Choose No digest in your inbox to stop it; while the restaurant has notices turned off, the inbox is closed and cannot change it. Once sending is on, the unsubscribe link in a digest email turns off all of that restaurant's marketing emails to that address, the digest included, and replying stop to a digest text works as described above. Owners and managers see how many members chose a digest by email and by text, not who.

RsrvX accounts: an account on rsrvx.com is optional and only for people 18 and over, which you confirm with a checkbox. You sign in with a code texted to a US mobile number or, when RsrvX turns them on, with Google or Apple. Asking for a code saves your number as a sign-in, even if you stop before creating the account, and a scrambled form of your number and of your internet address is kept, usually for a few hours, to limit how many codes are sent. RsrvX keeps your phone number or the email Google or Apple gives us, how you sign in, your handle and first name and, if you add them, your last name, bio, favorite cuisines, birthday (month and day) and home neighborhood, your sharing choices, and when you confirmed you are 18 or older.

A dining community membership at any restaurant joins your account on its own when every email and number on it is one your account verified, even one typed in at a table. If this browser joined a community with an email or number your account has not verified, your account page asks Is this you? and adds the membership only if you say yes. If you turn on a restaurant's messages from your account page and your membership there has no email or number for that channel, the restaurant gets the one verified on your account.

Your profile page at rsrvx.com/u/your-handle shows only what you choose. By default anyone can see your handle, and people with an RsrvX account who belong to one of the same restaurant communities also see your first name and last initial, bio, favorite cuisines, levels and the communities you joined. Anyone can join a restaurant's community from its page, so this can include people you do not know. Your birthday, neighborhood, contact details and visits are not on the page unless you change their settings, and your neighborhood, contact details and visits are never shown to everyone. Make my profile public shows your name, bio, cuisines, levels, communities and birthday to everyone, signed in or not. Restaurant staff are not shown the fields you share with Restaurants I've joined. So far only the birthday perk described above uses one: it can read your birthday month, and when you use the perk, the staff who see it can tell it is your birthday month. Profile pages ask search engines not to list them. This page is separate from your member profile in each community, described above: the sharing settings here, such as Levels and badges or hiding a community on your profile, do not change what members see in a community's members directory.

Your dining home: with an RsrvX account, rsrvx.com/dining shows each dining community your account can prove is yours (see Deleting your data), with your level, points, unread notices and next event there, the upcoming events across them and the dishes you saved. A community you hid on your profile still shows there, marked as hidden. Save this dish, on a kitchen note, on a lesson in a course or on your favorite dishes in a community, saves the dish to your RsrvX account, up to 100 dishes, and RsrvX keeps which dish, at which restaurant and when. Only you see your dining home and your saved dishes; restaurant staff and other members do not. Saved dishes stay on your account when you leave a community, and they are deleted when you remove them or when you delete your account. A dish the restaurant takes off its menu stays saved, shown without its name, until you remove it. When you combine two accounts, the dishes saved on the account that is folded in move to the account you keep, newest first, up to its 100 dishes; any left over are deleted. The dining pages ask search engines not to list them.

An RsrvX account also offers separate boxes for news and offers from RsrvX itself by email or text, only for an email or number your account has verified. They start unticked, and restaurants never see them. RsrvX's own marketing can go only to the verified email or number a yes was given for. Each time you change one of these choices, or a restaurant's from your account page, we record the exact words, the language and when, with the email or number each yes covers. An unsubscribe link in an RsrvX email, or replying stop to RsrvX's texting service, also turns your RsrvX choice off for that email or number, and we record that too. RsrvX does not send marketing of its own yet.

The server's assistant chat

We save assistant chats only for dining community members who were told at sign-up that their chats are saved. If you are not a member, nothing you type in the chat is saved. Your server may get a short topic note for your visit, such as a wine pairing or a celebration, never your words.

For members, we save the chat's messages and the dishes it mentions, linked to that visit, to this phone and to your membership. We use them to personalize your visits and the offers you get if you agreed to hear from the restaurant.

Questions about allergies, intolerances or diet safety are never stored, for members or anyone else. They reach the staff only as a topic for that visit, so your server can check with the kitchen.

Saved member chats are deleted after 365 days.

A chat assistant provider processes your messages to write the replies. We do not use these chats to train AI models.

Members can delete their saved chats at any time: use Remove what this phone shared at the end of the menu, or Leave the community. Clear my preferences in the chat deletes the preferences we learned from your chats.

Who else handles it

Supabase stores the data and runs sign-in. Vercel runs the website and the staff app, and sees your internet address with each request. Your browser loads dish photos and a restaurant's logo straight from where they are kept: Supabase for photos added through RsrvX, or any web address the restaurant gave, and that site sees your internet address and browser type too. A video in a course lesson is a link to YouTube or Vimeo: nothing loads from those sites until you tap it, and then it opens there in a new tab, where that site sees your internet address and browser like any site you visit. RsrvX does not tell it which page you came from. Anthropic runs the server's assistant, RsrvX's menu tools and Studio, where owners and managers build their menu. It receives chat messages, a member's first name and taste notes, and what owners and managers write in Studio and the menu files and photos they attach there, which go again with later messages in that conversation. When Studio looks up the community or rewards for them, for example for a weekly briefing, Anthropic also receives the first names and member numbers of up to ten of the newest and ten of the most active members, when and how they joined, their points, levels, how often they took part and when they last did, up to ten recent rewards used, by member number, and how many members agreed to marketing emails or texts. When RsrvX's support team asks for a drafted reply to a restaurant, Anthropic receives the restaurant's name and the last 12 messages of its Inbox conversation with RsrvX, with the writers' names. For a Spanish menu, Anthropic receives the menu's text only, and the restaurant approves the result before guests see it.

Twilio texts the sign-in codes for staff and for RsrvX accounts. Google and Apple run sign-in when RsrvX turns them on and give RsrvX an email address for you, and they deliver staff alerts to phones. Stripe handles restaurants' payments to RsrvX and gets no guest data. When RsrvX turns on photo styling, Higgsfield receives each dish photo an owner or manager chooses to style with AI, with the location and camera details stored in the file removed (its color profile stays), and the dish name and any short note about the scene. It gets no guest data, and RsrvX does not delete the copies Higgsfield keeps. When error reporting is on, Sentry gets a report of each error on RsrvX's servers: the error message, where in RsrvX's code it happened, the kind of page or request (never its address) and facts about the server. It gets no cookies, headers, internet address, browser details or form contents, and errors in your browser are not reported. Once RsrvX switches on email and texting, Resend will send the emails and Twilio the texts, with the address and the message: a restaurant's messages to its members, and RsrvX's notices and support replies to restaurant owners and managers. Twilio will also pass on texts sent back to RsrvX. Neither is switched on yet.

If a restaurant connects its own AI assistant or its own software to RsrvX on its AI connections page, that tool can read what the staff member who approved the connection can see. Owners and managers can connect one whether or not Staff assistants is on; other staff can connect theirs only at a restaurant where an owner or manager turned on Staff assistants, and while it is off their connections there are paused. Someone who works at more than one restaurant of the same group can let one connection reach each of them, with their role at each. For an owner or manager that includes members' first names and member numbers, when and how they joined, their points and what each was for, levels, check-ins, rewards and event sign-ups (party size, waitlist and whether they came), the full text of the replies they wrote under the restaurant's own posts, even ones a manager held or hid, their What I had claims (the dishes, the table, the points and the check amount staff entered), how often they took part (likes, poll votes, replies, events, invites, and kitchen notes and course lessons read, counting likes and replies on members' own posts) and when they last did, and totals about the restaurant's guests, such as how many there are, how big each group is and how each dish does, even when a total covers a single guest. When the connection covers reservations, for owners, managers, floor leads and hosts it also includes the first name, party size, time and status of each booking and waitlist entry, a booking's table and whether its guest is a member, and whether there is a note. It never gets a guest's email address, phone number, booking note, perk codes or assistant chats, and never gets members' own posts, their photos or the replies under them. RsrvX records each request the tool makes (which tool, the outcome, when and at which restaurant), not what it read, and cannot take back what a tool already read: leaving a community or deleting your data does not reach those copies. Owners and managers of the restaurant where the connection was made see an alert on that page when it is refused many times or a new one calls many different tools at once. Owners and managers of any restaurant it reaches can revoke it, and that stops it at once. When photo styling is on, a connection can also send a dish photo to be styled with AI. Connections stop working at a restaurant while its Smart Menu plan is paused.

A connection allowed to draft changes can also draft a booking or a waitlist entry, which waits for a person at the restaurant to approve it. While it waits, the draft holds the guest's name, email or phone and note: the restaurant's owners, managers, floor leads and hosts see them on the AI connections page and the host stand, and the assistant sees only the first name and whether a contact or note was given. Approving it makes the booking or waitlist entry. Approving or declining it removes those details from the draft, and so does a deletion request for that email or number through the account deletion page. A draft not decided in time (at most 7 days for a booking, 2 hours for a waitlist entry) can no longer be approved, and RsrvX's daily cleanup, once switched on, removes its details.

A restaurant can also set up notices to a web address it chooses when its menu, its look or its community posts change. A notice carries ids and the titles and summaries staff or an assistant wrote, never a guest's email address or phone number. Members' own posts and What I had shares never send a notice.

Diners' AI assistants: an AI assistant you use can look up restaurants that take bookings on rsrvx.com, their opening hours and free times, and give you a link to the booking page. It never books for you and never gets or sends your name or contact details; you enter those on the booking page. RsrvX keeps only a scrambled form of the assistant's internet address, usually for a few minutes, to limit lookups, and notes failed lookups in its server log. A restaurant can turn this off.

Forms on rsrvx.com: the Book a demo form keeps the name, email, restaurant, city, number of locations, interests and note you send, and the restaurant sign-up form keeps the details about you and your restaurant you send. Both keep when the form arrived, how long it took to fill in and the page you sent it from, in private files at Vercel. The account deletion form keeps the email or phone and the details you send, your browser type and a scrambled internet address. Asking our team to set RsrvX up for you from the home page keeps your name, phone and email, the description of your restaurant, a note with the look you picked and the names of the menu files you chose, and a scrambled form of your internet address, and the RsrvX team sees them. None of these has a set deletion date yet, and the account deletion form does not reach the files at Vercel.

If you describe your restaurant on the rsrvx.com home page and press send, your browser keeps the description, the look and the file names in a cookie for a day. The menu files themselves stay on your device. Your browser sends the cookie with each visit to rsrvx.com and the RsrvX sites under it, and their pages can read it. The first time Studio opens in that browser, it puts the description in its message box for whoever is signed in there, then deletes the cookie; signing out does not delete it. Until you close the tab, the page also keeps the name, phone and email you typed for our team. The description reaches Anthropic only if someone sends it as a Studio message.

Global Privacy Control

If your browser sends a Global Privacy Control signal, the menu stops recording what you open and look at. What you do on purpose, like picks, ratings and calls, is still recorded because your table needs it.

How long it is kept

The allergy card and your notes for staff are deleted when staff clear your table. Saved member chats are deleted after 365 days, notices in a community inbox after 90 days, and the assistant's scrambled internet address after 2 days. A member post still waiting for review after 14 days is hidden and its photo deleted.

A note you add to a booking stays with the booking. An RsrvX account, its settings and the history of its message choices are kept until you delete the account, or until the sign-in it uses is deleted in the RsrvX Staff app or through the account deletion page. Dishes you saved stay on the account until you remove them or the account is deleted, even after the restaurant takes the dish off its menu. Combining two accounts moves the dishes saved on the account that is folded in to the account you keep, up to its 100, and deletes any left over. After a download, a deletion or two accounts being combined, RsrvX keeps a record of it with internal numbers only.

RsrvX keeps a record of each email and text it prepares or receives. When a membership, an RsrvX account or a sign-in is deleted, RsrvX clears the wording of the messages it sent to that person. Unless another membership or account still uses the same email or number, it also takes that email or number off those records and deletes the emails and texts received from it. A message still waiting to go out to that person is not sent. An email or number that asked RsrvX to stop messages stays on its do-not-send list, so they stay stopped. Once RsrvX switches on its daily cleanup, the address and wording of a message are also cleared 180 days after it was prepared, and emails and texts sent to RsrvX are deleted after 90 days.

Once RsrvX switches on the daily cleanup for AI connections, the reservation drafts connected assistants make are deleted 90 days after they were made, and records of requests from connected assistants and software after 13 months.

Bookings, waitlist places, community activity such as posts (hidden ones included), mentions, event sign-ups, lesson reads and perk uses, member profile choices and favorite dishes, requests for a call from RsrvX's team, Inbox conversations with RsrvX's support team and the rest have no set deletion date yet. A schedule will be set before launch and listed here.

Deleting your data

At the table: open the menu on the same phone, scroll to the end and tap Remove what this phone shared. It deletes what this phone opened there, its allergy and access notes, its assistant chats and any dining community membership joined from it. Your order, your picks, your ratings and any review line you shared, your calls and requests and your server's notes stay with the restaurant. While your visit is open, Remove my line on the menu takes a review line back.

Table activity is tied to the phone, not to your name, email or number, so only that phone can remove it. If a manager linked this phone to a membership you joined somewhere else, Remove what this phone shared signs this phone out of it but does not delete the membership.

Members can also leave the community from their member page. Leaving deletes the membership with its points, check-ins, saved chats, posts and their photos, replies, shares, reviews, event sign-ups, lesson reads, perk uses, notices, notice settings, member profile choices, favorite dishes and the record of where you were mentioned, on every phone. Replies other members wrote under your posts and shares go too. Anything another member typed about you, such as @ with your first name and member number, stays in their post or reply. The notices that told members you mentioned them are deleted too. Dishes you saved to an RsrvX account stay on the account.

If you have an RsrvX account, sign in at rsrvx.com/account. Download my data gives you a file with your profile, sharing settings, sign-in contact, message choices and their history and, for each linked membership, its member record, check-ins and rewards points; an email or number on a membership that your account has not verified is left out. For a membership your account can prove is yours (the kind Delete my account erases), the file also has what you did in that community: posts (with the type and size of a photo, not the photo itself) and your photo consent, shares, visit reviews, likes, poll votes, replies, your reports, the members you blocked or muted, your leaderboard choice, your invite code, where you were mentioned, how many posts, replies and shares you wrote each day, member profile choices, favorite dishes, event sign-ups, lessons read and course progress, perks used, notices and notice settings. The file also lists the dishes you saved. Other members appear in it only by member number, including the friends you invited. A linked membership your account cannot prove has no community part. Without an RsrvX account there is no download. Delete my account erases each membership linked to your account, with its points and perks, plus your profile and its public page, your sharing settings, your saved dishes and your message choices. A membership with an email or number your account has not verified is only taken off your account and stays with the restaurant, unless you added it with Is this you? or it came with an account you combined. If you also work at a restaurant, your staff sign-in stays. If you do not, your sign-in and your requests for a call from RsrvX's team are deleted too.

Bookings and waitlist places are tied to the email or mobile number you gave. Cancelling a booking or leaving the waitlist keeps it in the restaurant's book, and leaving a community or deleting your RsrvX account does not remove your name, contact or note from it.

If you no longer have the phone, the account deletion page takes requests to delete a dining community membership or a staff account by its email or phone number. After RsrvX checks a request by hand, it deletes every membership with that email or number and every sign-in that uses it, staff or not, unless that sign-in belongs to a restaurant's only owner, a restaurant's shared floor screen or RsrvX's own team. Deleting a sign-in also deletes the RsrvX account on it, the way Delete my account does; dishes saved to an RsrvX account go only with the account. The same request removes your name, email, mobile number and note from bookings and waitlist places made with it at every restaurant, and from those made through a membership it deletes, which keep their time, party size and outcome. It deletes requests for a call from RsrvX's team that were sent without signing in with that email or number, with everything in them, and takes the email or number off requests someone sent while signed in. Send one request for each email address and each mobile number you used.

If you work at or own a restaurant on RsrvX

Staff sign in with a code texted to their phone (sent through Twilio), a sign-in link sent to their email, or an email address and password. Google and Apple sign-in and passkeys can be turned on later; with a passkey, your fingerprint or face check stays on your phone. RsrvX keeps your phone number or email, your name if one is on your profile, your roles and shifts at each restaurant, which table calls you were alerted to, answered, handed to a teammate or closed and when, a scrambled form of your floor-screen PIN, the alert settings of the phones you turn alerts on, when each alert reached your phone, which member perks you confirmed at a table and, in a dining community, which member posts and replies you approved, declined, hid, restored or marked helpful, which post categories, courses and perks you created or changed and the photos you put on the restaurant's posts and on its courses, lessons and events, each recorded with your account.

Owners, managers, floor leads and kitchen staff see on Pulse how quickly each person answered and finished table calls, by person and by shift. When a guest raises an allergy call, the guest's phone shows whether a staff phone got the alert, not whose.

If you use menu training, RsrvX keeps, for each dish, how many times you checked yourself, your last answer and when you passed. Owners and managers see, by name, how many dishes each person has learned and when they last passed one.

Alerts go through Apple, Google or your browser's push service, and their text can show on your lock screen.

Owners add a card on Stripe's own page. Stripe keeps the card and the billing details you give it; RsrvX never sees the card and keeps only Stripe's customer and subscription numbers and your plan's status and dates. Once RsrvX switches on these notices and its email and texting, each owner of a restaurant gets a notice when its 30-day start is ending, a payment fails or its plan pauses, naming the restaurant and linking to Billing: by email, or by text to an owner with a phone number and no email. Notices wait until between 9 am and 9 pm in the restaurant's time zone and are not sent to a number that replied stop. If you ask RsrvX's team for a call with Talk to us on the Billing page, RsrvX keeps the topic and the phone number and note you give, and the RsrvX team sees them with the name and phone on your profile and your sign-in email.

Owners and managers can write to RsrvX's support team in Inbox. RsrvX keeps each message with who wrote it and when, and for each request its type, how quickly the team replied and when it was closed. The restaurant's other owners and managers see the latest 100 messages of the conversation with each writer's name, and everyone on RsrvX's support team can read every restaurant's conversation. The team also keeps notes about the restaurant, its preference for approving menu changes and a health score made from its visits, new members, ratings and open problems; owners and managers see only who their account manager is. A menu change the team drafts waits in Inbox for an owner or manager to approve, but the team can publish a waiting change itself when it changes no price, allergen or nutrition detail, unless the restaurant asked to approve every change. Once RsrvX switches on texting, a text to RsrvX from the phone number you sign in with joins the Inbox of a restaurant where you are an owner or manager, the one whose conversation was active most recently, and the team's reply comes back by text. Once email is on, RsrvX can also email each owner a weekly and a monthly summary of the restaurant's visits, new members and ratings; there is no setting to turn these off yet.

You can delete your account under More in the staff app. If you are a restaurant's only owner, add another owner first. It removes your name and phone number, your roles, your alerts, any AI connections you made, your menu training results and your requests for a call from RsrvX's team, and signs you out on every device. It also clears the wording of the emails and texts RsrvX sent to your number or email, takes your number and email off those records and deletes the texts and emails you sent to RsrvX. If you sign in to an RsrvX account on rsrvx.com with the same phone number or email, it deletes that account too, the way Delete my account does. What you wrote to RsrvX in Inbox, in the app or by text, stays in the restaurant's conversation without your name. The record of what was done during service stays, and so does the record of the member perks you confirmed and, in a dining community, of the posts and replies you approved, declined, hid, restored or marked helpful, the post categories, courses and perks you created or changed and the photos you put on the restaurant's posts and on its courses, lessons and events, all without your name or phone number, and your restaurant's plan and billing records stay with the restaurant.

Contact

A contact address for these questions will be listed here before launch. Until then, send any request about your data through the account deletion page.