Carmelevy, Inc. · Effective November 3, 2026 · Version 2026-11-03
Privacy Policy
We use account and property information to operate your concierge, Stripe to process subscriptions, and Voiceflow to power guest conversations. Property details are available to people with the guest link. Optional Google advertising measurement starts only after you allow it on our website.
1. Who this policy covers
This policy describes how Carmelevy, Inc. handles information through carmelevy.com, owner accounts, support, and guest concierge experiences. It applies to owners, guests, and website visitors. Hosts separately decide what property and guest information they give us and may have their own privacy obligations.
2. Information we collect
- Account and contact details: email address, authentication information, and any name, phone number, or address you provide in your profile.
- Property details: condo descriptions, location, Wi-Fi information, rules, amenities, arrival and departure instructions, recommendations, and other content an owner enters.
- Guest conversations: questions, answers, conversation identifiers, and information you choose to type into the concierge. Guests do not need a Carmelevy account.
- Billing records: Stripe customer, checkout, and subscription identifiers, subscription status, transaction information, and records of checkout agreement. Stripe collects payment details and billing addresses directly. Our site does not collect full card numbers or card security codes.
- Support and technical information: support messages, contact details, request references, IP addresses, browser or device information, timestamps, security logs, and records needed to operate and troubleshoot the service.
- Optional advertising measurement: ad click identifiers and website or successful signup events when you allow measurement cookies.
Please do not submit payment card details, passwords, identity documents, door access codes, medical information, or other sensitive personal information in property descriptions, chat messages, or support requests.
3. How we use information
We use information to authenticate accounts, save and serve property content, generate guest access, produce AI responses, process subscriptions, prevent abuse, respond to support and privacy requests, troubleshoot problems, maintain security, meet legal and accounting obligations, and, with your measurement choice, understand advertising results. We do not use agreement to our Terms as a marketing email opt-in.
4. How information is shared
- Guests and hosts: guest-facing property details can be seen by anyone holding that property's link or QR code. Do not treat a link as proof of a guest's identity. Authorized service administrators may access records for support, security, and operation.
- Service providers: Supabase supports authentication and property/account storage; Voiceflow and its AI processing providers handle concierge conversations and responses; Stripe handles payments, billing, and checkout consent; our hosting and email delivery providers handle website delivery and service messages. Providers receive information needed for their role and handle it under their applicable terms and privacy practices.
- Google: if you allow advertising measurement, Google receives measurement events and associated online identifiers. Our measurement integration excludes account email addresses, passwords, property content, private guest tokens, and authentication parameters from event payloads. Enhanced conversions using customer-provided identifiers and advertising personalization signals are disabled in this integration. Google may process technical information associated with requests to its services.
- Legal or business needs: we may disclose information when legally required, to protect people or the service, or in a business transfer subject to applicable safeguards and notice obligations.
Links to OpenTable, Uber, or other services take you to independently operated sites. Those providers collect information under their own policies when you use their services.
5. Cookies and local storage
We use browser storage for essential sign-in sessions and preferences such as language and cookie choice. On our marketing, contact and owner pages, optional Google advertising measurement is off until you select Allow measurement. You can decline without losing account or concierge functionality.
Use Cookie choices on the home, contact or owner page to change your preference. Declining later stops future measurement through our integration and removes its accessible Google measurement cookies where possible. It does not erase information already received by Google. Your choice is specific to your browser and device. Third-party checkout and chat services may use storage needed for their own functionality.
Our optional measurement integration does not enable personalized advertising or customer-list uploads. Browser Do Not Track signals do not change essential service operations; optional measurement follows your cookie choice. We do not sell customer lists or guest conversations. We do not represent that every provider's processing has the same legal classification in every jurisdiction. Contact us with any applicable sale, sharing, or targeted-advertising opt-out request.
6. Retention, security, and international processing
We retain information as needed to provide the service, maintain account and subscription records, handle support and disputes, comply with law, and protect security. Retention depends on the type of record, account status, legal requirements, and our providers' backup and log cycles. Subscription consent records may need to be retained after cancellation. We do not promise immediate deletion from every backup or provider system.
We use account authentication, access controls, and other safeguards appropriate to the service. No online service is completely secure. Information may be processed in the United States and other countries where our providers operate; privacy rules may differ from those in your location.
7. Your choices and privacy requests
Owners can view and update contact and property details in My account. You can request access, correction, deletion, an available copy, or other privacy rights applicable to your location by emailing help@carmelevy.com with the subject Privacy request. We may verify your identity and authority before fulfilling a request. We will respond within applicable legal time limits. Some records may be retained for legal, billing, security, or dispute reasons.
Guests can contact us about information submitted to the concierge and should contact their host about the host's property records. Where applicable, you may object to or restrict processing, withdraw consent prospectively, use an authorized agent, or complain to your local privacy regulator. We will not unlawfully discriminate against you for exercising privacy rights. Exact rights and exceptions depend on applicable law.
Deleting information or closing an account is separate from canceling billing. To prevent another charge, cancel your subscription through the cancellation instructions. If you ask us to close an account with an active subscription, tell us you also want billing canceled.
8. Children, policy updates, and contact
The service is not directed to children under 13. Owners must be at least 18. If you believe a child has provided personal information without appropriate authorization, contact us so we can investigate and take appropriate action.
We will update the date on this policy when practices change and provide additional notice or obtain consent when required for material changes. For privacy questions, contact Carmelevy, Inc. at help@carmelevy.com or use our support form.
Optional local weather
When an owner enables weather, we use the condo country and postal-code area to retrieve approximate forecasts from Zippopotam.us / GeoNames and MET Norway. Provider requests contain only the postal area or rounded area coordinates, not guest location, guest access tokens, contact details or the full condo address. Public forecast and postal-area data are cached server-side.
