Integration Terms

Last updated: September 2026

These Integration Terms (the "Integration Terms") apply when you install and use an integration provided by Vaxal (the "Company") on a third-party platform such as Vercel, and the Company acts on your behalf within your account on that platform. These Integration Terms apply together with our Terms of Service and Privacy Policy. Matters not addressed here are governed by the Terms of Service. Where these Integration Terms conflict with the Terms of Service, these Integration Terms prevail with respect to the use of the integration.

1. Scope

These Integration Terms apply to integrations published by the Company on third-party platforms and installed by you. Installing an integration means you have read, understood and agreed to these Integration Terms in full. If you do not agree, do not install the integration, or remove it from the platform.

These Integration Terms do not change your relationship with the third-party platform. Your rights and obligations towards that platform remain governed by its own terms.

2. What you authorise the Company to do

Once installed, and for as long as the authorisation remains in place, you authorise the Company to perform the following actions on your behalf, within the account or team scope you selected: create projects, configure project environment variables, create and update deployments, and read the status of those resources in order to display progress.

The Company exercises this authorisation only to the extent necessary to provide the service, and for no other purpose.

3. Permissions the integration obtains

The integration discloses the permissions it requires at install time, so that you can review each one before deciding whether to consent. The integration requests only the minimum permissions necessary to provide the service.

The integration does not request and does not obtain full control of your account. You may review the permissions it actually holds at any time from the management interface of the platform.

4. What the Company will not do

The Company does not read, copy or analyse the source code or content of your existing projects, unless you actively provide that content through the service.

The Company does not modify or delete resources that were not created through the service.

The Company does not use data obtained through the integration to train models, nor does it provide such data to third parties for marketing or other unrelated purposes.

5. Ownership and deletion of resources created by the integration

Projects and deployments created through the service belong to your account on the platform from the moment they are created. You own and manage them, and the Company retains no control after delivery. You may use, modify or delete them at any time.

Please note: some platforms treat environment variables created by an integration as owned by that integration. On Vercel, for example, environment variables created by this integration are deleted by the platform when the integration is disabled or removed, which may prevent later deployments from working. If you wish to keep those settings after removing the integration, back them up beforehand or recreate them under your own account.

This behaviour is a mechanism of the third-party platform and is outside the control of the Company. It is disclosed here so that you can prepare before removing the integration.

6. Handling of credentials

Access tokens obtained by the Company are stored encrypted, used only on the server side, and never appear in front-end pages or in the artefacts delivered to you.

The Company does not disclose your credentials to third parties, and does not use them for operations outside the scope described in these Integration Terms.

After you remove the integration or revoke the authorisation, the Company deletes the stored credentials within a reasonable period.

7. Termination and revocation

You may remove the integration at any time from the management interface of the third-party platform, which terminates the authorisation described in these Integration Terms. After removal, the Company can no longer act on your resources on that platform.

Revoking the authorisation does not affect the continued existence of projects and deployments already delivered into your account. However, as described in section 5, environment variables created by the integration may be deleted by the platform.

The Company may suspend or terminate the integration if it identifies use that violates these Integration Terms or applicable law.

8. Disclaimer, limitation of liability and governing law

The integration is provided on an "as is" basis. To the maximum extent permitted by law, the Company is not responsible for the availability of the third-party platform, for changes to its policies, or for the consequences thereof.

Disclaimers, limitations of liability, changes to terms, governing law and jurisdiction are all governed by the Terms of Service.