Beta Test Terms

(1) RYVIO is in a closed test phase. Its purpose is to test the software under real conditions, find defects and feed participant feedback into development.

(2) The software is under active development. Features may change, be added, be temporarily restricted or removed. Individual features may contain errors, including the creation, scheduling and publishing of social media posts.

(3) The Provider does not represent that the software is error-free or continuously available. The participant's statutory rights remain unaffected (§ 9).

(1) Participation is open only to entrepreneurs within the meaning of § 14 BGB and public-law entities. Consumers are excluded.

(2) Access is by invitation only; registration requires a valid invite code. Codes are personal and must not be shared.

(3) The participant decides who works in its workspace (team feature) and ensures those persons know and comply with these terms.

(1) The test phase starts with the participant's confirmation of these terms and initially lasts 30 days; the Provider may extend it in text form.

(2) Participation is free of charge during the test phase.

(3) There is no automatic conversion to a paid subscription. A paid contract only arises through a separate, express agreement naming scope, term and price.

(4) Participation is voluntary and may be ended at any time (§ 11).

(1) The Provider makes the current test version available via the internet. There is no entitlement to specific features or their retention.

(2) Known limitations at the start of the test phase include:

• Publishing runs through the official interfaces of Meta (Instagram, Facebook), LinkedIn and Pinterest; their availability, approvals, quotas and rules are outside the Provider's control.
• Some platform features (e.g. TikTok publishing, Instagram stories with stickers, LinkedIn company pages) are not yet or only partially available and may require manual completion on a smartphone.
• Platform connections can expire or be revoked by the platform; the participant is notified in the app and must reconnect.
• Metrics are collected only from the time of connection and may be incomplete.

(3) The Provider may update the software at any time. Maintenance may temporarily limit availability; planned maintenance is announced in advance where possible.

(1) The participant double-checks scheduled posts during the test phase (date, target account, text, media) and keeps backups of important content outside RYVIO.

(2) The participant uses RYVIO only for accounts it is authorised to publish to and within each platform's terms.

(3) The participant keeps credentials secret, uses strong passwords and reports suspected unauthorised access without delay. Two-factor authentication is recommended.

(4) Prohibited in particular: circumventing technical protections, automated mass access outside the documented API, uploading unlawful content and attempts to access other customers' data. Security issues should be reported confidentially.

(1) All content uploaded or created by the participant remains the property of the participant or its clients.

(2) The participant grants the Provider a simple right, limited to the participation period, to store and technically process the content (e.g. format conversion, preview, checks) and to transmit it to the selected platforms on instruction. No further use takes place, in particular no advertising and no training of AI models with customer content.

(3) Every publication is made on the participant's instruction and in its name. The participant is responsible for the lawfulness of content, labelling duties and third-party rights.

(1) Feedback, bug reports and suggestions may be used by the Provider without remuneration to improve the software. The Provider is not obliged to implement suggestions.

(2) The Provider will not name the participant publicly as a reference without separate consent.

(1) Non-public information about the test version (unreleased features, security findings, pricing considerations) is kept confidential by the participant until the end of the test phase; use within its company and towards its clients in normal work is permitted.

(2) The Provider treats the participant's content and data confidentially and processes them only under the Terms, the DPA and the privacy policy.

(1) The Provider is liable without limitation for intent and gross negligence, for injury to life, body or health, under the Product Liability Act, where a guarantee was given and in cases of mandatory statutory liability (in particular Art. 82 GDPR).

(2) As participation is free of charge, the Provider is not liable for slight negligence, in line with the statutory standard for gratuitous services (§§ 599, 521 BGB). If the Provider slightly negligently breaches a material contractual obligation (an obligation whose fulfilment is essential for the proper performance of the contract and on which the participant may regularly rely), it is liable by way of exception, limited to the foreseeable, typical damage and at most €1,000 per claim. Liability under paragraph 1 remains unaffected.

(3) The beta label does not change the Provider's liability under paragraph 1 for its own breaches in data protection and security.

(4) The Provider is not liable for outages, changes or blocks of platform interfaces it is not responsible for. Delayed or failed publications caused by such circumstances or by the test version do not give rise to claims absent fault.

(5) In case of data loss the participant is obliged to keep its own backups under § 5 (1); liability is limited to the effort that would have been needed for restoration with proper backups.

(6) These limitations also apply in favour of the Provider's agents.

(1) The privacy policy and, where the Provider processes data on the participant's behalf, the DPA apply. Both are available in the app at any time.

(2) The beta environment processes real data of the participant and its clients. The Provider applies the same technical and organisational measures as for regular operation (encrypted transport, encrypted platform credentials, tenant isolation, access restriction, logging of security-relevant events, database and application in the EU; uploaded media files are kept in the hosting provider's object storage, which may be located outside the EU, see privacy policy).

(3) Confirming these terms is not a consent under data protection law. RYVIO does not use tracking or advertising cookies.

(1) Either party may end participation at any time in text form (email to kontakt@ryvio.me); the participant may also delete its account in the settings.

(2) The participant can export its data at any time in a common, machine-readable format from the settings. Export remains possible for 30 days after the test phase ends.

(3) Thereafter the Provider deletes the participant's content and account data unless statutory retention duties apply. Platform connections are disconnected and tokens deleted.

(4) Transition to a paid plan occurs only by separate agreement (§ 3 (3)).

(1) Technical improvements and bug fixes within the agreed scope do not require new consent.

(2) Material changes (cost, liability, data processing, rights in content) are presented in the app with a new version number and take effect only upon express confirmation. Until then the last confirmed version applies; the Provider may restrict access until confirmation.

(3) Each confirmed version is stored with date, version number and text checksum and can be retrieved in the settings.

(1) German law applies, excluding the UN Sales Convention.

(2) Place of jurisdiction for merchants and public-law entities is Bremen.

(3) Should individual provisions be invalid, the remaining provisions remain unaffected.