These Beta Programme Terms ("Beta Terms") are supplemental to the Rople Terms of Service (TERMS_OF_SERVICE.md) between [ROPLE LEGAL ENTITY NAME] ("Rople", "we") and the Customer. Words defined in the Terms of Service have the same meaning here.
They apply only if the Customer joins the Beta Programme, and only to Beta Features and Developer Support. Everything else about the Customer's use of Rople continues to be governed by the Terms of Service, the Data Processing Agreement and the Acceptable Use Policy, unchanged.
1. Definitions
- Beta Programme — the programme through which a workspace receives early access to Beta Features and Developer Support.
- Beta Features — features, modules and functionality that Rople identifies in the product as "Beta", "Preview", "Pilot" or similar, and that are not yet generally available. At the effective date this includes the Workflows module and its automation engine.
- General Availability — the point at which Rople makes a feature available to all Customers on the applicable plan without the "Beta" designation.
- Developer Support — the support described in §5.
- Feedback — suggestions, comments, bug reports, ideas and other information the Customer or its Users provide about Beta Features.
2. Joining and leaving
Joining. A workspace joins the Beta Programme when an org admin or the workspace owner accepts these Beta Terms in the workspace's settings. The person accepting confirms that they are authorised to bind the Customer. Rople records who accepted, when, and which version of these Beta Terms was accepted.
Leaving. The Customer may leave the Beta Programme at any time from the same setting, with immediate effect. Rople may end the Customer's participation, or the Beta Programme as a whole, on [14] days' notice, or immediately where required for security, legal compliance or to prevent harm to the service.
Effect of leaving. Beta Features stop being available to the workspace. Customer Data created through them is not deleted: it is retained under the Terms of Service and the Data Retention and Deletion policy, and is available again if the workspace rejoins or the feature reaches General Availability. Automations paused while the workspace is outside the Beta Programme are not replayed when it rejoins.
Eligibility. Rople may decide which workspaces and plans are eligible for the Beta Programme and which Beta Features are offered to them.
3. Nature of Beta Features
The Customer acknowledges that Beta Features:
- are pre-release and may contain errors, defects or incomplete functionality;
- may be changed, suspended or discontinued at any time, with or without General Availability following;
- are not covered by any service level, uptime, response-time or support commitment in the Terms of Service or an order form, other than Developer Support under §5;
- may perform differently from generally available features, including in how quickly they process events and send notifications; and
- should not be relied on as the sole means of performing a business-critical, legal, financial or employment process. The Customer is responsible for checking the results of any process it runs through a Beta Feature.
Rople will give reasonable notice before discontinuing a Beta Feature the Customer is actively using, and will make Customer Data created through it available for export under the Terms of Service.
4. Customer Data and data protection
Customer Data processed through Beta Features remains Customer Data. The Data Processing Agreement applies to it in full: the Customer is controller and Rople is processor, and Beta Features use only the sub-processors listed in SUB_PROCESSORS.md. Joining the Beta Programme does not change where Customer Data is stored, who may access it, or how long it is kept.
The Customer must not use Beta Features to process special categories of personal data, or other data it is not permitted to disclose to a processor, beyond what it already processes in its workspace.
5. Developer Support
During its participation the Customer receives Developer Support: a priority channel to Rople's product and engineering team at [BETA SUPPORT EMAIL], for questions about Beta Features, reports of defects and requests for help designing workflows. Rople will use reasonable efforts to respond within [2] business days; no service level applies.
Developer Support does not give Rople access to the Customer's workspace or Customer Data. Where looking inside the workspace would help, Rople will ask, and access remains subject to a support-access grant issued by the Customer under the support access process (time-limited, logged and revocable by the Customer).
Rople may contact the administrators of a participating workspace about Beta Features, including to ask for Feedback. These communications are service communications, not marketing.
6. Feedback
The Customer is not obliged to provide Feedback. Where it does, Rople may use, copy, modify and incorporate the Feedback into its products and services without restriction or payment, consistent with §10 of the Terms of Service. Feedback does not include Customer Data, and Rople will not identify the Customer as its source publicly without consent.
7. Confidentiality
Beta Features, their documentation and any non-public information about Rople's product plans disclosed through the Beta Programme are Rople's Confidential Information under §11 of the Terms of Service. The Customer may share them with its own Users and advisers who need to know and are bound by equivalent obligations, but not publish them or share them with third parties before General Availability.
8. Fees
There is no additional fee for participating in the Beta Programme or for using Beta Features during it. If a Beta Feature becomes chargeable at General Availability, Rople will give the Customer at least [30] days' notice of the price, and the Customer will not be charged for it unless it chooses to continue using it after that date.
9. Disclaimer
To the fullest extent permitted by law, Beta Features and Developer Support are provided "as is" and "as available", without warranty of any kind. The warranty of reasonable skill and care in §12 of the Terms of Service does not apply to Beta Features. Rople does not warrant that Beta Features will be uninterrupted, error-free or secure against every threat, that defects will be corrected, or that any Beta Feature will reach General Availability.
Nothing in these Beta Terms reduces Rople's obligations under the Data Processing Agreement, or Rople's security obligations for Customer Data generally.
10. Limitation of liability
Nothing in these Beta Terms excludes or limits liability that cannot lawfully be excluded or limited, including for fraud, death or personal injury caused by negligence, or a breach of the Data Processing Agreement.
Subject to that, Rople's total aggregate liability arising out of or in connection with Beta Features and Developer Support is limited to [AMOUNT]. This limit is within, and not in addition to, the overall cap in §13 of the Terms of Service.
11. Order of precedence
For Beta Features and Developer Support, these Beta Terms prevail over the Terms of Service where the two conflict. For everything else, the Terms of Service prevail. The Data Processing Agreement prevails over both on the processing of personal data.
12. Changes
Rople may update these Beta Terms. A new version will be shown to the workspace's administrators in the product, and the Customer's continued participation requires acceptance of it; the Customer may instead leave the Beta Programme. Rople records the version each workspace accepted.
13. General
§16 of the Terms of Service (General), including governing law and jurisdiction, applies to these Beta Terms.