Effective and last updated: October 22, 2026
This Privacy Policy explains how ARVL, LLC (ARVL, we, us, or our) collects, uses, discloses, safeguards, and retains personal information through getarvl.com, arvl.shop, ARVL-powered services, and our business, owner, operations, partner, and shopper applications. It covers website visitors, grocery-ordering guests, business owners and administrators, shoppers, and referral partners. The Google Calendar section specifically describes our handling of information obtained through Google APIs.
Mobile information and SMS consent
ARVL sends optional transactional and operational text messages only with the applicable recipient’s separate consent. We retain the phone number, opt-in date and source, disclosure and policy version, and consent and opt-out history. A phone number, required terms acceptance, or business notification setting alone does not grant SMS consent.
Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with third parties, except aggregators and providers of the text message services needed to operate the SMS program on our behalf. These SMS restrictions take precedence over broader sharing provisions elsewhere in this policy.
Reply STOP to stop ARVL text messages or HELP for help. Manage optional account SMS through your own notification settings, or contact hello@getarvl.com. Opting out does not prevent account access, work assignments, or purchases. We may retain consent and opt-out records to honor your choice, resolve disputes, and meet applicable recordkeeping requirements.
1. Our role and independent businesses
ARVL operates a grocery-delivery technology and operations platform and provides or coordinates services under the ARVL brand and participating brands. Depending on the transaction, a business may use ARVL to operate its own storefront, manage its own guests and shoppers, and administer orders. The business identified on your storefront or order may have its own privacy notice and responsibilities. Contact that business about its independent handling of your information; contact ARVL about the platform and our handling of information.
For our own accounts, website operations, security, billing, and ARVL services, we determine how information is used. When we handle a participating business’s guest or team information on its behalf, our role is governed by our agreement with that business and applicable law. This policy does not grant a business permission to use guest information for unrelated purposes or replace any required data-processing agreement. Third-party websites, banks, payment providers, and Google have their own notices governing their independent services.
2. Information we collect
Information you provide includes your name, email address, telephone number, reservation name, delivery address, property management company or hotel, destination, estimated arrival date and time, property-access and delivery instructions, grocery selections, substitution preferences, gratuity selection, dietary notes you choose to provide, and messages or support requests. Saved grocery lists, order changes, delivery records, receipts, invoices, refunds, and communications may be associated with your order or account.
For businesses, team members, shoppers, and partners, we collect account and profile information, business names and contact details, team roles and permissions, destinations and coverage, assignments, business preferences, referral attribution, subscription information, purchasing-card records where applicable, and payment or payout status. Payment and identity-verification providers may collect additional information, including bank, tax, identity, or card information, directly under their own policies. ARVL may receive verification results, account identifiers, and the information necessary to administer the corresponding service.
Payment information is submitted through payment-provider tools such as Stripe. Our platform uses payment-method and transaction identifiers, payment status, card-brand or last-digit information where available, and billing records to administer transactions. Do not send full payment-card numbers, security codes, passwords, or identity documents in grocery instructions or ordinary support messages.
Technical information may include IP address, browser and device characteristics, approximate location derived from IP address, pages viewed, referring pages, timestamps, cookie or similar identifiers, interactions with pages, and diagnostic information. We also receive information from participating businesses, assigned shoppers, property contacts, referral partners, and service providers when needed to operate and support the service. We do not need continuous precise device location to provide the Google Calendar integration.
Property-access codes and dietary notes can be sensitive. Provide only information needed for fulfillment, avoid medical records or unrelated details, and tell us when access instructions should be replaced. Account holders are responsible for obtaining authority before providing information about another person.
3. How we use information
We use information to accept and fulfill orders; shop and coordinate substitutions; arrange property access and delivery; communicate confirmations, changes, invoices, and support responses; process authorized charges and refunds; administer subscriptions, payouts, commissions, purchasing cards, and referral attribution; and maintain business and shopper accounts and permissions.
We also use relevant information to investigate problems, detect fraud and misuse, protect accounts and property, maintain records, comply with legal obligations, resolve disputes, and evaluate and improve our services. We may send business or partner information and marketing communications where permitted. Marketing recipients can unsubscribe; necessary transactional and security messages are separate. Information obtained through Google APIs is subject to the narrower purposes and restrictions in Section 6, even if another provision of this policy describes a broader use of other information.
Where applicable law requires a legal basis, we process information as necessary to provide requested services or perform a contract, comply with legal obligations, pursue legitimate interests such as security and support subject to applicable balancing requirements, or act on consent where required. Withdrawing consent does not make prior lawful processing unlawful, and some services may no longer be available without the necessary information.
4. When we disclose information
Order fulfillment: we disclose relevant order and delivery information to the business selling or fulfilling your order, authorized administrators, assigned shoppers, and property or hospitality contacts involved in access or delivery. Information is shared according to the operational role and available permissions. A property contact may receive the information necessary to coordinate an arrival without needing your payment credentials. Referral partners may receive attribution, commission, and related order reporting needed to administer their program.
Service providers: we use providers for hosting and infrastructure, databases and authentication, payment processing, transactional email, SMS and push delivery, error monitoring, analytics, and business support. Examples used by our platform include Vercel, Supabase, Stripe, Postmark, Twilio, Sentry, Google, and Yandex, depending on the feature and configuration. Providers receive information needed for their functions. Payment providers may also process information independently for fraud prevention, verification, regulatory obligations, and their own payment services.
Legal and safety purposes: we may disclose information when required by law or valid legal process, or when reasonably necessary and legally permitted to investigate fraud, protect rights and safety, or address a security incident. Business transactions: information may be involved in a merger, financing, acquisition, or transfer of business assets, subject to applicable law and confidentiality protections. Information obtained through Google APIs is governed by the specific transfer restrictions in Section 6, which take precedence over these general provisions.
We may also disclose information at your direction or with the consent required by law. Publicly posted content or information you send directly to an independent recipient is subject to that recipient’s handling. We do not sell Google user data or disclose it for advertising. The analytics practices for ordinary website browsing are described separately below.
5. Cookies, website analytics, and communications
Cookies, local storage, and similar technologies help maintain sign-in sessions, shopping lists, preferences, referral attribution, and security. Where configured, we use Google Analytics and Yandex Metrica to understand website traffic and interactions. Yandex Metrica features can include click maps, link tracking, and session-replay technology on eligible public pages. These technologies may collect browsing and device information and transmit it to the analytics provider. Google Calendar credentials and API responses are handled by our server integration and are not provided to website analytics.
You can manage cookies and storage through your browser, use available provider controls, and restrict analytics through browser settings or blocking tools. Blocking essential storage may interfere with sign-in, saved lists, checkout, or referral attribution. Where consent is legally required for a technology, that requirement applies regardless of this policy. A privacy notice alone does not substitute for required consent. Contact hello@getarvl.com with a question or a request concerning tracking or an applicable opt-out right.
For marketing emails, use the unsubscribe link or contact us. Manage push notifications through your device or browser and available account preferences. Reply STOP to stop the ARVL SMS program, including its transactional and operational texts. Carrier message and data rates may apply. We can use other available channels for communications needed to administer an order, billing, account security, or a legal obligation.
On getarvl.com and www.getarvl.com, optional Google Analytics and Yandex Metrica scripts are blocked until you accept analytics cookies. Rejecting optional cookies leaves essential website functions available. Use Cookie Preferences in the footer to review, accept, reject, or change your analytics choice. This control does not enable advertising cookies or personalized advertising. Your choice is stored in this browser for up to 180 days on the website where you made it; if storage is unavailable, the choice may last only for the current page. Withdrawing analytics consent clears accessible analytics storage and reloads the page to stop previously loaded analytics scripts. Cookie consent controls on other ARVL-powered domains may differ.
6. Google Calendar and Google user data
Optional connection and permissions. An authorized manager of a participating independent business may connect a Google account to synchronize that business’s eligible orders with a calendar the manager can edit. The integration requests https://www.googleapis.com/auth/calendar.calendarlist.readonly to list calendars and inspect calendar identifiers, names, and access permissions, and https://www.googleapis.com/auth/calendar.events to create, update, and delete calendar events. The calendar-event permission permits access to events on accessible calendars; ARVL uses it for ARVL order-event synchronization and does not import unrelated personal events, scan your calendar for advertising, or build a profile of unrelated activities. We do not request Gmail, Google Drive, or Google Contacts access for this integration.
Data accessed and stored. Google provides OAuth authorization data and access and refresh credentials. ARVL accesses calendar-list information, including calendar identifiers, display names, primary-calendar status, and edit permissions, to let you select a writable calendar and check continued access. We save the selected calendar identifier and name, an encrypted refresh credential, connection and synchronization metadata, and mappings between ARVL orders and Google event identifiers, including a fingerprint used to avoid duplicate updates. Calendar-list choices and short-lived access credentials are used during the connection or synchronization process. A calendar identifier may contain an email address. We do not request a separate Google profile or email scope for this feature.
Use of Google data. We use these Google credentials and calendar data only to connect the account, show and validate available calendars, maintain your authorized connection, and create, update, or remove ARVL order events in the selected calendar. We use limited connection metadata to display synchronization status, prevent duplicate events, and diagnose connection failures. Connecting alone does not enable order export: you must select a calendar, enable automatic synchronization, and save the settings. The integration is one-way; editing a Google event does not edit an ARVL order.
Information sent to Google. Order events can include the reservation or guest name, order number, property address, delivery instructions you or the business provide, estimated arrival and event timing, assigned shopper name, order status, and an authenticated dashboard link. Free-text instructions may contain additional personal information supplied by you or the business. The current integration omits guest email, guest phone, grocery prices, and payment details. Events are created with private visibility and do not invite attendees. A shared calendar’s permissions, account administrators, or a user’s subsequent sharing may nevertheless allow others to access events; choose the calendar and its sharing settings carefully.
Sharing, transfer, and disclosure of Google user data. ARVL does not sell Google user data; use it for advertising, retargeting, creditworthiness, or unrelated marketing; or use it to develop, improve, or train generalized artificial intelligence or machine-learning models. Google receives the API requests and order-event information needed to perform your chosen synchronization. Our hosting and database infrastructure providers, currently Vercel and Supabase for this integration, process the credentials and metadata only as needed to operate and secure the integration on our behalf. Other transfers of Google API data are limited to those permitted by Google’s applicable user-data policies: with consent where necessary to provide or improve the user-facing integration; for security purposes such as investigating abuse; to comply with applicable law; or in a merger, acquisition, or asset sale after obtaining the explicit prior consent required by Google’s policies. The general business-transfer provision above does not override this restriction.
Human access. Personnel do not routinely read Google user data. Any human access is restricted to cases permitted by Google’s policies, such as your affirmative agreement to access specific data for support, a necessary security investigation, compliance with law, or data aggregated and anonymized for internal operations as permitted by those policies. We do not disclose Google credentials or API payloads to marketing, referral, or website-analytics providers. Google’s own handling of information in its services is governed by Google’s policies.
Data protection. Google API communications use HTTPS. Stored refresh credentials are encrypted using AES-256-GCM, with business-specific authenticated data; the encryption key is held in server-side configuration. Credentials are not returned to the browser. Integration database tables are restricted to service-side access, and management actions check the signed-in user’s business authority. OAuth authorization uses PKCE, an expiring state record, and a secure HTTP-only state cookie. Operational error reports use generic failure messages rather than Google credentials, authorization codes, or event payloads. These measures reduce risk but cannot guarantee that every system or recipient is immune from unauthorized access.
Retention. We retain the encrypted refresh credential while the business maintains its connection, including while synchronization is paused, so it can resume without reconnecting. Selected-calendar information and event mappings are retained as needed to operate and reconcile the integration, including subsequent authorized updates or reconnection. Access credentials are used during server requests rather than saved as persistent connection credentials. OAuth state is valid for ten minutes and consumed during the callback; expired state records may remain until cleanup. Connection history and event-link metadata are distinct from grocery-order and accounting records. They may remain after disconnect until no longer needed for reconnection, support, or permitted security purposes, or until you request their deletion. We do not retain Google data for unrelated future uses.
Disconnecting, revocation, and deletion. In the business dashboard, open Features → Google Calendar and select Disconnect. Disconnecting disables synchronization and removes the saved refresh credential, selected calendar identifier, and selected calendar name from the active connection record. Turning synchronization off without disconnecting keeps the connection credential. You can additionally revoke ARVL’s Google access through your Google Account’s third-party connections controls. Revoking in Google prevents further authorized API access but does not by itself delete ARVL’s retained integration records.
To request deletion of retained Google connection history, calendar/event mappings, and other Google integration data held by ARVL, email hello@getarvl.com with the business and connected-calendar information needed to identify the connection. Do not send credentials. We verify your authority and delete data that is no longer necessary, subject only to applicable legal requirements and Google’s permitted retention purposes; if an exception applies, we explain it. Residual backup copies may remain until the applicable backup cycle expires and are not used to resume synchronization without authorization. Deleting integration data does not automatically delete ordinary ARVL order, invoice, or payment records, which have separate purposes and retention obligations.
Events already created in Google Calendar remain after pausing, disconnecting, revoking access, or deleting ARVL’s integration records. You can delete those events directly in Google Calendar. If you want assistance removing them, contact us before revoking access; we cannot delete events from an account we can no longer access. Google controls retention of copies within its services. ARVL’s use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including the Limited Use requirements, and the applicable Google Workspace user-data policies.
7. Security and account protection
We use technical and organizational safeguards appropriate to the information and service, including encrypted network connections, authenticated access, role and business access controls, server-side handling of sensitive integration credentials, and operational monitoring. Payment-provider tools handle payment credentials. Access to sensitive information should be limited to persons and providers with a legitimate operational need. No internet transmission, storage system, email, property-access process, or third-party service is completely secure.
Keep your password, device, and account links secure. Do not share a team login or publish an order-management or saved-list link. Remove access for departing personnel and keep property codes current. Report suspected unauthorized access to hello@getarvl.com promptly. We assess incidents and provide notices when applicable law requires them.
8. Retention and deletion of other information
We retain personal information for as long as reasonably necessary for the purposes described here, taking account of active accounts and services, order fulfillment and support, refunds and payment disputes, tax and accounting requirements, fraud prevention, legal claims, contractual obligations, and applicable retention requirements. Different categories have different retention needs. Order and financial records may need to be retained after an account closes; property-access information should be kept only as needed for delivery, support, and any necessary investigation.
You may request account closure or deletion through hello@getarvl.com. We verify the request and your authority before acting. We delete or de-identify information when no longer needed, subject to lawful exceptions. A deletion request does not cancel an order, subscription, outstanding charge, or contractual obligation; those require their own cancellation process. Backup copies may remain until overwritten or expired under the relevant provider’s backup process. A business or third party that has independently received information may have its own retention obligations, and you may need to contact it directly. See Section 6 for the distinct Google-data controls.
9. Your choices and privacy rights
Depending on your location and the law that applies, you may have rights to know about and access personal information, receive a portable copy, correct inaccuracies, request deletion, withdraw consent, restrict or object to processing, or opt out of certain sales, sharing, targeted advertising, or qualifying automated decisions. These rights are subject to legal conditions and exceptions. We do not describe a right as unavailable solely because you contacted the wrong participating business; we will explain the appropriate recipient where possible.
Send requests to hello@getarvl.com, identifying the relevant account or order and the action requested. We may verify identity and, for a business or another person’s information, authority. Do not email payment credentials or identity documents unless we arrange a secure method. An authorized agent may make a request where permitted by law with appropriate proof of authority. We respond within the applicable legal period, explain any applicable refusal or exception, and describe any available appeal process. You may ask us to reconsider a decision and may contact the relevant privacy regulator where applicable. We do not unlawfully discriminate against you for exercising privacy rights.
For a participating business’s own guest records, contact that business as well; ARVL will assist as required by our role and applicable law. Essential processing needed for an order or payment may continue even if you opt out of marketing. Browser privacy settings and legally recognized opt-out signals have the effect required by applicable law; contact us if you need assistance exercising a relevant right.
10. Children and international processing
Our services are directed to adults and business users, not children under 13. We do not knowingly collect personal information from children under 13. Contact us if you believe a child has supplied information so we can investigate and take appropriate action. You must meet the age requirements stated in the applicable terms and any additional requirements for regulated products.
ARVL operates in the United States. Information may be processed by us and our providers in the United States and other locations where they operate, subject to applicable safeguards and law. Laws in those locations may differ from those in your home jurisdiction. This policy does not waive any mandatory rights or replace transfer safeguards required by applicable law.
11. Policy updates and contact
We may update this policy to reflect changes in our services, practices, or law. The date above identifies the current version. Where required, we provide additional notice or seek consent before implementing a materially different use. A policy update does not authorize a prohibited use of Google user data.
For privacy questions, Google-data deletion, account requests, or a security concern, contact ARVL, LLC at hello@getarvl.com. Include enough information to identify the relevant service and request, and avoid unnecessary sensitive information.