Privacy policy

RV Park Apps (RVParkApps.com) provides an app that RV parks use to share information with guests and residents. Client to confirm: legal entity name, registered address and governing jurisdiction.

Each park decides what it publishes and who its members are. The parks and RV Park Apps both handle the information described here. Client to confirm: how responsibility is split between RV Park Apps and each park.

• Account details: your email address and the name you enter. Park staff accounts may also have a username and a password, which is stored only as a secure hash.
• Park memberships: which parks you belong to, your role (for example guest, resident or staff), membership status and dates, and stay details a park records.
• Sign-in records: active sign-ins (stored as unreadable hashes, with your device's browser type), and one-time sign-in links.
• Messages and discussion: which park notices were sent to you and whether you opened them, your message settings, discussion posts and replies you write, reports you file, and private group memberships.
• Events: events you save to My Agenda and your RSVPs.
• Parkie questions: the text of questions you ask Parkie is sent to our AI service provider to produce an answer. We don't store the question with your name. When Parkie can't answer, we keep a short topic label with emails, phone numbers and other numbers removed, plus a count, so the park can fill gaps. A name typed directly into a question may remain in the label.
• Usage statistics: page views, searches, notice opens, saves and RSVPs, counted so parks can see what is useful. Views and searches are linked to an anonymous key, not to your name or email. Staff and test accounts are not counted.
• Park content: pages, documents, images, maps, events and notices published by park staff.
• Security and audit records: sign-ins, access denials and administrative actions, kept so misuse can be investigated.

The app doesn't use your location, contacts or photos. The microphone is used only when park staff tap the dictation button, and only for that recording.

We use it to sign you in, show you the right park content, deliver park notices, run events and discussion, answer Parkie questions, help parks improve their information, and keep the service secure. We don't sell personal information or use it for advertising.

• The park: staff at a park you belong to can see your name, email, role and membership details for that park. Other parks cannot.
• Service providers who run the app for us: hosting and database, an AI service for Parkie answers, and an email provider for sign-in links once email sending is enabled. Client to confirm: the final list of providers and where they process data.
• When the law requires it.

Connections are encrypted (HTTPS). Sign-in tokens and links are stored only as hashes, and staff passwords as secure hashes. Each park's data is kept separate and checked on the server for every request. Platform administrators need a second verification step to sign in. No system is perfectly secure.

Account and membership details are kept while your account exists. Sign-in links expire after 15 minutes, and sign-ins expire automatically. Security and audit records are kept to protect the service. Client to confirm: specific retention periods for audit records, usage statistics and Parkie topics.

You can delete your account yourself: sign in, open Account in any park, and choose Delete my account. This immediately:

• removes your name, email and sign-in details, and signs you out on every device
• ends your memberships in every park and removes stay details
• removes your saved agenda, RSVPs, private group memberships and message settings

Discussion posts you wrote, content you published as staff, and security and audit records are kept but no longer show your name; they appear as "Deleted user". Client to confirm: whether discussion posts should be deleted rather than kept anonymously.

Help is on the support page.

Client to confirm: minimum age for accounts and any policy for children's data.

Privacy contact: Client to confirm: privacy contact email and postal address. If this policy changes, we'll update this page.

Last updated: draft, not yet effective.