Terms of service

Effective date: August 1, 2026

These terms are an agreement between you and Veld Labs LLC (“Veld”, “we”), a Delaware limited liability company and the maker of Juno. They apply to the Juno website and editor, the Juno API, the Juno Store, and the Juno Discord bot. You accept them when you sign in, install the bot on a server, buy a paid plan, or publish to the Store — and we may ask you to confirm that acceptance explicitly at those moments. They are longer than we would like, because they have to settle who owns what and who answers for what; they are still written to be read. Questions go to hello@veld.gg.

Juno is not affiliated with Discord. Your use of Discord itself is governed by Discord's own terms, and workflows that touch Discord data must respect Discord's Developer Policy just as Juno itself does.

Who can use Juno#

You need a Discord account in good standing and must meet Discord's minimum age requirements. To buy a paid plan you must be at least 18 years old or the age of legal majority where you live; if you are younger, a parent or legal guardian must make or authorize the purchase. If you accept these terms for a company or another organization, you confirm you are allowed to bind it.

Your account#

You sign in with Discord; there is no separate Juno password. You are responsible for what happens through your account and your active sessions. If you believe your account has been compromised, secure your Discord account and contact us.

Installing Juno on a server#

Only install Juno on servers you are authorized to manage, and stop running workflows on a server when you lose that authority. When you install the bot or deploy a workflow, you are acting on behalf of that server, and you are responsible for determining whether and how a workflow may lawfully process data there. That means you must:

provide members with any legally required notices — including, where applicable, notice that message-processing workflows are active;
obtain any legally required permissions or consents before deploying a workflow;
configure workflows proportionately, and avoid collecting sensitive or excessive information;
respond to your members' questions and requests about the workflows you run;
follow any privacy rules specific to your community, such as employment or education rules, where they apply.

Workflow data is processed on your instructions as described in the privacy policy; organizations that need a data processing addendum can request one at hello@veld.gg.

What you build#

You own your workflows. Workflows, their settings, and everything you put into them remain yours; these terms do not transfer ownership of any of it to us.

So that Juno can work, you grant Veld a worldwide, non-exclusive, royalty-free license to host, store, reproduce, execute, back up, and display your workflows — to you, to the people you share them with, and on the servers that install them — solely to operate, secure, and improve Juno. This license ends when the content is deleted, with three narrow tails:

backups — deleted content persists in backups until they expire in rotation, and this license covers those copies until then;
evidence — the payload-limited operational records described in the privacy policy are kept for their stated retention periods; keeping them does not require, and does not grant us, any continuing right to your deleted workflow itself;
Store installs — copies other servers lawfully installed before a listing was removed remain licensed to them under the Store license described in The Store.

You are responsible for what you put in and what it does. You represent that:

you own what you put into your workflows or have all permissions needed to use it;
your workflows and their content do not violate law, contracts, or anyone's rights — including intellectual-property and privacy rights;
you have the authority to process the Discord data your workflows use;
you will not put secrets, credentials, or regulated data into workflows except through features expressly built for them;
our operation of your workflow as permitted above will not itself infringe anyone's rights.

A workflow acts with the permissions the server gave the bot; do not build things you would not be allowed to do yourself as a moderator of that server.

The Store#

Publishing a workflow to the Store is deliberately public: the listing, its releases, and its release notes become visible to everyone, and other servers can install and remix what you published. Never publish confidential information — publication is the point.

The license you grant by publishing. You keep ownership of your workflow. The Store is a commons scoped to Juno: everything published there may be built upon within Juno, and every descendant stays part of the same remixable lineage. Publishing a release makes that happen through three grants:

To Veld — a worldwide, non-exclusive, royalty-free, transferable and sublicensable license to host, store, reproduce, execute, adapt, display, distribute, and otherwise use the release as necessary to operate, secure, promote, and improve Juno and the Juno Store.
To every Juno user — a worldwide, non-exclusive, royalty-free license to access, install, execute, inspect, reproduce, modify, and create derivative works from the release through Juno's functionality.
Derivatives stay in the commons — any remix or other derivative release published through Juno must remain available for installation, inspection, and further remixing through Juno under these same Store terms. You cannot publish a derivative and close it off.

Removing your listing stops new installs and new remixes, but the grants already given are irrevocable for what people already have: installed copies stay pinned to the release they installed, and derivatives already published stand — and stay remixable. Veld may adapt published releases as the first grant permits — in practice, for compatibility and security.

Remixes and contributions. Three different things can happen to a published workflow, and they work like this:

A remix is a new descendant owned and maintained by you. Your own contributions are yours; the material you inherited remains subject to the original's Store license. You cannot revoke the upstream permissions, and you cannot present the whole work as solely your own — Juno's recorded lineage stays intact.
A proposed edit is a change you submit to another workflow's maintainer. Until accepted it remains yours, licensed to the maintainer as needed to inspect, modify, accept, and incorporate it.
An incorporated contribution becomes part of the release it was accepted into, under that release's same Store terms — inbound equals outbound. You keep the copyright in what you contributed; everyone receives it under the Store license, and Veld never takes an assignment of your copyright.

What the Store is not. We do not review every workflow before publication, do not endorse listings, and do not guarantee that a listed workflow is safe, correct, compatible with future changes to Juno or Discord, compliant with your server's rules or local law, or wise about the external services it calls. Store workflows are made by their creators, not by us — inspect what a workflow asks for before installing it.

We moderate the Store and may remove or suspend listings under Enforcement; where reports are involved, we keep records of what was decided and why. If your listing is removed and you disagree, contact us.

Copyright complaints#

If you believe content on Juno — a Store listing, a release, a workflow shared with you — infringes your copyright, send a notice to our copyright agent: Copyright Agent, Veld Labs LLC, 1111B South Governors Avenue, Dover, DE 19904, United States, or hello@veld.gg with the subject “Copyright notice”. Include the information section 512(c)(3) of the DMCA requires: identification of the work and the infringing material, your contact details, a statement of good-faith belief, a statement of accuracy under penalty of perjury, and your physical or electronic signature.

We act expeditiously on valid notices, notify the affected user, and accept counter-notices meeting section 512(g). Where a valid counter-notice is not followed by a court action within the statutory window, we may restore the material. We terminate the accounts of repeat infringers in appropriate circumstances. Knowingly false notices can make you liable for damages.

Acceptable use#

Do not use Juno to:

break the law, or infringe anyone's rights;
harass, threaten, or deceive people, or target minors;
send spam or unsolicited mass messages;
distribute malware, or workflows deliberately built to harm servers or their members;
violate Discord's terms, community guidelines, developer policy, or rate limits;
collect data about people beyond what a workflow legitimately needs — monitoring for legitimate server management, like moderation and safety, is fine; covertly monitoring individuals beyond that is not;
build workflows that collect information from or about children, solicit ages or birth dates without a legitimate approved purpose, or knowingly process data of users below Discord's minimum age;
collect or store — unless Juno expressly supports it for that purpose — passwords or authentication codes, payment-card details, government identification numbers, health information, precise geolocation, biometric identifiers, private keys or other secrets, or sensitive employment or educational records. Workflow state is not a general-purpose secure database.

And do not attack the platform itself. You must not:

bypass authentication or authorization, or access data you are not authorized to access;
obtain or use another user's tokens, credentials, or sessions;
exploit vulnerabilities, introduce malicious code, or conduct security testing without our permission;
reverse engineer Juno except where the law makes that restriction unenforceable;
use undocumented internal interfaces;
probe, overload, or interfere with Juno, or evade its limits and moderation;
evade a suspension or termination — including by creating or using another account or server to get around enforcement or quotas — or help someone else do so.

Good-faith security research is welcome: if you find a vulnerability, report it to hello@veld.gg and give us a reasonable chance to fix it. Research conducted that way — without harming users, taking data, or disrupting the service — will not be treated as a violation of this section.

The API#

Access to the Juno API — directly or through connected tools — comes with a few rules of its own:

keep your credentials and tokens secret, and don't share, resell, or sublicense API access;
respect rate limits and quotas; don't scrape or bulk-extract data beyond what your integration legitimately needs;
don't use the API to build a substitute for Juno out of Juno's own data;
where your integration touches Discord data, Discord's developer terms flow through to you;
APIs evolve: we version and deprecate endpoints, and where a change breaks documented behavior we will say so ahead of time. Undocumented endpoints may change or vanish without notice — building on them is at your own risk;
we may throttle or revoke API access immediately for abuse.

Plans and billing#

The Starter plan is free. Paid plans are billed per server through Stripe at the prices and billing frequency shown when you subscribe.

Subscriptions renew automatically each billing cycle until cancelled, and by subscribing you authorize those recurring charges to your payment method.
Cancel any time from billing settings — cancellation is effective at the end of the period you already paid for, and paid features stay active until then. Removing the bot from a server does not cancel its subscription; cancel it in billing settings.
A subscription belongs to the specific server it was bought for. If you need to move one to another server, contact us.
Prices may change; changes never apply mid-cycle and we will tell you before a renewal costs more. Prices may exclude taxes: where sales tax, VAT, or similar applies, it is added at checkout or on the invoice, and you are responsible for taxes other than taxes on our income.
Plan changes take effect as shown at the time you make them, including any proration shown there.
Failed payments: we (through Stripe) may retry the charge and update expired card details where the law and card networks permit. If payment ultimately fails, paid features pause until it is fixed. Lapsed subscriptions never delete your workflows — features that need the paid plan simply stop until it is renewed.
Keep your billing information accurate. Stripe processes payments under its own terms; your contract for the subscription is with us.

Refunds. Payments already made are non-refundable, except that: we correct duplicate and erroneous charges; charges established to be fraudulent are refunded; if we terminate your paid plan without you being at fault — including by discontinuing the service — we refund the unused part of what you prepaid; and nothing here overrides refund or withdrawal rights the law gives you where you live. We may occasionally offer a credit or refund as a courtesy; doing so once does not create an entitlement to another.

Connected AI tools#

You can let AI tools and agents act on your account through scoped, revocable grants. Connected tools are operated by third parties: we do not control their availability, accuracy, or data practices, their own terms may apply to you, and choosing, configuring, and supervising a tool is your responsibility. By creating a grant you authorize Juno to disclose to that tool the data its scopes cover. Revoking a grant stops future access; it does not erase data the tool already received — that is between you and the tool.

Actions correctly authenticated and performed within a grant you created are treated as authorized by you, unless caused by a security failure attributable to Juno. Remember that AI-generated actions can be wrong in confident and creative ways; review what your tools do, especially anything they publish or send to your members.

Enforcement#

Where something breaks these terms, creates risk for users or for Juno, or the law requires it, we may: remove or disable content and listings, quarantine a workflow, suspend or restrict accounts and features, revoke API access and grants, preserve evidence, notify affected servers, and cooperate with Discord or authorities.

Where the problem is fixable and not urgent, we will normally tell you what is wrong before or when we act — but for urgent security, safety, or legal concerns we act first and explain afterwards. If you think we got it wrong, contact us and we will review it; on moderation of content and listings, our good-faith decision after that review is final.

Juno is young#

Juno is a new product. Features will change, and occasionally break. We may add, alter, or retire functionality; where a change removes something you depend on, we will do our best to say so ahead of time. We do not promise uninterrupted availability.

Ending things#

You can leave at any time: remove the bot from your servers, revoke its authorization in Discord, cancel any subscriptions in billing settings, and ask us to delete your data as described in the privacy policy.

We may suspend or terminate access as described in Enforcement. If we terminate your access without such a reason, we will give you reasonable notice, and refund prepaid amounts as described in Plans and billing.

When your account or access ends, whatever the reason:

your access to the editor and API stops;
for 30 days you may ask us for an export of your unpublished workflows, unless we terminated you for serious abuse or the law prevents it;
your data is then deleted on the schedule in the privacy policy; fees you already owe remain due;
published Store listings are removed from new installation, but copies other servers already installed keep the license described in The Store;
the provisions that by their nature should survive do survive — including accrued payment obligations, the licenses needed for backups and installed Store copies, content warranties, disclaimers, liability limits, indemnification, and the dispute terms.

Feedback#

If you send us feedback or suggestions about Juno, we may use them without restriction or compensation — though we will not publicly attribute them to you without permission. This covers feedback you volunteer about the product; it does not turn your support requests or private information into material we may use freely.

What Veld owns#

Juno itself — the software, editor, bot, APIs, documentation, interface design, branding, and the technology the platform generates, including aggregated and de-identified operational information where the law permits — belongs to Veld and its licensors. These terms give you no rights to Juno's or Veld's trademarks, except to truthfully say that something works with Juno. Nothing in this section claims ownership of your workflows, your data, or general workflow ideas and logic.

Disclaimers#

Juno is provided “as is” and “as available”, without warranties of any kind — express, implied, or statutory, including merchantability, fitness for a particular purpose, and non-infringement — to the extent the law allows. We do not warrant that workflows will run without error or that Juno will always be available, and the Store carries the risk allocation described in The Store. Nothing in this section excuses us from operating Juno with reasonable skill and care.

Liability#

To the extent the law allows, and whatever the theory of liability — contract, tort (including negligence), strict liability, or otherwise, even if we were advised such damages were possible:

neither party is liable to the other for indirect, incidental, special, consequential, or punitive damages, lost profits, or lost data;
our total aggregate liability for all claims arising out of or relating to Juno or these terms — across all events and theories combined — is limited to the greater of $50 or the amount you paid us in the twelve months before the first event giving rise to liability.

These limits do not apply to your payment obligations, to your indemnification obligations, or to your infringement of our intellectual-property rights. Nothing in these terms excludes or limits liability to the extent it cannot lawfully be excluded or limited — which, depending on jurisdiction, may include fraud, willful misconduct, gross negligence, and death or personal injury. Both parties agree these limits are an essential basis of this bargain, and that the pricing reflects them.

Indemnification#

If a third party brings a claim against Veld or its personnel arising from your violation of these terms or of the law — a fraudulent or unlawful workflow, for example — you will indemnify us for the damages, penalties, and reasonable legal costs that result. This obligation does not apply to the extent a claim results from our own violation of these terms or of the law. We will notify you promptly of any such claim, and you may not settle a claim in a way that imposes obligations on us without our consent.

Privacy#

How we handle data is described in the privacy policy, which is part of this agreement.

Changes to these terms#

We can update these terms as Juno evolves. When we do:

changes are not retroactive, and material changes take effect no sooner than 14 days after we announce them on this page and in the product;
for material changes — new payment obligations, changed licenses, changed dispute terms — we will ask for your explicit acceptance where a reliable way to do so exists;
if you do not accept updated terms, stop using Juno before they take effect and, if you have a paid plan, cancel it; the old terms govern until then. Continuing to use Juno after the effective date means the updated terms apply.

Governing law and disputes#

These terms are governed by the laws of the State of Delaware, USA, without regard to its conflict-of-laws rules. Disputes belong to the state courts located in Delaware or the United States District Court for the District of Delaware, and both parties consent to personal jurisdiction and venue there — except where the law of your country or state of residence gives you protections, remedies, or venues that cannot be taken away by contract.

The fine print#

Entire agreement. These terms, the privacy policy, any data processing addendum, and the purchase terms shown at checkout are the whole agreement about Juno. If we sign a separate written agreement with you, that agreement wins where they conflict; a data processing addendum wins on data-processing matters.
Severability. If part of these terms is found unenforceable, the rest stands.
No waiver. Not enforcing something once does not waive our right to enforce it later.
Assignment. You may not assign this agreement without our consent. We may assign it in connection with a merger, acquisition, financing, reorganization, or sale of Juno, to a party that takes on our obligations under it.
Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control — internet or cloud failures, Discord outages, attacks, labor disputes, government action — except for payment obligations already accrued.
Notices. We send ordinary notices in the product or through Discord; formal legal notices to us go to Veld Labs LLC, 1111B South Governors Avenue, Dover, DE 19904, United States, with a copy to hello@veld.gg.
Interpretation. Headings are for convenience; “including” means “including but not limited to”.
No third-party beneficiaries. Except for the Store license granted to Juno users in The Store, these terms create rights only between you and Veld.

Contact#

Veld Labs LLC, a Delaware limited liability company 1111B South Governors Avenue, Dover, DE 19904, United States hello@veld.gg