Terms of service — Vibe Coder verification service
The rules for using this service. Last updated 2026-08-04.
What these terms cover
These are the terms for the Vibe Coder verification service: the certificate pages, the directory, the badge images, the public revocation list, the free tools, the form that relays a report request to an app owner, and the form that disputes a verdict. The service is operated by Vibe Coder Playground LLC, 7901 4th St N, STE 300, St. Petersburg, FL 33702, USA, and you can reach us at contact@vibecoderplayground.ai.
Using the service means accepting these terms. If you do not accept them, do not use it. What happens to personal data is set out in the privacy notice at /privacy, which forms part of these terms.
The Vibe Coder Playground desktop app is licensed separately, under the licence shipped with it. Nothing here replaces that licence.
The beta: free, and liable to change
The service is in beta. Everything on it is free, no payment method is collected, and nothing is for sale.
Beta also means it moves. We may add, change or remove features, and we may reset data — with notice where we can give it. There is no uptime commitment and no support commitment. If we shut the service down for good, we will say so on these pages first.
What a certificate is, and what it is not
A certificate records an automated audit of a body of code at one moment in time, against a published rubric, keyed to a hash of exactly what was audited. It reports what the rubric measured, and it reports what it could not measure rather than passing it.
It is not a warranty. It is not a penetration test, a security certification, an audit of a company, an accountant's opinion, a lawyer's opinion, or advice to buy, sell or invest in anything. It describes code on a date — not the business behind it, and not the site you are looking at today.
Do not make it the only basis for a decision that matters to you. If you are buying software, do your own diligence as well.
A certificate expires. Editing the audited code makes it stop reading as current, which is deliberate. An owner can withdraw one and we can revoke one; withdrawn and revoked ids are published at /revocations.json so anyone can check without trusting the page they came from.
If you publish a certificate
Publishing needs a token. Keep it secret: anything done with your token is treated as done by you, and you should tell us at once if it leaks.
Publish only about software you have the right to publish about, and only content you own or are licensed to use. Do not put anyone else's personal data into a certificate or a listing profile.
Display the badge as we serve it. Do not redraw it, alter it, or re-host the image, and do not display a badge for a certificate that has expired, been withdrawn or been revoked. Permission to display it lasts exactly as long as the certificate is valid.
We can revoke a certificate — for a false claim, for a misused badge, for a breach of these terms, or because the audit itself turned out to be wrong. Revocations are published, with a reason.
If you ask an owner for a report
The form passes your note and your contact detail to that app's owner. We are the messenger. We do not promise you a reply, and whatever the owner sends you afterwards is between you and them.
Do not use the form to send anything unlawful, threatening, or bulk. It is rate-limited, and we can block an address that abuses it.
If you challenge a verdict
Anyone may file a dispute. Say what is wrong, and leave a contact so it can be resolved. A dispute is reviewed before it appears on a certificate; if it is accepted, it appears whether or not it goes your way, and so does our written resolution.
Do not file a dispute you know to be false. We do not accept anonymous disputes, and we do not publish your contact detail.
The free tools
The free tools measure what you paste, deterministically. Each run accepts up to 64 KB of request — roughly 65,000 characters of plain source, fewer for text that takes more than one byte a character — and there is a fixed number of runs a minute. Nothing you paste is stored.
Paste only what you are entitled to paste. You keep every right in your own content, and you give us only the permission needed to run the tool and hand you back the answer.
A free tool's answer is not a certificate, not a verdict against the standard, and not a security review. It reports what a deterministic scan could see, and it names what it did not look at. Read it that way.
Acceptable use
- Do not try to overload the service, evade its rate limits, or guess certificate ids in bulk.
- Do not crawl it in ways its robots file asks you not to.
- Do not forge, imitate or reproduce a Vibe Coder badge, certificate page or verdict for software that does not have one.
- Do not use the service to break the law or somebody else's rights.
Our marks and our words
The name Vibe Coder Playground, the Vibe Coder Standard, the rubrics, the badge artwork and the wording of these pages are ours. You are welcome to quote a certificate and to link to it. You may not present our marks as your own, and you may not suggest we endorse you beyond what a valid certificate actually says.
Credits: written now, not in use, and not part of the paid plan
No credits exist today. The beta is free, there is nothing on this service or in the app to pay for, and nothing offers a credit for sale — and none ever has been sold: the purchase path has been shut since the day it was written, so nobody is holding a credit they paid us for. This section was published in advance so that leaving beta would be a switch rather than a legal project. It has no effect until we announce that credits are live, and that announcement will name the date these clauses start to apply — and as things stand we do not plan to make it.
What the paid plan is instead. A monthly subscription, with the audits run on API tokens you bring yourself. Nothing meters a balance you bought from us, so there is no prepaid balance of ours to hold, to spend down or to lose, and what you would pay for is the subscription rather than credits. The clauses below stay published and dormant because the mechanism they describe is still in the software: we would rather leave its rules in plain sight than delete them and have to write them again in a hurry.
What a credit is. A credit is a unit of account that pays for one metered operation of the service — for example, one audit run. What a credit costs and what it buys will be stated at the point of payment, along with any tax.
A credit is not money. Credits are paid for in advance and are a right to use the service, not a currency, a deposit, a stored-value instrument, a gift card or a security. They have no cash value, they earn no interest, they cannot be exchanged for cash, they cannot be transferred, sold or given to anyone else, and they give you no stake in the company.
Refunds. A credit added to your balance is not refundable, with two exceptions: where the law where you live gives you a refund right that cannot be waived; and where we charged you in error or charged you twice. Neither has ever arisen, because no credit has ever been sold. Separately, a run that fails because of a fault on our side should not cost you anything — if it consumed a credit we put the credit back, rather than refunding cash. What happens to credits if the service ends is covered below, and it is not a cash refund.
Expiry. A credit you paid for expires 90 days after the purchase that added it, if it is still unused. Each purchase carries its own expiry date and a later purchase never extends an earlier one. When a purchase expires, the unused remainder of it stops being spendable and there is no grace period — but nothing is deleted: the amount that was lost and the day it was lost stay in your balance history, because "where did my credits go" has to have an answer. A credit we gave you at no charge — a trial, a promotion, a goodwill gesture — expires on the term we state when we grant it, which is never longer than 90 days and is 7 days for the free trial, and it is never refundable. Where the law where you live does not allow a balance paid in advance to expire, it does not expire.
How you are warned before a credit expires. There are no accounts here and we store no contact address for you, so the warning is in the software rather than in your inbox: from 14 days before a purchase expires, the app's Credits panel lists that purchase, the credits still on it, the days remaining and the date it goes — and what expired unused stays on that panel afterwards rather than disappearing.
Which credits are spent first. The ones expiring soonest, whether we gave them to you or you paid for them — so the credits closest to being lost are always the ones spent first. Nothing else reorders it, and you do not have to choose.
Prices. We can change what a credit costs for future payments. A change does not alter, add to or take away from a balance you already hold.
If the service ends, or the paid tier does. We will give at least 90 days' notice on these pages and in the app, stop taking payment immediately, and keep the service running through the notice period so you can spend what you hold. Credits we granted at no charge simply lapse, with nothing to refund. We are not promising to send money back for unused credits, and the reason is plain: no credit has ever been sold, so none of your money is sitting here against one, and there is no mechanism in this software for returning money against a credit balance. If credits are ever offered for sale, the terms published before the first sale will say what a wind-down does with a balance that was paid for — and we will not take a payment for credits until that is written down.
A subscription is not a credit. Money you paid for a monthly subscription is not governed by this section: a refund on one is asked for in the app, where on every plan but enterprise the software issues it itself against the payment processor, and where it cannot confirm the charge it records the request for a person instead. An enterprise refund is only ever recorded by the software and issued by a person, under the written enterprise refund policy, because an enterprise agreement is negotiated and has to be read before money moves.
If we end your access for a breach of these terms, unused credits are forfeit — except that if it turns out we were wrong, we will not keep money you had paid for credits you never got the chance to use. That has never applied to anyone, because no credit has ever been sold. There is no account here to close: what ends is your access to the service, not a login.
No warranty
The service is provided as it is and as it happens to be available. To the fullest extent the law allows, we disclaim the implied warranties of merchantability, fitness for a particular purpose and non-infringement.
We do not warrant that a certificate is free of error, that the service will be uninterrupted, or that a free tool has found everything there is to find — it is a deterministic scan, and it says so. Where the law where you live does not allow these exclusions, they do not apply to you.
Limits on what we owe you
To the fullest extent the law allows, we are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, lost business or lost data arising out of the service — including a decision you took because of a certificate.
Our total liability on any claim is capped at the greater of what you paid us in the twelve months before the claim and 100 United States dollars. During the beta nobody pays us anything, so in practice that cap is 100 dollars.
Nothing here limits liability that cannot be limited by law, including liability for fraud.
What you cover us for
If a claim is brought against us because of something you published through the service, or because you did not have the right to publish it, you will cover our reasonable costs of dealing with it. We will tell you promptly and let you have a say in how it is handled.
Ending it
You can stop using the service whenever you like, and an owner can withdraw a certificate at any time. We can suspend or end access for a breach of these terms, and we will say why unless the law prevents us.
The parts meant to outlive the relationship do: the disclaimers, the limits above, what you cover us for, and the governing law.
Changes to these terms
We can change these terms, and the date at the top changes when we do. If a change matters to you — a new charge, a new limit on your rights — we will say so on the certificate pages before it takes effect, and where credits are concerned we will name the date it starts.
The law, and where a dispute goes
These terms, and any dispute about them or about the service, are governed by the laws of the State of Florida, USA, without regard to its conflict-of-laws rules.
Before going to court, write to contact@vibecoderplayground.ai and give us 30 days to put it right. Most things end there.
If it still needs a court, that court is in Pinellas County, Florida, USA — the state and federal courts sitting there — and we both agree to their jurisdiction. If a consumer-protection law where you live gives you the right to bring a claim locally instead, that right stands.
Odds and ends
If a clause here turns out to be unenforceable, the rest still stands and that clause is read as narrowly as it needs to be. Not enforcing something once does not mean we have given it up. You may not transfer these terms; we may transfer them to a successor of the business. These terms and the privacy notice are the whole of the agreement about this service.
How to reach us
Vibe Coder Playground LLC, 7901 4th St N, STE 300, St. Petersburg, FL 33702, USA. contact@vibecoderplayground.ai.