Privacy Policy

This Privacy Policy describes how REVAAI LLC, a New Jersey limited liability company doing business as “R.ai” (“R.ai,” “we,” “us”), collects, uses, discloses, retains, and protects information in connection with the R.ai AI phone-agent service for restaurants (the “Service”).

1. Roles and scope

1.1 R.ai operates the Service for restaurants located in the United States. Restaurants that subscribe to the Service are referred to as “Customers.” The diners and members of the public who call those restaurants are referred to as “Callers.”

1.2 With respect to Caller data captured during inbound calls (order history, caller phone number, optional name, transcripts, audio outside of payment portions), R.ai acts as a service provider and data processor on behalf of the Customer. The Customer is the business that determines the purposes for which Caller data is collected through the Service. R.ai processes Caller data on the Customer's instructions and under the Customer's data-processing agreement.

1.3 With respect to Customer account data (business contact information, billing information, configurations, and Dashboard activity logs), R.ai is the controller of such data.

1.4 The Service is offered only in the United States in V1. International availability and international transfers are addressed in Section 8.

2. Information we collect

2.1 Information we collect from Customers (restaurant accounts)

• Business legal name, address, and operating addresses.
• Owner and authorized personnel name(s) and email address(es).
• Telephone numbers, including the public-facing number the Customer forwards to the Service and the back-line number used for human handoffs.
• Business hours, holiday schedule, and time-zone information.
• Menu, modifiers, prices, ingredient and allergen designations, tax rate, and out-of-stock states.
• Point-of-sale credentials necessary to integrate with the Customer's POS provider. POS credentials are stored encrypted at rest and used solely to operate the Service on the Customer's behalf.
• Subscription billing reference data (Stripe customer and payment-method identifiers) used solely to manage and reconcile each monthly charge. Full card numbers, CVV codes, and expiration dates are held by Stripe, not by R.ai.
• Dashboard activity logs, including sign-in events, configuration changes, and feature use, used for security, troubleshooting, and audit.

2.2 Information we collect from Callers (the diners)

• Telephone number (captured via inbound caller ID).
• Name, if the Caller provides one during the call.
• Order history — items, modifications, totals, pickup or delivery designation, and delivery address where applicable.
• Audio recording of the call. Card details are not spoken to the Agent — payment is collected on a separate PCI-scoped keypad flow operated by our telephony provider (see Section 3).
• Machine-generated transcripts of the audio.
• Preferred language as detected by the Agent.
• Payment method information is never captured by, transmitted through, or stored on R.ai systems. When a Caller pays by card, the card is entered on the telephone keypad inside our telephony provider's PCI-DSS Level 1 certified payment flow, or on a hosted Stripe checkout page; R.ai receives only a payment token. R.ai does not receive or retain primary account numbers, CVV codes, expiration dates, or magnetic-stripe data. See Section 3.2.

2.3 Information collected automatically on joinrai.com

• Standard server logs (IP address, browser user agent, requested URL, timestamps), retained for security and abuse-monitoring purposes for up to ninety (90) days.
• Cookies necessary to provide the Service (authentication session, theme preference) — see Section 9 and the Cookie Policy.
• Product-analytics events captured by PostHog (page views, button clicks, funnel events). These are configured to drop unique identifiers for non-authenticated visitors and to associate authenticated visitors with their R.ai account identifier only.

3. Call recording and recording-consent compliance

3.1 Inbound calls handled by the Agent are recorded and transcribed for order accuracy, quality assurance, dispute resolution, and analytics. The Agent does not play a spoken call-recording or AI disclosure at the start of calls.

3.2 Card details are never spoken to the Agent. When a Caller pays by card on the call, the call is handed to a PCI-scoped payment flow operated by our telephony provider (Twilio), where the Caller enters their card on the telephone keypad and the card is tokenized before it reaches R.ai. Alternatively, the Caller may be sent a secure hosted payment link by text message. In both cases, primary account numbers, expiration dates, and CVV codes are never transmitted to, processed by, or stored on R.ai systems.

3.3 Because the Agent does not announce recording on the call, and because the Dashboard does not expose a setting for a Customer to enable such an announcement, Customers are responsible for determining whether their use of call recording satisfies the consent requirements of every jurisdiction in which they accept calls, including all-party-consent states such as California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, and Washington. That determination is the Customer's to make with its own legal counsel. See the Terms of Service, Section 5.1, for the Customer's recording-compliance covenants.

4. How we use the information

4.1 R.ai uses the information described in Section 2 to:

• Operate the Service — answer inbound calls, take orders, collect payment, push orders to the Customer's POS, and send order-confirmation SMS to the Caller.
• Provide the Dashboard, including call history, transcripts, audio playback, analytics, and the “Ask R.ai” assistant.
• Bill the Customer's account and handle billing-related correspondence.
• Detect, investigate, and respond to abuse, fraud, security events, and violations of the Terms of Service.
• Improve the Service. R.ai may use aggregated and de-identified data derived from Customer Data and Caller Data for product improvement, model evaluation, and benchmarking. R.ai does not use Customer or Caller data to train third-party general-purpose AI models that operate outside the Service.
• Send transactional communications, including service announcements, security alerts, billing notices, and onboarding instructions. Marketing communications are sent only with separate consent and can be turned off at any time.
• Comply with applicable law and respond to lawful requests, subpoenas, and court orders.

4.2 SMS / text-message program and consent

When a Caller places an order by phone or by messaging, R.ai sends order-related text messages — order confirmations, order-ready and delivery-status updates, and replies to questions about the order — to the mobile number the Caller provides. By providing a mobile number at the time of an order, the Caller consents to receive these messages.

• Message frequency varies by ordering activity; Callers typically receive one to five messages per order.
• Message and data rates may apply, depending on the Caller's mobile carrier and plan.
• Callers may reply STOP at any time to opt out of further messages, or HELP for assistance.
• Mobile phone numbers are never sold, and are never shared with third parties or affiliates for their own marketing purposes. A Caller's mobile number is shared only with R.ai's messaging subprocessor (Twilio) for the sole purpose of delivering the messages described above. No mobile opt-in information is shared with any third party for marketing.

We do not share, sell, or otherwise provide your mobile phone number or messaging consent information to any third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties.

5. Who we share with (subprocessors)

5.1 R.ai uses a small set of vetted third-party subprocessors to operate the Service. Each subprocessor processes information only on R.ai's documented instructions and under a written contract that includes appropriate confidentiality and security obligations. A current list is maintained at joinrai.com/subprocessors. The subprocessors as of the effective date of this policy are:

• Vapi (Vapi Labs, Inc.) — voice AI orchestration; processes call audio in real time and produces transcripts. vapi.ai/privacy
• Twilio Inc. — inbound and outbound telephony and SMS. Provides the carrier infrastructure for the R.ai-provisioned number that forwarded calls arrive on, and for order-confirmation messages. twilio.com/legal/privacy
• Stripe, Inc. — payment processor for customer card payments and for restaurant subscription billing. We never store card numbers, CVV, or expiration dates — Stripe tokenizes. stripe.com/privacy
• Resend (Resend, Inc.) — transactional email delivery (account confirmations, password resets, billing notices). resend.com/legal/privacy-policy
• Clerk (Clerk, Inc.) — authentication and user-session management for the Dashboard. clerk.com/legal/privacy
• Neon (Neon, Inc.) — managed Postgres database hosting in the United States. neon.tech/privacy-policy
• Vercel Inc. — application hosting, edge networking, and blob storage for call audio recordings. vercel.com/legal/privacy-policy
• OpenAI, L.L.C. — large-language-model inference for the telephone Agent, speech transcription (Whisper), and text embeddings for semantic search. Processes call transcripts, call audio, system prompts, and caller order history. openai.com/policies/privacy-policy
• Anthropic (Anthropic, PBC) — large-language-model inference for the Dashboard's Ask R.ai assistant, call summaries, inbound-message handling, and de-identification. Anthropic processes prompt and response data and does not use it to train its models. anthropic.com/legal/privacy
• Meta Platforms, Inc. — WhatsApp Business Platform message delivery (reached via Twilio), for restaurants that enable the WhatsApp add-on or the WhatsApp-only plan. Processes recipient WhatsApp number, message body, and delivery metadata. whatsapp.com/legal
• ItsaCheckmate (Checkmate Labs, Inc.) — point-of-sale order aggregation for restaurants configured on that path. Processes order contents, caller name, caller phone number, and delivery address where applicable. itsacheckmate.com/privacy-policy
• Sentry (Functional Software, Inc.) — application error monitoring. Captures stack traces and limited request metadata; configured to redact known sensitive fields. sentry.io/privacy
• PostHog (PostHog, Inc.) — product analytics for joinrai.com and the Dashboard. posthog.com/privacy

5.2 R.ai also discloses information when required to do so by law (subpoena, court order, valid governmental request) and when necessary to investigate or address a violation of the Terms of Service or to protect the safety of the public or any person. R.ai will provide notice to affected Customers of a legal-process disclosure unless prohibited from doing so.

5.3 In the event of a merger, acquisition, financing, or sale of substantially all of R.ai's assets, information may be transferred to the successor entity under these same commitments.

5.4 R.ai does not sell personal information.R.ai does not share personal information with third parties for those parties' own marketing purposes.

6. Where information is stored

6.1 R.ai stores Customer Data, Order Data, and Caller Data primarily on infrastructure operated by Neon and Vercel in data centers located in the United States. Call audio recordings are stored in Vercel Blob in the United States.

6.2 Voice processing performed by Vapi occurs at Vapi's United States edge locations.

6.3 Cross-border transfers are not made in V1. Customer operations outside the United States are not supported in V1 and will be addressed in a future version of this policy.

7. Security

7.1 R.ai protects information using a layered set of administrative, technical, and physical safeguards, including:

• Encryption in transit — TLS 1.2 or higher for all connections to joinrai.com, the Dashboard, and the API.
• Encryption at rest — AES-256 encryption applied by the underlying providers (Neon for the database, Vercel Blob for audio files).
• Payment processing — card data captured during the call is transmitted to our PCI-DSS-compliant payment processor (Stripe) for processing and tokenization. Card numbers, CVV codes, and expiration dates are not stored on R.ai systems.
• Access controls — production data access is restricted to a limited set of R.ai personnel under role-based controls and is logged.
• Authentication — multi-factor authentication is supported for Dashboard accounts via Clerk and is strongly recommended for all administrator accounts.
• Monitoring — Sentry error monitoring, Vercel and Neon platform logs, and PostHog event capture are used to detect operational anomalies.
• Vendor diligence — all subprocessors are reviewed for security and contractual privacy protections before being engaged.

7.2 No security program is perfect. In the event of a security incident affecting Customer Data or Caller Data, R.ai will notify affected Customers without undue delay and in compliance with applicable breach-notification laws.

8. Retention

8.1 R.ai retains information only as long as needed for the purposes described in this policy, unless a longer retention period is required by law. Specific windows are:

• Call audio recordings — retained for the duration of the Customer's service relationship with R.ai, and indefinitely thereafter unless deletion is requested. Deletion is available on request as described in Section 10.
• Call transcripts — retained for the duration of the Customer's service relationship with R.ai, and indefinitely thereafter unless deletion is requested. Deletion is available on request as described in Section 10.
• Order records — for the lifetime of the Customer's account, deleted within 90 days of account termination.
• Caller records (name, phone number, order history) — for the lifetime of the Customer's account, deleted within 90 days of account termination, subject to the rights described in Section 10.
• Customer account data and Dashboard activity logs — for the lifetime of the account, deleted within 90 days of account termination.
• Subscription billing records, invoices, and tax records — retained for seven (7) years following the date of the transaction to comply with United States tax and audit obligations.
• Demo and meeting bookings (name, email, phone, and any notes you enter when booking) — the calendar entry holding these details is deleted 90 days after the meeting ends. R.ai separately keeps a sales-contact record for the person who booked; that record can be deleted on request as described in Section 10.
• Server logs (IP, user agent) — up to 90 days.
• De-identified or aggregated data — retained indefinitely.

8.2 R.ai honors data-subject deletion requests as described in Section 10. Verified deletion requests will be completed within thirty (30) days of receipt, subject to legal-retention exceptions (e.g., billing and tax records that R.ai is required to retain).

9. Cookies and tracking technologies

9.1 joinrai.com and the Dashboard use a small number of cookies and similar technologies, all classified as either strictly necessary or analytics. A full list is in the Cookie Policy.

9.2 R.ai does not use advertising cookies and does not sell or share personal information with advertising networks. R.ai honors the Global Privacy Control browser signal as an opt-out request for analytics processing.

10. Your rights

10.1 California residents

Residents of California have the following rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (collectively, “CCPA”):

• Right to know. Request a copy of the personal information R.ai has collected about you, the sources of that information, the purposes for which it is processed, and the categories of third parties with whom it has been shared.
• Right to delete. Request deletion of personal information R.ai has collected about you, subject to legal-retention exceptions.
• Right to correct. Request correction of inaccurate personal information.
• Right to limit use of sensitive personal information. R.ai does not use sensitive personal information for purposes that trigger this right.
• Right to opt out of sale or sharing. R.ai does not sell or share personal information for cross-context behavioral advertising. No opt-out is required.
• Right to non-discrimination. R.ai does not discriminate against any consumer for exercising their privacy rights.

To exercise any of these rights, email ezra@joinrai.com or eitan@joinrai.com from the email address associated with the account, or, if you are a Caller, identify the restaurant you called and the approximate date of your call. R.ai will verify your identity and respond within forty-five (45) days, subject to a one-time forty-five-day extension for complex requests.

10.2 GDPR and other jurisdictions

The Service is offered only in the United States in V1. R.ai will update this section and provide GDPR-specific rights (access, rectification, erasure, restriction of processing, data portability, objection, and rights related to automated decision-making) prior to making the Service available in jurisdictions where the GDPR or comparable laws apply.

10.3 Callers — how to request deletion

Because R.ai processes Caller data on behalf of the Customer (the restaurant), Callers have two routes to delete their information:

• Text or call the restaurant directly and ask to be removed from their customer list. The Customer can delete the Caller record from the Dashboard.
• Email ezra@joinrai.com with the restaurant's name and the phone number used to call. R.ai will route the request to the Customer, verify identity, and confirm deletion within thirty (30) days.

11. SMS

11.1 Order-confirmation SMS messages are sent only to phone numbers that have placed an order with the Customer through the Service. These messages are transactional and are sent on the Customer's behalf via Twilio.

11.2 Every SMS includes a “Reply STOP to opt out” instruction. Replying STOP immediately sets sms_opt_out = true on the Caller record and stops future messages. Replying HELP returns a one-line description and the restaurant contact email.

12. Children

12.1 The Service is not directed to children under thirteen (13) years of age. R.ai does not knowingly collect personal information from children under thirteen. If a child has called a Customer restaurant and a parent or guardian wishes to request deletion of that information, email ezra@joinrai.com.

13. Changes to this policy

13.1 R.ai may update this Privacy Policy from time to time. Material changes will be communicated by (a) email to the account owner's registered email address and (b) a posted revision at joinrai.com/privacy with an updated effective date. Material changes take effect thirty (30) days after notice.

14. Contact

Privacy questions, data-subject requests, and complaints should be sent to ezra@joinrai.com or eitan@joinrai.com, or by mail to REVAAI LLC, 459 Warwick Avenue, Teaneck, New Jersey 07666. R.ai responds within five business days of receipt.

© 2026 REVAAI LLC. This policy applies to joinrai.com and any subdomain operated by R.ai.