Acceptable use

Acceptable use policy.

What we expect of people who use Orynt, and what we may act on. Short and plain, and not yet checked by a lawyer.

Draft — not reviewed by counsel

This draft was written without legal advice and has not been adopted by any legal entity. It describes our intent and will change. It is not a contract, and no public instance exists to which it could apply yet.

The short version

Use Orynt to pay people you are entitled to pay, with money you are entitled to spend, in ways that are lawful where you and they are. Do not use it to hurt others or to hurt the service.

You may not

  • Break the law. That includes paying for illegal goods or services, financing terrorism, laundering money, evading sanctions, or taking part in fraud, scams or extortion.
  • Spend money that is not yours to spend. Do not use a wallet, credential or approval key without the authority of whoever owns it, and do not get around another organisation's approval controls.
  • Misrepresent payments. Do not present a simulator payment as real, alter a receipt, or use a receipt to claim a payment that did not happen.
  • Attack or overload the service. No scanning, probing or load testing against an instance you do not run or have permission to test, no attempts to bypass rate limits, plan limits or tenant isolation, and no malicious uploads in CSV or text fields.
  • Evade limits. Do not create accounts or workspaces to get around plan limits or a suspension.
  • Send secrets to us. Never put wallet credentials, macaroons, seed phrases, private keys or API keys into forms, support requests or notes.
  • Harass or target people. Do not use payment memos, references or recipient names to abuse, threaten or expose anyone, and do not add other people's personal data you have no reason to hold.

Things to keep in mind

  • Lightning payments are final. Orynt cannot reverse them or recover funds sent to the wrong place.
  • Orynt does not hold funds, check who a payee really is, or judge whether a payment is lawful. Those responsibilities stay with you.
  • You are responsible for everyone you invite to your workspace and every API key you create.

What we may do

If we believe this policy is being broken, we may ask you to stop, restrict or suspend a workspace or key, or close an account. A formal process for notice, appeals and reporting to authorities has not been written, and will be set out, with counsel, before any public launch.

Reporting abuse

To report misuse or a security problem, use Contact support. Please describe it in general terms and do not include secrets or exploit details.

Related drafts

See the terms of use and the privacy notice, both also unreviewed drafts.

Questions about what is allowed?

Ask before you build around something that might not be. We would rather answer than guess.