Data Sharing Agreement

This Data Sharing Agreement (“Agreement”) is entered into between Outdoor Hospitality Research, Inc., a Delaware corporation (“OHR Report”), and the operator identified at signup (“Operator”), and governs Operator’s authorization for OHR Report to access, receive, and use data from Operator’s Property Management System (“PMS”) in connection with the OHR Report Service. This Agreement supplements and is incorporated into the OHR Report Terms and Conditions and the OHR Report Privacy Policy.

OHR Report operates a benchmarking service for the outdoor hospitality industry. To generate a Park Profile, calculate KPIs, and construct comp set benchmarks for Operator’s park(s), OHR Report requires ongoing access to certain performance data from Operator’s PMS. This Agreement sets out what data OHR Report accesses, how it is used, and the commitments OHR Report makes in exchange for that access.

Operator authorizes OHR Report to connect to Operator’s PMS account via API using credentials or an API key reference provided by Operator, and to extract data on an ongoing, automated basis (currently daily) for as long as this Agreement remains in effect. Operator represents that it has the right to grant this authorization, including under the terms of its agreement with its PMS provider.

By connecting a PMS source directly and becoming an OHR Report customer under this Agreement, Operator consents to have its park’s identity (name and matched dimensions, as described in Section 6) visible to other identified operators within its comp set(s), on the same reciprocal basis those operators are visible to Operator. This is distinct from parks supplied to OHR Report only through an anonymized, platform-level PMS arrangement, whose identity is never disclosed because OHR Report never has an identifying relationship with them directly. Operator’s individual KPIs remain confidential regardless of this identity visibility, as described in Section 5 and Section 6.

Operator is responsible for ensuring that any data-sharing consent, attestation, or agreement required by its PMS provider before releasing API credentials to a third party has been separately satisfied. OHR Report will provide reasonable documentation about its data handling practices to support that process on request.

Data accessed under this Agreement includes, at the park level:

• Occupancy and availability data (available, occupied, maintenance, and allotted site nights);
• Earned accommodation revenue and rate data, at the booking and stay level, sufficient to calculate Occupancy Rate, ADR, and RevPAS;
• Stay duration and booking pattern data used to derive the Length-of-Stay Profile;
• Site and inventory configuration data (RV, lodging, and tent site counts and types) used to derive the Accommodation and Scale Profiles;
• Amenity and facility data, sourced from PMS metering fields and the operator onboarding questionnaire;
• Property location data (address or GPS coordinates) used for geographic enrichment and the Location Profile.

Consistent with the OHR Report Privacy Policy, OHR Report’s PMS integration is built to read only the operational fields listed above. OHR Report does not retain guest-level personal information — including guest names, contact details, and payment information, which a PMS typically also holds — even where such information may be transiently included in raw data returned by a PMS’s API. Any such information is discarded immediately upon receipt and is never stored, retained, or used for any purpose.

OHR Report will use data accessed under this Agreement solely to:

• Calculate Operator’s own park-level KPIs and Park Profile dimensions, and display them to Operator;
• Include Operator’s park, in de-identified and aggregated form, in peer comp set, regional comp set, and national market average benchmark calculations for other parks;
• Operate, maintain, and improve the Service, including comp set matching methodology;
• Fulfill obligations under any platform-level data sharing arrangement between OHR Report and Operator’s PMS provider, where applicable.

OHR Report will not sell Operator’s raw, park-identifiable performance data to third parties. Aggregated Data (defined below) may be used in de-identified, aggregate form for market research, published industry reports, and materials shared with investors or partners, provided that no such use discloses Operator’s individual park-level KPIs.

No operator, including Operator, is ever shown another park’s individual Occupancy Rate, ADR, or RevPAS. Benchmark values shown to any operator are always pre-aggregated across a qualifying comp set; the underlying performance data of each member is never disclosed on its own. Where comp set membership includes identified parks, Operator may see which named parks are included and which Park Profile dimensions they matched on, consistent with Section 6 below, but never their individual performance figures. Minimum pool sizes are enforced before any benchmark is displayed, so that the aggregate cannot be reduced to a single member’s figures by simple subtraction.

In addition to the commitments above, OHR Report’s benchmark methodology is built around the following safeguards, which OHR Report will maintain for as long as this Agreement is in effect:

• Minimum contributor floor.No comp set, regional, or national benchmark is displayed unless it is built from data contributed by at least five qualifying parks, subject to OHR Report’s ability to adjust that floor as its methodology evolves, provided the floor is never set below three.
• Banded disclosure of pool size. At grades where comp set membership is not individually identified to Operator (for example, when a comp set includes partner-supplied, anonymized parks), the number of parks underlying a benchmark is disclosed only as a range (for example, “5–10” or “10–20”), never as an exact count.
• Member identity is visible, but performance is not. Becoming an OHR Report customer means Operator’s park identity is visible to other identified operators within its comp set(s), including any dynamic comp set Operator builds itself, on a reciprocal basis — a park appears in another operator’s comp set only when that visibility runs both ways (see Section 2). Regardless of identity visibility, OHR Report never discloses any comp set member’s individual Occupancy Rate, ADR, RevPAS, or other performance figure to another operator; only the pre-aggregated comp set value is ever shown. Parks supplied to OHR Report only through an anonymized, platform-level PMS arrangement are not OHR Report customers, are never identified through this mechanism, and contribute to benchmarks in aggregate only.
• PMS partner boundary. PMS partners accessing benchmark data through the OHR Report Partner Benchmark API never receive comp set member identities, regardless of what an operator can see in the OHR Report product directly. Partner-facing benchmarks are capped at a broader comparison grade than the tightest grade available to operators, and disclose only banded pool sizes.
• Independent, automated construction. Comp set matching and benchmark aggregation run on a fixed, automated methodology applied uniformly to all parks, without manual or per-operator adjustment, and without input from any operator, investor, or PMS partner into how a specific comp set is constructed.
• Consistent access terms. Benchmark features are made available to similarly situated operators on the same published or quoted terms, regardless of which PMS platform an operator uses.

These safeguards describe how OHR Report’s methodology currently operates and are intended to reduce the risk that participation in OHR Report could be used, or perceived as being used, to facilitate coordination among competing operators. OHR Report may refine the specific mechanics of its methodology over time (for example, adjusting the minimum contributor floor as the dataset grows), provided the safeguards above continue to be honored in substance.

As between OHR Report and Operator, Operator retains all right, title, and interest in the raw data generated by its park’s operations (“Operator Data”). OHR Report owns the derived Park Profile dimensions, calculated KPIs as displayed within the Service, and all aggregated, de-identified benchmark and comp set output produced from the combined dataset of participating parks (“Aggregated Data”). Aggregated Data does not include, and cannot be reverse-engineered to reveal, any other individual operator’s park-level Operator Data.

OHR Report maintains administrative, technical, and physical safeguards designed to protect Operator Data, including credential storage via a dedicated secrets manager (PMS API keys are never stored directly in OHR Report’s application database), encryption in transit, and role-based access controls limiting internal access to Operator Data to personnel who need it to operate the Service. Further detail on OHR Report’s security practices is available at ohrreport.com/security.

OHR Report is hosted on Google Cloud infrastructure located in the United States, and uses other third-party service providers to operate the Service. OHR Report remains responsible for Operator Data handled by its sub-processors under the terms of this Agreement. A current list of sub-processors is maintained at ohrreport.com/legal/subprocessors.

Consistent with the Privacy Policy, OHR Report retains Operator Data for as long as Operator’s account is active or as needed to provide the Service, and afterward for as long as needed for legitimate business or legal purposes. Upon termination of Operator’s account, OHR Report will cease active syncing of new data from Operator’s PMS. On written request to privacy@ohrreport.com, OHR Report will delete or de-identify Operator’s park-identifiable historical data from its operational systems, except that: (a) Aggregated Data already incorporated into comp set benchmarks as of the termination date may be retained in de-identified, aggregate form, and (b) OHR Report may retain data as required by law or for legitimate backup and audit purposes.

Operator is responsible for the accuracy of data entered into its PMS. OHR Report does not independently verify PMS-sourced data beyond automated quality checks (for example, quarantine of parks with anomalous data patterns) and disclaims responsibility for benchmark inaccuracies caused by inaccurate source data.

This Agreement remains in effect for as long as Operator maintains an active PMS connection with OHR Report, and terminates automatically upon termination of Operator’s account under the Terms and Conditions, or upon either party’s written notice as provided in the Terms and Conditions. Sections 6, 7, 10, and 11 survive termination.

This Agreement is part of, and incorporated into, the OHR Report Terms and Conditions. Capitalized terms not defined here have the meaning given in the Terms and Conditions. This Agreement is governed by the laws of the State of Delaware and is subject to the same exclusive Delaware jurisdiction set out in the Terms and Conditions.

OHR Report is operated by Outdoor Hospitality Research, Inc., 2915 Ogletown Rd, Newark, DE 19713. Questions about this Agreement can be directed to hello@ohrreport.com; questions about data handling specifically can be directed to privacy@ohrreport.com.