Skip to main content

Terms of service

What you agree to when you publish Brandfronts and Links through Zaps.

Last updated:

Pre-launch draft. This document describes how Zaps is built and operated today and is pending legal review before general availability. It is not yet a binding agreement.

What these terms cover

These terms cover your use of Zaps: the workspace application, the Brandfronts and Links you publish through it, the analytics it reports, and the public API.

By creating an account you agree to them. If you use Zaps on behalf of an organisation, you confirm you are allowed to accept them for that organisation.

Your account and workspaces

You are responsible for the activity in your workspaces, including anything done by the people you invite and by any API key you create.

Roles decide what a member can do. Removing someone from a workspace ends their access; it does not delete the Links or Brandfronts they created.

What you publish

You keep ownership of everything you publish through Zaps. You grant us only the permission needed to host it, serve it to visitors, and back it up.

Public Brandfronts serve the published snapshot. Draft edits stay private to your workspace until you publish them.

Acceptable use

Zaps may not be used to publish or redirect to:

  • Phishing, impersonation, or credential harvesting.
  • Malware, or downloads that misrepresent what they are.
  • Content that is illegal where it is served, or that infringes someone else’s rights.
  • Automated traffic intended to inflate analytics or evade plan limits.

Reports and enforcement

Anyone can report a Link or Brandfront through the report form. We review reports and may disable an address, a Handle, or an account that breaks these terms.

A disabled address serves the unavailable page. We do not disclose the outcome of a report to the person who filed it, because doing so would expose information about another account.

Plans, limits, and billing

Each plan carries limits on tracked visits, Brandfronts, workspaces, seats, and analytics retention. The published limits for each tier are on the pricing page and are enforced by the API.

Paid plans are billed in advance for the period you choose. Downgrades take effect at the end of the period you have already paid for, so nothing is cut off mid-cycle.

Custom domains are not part of any plan today. Every Handle you claim gets a Zaps host at no additional cost.

Availability and changes

We work to keep redirects and published Brandfronts serving continuously, and we will give notice before a change that would break an integration built on a documented API route.

Outside an Enterprise agreement, Zaps is provided without an availability commitment.

Ending your use of Zaps

You can close your account at any time. We may end an account that breaks these terms, or after a sustained period of non-payment.

When an account ends, its Links stop redirecting and its Brandfronts stop serving. Export anything you want to keep before you close it.

Questions about this document go to legal@zaps.one.

Back to Zaps