Cookie Policy
Last Updated: July 13, 2026
This Cookie Policy explains how Reslify uses cookies and similar browser technologies, including local storage and session storage, across reslify.com and Reslify subdomains. Please also read our Privacy Policy.
If you have questions, contact privacy@reslify.com.
1. How We Use Cookies and Similar Technologies
Reslify uses a small number of browser technologies to operate our website, booking pages, merchant tools, onboarding flow, product documentation, and operations console. These technologies may remember choices, keep sessions secure, support payments and bookings, measure product performance, or attribute bookings from partners.
We group them into these categories:
Necessary. Required for security, authentication, booking flows, payment flows, fraud prevention, consent management, language selection, and service delivery. These include merchant authentication/session storage, portal access tokens, booking flow state, payment processor storage used by Stripe, and similar technologies needed to provide requested services. These cannot be turned off through Reslify's cookie banner.
Preferences. Used only with your consent to remember optional choices such as the selected merchant, dismissed interface notices, booking-assistant continuity, and locally saved portal-design drafts. These improve the service experience and are not used for advertising.
Analytics and performance. Used only with your consent to understand page views, feature usage, conversion funnels, errors, browser performance, and service reliability. This category includes Reslify first-party analytics identifiers; Google Analytics 4 on the landing site, product documentation, onboarding, merchant panel, and guest booking portal where external analytics is enabled; and AWS CloudWatch RUM only on the production onboarding and merchant panel applications when its monitor configuration is enabled.
Marketing and partner attribution. Used only with your consent to measure partner booking attribution, including Reserve with Google attribution through _rwg_token. Reslify will not use additional marketing or advertising pixels unless they are enabled in the product and described in this policy or in the cookie settings.
2. Consent Storage
We store your cookie choice in the reslify_consent cookie and mirror the same choice in reslify.consent.v1 local storage as a same-origin fallback and browser-tab broadcast mechanism. In production, reslify_consent is scoped to reslify.com so your choice can apply across Reslify subdomains such as onboarding.reslify.com, panel.reslify.com, docs.reslify.com, and reserve.reslify.com. In development environments, consent is scoped separately to dev.reslify.com.
The consent record includes the categories you selected, when the choice was updated, and when it expires. It lasts for up to 180 days. If the consent record is missing, expired, or invalid, Reslify treats optional preferences, analytics, performance, marketing, and partner attribution storage as denied until you make a new choice. Necessary market and application-language storage remains available so the requested regional and language experience continues to work. Public content language is taken from the URL. Reslify no longer writes or uses a separate public-language cookie.
3. Current First-Party Storage
| Name or pattern | Type | Category | Purpose | Duration |
| --- | --- | --- | --- | --- |
| reslify_consent | Cookie | Necessary | Stores your cookie choices across Reslify subdomains. | Up to 180 days |
| reslify.consent.v1 | Local storage | Necessary | Mirrors your cookie choices for same-origin fallback and tab-to-tab updates. | Up to 180 days through the stored expiry, unless browser storage is cleared sooner |
| reslify-market | Cookie | Necessary | Keeps the active market because language URLs do not distinguish regional pricing, onboarding, or legal context. | Up to 180 days |
| reslify-language (onboarding) | Local storage | Necessary | Applies the interface language you selected in onboarding. | Until browser storage is cleared |
| portal_lang | Cookie | Necessary | Applies the booking portal language you selected. | Up to 180 days |
| portal_access_token, portal_designer_session | HttpOnly cookies | Necessary | Keeps secure access to private booking portal or designer sessions after a user-requested launch flow. | Access token until its related session expires; designer session up to 8 hours |
| CognitoIdentityServiceProvider.<clientId>.LastAuthUser and CognitoIdentityServiceProvider.<clientId>.<user>.* | Local storage | Necessary | Retains the authenticated merchant or operations session, including the tokens and session metadata Cognito uses to restore it. | Until sign-out, browser storage is cleared, or Cognito no longer accepts the stored credentials |
| onboarding-session | Session storage | Necessary | Keeps an in-progress onboarding flow working across steps. | Browser session, or until the flow clears it |
| booking-widget:flow:v1 | Session storage | Necessary | Preserves in-progress booking search, guest, and selection state that you entered or selected. Gift-card codes and notes are not stored. | Browser session; cleared when a reservation is created, a cancellation finishes, or the flow restarts |
| booking-copilot:* and booking-copilot:no-availability-dismissed:* | Session storage | Preferences | Keeps booking assistant conversation continuity and dismissed booking suggestions for the current browser session. | Browser session |
| panel:selectedMerchantId and panel:setup-banner-dismissed:* | Local storage | Preferences | Remembers selected merchant and dismissed setup notices in the merchant panel. | Until changed, reset, or browser storage is cleared |
| reslify-operations-language | Local storage | Necessary | Applies the interface language you selected in the operations console. | Until changed or browser storage is cleared |
| portal-designer-local:v1:<merchantId> | Local storage | Preferences | Preserves a merchant's locally saved portal-design draft. | Until removed or browser storage is cleared |
| reslify:pending-menu-import-draft | Session storage | Necessary | Transfers the menu import draft you selected into the editor. | Browser session, or until imported or cleared |
| reslify.analytics.anonymous_id, reslify.analytics.session_id | Session storage | Analytics and performance | Measures feature usage, funnels, and reliability after analytics consent. | Browser session |
| cwr_c, cwr_i | Local storage | Analytics and performance | Caches temporary AWS credentials and a Cognito identity used only to deliver consented CloudWatch RUM telemetry. | Until the credentials expire, analytics consent is withdrawn, or browser storage is cleared |
| cwr_s, cwr_u | Cookies | Analytics and performance | Maintains the consented CloudWatch RUM browser session and user identifier. | Controlled by the RUM session and retention configuration; cleared when analytics consent is withdrawn where technically possible |
| _rwg_token | HttpOnly cookie | Marketing and partner attribution | Stores Reserve with Google attribution for booking conversion measurement after marketing consent. | Up to 30 days |
4. Third-Party Technologies
Some features rely on third-party providers:
| Provider | Used for | Consent category | Notes |
| --- | --- | --- | --- |
| Stripe | Payment processing and fraud prevention in payment flows. | Necessary | Stripe may set cookies or similar technologies needed to process payments and prevent fraud. Stripe's use is also governed by Stripe's policies. |
| Google Analytics 4 | Page views, feature usage, and conversion funnel analytics on Reslify's landing site, product documentation, onboarding, merchant panel, and guest booking portal. Browser interaction events are sent directly to GA4; server-confirmed product and conversion events may also be sent through Google's Measurement Protocol. | Analytics and performance | Used only after analytics/performance consent where external analytics is enabled. Reslify configures _ga and _ga_* for up to 180 days without extending their expiry on later visits. Google may use shorter-lived cookies such as _gid. |
| AWS CloudWatch RUM | Browser performance, errors, HTTP telemetry, and service reliability for the production onboarding and merchant panel applications. | Analytics and performance | Used only after analytics/performance consent when the RUM monitor configuration is enabled. RUM is not used in Operations. RUM uses cwr_c and cwr_i in local storage and may use cwr_s and cwr_u cookies. Reslify disables RUM and clears these known items when analytics consent is withdrawn. |
| Reserve with Google | Partner booking entry and conversion attribution. | Marketing and partner attribution | Reslify stores _rwg_token only after marketing consent and sends conversion attribution to Google only when the related booking flow requires it. |
For U.S. privacy laws that provide opt-out rights for sale, sharing, targeted advertising, or cross-context behavioral advertising, Reslify does not currently use optional marketing storage for cross-context behavioral advertising. If that changes, we will update this policy and provide required opt-out controls. When your browser sends a Global Privacy Control signal, Reslify treats analytics, marketing, and partner attribution storage as denied, even if you previously selected those categories.
Third-party use of cookies and similar technologies is also governed by those providers' policies.
5. Managing Your Choices
You can accept all optional technologies, reject non-essential technologies, or customize your choices. You can reopen cookie settings from the Reslify interface at any time.
If you withdraw consent, Reslify updates Google Consent Mode, applies the new setting immediately, may reload the page where needed, and clears known non-essential browser storage where technically possible. Some cookies set as HttpOnly for security or partner flows may need to be cleared by the server on the next relevant request.
Browser settings may also let you block or delete cookies. Blocking necessary cookies may prevent parts of the Services from working correctly.
6. Changes
We may update this Cookie Policy from time to time. When we make changes, we will update the “Last Updated” date and publish the revised policy on our Services.