This Privacy Policy explains how RV Park Apps, LLC, doing business as RV Park Apps (Company, we, us, or our), collects, uses, shares, and protects personal information through RVParkApps.com, our guest web and mobile applications, administrative consoles, and related services (Platform). It applies to website visitors, park owners and managers, staff, guests, residents, and tenants.
RV Park Apps provides software to RV parks, campgrounds, resorts, and similar properties (Parks). Each Park may customize its portal and enable different features. The information processed depends on the features you use, what you provide, and your permissions. This Policy is a notice of our practices; reading it or using the Platform is not blanket consent to every type of processing. We request separate consent where law requires it.
1 Our role and the Park's role
We determine how information is used for our own account administration, billing, website inquiries, security, and business operations. Where relevant privacy law applies, we generally act as a controller for those activities.
For information a Park collects through its portal, including resident records, messages, requests, bookings, and documents, the Park generally determines the purpose and we process information on its instructions as a processor or service provider. Actual roles depend on the activity and applicable agreements; shared account features may involve processing for our own purposes as well.
A Park's own privacy notice explains its independent practices. We do not give a Park unrestricted access to information associated with unrelated Parks. Selecting a Park may establish a membership or preference, but does not by itself authorize every disclosure of your profile. Information shared with a Park depends on the feature, its disclosed purpose, and your relationship with that Park.
2 Information you provide
Account and profile information may include your name, email, phone number, account identifiers, authentication information, preferred Park, membership, role, site or unit information, and notification preferences. Park administrators may provide organization details, property addresses, staff invitations, branding, and billing contacts.
Content and communications may include uploaded documents, images, notices, forms, event details, messages, support requests, questions to Parkie, speech transcripts, and related metadata. When enabled, bookings, check-ins, RSVPs, and agenda features may process event participation, dates, guest details, and confirmation information.
Website inquiries and demonstration requests may include contact details and information about your business or needs. Provide only information necessary for the request. Do not upload passwords, payment-card details, government identifiers, health records, or other sensitive information unless an expressly supported feature requires it and provides appropriate notice.
If you submit another person's information, such as a resident list or emergency contact, you must have the authority and permissions required by law. The fact that a manager uploads information does not remove the affected person's privacy rights.
3 Information collected automatically and from others
The Platform may collect IP addresses, browser and operating-system details, device type, timestamps, referring pages, session identifiers, and error or diagnostic logs. Native apps may use push tokens or similar identifiers to deliver notifications. These identifiers and activity records can constitute personal information even when they do not include your name.
We collect basic engagement events such as section views, document opens, event interactions, search-feature usage counts, and notification engagement. Park managers receive aggregated engagement reports rather than individual browsing histories. Individual RSVPs, bookings, requests, and message delivery records may remain visible to authorized staff for operational purposes. Raw Parkie questions and answers are not recorded in engagement analytics.
Legal and implementation review: Confirm the event inventory and aggregation controls, including protection against identifying individuals in small groups.
We may receive information from Parks that invite or register users, authentication services you choose, payment processors, messaging providers, and integrations you authorize. Examples include membership details, payment status, delivery receipts, and booking confirmations. We do not receive every record held by an external provider merely because you follow a link.
4 How we use information
We use information to create and authenticate accounts; enforce roles and Park access; save drafts and settings; publish approved Park content; provide documents, events, requests, and enabled booking features; deliver messages; and respond to support requests.
We also use relevant information to process subscriptions, reconcile payments, prevent fraud and abuse, troubleshoot errors, measure engagement, improve usability, maintain security, comply with law, and resolve disputes. Marketing communications are sent subject to applicable permissions and unsubscribe choices.
We may create aggregated or de-identified reports that do not reasonably identify a person and maintain appropriate safeguards against re-identification. Information is not treated as anonymous merely because a name has been removed. We do not use a Park's private records to market another Park's services.
5 Parkie AI and speech input
If you use Parkie, we may process your question, conversation context, relevant authorized Park content, and information from your own profile needed for the request. If you use speech input, audio may be sent to a transcription service and converted into text. Your text or transcript and relevant retrieved passages may be sent to an AI provider to generate an answer or draft.
Parkie should receive only information you are permitted to access and that is relevant to the request. It is not intended to expose private data from another Park or another person's profile. Provider processing is subject to the arrangements and disclosures identified below. Responses can be inaccurate; confirm important details with the source or Park.
We send AI and speech providers only the audio, request text, relevant conversation context, and authorized content necessary to transcribe a request or generate a response. We do not retain voice recordings in our own storage after transcription. Provider processing and retention may differ from our own. Authorized Company staff may review conversations only when necessary for support, security, or troubleshooting, subject to access controls and logging.
Legal and implementation review: Provider names, processing countries, logging, retention, and contract terms remain unconfirmed. Add their actual details before publication; confirm speech processing does not persist audio in logs or temporary storage beyond necessary processing.
We do not use private Park documents, personal profiles, speech inputs, or Parkie conversations to train general-purpose AI models, and we require AI and speech providers to process this information under arrangements consistent with that restriction.
Legal and implementation review: Confirm provider settings and agreements support this promise. No-training does not mean zero provider retention.
Speech input converts spoken words into text; it does not create voiceprints or identify users through biometric characteristics. Microphone access is requested when needed, and users can use typed input instead.
Legal and implementation review: Verify transcription providers and the released application do not create biometric identification.
6 Documents images and public visibility
Parks may upload documents and organize them for authorized search and retrieval, including by Parkie. Content visibility is determined by the Park and the feature's access settings. Publicly published rules, images, events, or directories may be visible without login; restricted documents and user records require appropriate authorization.
If a Park publishes a document containing personal information, that information may be accessible to the intended audience and, for public pages, search engines or people who copy it. Managers should remove unnecessary personal information and verify permissions before publication. Contact the Park and us promptly if you believe content was exposed improperly.
Uploaded photographs may show people or contain embedded metadata. We remove embedded GPS and unnecessary EXIF metadata from images made available through the Platform, including displayed images and thumbnails. Uploading an image does not automatically authorize Company to use it for external advertising or social media. A Park must obtain appropriate permissions for its own promotional use.
Legal and implementation review: Verify metadata removal before files become accessible, including downloadable originals and transformed copies. Do not promise removal of all metadata from every document format.
7 Device permissions and location
The Platform may request microphone, camera, photo or file access, and notification permissions to provide a feature you choose. You can manage permissions through device or browser settings. Denial may limit the related feature while other functions remain available.
We may infer a general geographic area from an IP address. Displaying a Park's address or map does not require tracking your precise device location.
The MVP does not collect precise device GPS, background location, geofencing data, or device location history. Park addresses and maps are displayed without tracking a guest's location. General location inferred from an IP address may still be processed as described above.
Legal and implementation review: Confirm every app, SDK, map integration, weather feature, and server log follows this practice. Add a specific disclosure and permission flow before enabling location features.
8 Payments and SaaS onboarding
An authorized Park purchaser enters payment details through a payment processor's hosted payment interface. Company systems do not receive or store full payment-card numbers or card security codes. We receive billing contact information, transaction references, subscription status, invoices, and limited payment-method details needed to administer subscriptions.
Legal and implementation review: Payment processor name remains unconfirmed. Identify the selected processor and verify hosted-checkout integration, webhook payloads, support tools, and logs.
Creating a Park account and completing setup do not themselves authorize a charge. Saved setup information and drafts are retained if the manager does not publish or pay, subject to Section 13 and applicable deletion rights. Payment and publication status may determine guest access but do not authorize unrelated use of personal information.
A manual branded-app submission request may include Park branding, store descriptions, support contacts, and authorized developer-account details. Store operators process information under their own policies. Avoid uploading account passwords through general forms.
9 Who receives information
Authorized Park staff may receive relevant membership, request, reservation, event, document, and communication information to serve their community. Segmenting notices may use membership, site, stay, or other disclosed criteria. Private information is not made available to unrelated Parks simply because they use the same Platform.
Service providers may process information to supply hosting, databases, storage, authentication, payments, email, SMS, push delivery, AI, speech transcription, analytics, monitoring, and support. We select providers and apply appropriate restrictions for their role. Some providers, such as independent payment or store operators, also process information for their own legal or operational purposes.
We maintain information about the service providers that process personal information on our behalf, their functions, and relevant processing locations. This information is available by contacting legal@rvparkapps.com. Providers are authorized to process private Park and user information only for the agreed service purposes and applicable legal obligations.
Legal and implementation review: Finalize the actual provider inventory, privacy links, countries, and processing agreements. Confirm whether applicable law or customer agreements require a published subprocessor list or change notices.
10 Cookies analytics advertising and SMS privacy
We use essential cookies or similar storage for authentication, security, preferences, and session management, and limited analytics for performance and engagement. The MVP does not use advertising pixels, cross-site retargeting, or session-replay tools. Where analytics technologies require a choice or consent, we provide the applicable controls.
Legal and implementation review: Confirm tools, cookie lifetimes, provider retention, and consent controls. Inspect both the marketing website and guest/admin apps; do not assume first-party analytics is exempt from consent requirements.
We do not sell personal information, share it for cross-context behavioral advertising, or use it for targeted advertising. Parks may display static sponsored listings without tracking users across unrelated websites. External links lead to services governed by their own privacy practices.
Legal and implementation review: Verify pixels, SDKs, data flows, provider contracts, and any applicable reporting period before publication.
A Park's sponsored listing does not necessarily involve cross-site advertising. Following an advertiser's link takes you to a service with its own practices. We do not label device identifiers or browsing histories as nonpersonal simply because an advertising provider does not receive a name.
Mobile numbers, SMS opt-in records, and messaging consent are not sold or shared with third parties or affiliates for their own marketing or promotional purposes. They may be processed by providers to deliver and support the messaging program or disclosed as required by law. We retain consent and opt-out evidence to administer the program and honor messaging choices.
11 Messages and communication choices
You can manage available notification preferences in your account or device settings. Push tokens, recipient details, message content, audience selection, timestamps, and delivery records may be processed to send and administer notices. Parks are responsible for their messages and lawful recipient selection.
Use the unsubscribe link in marketing emails. For SMS, follow the sender's instructions, including STOP to opt out and HELP for assistance where supported. Message frequency varies and carrier message and data rates may apply. Each messaging program must identify its sender and purpose; opting out of one Park's program does not necessarily opt you out of every separately authorized program.
Withdrawing marketing consent does not prevent necessary account, security, or billing notices through lawful available channels. SMS opt-outs must still be honored under applicable law. Delivery is not guaranteed, and the Platform is not an emergency notification service.
12 Security and authorized administrative access
We use reasonable administrative, technical, and organizational safeguards, including controls that separate Park data and restrict access by role. Superuser access requires multifactor authentication. No system or transmission method can be guaranteed completely secure.
Legal and implementation review: Validate tenant isolation, role controls, multifactor authentication, and supporting operational procedures before representing them as implemented.
Authorized Company staff may access information or impersonate an account only for legitimate support, troubleshooting, security, or administration. Impersonation requires a recorded reason, displays an impersonation banner to the staff member, and is logged with the acting staff identity, target account, and relevant activity. Park managers have access according to assigned roles.
Legal and implementation review: Confirm audit coverage, session limits, log access, and restrictions on sensitive actions. The banner does not mean the end user is notified of each support session.
Protect your credentials. We will provide breach notifications where required by applicable law and contractual obligations. A Park's own mishandling of information does not remove any obligations we have for our own conduct.
13 Retention account closure and deletion
We retain information as needed for the purposes described, applicable service instructions, and legal obligations. Criteria include account status, the type and sensitivity of information, necessity for service delivery, security and fraud prevention, dispute resolution, and applicable recordkeeping requirements.
We do not delete saved Park data solely because setup was abandoned, payment was not completed, or a subscription lapsed. This business retention practice does not override a valid individual deletion request or authorize indefinite personal-information retention. Closing a subscription, unpublishing a Park, deleting an individual account, and deleting a Park workspace are different actions.
Park content, branding, and documents remain saved through draft, unpaid, and canceled states until an authorized deletion request or another lawful basis for removal applies. We periodically review dormant workspaces without deleting them solely for nonpayment. Parkie conversation history is retained for 30 days by default, with a clear-history option; content deliberately saved into the CMS follows the Park-content rules. We do not retain voice recordings in our own storage after transcription. Raw engagement events are retained for 90 days, after which appropriately de-identified summaries may remain. Security and impersonation logs are retained for 12 months and exclude unnecessary message or document content. Profiles, operational messages, RSVPs, and requests are retained while needed for the account or Park operations, subject to valid deletion requests and applicable recordkeeping needs. Billing records and SMS consent evidence are retained for applicable accounting, legal, dispute, and messaging-program purposes.
Provider retention is addressed separately.
Legal and implementation review: The 30-day, 90-day, and 12-month periods are proposed defaults, not confirmed implementation or legal minimums. Approve and implement them; set post-stay/account-closure criteria for personal records and specific billing/SMS evidence schedules with counsel and the accountant. Check provider retention and any legal holds.
Backups use a rolling 30-day retention window. Deleted information may remain in protected backups until that window expires or in restricted records required for lawful purposes. We track deletions and reapply them if a backup is restored, so deleted personal information is not reactivated in ordinary use. Retained information is restricted to its permitted purpose.
Legal and implementation review: The 30-day backup window is proposed. Confirm every database, object-storage copy, disaster-recovery backup, deletion queue, and provider supports this schedule; document justified exceptions.
Uninstalling an app does not itself delete hosted data or cancel a Park subscription. You can request deletion through the account controls where available or legal@rvparkapps.com. Content already published or copied by independent recipients may require contacting them separately; we remain responsible for requests concerning information we control.
14 Privacy rights and requests
Depending on your location, applicable law, and our role, you may have rights to access or confirm processing, obtain a copy, correct information, request deletion, or restrict or object to processing. You may also have rights to portability, withdraw consent, and opt out of sale, qualifying sharing, targeted advertising, or certain profiling with legal or similarly significant effects.
Submit a request to legal@rvparkapps.com. We may verify your identity using proportionate information and, where permitted, the authority of an agent acting for you. Do not send sensitive identity documents unless requested through an appropriate secure channel. We will respond within applicable statutory timeframes and explain any permitted refusal or extension.
For records a Park controls, we may coordinate with or direct you to that Park and assist it under our processing agreement. We still address requests relating to our own processing. We do not discriminate unlawfully against people for exercising privacy rights.
Where applicable law provides an appeal right, appeal a decision through legal@rvparkapps.com. We explain the outcome and available regulator complaint routes. We honor applicable opt-out rights and recognized universal opt-out signals, including Global Privacy Control where required. Our MVP does not engage in sale, cross-context behavioral advertising, or targeted advertising.
Legal and implementation review: Confirm signal handling and any required links or procedures against actual tracking and applicable laws.
Additional state-specific privacy disclosures and procedures apply where required by law. We provide the applicable information about data categories, purposes, recipients, retention, and available rights for our actual processing activities.
Legal and implementation review: Counsel must assess applicable state laws and supply any necessary supplemental notices before publication. This general paragraph does not substitute for required disclosures.
15 International processing and legal bases
We select US hosting for the Platform's primary application data. Service providers may process information in other countries under their applicable service arrangements. Where law requires safeguards for international transfers, we use the applicable lawful mechanism and provide relevant information on request.
Legal and implementation review: Confirm hosting and all provider countries, transfer mechanisms, and any required representatives. US primary hosting does not guarantee US-only processing.
Where European or UK data protection law applies and we act as controller, relevant legal bases may include performance of a contract for account and service administration; legal obligations for necessary records; legitimate interests for proportionate security, support, and improvement; and consent for processing that requires it. Each basis must correspond to the actual activity. Withdrawing consent does not affect earlier lawful processing.
Where we process on a Park's behalf, the Park identifies its lawful basis and our agreement defines its instructions. You may complain to your competent data protection authority. Contact legal@rvparkapps.com for details of our relevant legal bases, transfer safeguards, or required representative.
16 Children and sensitive information
The Platform is intended for Park managers and community users and is not directed to children under 13. We do not knowingly collect personal information directly from children under 13 without a legally permitted process. If you believe a child has supplied information contrary to this policy, contact us so we can investigate and take required action.
Parks should not upload unnecessary information about children. Where a Park must process family or child information, it is responsible for an appropriate legal basis and notices, and our role remains subject to the applicable processing agreement. Other age-related protections apply where required by law.
The MVP does not support biometric identification or automated decisions about leases, eligibility, or access with legal or similarly significant effects. Parkie assists with search and content drafting: authorized managers review generated content before publication or sending. Users and Parks should not submit unnecessary sensitive information.
Legal and implementation review: Verify actual workflows and providers. Add appropriate disclosures, permissions, and review before introducing sensitive processing or consequential automated decisions.
17 External services and changes
Booking engines, social networks, stores, local businesses, and other external services you choose have their own privacy practices. This Policy covers our processing, including our providers' processing on our behalf; it does not describe every independent action of a Park or external company.
We may update this Policy and show a revised effective date. Material changes will be communicated by a reasonable notice, and separate consent will be requested where required. A change does not retroactively authorize a materially different use of previously collected information contrary to applicable law.
18 Contact information
Legal operator: RV Park Apps, LLC Business name: RV Park Apps Website: https://RVParkApps.com Privacy requests and legal notices: legal@rvparkapps.com Support and billing: support@rvparkapps.com Support hours: 8:00 a.m. to 5:00 p.m., Monday through Friday, Eastern Standard Time (EST) Mailing address: 16908 Sanglier Drive, Austin, Texas 78738 Telephone: +1 818.660.5347