These terms are a contract between you and DVM Technologies Ltd, the company that operates dvmkit, for publishing DVMs on our platform. Like our terms of service, they are written to be read, not to be impressive. If something here is unclear, ask us before you rely on your own reading of it.
Two other documents sit alongside them. The data processing agreement forms part of these terms and covers the personal data we handle for you when we host your DVM. The terms of service still govern your use of the website and of the DVMs we operate ourselves.
In these terms, "we", "us" and "our" mean DVM Technologies Ltd. "You" means the person or organisation that holds the builder account. "The platform" means the builder account and dashboard, the builder API that dvmctl uses, hosting on dvmkit Cloud, and any listing of your DVM on our site. "Callers" are the people and software agents that use your DVM.
1. What these terms cover
They cover everything you do with a builder account: signing in, managing organisations and API keys, deploying and operating DVMs, publishing them, and paying for a plan.
Hosting. When you deploy to dvmkit Cloud, we build and run your code, give it a database if it needs one, route requests to it at an address under dvmkit.ai, and keep its logs and metrics so you can operate it.
What they do not cover. dvmctl and the dvmkit SDK are distributed under the Apache License 2.0. That licence, and not these terms, governs what you may do with the code itself. A DVM you run on your own infrastructure is not hosted by us, so the parts of these terms about hosting, and the data processing agreement, do not apply to it. Your agreement with your callers is between you and them, as section 6 explains.
2. Who can be a builder
The platform is for business use. By accepting these terms you confirm that you are using the platform for the purposes of your trade, business, craft or profession, and not as a consumer. Self-employed individuals and one-person companies are welcome. The consumer rights in section 12 of our terms of service do not apply to this agreement.
Age and authority. You must be 18 or over. If you accept these terms for an organisation, you confirm you have authority to bind it, and "you" means that organisation.
Sanctions. You confirm that you are not located in, or ordinarily resident in, any of the regions listed in section 3 of our terms of service, and that you are not named on a UK, EU, US, or UN sanctions list. We refuse requests to the platform that appear to come from those regions, judged by the location of the IP address they come from.
Your account. Keep your account details accurate, including your billing details and any VAT number. You are responsible for everything done with your account, your API keys and your builder signing key. Keep them secret, and revoke any key you think has been exposed.
Organisations. An organisation owns its DVMs, their payment configuration, their secrets and their revenue records. The organisation is responsible for what its members do on its behalf.
3. The platform is in beta
The platform is in a closed beta. It changes often and it will have faults. We may add, change or withdraw features at any time, and we do not promise any level of availability. There is no service level agreement.
If we decide to stop offering hosting altogether, we will give you at least 30 days' notice so you can move your DVMs. dvmctl deploy --target self-host produces what you need to run a DVM on your own infrastructure.
4. Plans, trials and payment
Plans are subscriptions. A plan is billed monthly or yearly, in advance, at the price shown when you subscribe. It renews automatically at the end of each period until you cancel.
The free trial. You can host one DVM free, without adding a payment method. The trial starts at your first successful deployment and ends when its time or its hosting allowance runs out, whichever comes first; our pricing page shows both. It does not turn into a paid plan, and we do not charge you for it. When it ends, your DVM stops taking jobs. For the next 7 days you can export its data, or buy a plan to bring it back as it was. After that we delete it and its data, keeping only the records the law requires. If it holds caller balances, section 6 applies first: its callers keep at least 30 days to reclaim them. Your account stays open. You can have one trial: creating another organisation, or deleting and redeploying a DVM, does not start a new one. When trial places are full, you can wait for one or buy a plan.
Price changes. We may change our prices. A new price applies to you from your first renewal after we have given you at least 7 days' notice by email.
Cancelling. You can cancel at any time from the billing settings in the dashboard. Cancelling stops the next renewal: your plan continues to the end of the period you have paid for, and then ends. We do not refund a period that has already started, except where the law requires it, where we have made a mistake, or where section 9, section 13 or the data processing agreement says so.
When a paid plan ends. A paid plan ends when you cancel it, or when a payment fails and is still unpaid after we have retried it. There is no free plan to move to, so we then suspend your DVMs. Suspension works as section 9 describes. We keep a suspended DVM and its data for at least 30 days, and we email you before we delete anything.
Tax. Prices are stated exclusive of any value added tax or similar tax that we are required to charge. Where we must charge it, we will show it before you pay. If you give us a VAT number, you confirm that it is yours and valid.
5. Your revenue is yours
We take no share of what your DVMs earn, and we charge no fee on the payments callers make to them. Your plan is the only thing we charge you for.
Callers pay you directly. Every payment a caller makes goes to a destination you configured for the rail they paid on: your own address for stablecoins on Base or Tempo, your own wallet for Lightning top-ups, and, for Cashu ecash, your DVM, locked to a key derived from your recovery words. Payments do not pass through us, and we never control them. Ecash waits in your DVM's database on our infrastructure until you move it, but it is locked to your key, so we cannot spend it.
What that means for you. Because we never control your revenue, we cannot pay it out, recover it, freeze it or reverse it for you, on any rail. Keep the keys, recovery words and wallets behind your payment destinations safe. If you lose access to them, or configure a destination you do not control, money sent there may be lost for good. The revenue and payout figures in the dashboard and in dvmctl are reports of what your DVMs earned and what has reached you, not a balance we hold for you.
Tax on your revenue is your responsibility.
6. You and your callers
Your DVM is your service. When a caller uses your DVM, the agreement for that job is between you and the caller. You set its price, you run it, and you are responsible for what it does and what it returns. We host it for you, and we are not a party to your agreement with the caller.
Say who you are. Your DVM's description, or a page it links to, must say who runs it and how to contact you. If your callers include consumers, you are responsible for giving them the information and rights that consumer law requires. Do not present your DVM as ours or as endorsed by us.
Keep the payment safeguards. The SDK quotes a price before it charges and does not keep payment for a job that fails. Do not change or work around that behaviour to keep payment for work your DVM did not do.
Prepaid balances are money you owe. A balance a caller holds at your DVM belongs to that caller, and paying it back on request is your obligation. When you withdraw a DVM that holds balances, it stops taking new jobs and deposits, and callers have at least 30 days to reclaim what they are owed before it is deleted. The platform enforces this: it will not delete a DVM that holds caller balances before those 30 days have passed, and a DVM that is suspended or being withdrawn keeps answering reclaim requests, except those our sanctions check refuses under section 7. A balance still unclaimed after that remains a debt you owe the caller.
Personal data. For the personal data your DVM handles, you are the controller: you decide what it collects, why, which of your providers receive it, and how long it is kept, and you are responsible for the duties that come with that. Our privacy policy does not cover your DVM. When we host it, we handle its personal data for you under the data processing agreement. The SDK defaults to removing caller-controlled job content 730 days after a job reaches a final status. You can set jobRetentionDays to a shorter or longer whole number of days, or to 0 to disable automatic age expiry. Reading a job does not renew the period. A support or dispute hold retains only the affected job until explicitly cleared, including when its review is overdue. Choosing the policy and reviewing your holds are your decisions. Content expiry leaves the durable job outcome, financial facts, and signed receipts subject to their separate retention rules.
Your providers are yours. Services your DVM calls, such as model APIs, are suppliers you choose. Your agreements with them are your own, and they are not our sub-processors.
7. Acceptable use
We do not approve DVMs before they are deployed, and we do not suspend a lawful DVM because we disagree with it. Your DVM, and your use of the platform, must not:
- do anything unlawful, or produce, store or distribute unlawful content. This includes child sexual abuse material, content that sexualises minors, terrorist content, and material that incites violence;
- take callers' money without doing the work it was paid for, take funds it is not owed, or collect callers' keys, recovery words or other credentials;
- attack the agents that call it, for example by returning output designed to take control of an agent, to make it reveal secrets or to make it spend money;
- distribute malware, or probe, scan or attack our systems or anyone else's;
- infringe anyone's intellectual property, privacy or other rights;
- synthesise a real person's voice or likeness without their consent, or impersonate any person or organisation;
- send spam, or harass, defame, threaten or endanger anyone;
- use our hosting for work unrelated to running your DVM, such as mining cryptocurrency;
- get around plan limits, suspensions or billing, including by spreading one service across several accounts;
- provide services to, or take payments from, anyone you know or have reason to believe is named on a UK, EU, US, or UN sanctions list, or is in a region listed in section 3 of our terms of service.
Sanctions at the router. Our router refuses requests, other than health checks, that appear to come from the regions listed in section 3 of our terms of service, judged by the location of the IP address they come from, before they reach any DVM we host. The check can be wrong, and it does not replace your own obligations. You are responsible for meeting sanctions law for any traffic your DVM serves other than through our router, including at a DVM you run on your own infrastructure.
Our terms of service also apply to how you use the website and the DVMs we operate.
Listing is our editorial choice. Being listed in our directory, featured, or shown on a public profile is a decision we make, not something a deployment entitles you to. We can decline or remove a listing at any time, and we record our reason. A DVM that is not listed keeps running at its address.
8. Names and handles
Handles and DVM names are available on a first-come basis, but they must not:
- impersonate a person, organisation or brand, or suggest a connection that does not exist;
- use a trademark or name you do not have the right to use;
- mislead callers about who runs a DVM;
- be unlawful or abusive.
We reserve the names the site uses and the names of the DVMs we operate. We may change or reclaim a handle or DVM name that breaks this section, or after a trademark complaint we consider valid. Unless it is urgent, we will tell you first and give you time to choose another. Changing a handle or DVM name changes the DVM's address.
Our name. You may say your DVM is built with dvmkit or hosted on dvmkit. Do not use our name or logo in a way that suggests we run, endorse or sponsor your DVM.
9. Complaints, suspension and ending this agreement
Reporting a DVM. Anyone can report a DVM to support@dvmkit.com, including someone who believes it infringes their rights. We may pass the report on to you and ask you to respond or put the problem right.
When we can suspend. We may suspend a DVM, your account or an organisation, or remove a listing, if:
- it breaches section 7 or section 8;
- the law, a regulator or a court requires us to;
- continuing would expose callers, us or anyone else to material risk; or
- your paid plan or your free trial has ended, as section 4 describes.
We will tell you before we act and give you a reasonable chance to put things right, unless the breach is serious, the law prevents us, or waiting would expose callers or anyone else to harm. Wherever we can do so safely and lawfully, we will tell you why we acted.
Callers can still reclaim. A suspended DVM stops taking jobs, but its callers can still reclaim their prepaid balances, as section 6 describes. The only exceptions are where the law prevents it, including where sanctions law requires us to refuse a reclaim or hold a balance, where our sanctions check under section 7 refuses the reclaim, or where the balance is the proceeds of fraud or of a breach of section 7.
Appeals. If you think we got it wrong, reply to our notice or email support@dvmkit.com. A person will review your appeal and reply within 14 days.
You can leave at any time. Cancel your plan, withdraw your DVMs, and ask us at support@dvmkit.com to close your account. Section 6 still applies to any DVM that holds caller balances.
We can end this agreement:
- straight away, if you seriously breach these terms;
- if you breach them in any other way and do not put it right within 7 days of us telling you;
- if the law requires us to; or
- for any other reason, by giving you at least 30 days' notice. In that case we will refund any fees you have paid for time after the agreement ends.
When it ends, your DVMs stop taking jobs, and any that hold caller balances keep answering reclaim requests for 30 days, as section 6 describes. You have 30 days to export their data, by connecting to their databases with dvmctl db connect or dvmctl db proxy, before we delete it. The data processing agreement sets out how we delete personal data.
What survives. Sections 5, 6 (as to caller balances and personal data), 10, 11 (as to confidentiality), 12 and 14 survive the end of this agreement, and so does any fee you already owe.
10. Intellectual property and data about your DVMs
Your code stays yours. You keep all rights in your code, your DVM and its content. You give us a worldwide, non-exclusive, royalty-free licence to copy, build, host, run, store and transmit them, only as needed to provide the platform to you and to keep it secure.
Your listing. While your DVM is listed, you also allow us to show its name, description, capabilities and prices, and your handle, display name and avatar, in our directory, on your public profile and on the DVM's own page. We will ask you before featuring your DVM in our marketing anywhere other than on our site.
Those licences end when you delete the DVM or, for the listing, when it stops being listed. Copies in backups and logs are deleted as they expire, and we keep anything the law requires us to keep.
Our platform stays ours. We own the platform, the site and our brand, and nothing in these terms transfers any of them to you.
Feedback. If you send us ideas or feedback about the platform, we may use them freely, without owing you anything.
Data about how your DVMs run. We record request counts, outcomes, errors, resource use and the revenue and payout reports your DVMs send us. We use these records to run the platform, bill you, show your dashboard and enforce these terms.
Public listings show your DVM’s delivery, speed, reachability, payment-behaviour warnings and verified feedback. We use these records to order search results. Your feedback setting controls optional text, not verdicts. Individual caller records are not public. Other operational data is published only in aggregate. We never sell this data. The privacy policy explains how we handle caller records.
11. Confidentiality and security
Your secrets stay confidential. We keep your secrets, settings and unpublished code confidential. We do not read job content in the ordinary course of running the platform. We access your DVM, its database or its logs only to keep the platform running, to fix a problem, to investigate abuse or a security incident, or to comply with the law.
Our security measures are listed in the data processing agreement.
Your part. Keep your code, its dependencies and your keys secure, and set secrets through the platform rather than in your source code. Tell us promptly at security@dvmkit.com if you believe your account has been compromised or you find a vulnerability in the platform. Our commitment on good-faith security research applies to builders as well.
12. Disclaimers and our liability to you
The platform is provided "as is" and "as available". To the fullest extent the law allows, we exclude all implied warranties, including any implied term that the platform will be uninterrupted, error-free, secure, or fit for a particular purpose.
Nothing in these terms limits or excludes liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else that cannot lawfully be limited or excluded.
Subject to that, we are not liable for:
- loss of profit, revenue, business, goodwill, anticipated savings or opportunity;
- loss or corruption of data;
- loss of digital assets through lost keys or recovery words, or any change in the value of a digital asset;
- any failure of a third-party service that you or we depend on, including a payment rail, a mint, a blockchain, a model provider or a hosting provider;
- claims your callers make against you;
- any indirect or consequential loss.
Subject to the paragraph on liability we cannot exclude, our total liability to you for all claims connected with these terms and the data processing agreement is limited to the greater of £100 and the fees you paid us in the 12 months before the claim arose.
Your indemnity. You will indemnify us against claims made by callers or anyone else, and against fines, losses and reasonable costs, that arise from your DVM, what it does or produces, your breach of these terms, or your breach of data protection law.
13. Changes to these terms
We may change these terms. The current version is always on this page, with the date it was last updated at the top. A change takes effect as soon as we publish it if it does not reduce your rights or add to your obligations, if it only covers a new feature, or if the law requires it. Any other change that materially affects you takes effect 7 days after we email you about it. If you do not accept it, you can cancel your plan before then, and we will refund any fees you have paid for time after the change takes effect. We may ask you to confirm that you accept a new version.
14. General
The whole agreement. These terms, the data processing agreement, and our terms of service as they apply to your use of the website, are the entire agreement between us about the platform, and they replace anything said before. If these terms and the terms of service conflict about the platform, these terms apply. If these terms and the data processing agreement conflict about personal data, the data processing agreement applies.
Independence. You are an independent business. Nothing in these terms makes us your partner, employer, agent or payment processor.
Suppliers. We use suppliers to provide the platform. Those that handle personal data for you are listed in the data processing agreement, and we remain responsible for them.
Events outside our control. We are not liable for failing to perform these terms because of events outside our reasonable control, including the failure of a payment rail, a mint, a blockchain, a hosting provider or the internet.
Notices. We send notices to the email address on your account, so keep it current. Send notices to us at support@dvmkit.com.
If a court finds any part of these terms unenforceable, the rest continues to apply. If we do not enforce a right straight away, we have not given it up.
You may not transfer your rights under these terms without our consent. We may transfer ours to a company that takes over our business, provided your rights are not reduced.
Nobody other than you and us has any right to enforce these terms under the Contracts (Rights of Third Parties) Act 1999.
These terms and any dispute arising from them are governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.
15. Contact
- General and support: support@dvmkit.com
- Privacy and data protection: privacy@dvmkit.com
- Security: security@dvmkit.com
DVM Technologies Ltd is registered in England and Wales under company number 17276970. Registered office: 167-169 Great Portland Street, 5th Floor, London, England, W1W 5PF.