LEGAL

Privacy Policy

Effective date: July 18, 2026

This Privacy Policy explains how RV Hoop ("we," "us," or "our") collects, uses, and shares personal information when you use our website and portals (the "Service"). It applies to park owners and managers ("Landlords"), residents ("Tenants"), and prospective guests and site visitors ("Guests"). By using the Service you agree to this Policy and to our Terms and Conditions.

1. Information we collect

Information you provide

• Account information. When a Landlord or Tenant signs in, we collect an email address or mobile phone number (used for one-time sign-in codes) and, optionally, a first and last name. We do not use or store passwords.
• Passkeys.If you enable biometric or device-PIN sign-in, we store the passkey's public key and related metadata (device type, last-used time). Your biometric data itself never leaves your device and is never sent to us.
• Reservation details. When you inquire about or reserve a lot, we collect your name, email address, phone number, party size, stay dates, and — optionally — your RV and vehicle license plate numbers.
• Inquiries and requests. Messages you send through inquiry forms and maintenance requests, which may include any details you choose to write.
• Lease and payment records. Lease terms (lot, dates, utilities, RV length), invoice amounts, due dates, and payment status. We record references to payments processed by Stripe, but card numbers and bank details are collected only by Stripe and never touch our servers.
• Signed documents. When you sign a lease electronically, your name and email address are shared with our e-signature system, which stores the signed document. The contents of lease documents are set by the Landlord and may include information beyond what this app itself collects.
• Photos and park content. Landlords may upload lot, amenity, and park map photos. These are property images, not personal photos, and public listings and shared park maps display them to visitors.

Information collected automatically

• Session cookie. Signed-in users receive one essential session cookie (valid for 7 days) that keeps you logged in. It is not used for advertising or analytics. See Section 5.
• Technical data. Like most web services, our servers receive your IP address and browser information with each request, and we keep standard server logs for security and troubleshooting. We do not run analytics or advertising trackers on the Service.

2. How we use information

• To operate the Service: sign-in, reservations, holds, leases, invoicing, maintenance tracking, and park maps.
• To send transactional messages: one-time sign-in codes, reservation links, signature requests, and payment notices.
• To process payments and subscriptions through Stripe.
• To prevent fraud and abuse (for example, rate-limiting and bot protection on public forms).
• To maintain, secure, and improve the Service, and to comply with legal obligations.

We do not sell personal information, and we do not use it for third-party advertising.

3. How information is shared

We share personal information only as needed to run the Service:

• With the park. Reservation, inquiry, lease, payment-status, and maintenance-request information is shared with the Landlord of the park involved — that is the point of the Service. Landlords are responsible for how they use and further handle that information.
• Stripe— payment processing. Receives your name, email, phone number, and payment details you enter on Stripe's pages.
• Auth0 — sign-in. Receives the email address or phone number you sign in with and delivers your one-time codes by email or SMS.
• Electronic signatures— processed on our own servers. Your agreement is generated, signed and stored by us; no third-party e-signature provider receives your data. We record the name you type, the time you sign, your IP address and your browser's user-agent string as evidence that the signature is yours.
• Brevo — transactional email delivery (for example, your reservation link). Receives your name and email address and the message content.
• Cloudflare R2— storage. Park and lot photos are held in a public bucket; documents and identity photos you upload (a driver's licence or licence-plate photo, where a park requires one) and your signed agreements are held in a private bucket, reachable only through short-lived links we issue to you and to that park's staff.
• Map providers. Park addresses are sent to Mapbox for geocoding during park setup, and map displays may load from Google Maps or OpenStreetMap, which receive standard request data (such as your IP address) when tiles load in your browser.
• Infrastructure providers that host our database, session store, and servers.
• Legal and safety. We may disclose information if required by law, to enforce our Terms, or to protect the rights, safety, or property of users, the public, or the Service.
• Business transfers. If we are involved in a merger, acquisition, or sale of assets, information may be transferred as part of that transaction.

4. Landlords and their tenants

For information about a park's tenants and guests — reservation details, lease documents, payment history, maintenance requests — the Landlord decides what is collected in its lease forms and how that information is used offline. We process that information on the Landlord's behalf to provide the Service. If you have questions about how a particular park uses your information, contact that park directly.

5. Cookies

We use a single first-party session cookie, which is strictly necessary to keep you signed in. It is HTTP-only (not readable by page scripts), expires after 7 days, and stores only a session identifier — your session data stays on our servers. We do not use analytics, advertising, or cross-site tracking cookies. Embedded third-party features — Stripe's checkout and embedded maps — may set their own cookies governed by those providers' policies. Because guests can complete a reservation without creating an account, reservation links sent by email act as your access credential — treat them like a key and do not forward them.

6. Data retention

We retain account, lease, reservation, and payment records for as long as needed to provide the Service and to meet legal, accounting, and dispute-resolution obligations, since these records document rental relationships and payments. Expired reservation holds that were never completed are voided automatically. If you would like information deleted, contact us (Section 9) — we will honor deletion requests except where we are required or permitted to retain records.

7. Security

We take reasonable measures to protect personal information: passwordless sign-in (no password database to breach), optional passkeys, HTTP-only session cookies, server-side sessions, role-restricted portals, rate-limiting on public forms, and payment processing handled entirely by Stripe so card data never reaches our servers. No system is perfectly secure, so we cannot guarantee absolute security; please protect access to the email account and phone number you use to sign in.

8. Your choices and rights

• You can view and update much of your information directly in the portals.
• You can request a copy of the personal information we hold about you, ask us to correct it, or ask us to delete it, subject to the retention needs described above. Depending on where you live, you may have additional rights under local privacy laws; we will honor valid requests as those laws require, and we will not discriminate against you for exercising them.
• Transactional messages (sign-in codes, reservation and payment notices) are required to use the Service and cannot be opted out of while your account or reservation is active.
• To exercise any of these rights, contact us using the details in Section 9.

9. Contact us

For privacy questions or requests, email hello@rvhoop.com.

10. Children

The Service is intended for adults and is not directed to children under 18. We do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact us and we will delete it.

11. Changes to this Policy

We may update this Policy from time to time. If we make material changes, we will update the effective date above and take reasonable steps to notify you, such as notice within the Service or by email. Your continued use of the Service after changes take effect means the updated Policy applies to you.