OpenApp
Login
Legal

Effective 2026-10-17 · Version 1.3

Terms of Service

These Terms of Service ("Terms") govern your access to and use of OpenApp, a physical access control platform offered as a service ("Service") by OpenApp ("OpenApp", "we", "us", or "our"). By creating an account, signing in, or otherwise using the Service, you agree to be bound by these Terms. If you are using the Service on behalf of an organization, you represent that you have authority to bind that organization to these Terms.

These Terms are not legal advice and are not a substitute for review by counsel licensed in each market where you operate, a fire-protection engineer, or the Authority Having Jurisdiction (AHJ). Codes are adopted locally. The adopted edition and the AHJ always win over product copy.

1. The Service

OpenApp provides software for managing inbound physical access — including doors, gates, virtual intercom, access policies, guest invitations, and audit logging — across individual and organizational accounts. OpenApp is ingress- only software. It is not a lock manufacturer, not a listed access-control system, not a fire-alarm control unit, and not an electrically controlled exit system. We may add, change, or remove features over time. We provide the Service on a commercially reasonable-effort basis and do not guarantee uninterrupted or error-free operation.

2. Accounts and authentication

You must provide accurate account information and keep your credentials secure. You are responsible for all activity that occurs under your account. You may authenticate using a supported identity provider (such as Google) or other methods we offer; your use of those providers is also subject to their terms. You must notify us promptly of any unauthorized use of your account.

3. Acceptable use and prohibited configurations

You agree not to:

  • use the Service to gain unauthorized access to any property, system, or data;
  • interfere with or disrupt the integrity or performance of the Service;
  • attempt to circumvent access controls, rate limits, or security measures;
  • reverse engineer the Service except to the extent permitted by law; or
  • use the Service in violation of any applicable law or third-party right.

You are solely responsible for configuring access policies correctly and for the physical security consequences of those configurations.

You must not:

  • use OpenApp as the sole electric lock on a means of egress, fire-door assembly, stair re-entry door, or elevator lobby special locking arrangement;
  • use hold_closed, emergency lockdown, curfew, or similar OpenApp denies to electrically lock people in, or to disable local exit hardware;
  • use hold_open on a fire-resistance-rated door except via listed hold-open hardware released by the fire alarm (not OpenApp);
  • market or operate OpenApp as a fire-alarm interface, fire unlock, certified life-safety system, UL / ULC / EN / NFPA listed access-control system, or substitute for BS 7273-4 / NFPA 72 door release;
  • require a phone, credential, app, or working internet to exit.

Occupants must be able to exit without OpenApp. Independent mechanical exit hardware, panic/lever hardware, hardwired request-to-exit, or a listed local special-locking system with fire-alarm, power-fail, and local emergency-door release must remain usable when the cloud is down.

4. Customer, installer, and AHJ duties

If you deploy the Service at a site, you (and any installer you engage) are the responsible person / dutyholder for fire safety and building-code compliance at that site. You must:

  • classify each opening in the product (life_safety_class) and store a commissioning attestation before production use;
  • provide listed free egress appropriate to the occupancy and opening;
  • obtain AHJ permits and inspections where required;
  • not alter a labeled fire-door assembly with unlisted hardware;
  • for vehicle gates, maintain listed operator entrapment protection (for example UL 325 / EN 12453).

The Life-Safety Addendum, when attached to an order form, is an exhibit to these Terms for that order.

5. Customer content and data

You retain ownership of the content and data you submit to the Service ("Customer Data"). You grant us a limited license to host, process, and transmit Customer Data solely to operate and improve the Service. Our handling of personal data is described in our Privacy Policy, which forms part of these Terms.

If you use the Service on behalf of an organization, you are the controller of resident, visitor, invitation, intercom, and access-event data you store in the Service, and OpenApp is your processor. That processing is also governed by our Data Processing Agreement. Personal workspaces remain consumer accounts under the Privacy Policy.

6. Service availability and security

We apply administrative, technical, and physical safeguards designed to protect the Service and Customer Data. No method of transmission or storage is completely secure, and you acknowledge that you provide Customer Data at your own risk. You are responsible for maintaining appropriate backup access methods for critical entry points, including independent exit that does not depend on the Service.

7. Third-party integrations

The Service can connect to third-party hardware, gateways, and platforms. Your use of any third-party product is governed by that third party's terms, and we are not responsible for third-party products or their availability. Current plugins are not listed egress controllers. OpenApp-operated subprocessors are listed at Subprocessors. Products you connect (for example PalGate Cloud at palgate.com) are not OpenApp-operated stores.

8. SMS messaging

OpenApp sends text messages (SMS) only to deliver access invitations and one-time verification, login, registration, and recovery codes for the Service. We do not send marketing or promotional messages by SMS.

  • How you agree to receive them. When you sign in or register with your phone number, you ask us to text a code to that number. When a host or administrator invites you, they request the invitation message for your number and confirm that you have agreed to receive it. Enter only phone numbers that you are entitled to use or whose owner has agreed to receive these messages.
  • Frequency. Message frequency varies. A message is sent only when someone requests a code or an invitation.
  • Cost. Message and data rates may apply.
  • Opt out and help. Reply STOP to any message to opt out; you will get one confirmation and no further messages. Reply HELP or write to support@openapp.house for help. Opting out stops SMS to that number only. Invitations to an opted-out number cannot be delivered by SMS, and the person who sent the invitation is shown that it was not delivered.
  • Delivery. Carriers and networks are outside our control. We are not liable for delayed or undelivered messages.

How SMS data is handled is described in the Privacy Policy.

9. Fees

Paid plans, if any, are billed as described at the time of purchase. Unless stated otherwise, fees are non-refundable. We may change pricing prospectively with reasonable notice.

10. Termination

You may stop using the Service at any time. We may suspend or terminate your access if you violate these Terms or if we reasonably believe your use poses a security or legal risk. Upon termination, your right to use the Service ends, and we may delete Customer Data after a reasonable retention period.

11. Disclaimers

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT, TO THE MAXIMUM EXTENT PERMITTED BY THE LAW THAT APPLIES TO YOU. OpenApp is a software service and is not a substitute for professional security, life-safety, or emergency systems. Some US states and Canadian provinces restrict consumer disclaimers; those restrictions apply where they must.

GPSR / product-liability notice (EU): Presentation and instructions are part of the safety a person is entitled to expect. Cloud software that can prevent escape can be treated as a product. You must follow the prohibited-configuration rules in §3.

12. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, OPENAPP WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, DATA, OR PHYSICAL PROPERTY, ARISING OUT OF OR RELATING TO YOUR USE OF THE SERVICE.

United Kingdom and European Union: nothing in these Terms excludes or limits liability for death or personal injury caused by negligence, or for fraud or fraudulent misrepresentation, or any other liability that cannot be limited by law (including the UK Consumer Rights Act and Unfair Contract Terms Act, and equivalent member-state rules).

Business customers (B2B) may agree additional caps in an order form. Those caps never apply to death or personal injury caused by negligence where local law forbids that exclusion. Consumers retain all non-waivable statutory rights.

13. Governing law and venue

If you use the Service primarily as a business (B2B), these Terms are governed by the laws of the State of Delaware, USA, excluding conflict-of-law rules, and the courts of Delaware have exclusive venue, except that (a) mandatory consumer-protection, product-liability, and fire-safety laws of your place of establishment still apply, and (b) if you are a UK or EU consumer, you may bring claims in the courts of your habitual residence and you cannot be deprived of mandatory protections of that law.

If you are a consumer, the mandatory consumer laws of your country of residence apply, and you may sue in the courts of that country.

14. Changes to these Terms

We may update these Terms from time to time. When we make material changes, we will update the effective date below and, where appropriate, provide additional notice. Your continued use of the Service after changes take effect constitutes acceptance of the updated Terms.

15. Contact

Questions about these Terms can be sent to legal@openapp.house. Privacy and data-subject requests: privacy@openapp.house. A short buyer-facing summary is at Compliance.