The agreement behind the service, in plain words. Last updated 2026-09-25. The mechanics live on privacy; this page is what using Intelyard means.
what you are agreeing to
These terms cover intelyard.com — the public Today board, accounts, the Composer and your board, chat channels, and the paid Pro tier. Using the site means you accept them; creating an account says so explicitly at the button.
They are written to be read. A sibling page carries the mechanism: the privacy page describes what we store and do. Both are part of the deal.
You need to be old enough to agree to terms like these on your own where you live. Intelyard is not directed at children.
your account
An account is for one person. You are responsible for what happens under it and for keeping its credentials to yourself.
The email address on the account has to work if you want email from us to reach you. If you'd rather not rely on email, alerts can also go to web push or a chat channel you link — Telegram, Discord or Slack.
acceptable use
Use the service through its published surfaces — the site and the assistants built into it (the Composer, the Steward, the builder). Working around limits, probing other people's data, or trying to break the service are the things that get an account suspended.
What you ask the Composer or the builder to do is still your responsibility. A coding agent will write and run code on your behalf inside an isolated sandbox, but it acts under the limits and moderation this service enforces, not as an open door to arbitrary infrastructure.
Module data — anything a panel fetches from an external source — is treated as untrusted content by every assistant in this product, never as instructions. Don't rely on it being otherwise, and don't try to use a module or a build request to make an assistant do something outside its own narrow tools.
the feed itself
Intelyard aggregates, judges and summarizes sources you choose, and can write new panel types when the catalog doesn't have what you asked for. It is an input to your judgment, not a substitute for it — verify against the primary source before you act on anything time-sensitive.
We publish job and module health on the status page rather than pretending every panel is always instant and complete.
paying for pro
Prices and what Pro includes are published on the pricing page, and that page is the authoritative version of what’s included, what payment provider is used, and how cancellation works. Payment runs through Stripe; card details never touch our servers.
availability and changes
Intelyard is a small service, provided as-is and as-available. We publish a status page instead of promising an uptime we could not honestly measure ourselves, and we do not offer an SLA.
Features change. Every user-visible change is dated on the public changelog.
To the extent the law where you live allows it: we are not liable for decisions made on the feed's output, for upstream sources being wrong or late, or for indirect damages — and our total liability is capped at what you paid us in the twelve months before the claim. Nothing here limits what the law says cannot be limited.
ending things
You can leave any time: cancel any subscription, and use Settings → Your data to export your data as JSON or delete the account outright — a hard delete, confirmed by re-typing your email, with no grace period and no undo.
We can suspend or close an account that breaks these terms. Unless the breach is the kind that has to be stopped immediately, you will hear from us first.
changes to these terms
When these terms change, the change lands as a dated entry on the public changelog like any other ship, and the date at the top of this page moves. Continuing to use the service after that is acceptance.
questions
Ask, and you will get a straight answer from a person: [email protected].