Beta Terms of Use

1. Beta and evaluation status

Hotel Budget Planner is being offered as a controlled beta for evaluation, product learning and real-world hotel planning use. Features, screens, calculations, workflows and limits may be refined during the pilot. Roadmap descriptions are directional and do not create a commitment to a particular release date or feature.

Access may be staged, paused or limited while we investigate reliability, security, capacity or product-quality issues.

2. Account and authority

You are responsible for keeping your login credentials secure and for activity performed through your account. If you use the service on behalf of a hotel or organization, you should have authority to enter and process that hotel’s planning information.

The first controlled cohort includes one principal hotel workspace per pilot account unless additional access is explicitly approved. Do not attempt to access another participant’s workspace or circumvent product access controls.

3. Financial-planning boundary

You remain responsible for the accuracy and completeness of information entered into the service; the assumptions and targets approved by management; reconciliation to authoritative accounting records; and any decision, filing, report or commitment made using outputs from the beta.

Financial Actuals from the hotel’s accounting records remain authoritative for accounting results. Calculated outputs should be reviewed before management or external use.

4. Hotel data and outputs

You retain responsibility for and rights to the hotel information you enter or upload. You grant the service the limited permission needed to host, process, calculate, display, back up, troubleshoot and export that information for operation of the beta.

We do not claim ownership of your hotel’s budgets, forecasts, actuals or confidential planning figures merely because they are processed through the platform.

Beta participants should export and retain their own approved copies of important budgets, reports and versions. Do not rely on the beta as the only repository for official hotel records.

5. Acceptable use

You agree not to misuse the service, interfere with its operation, attempt unauthorized access, probe another participant’s data, automate abusive request volumes, introduce malicious code, or use the service in a way that violates applicable law or another party’s rights.

The platform is intended for aggregated hotel financial and operating information. Do not upload guest payment-card data, passwords, passport or identity-document images, health information, or unnecessary guest/employee personal records.

Security testing or reverse engineering that could affect production availability or another participant’s data should not be performed without prior written authorization.

6. Feedback and pilot learning

We encourage participants to report bugs, confusing workflows, missing hotel use cases, calculation concerns and performance issues. Feedback may be used to improve the product, documentation and future services. Providing feedback does not authorize us to publish your hotel’s confidential financial figures or identify the hotel publicly without separate permission.

7. Availability, changes and support

Because this is beta software, the service may contain defects and may be changed, interrupted or temporarily unavailable. We aim to maintain a reliable pilot and use automated calculation, database and browser checks, but uninterrupted or error-free operation is not guaranteed.

Where practical, participants should report material defects through the in-app feedback channel and retain exported copies of critical planning outputs.

8. Suspension or ending beta access

Access may be suspended or ended for material misuse, security risk, repeated violation of these rules, non-authorized access attempts, or when necessary to operate or conclude the controlled beta. A participant may also stop using the beta and request account/workspace deletion through the support channel, subject to normal backup and record-retention processes described in the Privacy Notice.

9. Third-party infrastructure

The beta depends on third-party hosting and infrastructure services, including cloud application and database providers. Their availability can affect the service. Links to external eHMS resources or other sites are provided for convenience and may be governed by their own terms and privacy practices.

10. Disclaimers and limitation

To the extent permitted by applicable law, the beta is provided for evaluation and management-support purposes without a promise that it will meet every hotel requirement or be suitable for statutory, audit, tax, financing or other regulated reliance. Users should independently review material financial outputs before acting on them.

Nothing in these beta terms excludes obligations or liabilities that cannot legally be excluded. A jurisdiction-specific commercial agreement, governing-law clause and formal liability framework should be established before broad paid deployment where required.

11. Changes to these terms

These terms may be updated as the product and pilot develop. The date at the top identifies the current version. Continued beta access after a material update may be conditioned on accepting the updated terms.