General rules for using Vianium and its connected modules.

Vianium may be used to build, operate, and manage clients, integrations, and connected modules on top of the platform infrastructure.

Users agree not to use the service for unlawful activity, third-party abuse, provider restriction evasion, prohibited scraping, or any operation that violates applicable third-party service terms.

Each user is responsible for the security of their credentials, the activity performed through their account, and the use of any external account they choose to link through OAuth or local pairing.

The environment operator may suspend, revoke, or limit access when abusive use, policy violations, operational risk, or non-payment is detected.

Part of Vianium functionality depends on third-party services, including Meta Threads, Reddit, Google, and WhatsApp. Use of those modules is also subject to the policies and terms of those providers.

Vianium does not guarantee permanent availability of an integration when the external provider changes APIs, permissions, limits, review processes, or terms of use.

Some features may depend on the active plan, technical limits, approved permissions, or the healthy state of plugins and connected services.

The product, its modules, and its scopes may evolve. Vianium may modify functionality, limits, interfaces, or external dependencies to preserve security, operations, and compatibility.

Users are responsible for having sufficient rights over the data, accounts, content, and actions they send or execute through the platform.

The operator of each deployment remains responsible for properly configuring its environment, domains, secrets, internal policies, and support channels.

Vianium is provided on a reasonable operational basis, but uninterrupted availability, total absence of errors, or indefinite compatibility with third-party APIs is not guaranteed.

To the extent allowed by applicable law, the service is provided as is, with the normal limitations of software, infrastructure, and external dependencies.

Users may stop using the service at any time. The environment operator may also suspend or terminate access when there is non-compliance, security risk, or justified operational need.

Upon termination, the account and associated data will be handled in accordance with the privacy policy, the data deletion page, and applicable legal obligations.

If you operate a Vianium instance for third parties, you may supplement these terms with your own commercial or contractual terms for that deployment.