Valistry

The terms of using Valistry.

What each side does, what is owed, and how either side ends it. Written to describe what the software does, so nothing here has to be walked back.

Last reviewed 9 September 2026 · Valistry is operated by VedicSync Pvt Ltd, registered in Bangalore, India

The agreement

Using Valistry means accepting these terms. Where a signed order form says otherwise, the order form wins.

We may change these terms. A change that matters is announced to account owners by email before it takes effect, and the date above moves.

What you may do

Connect your sources, read your ledger, export it, and use what you find however you like. The numbers are yours.

  • One account per organization. Accounts are for people, not shared logins.
  • Read-only credentials only. We ask for the least access a source can give.
  • No reselling the service, and no probing it for weaknesses without asking us first. Ask, and we will usually say yes.

What we do

Read the usage and billing metadata you connect us to, compute a ledger from it, and show you what it says. We never read prompts or completions.

  • Your credentials are stored encrypted and shown only as their last four characters.
  • Each connector may call only the URLs it declares. A call anywhere else is refused before the request leaves.
  • Your data is yours. We do not sell it, and we do not train models on it.

Money

Paid plans are billed annually in advance unless the order form says otherwise. Fees exclude tax.

  • Starter costs nothing and carries no commitment.
  • An invoice is due thirty days from its date.
  • Where a first-year fee is capped at verified savings, the cap is measured from the ledger, not from a claim.

Ending it

You may stop at any time. Disconnecting a source stops the reading; deleting an organization deletes its records.

Either side may end a paid term on thirty days’ written notice. Where one side is in material breach, the other gives notice and fifteen days to put it right.

We may suspend an unpaid account, or one putting the service at risk, after telling you why. On termination you keep what you exported; we delete the rest within thirty days.

What we do not promise

The service is provided as it is. We work to keep it available and correct, and do not warrant that it will be uninterrupted.

Valistry reports what your vendors report. Where a vendor’s own data is wrong or missing, the ledger says so rather than filling the gap.

Neither side is liable for indirect or consequential loss. Our total liability in any twelve months is capped at the fees you paid.

Who owns what

Your data stays yours: the records we read, the ledger computed from them, and anything you export. We claim no ownership and take no licence beyond running the service for you.

Valistry stays ours: the software, the detectors, the pricing tables and the design. Nothing here transfers it.

We may report aggregate, de-identified statistics about how the service is used. Nothing that identifies you, your people or your vendors is in them.

Confidences

Each side will hold the other’s confidential information in confidence, use it only to perform this agreement, and protect it as carefully as its own.

That does not cover information already public, already known, or independently developed. Where the law compels disclosure, we tell you first unless we are forbidden to.

These obligations outlive the agreement.

If a claim arrives

We will defend you against a claim that Valistry infringes someone’s intellectual property, and cover what a court awards or we agree in settlement.

You will do the same for us where a claim arises from your data or from using the service against these terms.

Either way: tell the other side promptly, let them run the defence, and do not settle without them.

The rest

These terms are governed by the laws of India. The courts of Bangalore have exclusive jurisdiction.

Questions, or a clause your procurement needs changed: hello@valistry.ai.

These are our standard terms. An enterprise buyer will usually want a data processing agreement, a named list of sub-processors and a negotiated liability cap; all three are available on request, and we would rather agree them before you sign than after.

Read what we hold, and what we never do.

The privacy notice is written the same way: from what the software does.