RigRez
Privacy policy
Last updated November 15, 2026
RigRez is a reservation and park-management system for RV parks, run by AMDG Management. This page explains what information RigRez holds, why, and what you can ask us to do with it. Each park is responsible for the information about its own guests, residents and staff; RigRez stores and processes it for them.
What we hold
- Guests and residents: name, email address, phone number, address when given, vehicle and stay details, reservations, the account balance and payment history for your stays or tenancy, and messages you exchange with the park.
- Park staff: name, work email address, which parks you work at, what you are allowed to do, and a record of the changes you make.
- Technical records: sign-in records and basic request logs used to keep the service secure and working.
Payments
Card and bank payments are handled by Stripe. Your full card or bank details go to Stripe and are never stored by RigRez; we keep the amount, the date, the last four digits and the card or bank type so the park can show your receipts and balance. Stripe's use of your information is covered by Stripe's own privacy policy.
Email and text messages
The park uses RigRez to send booking confirmations, receipts, reminders and replies by email, and by text message where you have given a mobile number. Messages are sent through our email and text message providers only to deliver them. Reply STOP to a text message to stop texts.
Signing in with Google
Park staff can sign in with their park's Google Workspace account. RigRez asks Google only for your basic profile (name, email address and profile picture), uses it only to sign you in, and does not read your email, files or contacts.
Connected accounting
A park owner can connect the park's own QuickBooks Online or Xero account so RigRez can keep the park's books up to date. Only an owner can connect it, and it is off until they do. RigRez reads the account list (each account's name, number or code, type and whether it is active) and the company or organisation name. In Xero it also reads the journals RigRez has already sent, so it never sends the same day twice; if one sign-in reaches several organisations, it reads each one's account list while the owner chooses.
RigRez writes one summary journal entry a day: the park's totals by account, such as charges, taxes, payments, deposits, card fees and payouts, plus any corrections to days already sent. The entry carries the park's name, the date and RigRez's own line names (charge types, taxes and discounts). RigRez adds no guest name or contact details; guest detail stays in RigRez. For a connected park, RigRez reads the park's balance activity (processing fees and payouts) from Stripe, and posts it to the books only after the owner confirms no other app already does.
RigRez never receives the QuickBooks or Xero password. The sign-in QuickBooks or Xero gives RigRez is stored only on our servers, encrypted with a key kept apart from the database, and is never shown to staff. The owner can disconnect at any time from Settings › Accounting. Disconnecting deletes that sign-in and asks QuickBooks or Xero to remove RigRez's access (in Xero, unless another of the owner's parks still posts to the same organisation). If the owner removes RigRez from inside QuickBooks or Xero instead, RigRez stops posting and marks the connection as needing to be reconnected; the stored sign-in, which no longer works, is deleted when the owner disconnects in Settings › Accounting. The park keeps its account list, which account each line uses, and its record of the days already sent, so its history stays accurate; entries already in the books are the park's and stay there.
If an owner asks RigRez to suggest which account each line should use, RigRez sends the account names, numbers and types and RigRez's line names to our AI provider, Anthropic, to make the suggestions; RigRez adds nothing about guests. Otherwise accounting data is used only to keep the park's own books. It is not sold, not shared with anyone else, and not used for advertising.
How we use it
Only to run your reservation or tenancy: taking bookings and payments, keeping the park's accounts, contacting you about your stay, and keeping the service secure. We do not sell your information. The one advertising use is the measurement described under “Measuring the park's ads”, which you can turn off.
Measuring the park's ads
Some parks advertise on Google. When you reach a park's booking page from one of its Google ads, the link carries a click code from Google, and RigRez keeps it with your booking. When you book and pay online, RigRez tells the park's Google Ads account about the booking, with its value and time and any click code, so the park can see which ads bring bookings.
So that Google can match a booking when the click code is missing (for example, you clicked the ad on your phone and booked on a computer), RigRez also sends your email address and phone number in scrambled (hashed) form. Hashing turns them into codes that can't be turned back into the originals; Google only compares them with codes it already has. RigRez sends them with every online booking, whether or not you clicked an ad, because it can't always tell. These uploads don't include your name, street address or card details.
The booking pages, other than the payment page, also load Google's advertising tag. It tells Google you visited, including the page's address, which holds any dates and party size you searched for. On the confirmation page it also reports the booking's value and reference, with your hashed email and phone if the park sends them. Google can use these visits to build audiences the park can advertise to. Where the booking page asks you first, the tag sets no advertising cookies until you agree. It doesn't load at all if you've turned sharing off or your browser sends Global Privacy Control.
The Google Ads account belongs to the park. Google's use of this information is covered by Google's privacy policy.
You can turn this off on Your privacy choices. If your browser sends a Global Privacy Control signal, RigRez treats it as turned off. Turned off, nothing about your booking is sent to Google.
Where you came from
So the park can see which links bring bookings, RigRez notes how you reached the booking page: the website that linked to it (for example, the park's website or a search engine) and any campaign tags in the link. It keeps this with your booking for the park's own reports and doesn't send it to anyone. Turning off sharing on Your privacy choices or sending Global Privacy Control turns this off too, and where the park's ads ask first, nothing is noted until you agree.
Cookies
The booking pages use a few cookies of their own: one that holds your site while you pay, one that remembers your privacy choice, one that keeps a Google ad's click code for up to 90 days when you arrive from an ad, and one that keeps how you reached the booking page, also for up to 90 days. None of them is shared with other websites. Google's tag may also set its own advertising cookies, unless sharing is off.
Who can see it
Staff of the park you stay at, limited to what their job needs, and the service providers that run RigRez for us (hosting and database, payments, email and text messages), each only to provide their service, and the park's Google Ads account as described above. We share information with others only when the law requires it.
How long we keep it
Reservation, payment and account records are kept for as long as the park needs them for its accounts and the law (usually seven years). Messages are kept with your record for as long as the park keeps it. Technical logs are kept for shorter periods and then deleted.
Your choices
You can ask to see the information held about you, ask for it to be corrected, or ask for it to be deleted where the park does not need to keep it for its accounts or the law. Contact the park you stayed at, or email legal@rigrez.com.
Changes
If this policy changes, we will update this page and the date at the top.