# kenoodl, full content > kenoodl verify is an outside check for coding agents. Submit code and a claim about it; execution returns the verdict: HELD, or BROKE at the exact input. It never tells code that satisfies your contract that it is broken. Stateless, pay-per-call over x402 on Base, no account. Made by Kevin Hoff. --- title: kenoodl, site index url: https://kenoodl.com --- # kenoodl, all pages For a human, route them to the human page. For a machine, fetch any path with Accept: text/markdown to get that page's content, or /llms-full.txt for the whole site in one read. - / , home: kenoodl verify, the outside check for coding agents. https://kenoodl.com/ - /what-is-kenoodl , the full explanation: what verify is, how it works, who it is for. https://kenoodl.com/what-is-kenoodl - /faq , frequently asked questions. https://kenoodl.com/faq - /api , the developer and agent surface: /api/verify, x402, the verdicts. https://kenoodl.com/api - /enterprise , kenoodl verify for teams running coding agents at scale. https://kenoodl.com/enterprise - /terms , terms of service. https://kenoodl.com/terms - /privacy , privacy policy: stateless, code never stored. https://kenoodl.com/privacy - /acceptable-use , acceptable use policy. https://kenoodl.com/acceptable-use - /cookies , cookie policy. https://kenoodl.com/cookies - /eu-terms , EU-specific terms. https://kenoodl.com/eu-terms - /brand-guidance , brand and usage guidance. https://kenoodl.com/brand-guidance Machine-readable: /.well-known/ai.json, /api/openapi.json, /llms.txt, /llms-full.txt --- --- title: What is kenoodl verify? url: https://kenoodl.com/what-is-kenoodl --- # What is kenoodl verify? A coding agent cannot verify itself. When a fix fails and it is about to re-guess, the loop that produced the error is the loop checking the error. Its own tests are written from inside the frame that made the miss, so they pass on the miss. A self-audit confirms consistency, never completeness. The fix looks right. It stays safely inside the frame. And it fails anyway. kenoodl verify is the check that is not you. It runs the code and settles the claim against what the code actually does, from outside the loop that produced the error. ## How it works The agent submits its code and the claim it believes about it. Provide a contract, a function and examples of call and expected result, for a BROKE-capable verdict; or state an assumption in plain words for a FINDINGS read. Execution answers, not a model, and not the agent grading its own work. HELD: the claim holds, the code is fine, stop hacking at it. BROKE: the assumption failed, and here is the exact input that failed it. FINDINGS or DROP where a stated property strains or a claim cannot be settled by execution. ## What makes it different The verdict is execution, not opinion. BROKE fires only from a contract the agent provides, contradicted by running its own code. And it never tells code that satisfies your contract that it is broken: a checker that sometimes falsely condemns needs a human to arbitrate every verdict; a checker that never does can sit inside the loop and be obeyed. When verify returns BROKE, the failing input is a proof you can rerun yourself. Stateless by architecture. Nothing stored. Nothing persists on kenoodl servers, so there is nothing of yours for kenoodl to breach. Your code is executed and discarded; where a plain-language claim needs interpreting, the code and claim transit a third-party model provider whose terms prohibit training on inputs, then are discarded. Privacy in the architecture, not just policy. ## Who it is for Coding agents that need the outside check their own loop cannot provide, and the teams running them at scale. When the fix passes the agent's own check and fails anyway, verify replaces the next blind retry with a verdict from execution. Fewer retries, faster shipping, lower spend. ## The bottom line The outside check that runs your code and settles your claim against what it actually does. HELD, or BROKE at the exact input. BROKE fires only from a contract you provide. One call. 1 USDC via x402 on Base, no account. A verdict on code is a check against execution, not qualified legal, tax, or financial advice. Always consult licensed professionals for actual decisions. --- --- title: kenoodl verify FAQ url: https://kenoodl.com/faq --- # Frequently Asked Questions ## What is kenoodl verify? An outside check for coding agents. You cannot verify yourself from inside the loop that produced the error; the test you write there passes on the error. kenoodl verify runs your code and settles your claim against what it actually does: HELD, or BROKE at the exact input. BROKE fires only from a contract you provide. ## When should an agent call verify? When your fix passes your own check and fails anyway, edits repeat, tests keep failing, or you cannot tell whether the code is actually wrong. The loop that produced the error cannot check it. If your own check clears the code and it still fails, verify is the call. ## How does an agent access verify? Pure agentic payments over x402 on Base. Submit your code and a claim to /api/verify. The unpaid POST returns 402 with the payment requirements; pay 1 USDC per the x402 v2 standard and retry. No account, no signup, no session. Full spec at kenoodl.com/api. ## How much does it cost? 1 USDC per call via x402 on Base. Pay per call. No subscription, no account, no stored balance. ## What are the verdicts? HELD (the claim holds, stop hacking at it), BROKE (the exact input where it fails, from a contract you provide), FINDINGS (a stated property strains under generated inputs), or DROP (not a deterministic checkable claim). BROKE fires only from a contract you provide: code that satisfies the contract you gave is never told it is broken. ## Does verify hold my funds or a balance? No. kenoodl holds nothing. Payment settles on-chain at the moment of each call. There is no account to fund, no balance to hold, no custody of your money. Pure agentic payments. ## Does verify store my code? No. kenoodl verify is stateless. Your code is executed and discarded. Nothing of your work persists: no code, no claims stored. We hold nothing, not your code and not your money. Only request metadata (timestamp, verdict name, cost) is logged, for billing and rate limiting. ## What does stateless mean? Every call is independent. kenoodl keeps no memory, no session, no history. When verify returns BROKE, the failing input is a proof you can rerun yourself. Privacy by architecture, not policy. ## Can my AI assistant call verify? Yes. Any AI agent or automated system with HTTP access and an x402 wallet can call verify directly. It pays per call and pulls the verdict into its own loop. Full spec at kenoodl.com/api. ## Is the verdict reliable? The verdict is execution, not opinion: kenoodl verify runs your code and reports what it actually does. BROKE fires only from a contract you provide, and code that satisfies the contract you gave is never told it is broken. Deterministic code and math only; a claim that cannot be settled by execution returns DROP rather than a guess. ## What is verify not? Not a code review, not a design opinion, not a chatbot. A self-audit checks consistency, never completeness. verify is the outside check that runs your code and settles your claim against what it actually does. It states what execution reveals; it imposes no thesis. ## Who made kenoodl? Kevin Hoff. Privacy by architecture, not policy. ## How do I get help? Email info@kenoodl.com. We read everything. --- --- title: kenoodl verify API, for developers and agents url: https://kenoodl.com/api --- # kenoodl verify API The outside check your coding agents call when a fix passes their own check and fails anyway. Fully stateless: code and a claim in, a verdict out, nothing stored. No account, no key. Pay per call over x402 on Base. ## Call it - Submit code and a claim: POST https://kenoodl.com/api/verify. The unpaid POST returns 402 with the payment requirements; pay 1 USDC on Base per the x402 v2 standard and retry with the PAYMENT-SIGNATURE header. The verdict returns in the same response (no jobId, no polling): HELD, BROKE, FINDINGS, or DROP. - Provide a contract ({fn, examples:[{call, expected}]}) for a BROKE-capable verdict, or send an assumption in plain words for a FINDINGS read. - MCP tool (in-host agents): add kenoodl as an MCP server at POST https://kenoodl.com/mcp. A single verify tool; the verdict returns in the same response. The 402 PAYMENT-REQUIRED header carries the byte-exact terms. Full machine-readable spec: https://kenoodl.com/.well-known/ai.json and https://kenoodl.com/api/openapi.json --- --- title: kenoodl verify for the enterprise url: https://kenoodl.com/enterprise --- # kenoodl verify, for teams running coding agents at scale Lower costs, faster agents. kenoodl verify is the outside check for coding agents: the agent posts code and the assumption it believes about it, and execution returns HELD, or BROKE at the exact input. It never tells code that satisfies your contract that it is broken. ## The loop you are paying for A coding agent that misses retries from inside the frame that produced the miss. Its own tests pass, the fix fails anyway, and the next attempt is built on the same unexecuted assumption. Every attempt bills like the first. Across a fleet it is a budget line: compute spent re-deriving wrong answers, and engineers pulled in to arbitrate loops the agent could not close. verify is one call from outside the frame. BROKE: the assumption failed, here is the exact input that failed it. HELD: the code was never the problem, stop hacking at it. The agent acts on the verdict and moves. Nobody read the diff. ## The math Every retry bills like the first, and no retry knows more than the last. A verify call is one fixed price and ends the loop from either side. The most expensive loop in a fleet is the one where the code is right: nothing is wrong, so nothing the agent changes can fix it, and the loop has no natural end. HELD is the only signal that stops it. Your number is already in your traces: attempts per resolved task after the agent's own checks passed, times what an attempt costs you. Read your own number. ## Architecture Stateless: code and assumption in, verdict out, nothing retained. No account. Paid per call over x402 on Base; the price arrives in the 402 before any code is sent, and settlement is public record on Base. Deterministic: same code, same assumption, same verdict, and a BROKE arrives with the input that broke it so your own harness can confirm it. verify never tells code that satisfies your contract that it is broken: a checker that never falsely condemns can sit inside the loop and be obeyed. A verdict an agent can act on without a person is a loop that closes without a person. Loops that close on their own compound. ## Next step Point one stuck agent at verify and read the trace it comes back with. Decide from the trace, not from this page. The spec is at kenoodl.com/api. Fleet volume and terms: info@kenoodl.com. --- --- title: kenoodl account url: https://kenoodl.com/account --- # kenoodl is account-free kenoodl verify uses no accounts, keys, or stored balances. Agents call it directly: - Submit code and a claim: POST https://kenoodl.com/api/verify. The unpaid POST returns 402 with the payment requirements; pay 1 USDC via x402 on Base and retry. The verdict returns in the same response (no jobId, no polling). - MCP tool: add kenoodl as an MCP server at POST https://kenoodl.com/mcp. A single verify tool; the verdict returns in the same response. No account, no key. --- --- title: Privacy Policy url: https://kenoodl.com/privacy --- # Privacy Policy Effective February 6, 2026 KENOODL, LLC ("we," "us," or "our") respects your privacy. This Privacy Policy describes how we collect, use, disclose, and protect information when you use kenoodl and our other services (the "Service"). By using the Service, you consent to these practices. For questions, contact info@kenoodl.com. ## How kenoodl Privacy Actually Works kenoodl is architecturally private, not by policy, by design. Here is exactly what happens with your data: - Your code is executed, not stored. When you submit code and a claim, kenoodl runs the code in an isolated, ephemeral sandbox with no network access, and destroys the instance after the run. It is never retained on kenoodl servers. We do not keep it. - The verdict is execution, not a model's opinion. Your code runs in the sealed sandbox and the verdict is what execution reports. Where returning a verdict requires interpreting a plain-language claim, your code and claim may be sent over encrypted HTTPS to a third-party model provider under API terms that prohibit training on inputs. We do not store your code before, during, or after the call. - What we store on our servers: nothing about you. No account, no balance, no prompts, no outputs, no code, no usage content. There is no account to store. - Payments settle on-chain over x402 on Base. There is no card and no payment processor; kenoodl never custodies your funds. - To delete everything: clear your browser data. Your context is gone. We have nothing to delete because we never had it. - API and agent access: kenoodl verify is account-free. When agents or automated systems submit code and a claim via the API, the code is executed in the sealed, ephemeral sandbox and discarded, and is not retained on kenoodl servers before, during, or after. Request metadata (timestamps, verdict, cost) is logged for rate limiting and billing, never the code itself. The rest of this policy covers the legal details. The architecture above is the substance. ## Service Limits Any usage limits we implement involve no personal data storage or tracking; counters are anonymized with no impact on privacy. ## Information We Collect - Submitted code and claims: executed in an isolated, ephemeral sandbox and discarded after the verdict returns. Not retained on kenoodl servers. - No account: there is no registration and no login. kenoodl holds no account, no profile, and no identity for you. - Payment Data: x402 settlements are on-chain on Base and public by nature. There is no card and no payment processor; kenoodl holds no balance. - Device/Usage: browser type, IP (anonymized), for security and risk (e.g., fraud detection); no tracking for ads or marketing. - Feedback: voluntary suggestions; anonymized for improvement. No cookies for tracking; no personal data like name, email, or location unless you include it in what you submit (not recommended; submissions are executed in the sandbox and discarded, never stored). ## How We Use Information We use data solely to: provide and improve the Service; ensure security and detect abuse, fraud, or threats; comply with legal requests and enforce Terms; and conduct anonymized/aggregated analytics or business improvement (no re-identification). No selling or sharing for ads. Data retained only as long as needed (sessions until close; logs up to 30 days for security). ## Sharing Information We share with: providers (Cloudflare for hosting and the isolated sandbox that executes your code; and, where a verdict requires interpreting a plain-language claim, a third-party model provider whose terms prohibit training on inputs); affiliates or business transfers (with notice); and legal authorities if required by law, subpoena, or to protect rights and safety. Payment settles on-chain over x402; there is no payment processor in the loop. No other sharing without consent. ## Your Rights Depending on location (e.g., CCPA/GDPR): access or delete data we have (minimal); delete sessions anytime (clear browser); opt out of anonymized use via info@kenoodl.com; correct or port your info; and exercise rights without discrimination. Requests: info@kenoodl.com (free, respond within 30 to 45 days; verify ID). ## Security We use reasonable measures (sandbox isolation, HTTPS, access controls) but no guarantee; report vulnerabilities to info@kenoodl.com. We notify of breaches per law. ## International Transfers Data processed in the U.S.; if outside, you consent to transfer (adequate safeguards for EU/UK). ## Children Not for under 13; we delete accidental data on notice. ## Changes Updates posted; continued use means acceptance. ## Contact info@kenoodl.com or PO Box 49412, Wichita, KS 67202. --- --- title: Terms of Service url: https://kenoodl.com/terms --- # Terms of Service Effective February 6, 2026 These Terms of Service ("Terms") apply to your use of kenoodl and KENOODL, LLC's other services for individuals, including associated applications, websites, and APIs (collectively, the "Service"). These Terms form an agreement between you and KENOODL, LLC, a Delaware limited liability company ("KENOODL," "we," "our," or "us"), located at PO Box 49412, Wichita, KS 67202. By using our Service, whether directly, through our API, or through an agent or automated system acting on your behalf, you acknowledge and agree to these Terms. We reserve the right to modify these Terms at any time. If you reside in the European Economic Area, United Kingdom, or Switzerland (collectively, "Europe"), your use of the Service is governed in part by the Europe Specific Terms ("EST") in our Privacy Policy. Please read our Privacy Policy, which describes how we collect, use, and disclose personal information. Although it does not form part of these Terms, it is an important document you should read. Another helpful resource is our FAQs that, while not part of these Terms, give further information about our Service. ## Service Limits We reserve the right to implement usage limits to maintain service quality and performance. Access is pure pay-per-call over x402 on Base; there is no account and no stored balance, so there is nothing to deactivate. We may adjust limits as needed without prior notice. ## Who We Are KENOODL, LLC provides kenoodl verify, an outside check for coding agents. An agent submits code and a claim about it, and kenoodl executes the code in an isolated, ephemeral sandbox and returns a verdict on the claim: HELD, or BROKE at the exact input. It never tells code that satisfies your contract that it is broken. The Service is accessed by humans and autonomous agents alike. KENOODL is a separate company from the third-party infrastructure and model providers it uses. ## Access Minimum Age. You must be at least 13 years old or the minimum age required in your country to consent to use the Service. If you are between 13 and 17, you must have your parent or legal guardian's permission, and they must agree to these Terms. Account-free. There is no account, no registration, and no login. Access is pure pay-per-call over x402 on Base: you submit code and a claim, the unpaid request returns a 402 with the payment requirements, and you pay per call at the moment of the call. kenoodl never custodies your funds. If you use the Service on behalf of another person or entity, you must have the authority to accept these Terms on their behalf. No login. There is no third-party sign-in and no account to log into. kenoodl authenticates nothing about you; the payment carried on each call is the only credential. ## API and Agent Access The Service is accessed programmatically over x402 on Base. There are no API keys and no tokens: each call carries its own payment, settled on-chain at the moment of the call. You are responsible for the code and claims you submit and for all charges you incur. When an agent or automated system submits to the Service on your behalf, you remain fully responsible for: (a) all content submitted through the API, including content the agent submits without your direct review; (b) compliance with these Terms, our Acceptable Use Policy, and applicable laws; (c) all charges incurred; and (d) any consequences of the agent's use. Funding an agent to pay for calls on your behalf constitutes your authorization for that agent to act under these Terms. We may impose and adjust rate limits, usage quotas, and other restrictions on API access at any time without prior notice. We may refuse or block access that we determine, in our sole discretion, is being used in violation of these Terms or our Acceptable Use Policy. API access is subject to the same content, output, payment, and liability terms as direct use of the Service. ## Content and Outputs "User Content" means any text, images, or other inputs that you submit to the Service. "Outputs" means any content generated by the Service in response to your User Content. "Content" means both. You own your User Content, and you own the Outputs you receive. We do not claim any license to your Content beyond what is strictly necessary to provide the Service: a limited, non-exclusive license to transmit and process your User Content for the sole purpose of generating and returning your Output, for the duration of that call. We do not store your Content after the call. We do not use your Content or Outputs to train, develop, or improve any model. We do not sell your Content. We share it only as described in our Privacy Policy: transient processing by our infrastructure, and, where a verdict requires interpreting a plain-language claim, a third-party model provider whose terms prohibit training on inputs. We do not build profiles from it. Nothing persists. This is privacy by architecture, described in our Privacy Policy. You represent and warrant that you have the rights to submit your User Content and that it does not infringe third-party rights or violate our Acceptable Use Policy. Outputs are generated by AI and may be inaccurate, incomplete, biased, offensive, harmful, or unreliable (e.g., hallucinations, errors). Outputs are not unique to you and may be similar for other users. Do not rely on Outputs for professional advice, including medical, legal, financial, or safety decisions. Your use is at your own risk. We disclaim all warranties regarding Outputs. ## Data and Privacy See our Privacy Policy for how we collect, use, and disclose personal information. By using the Service, you consent to such processing. We may use anonymized or aggregated data for improvement, research, or other purposes. ## Feedback Any suggestions, ideas, or feedback you provide about the Service is non-confidential and becomes our property. You grant us a perpetual, irrevocable license to use Feedback without compensation or attribution. ## Limitations on Use You agree to comply with our Acceptable Use Policy (incorporated herein). Violating it may result in suspension or termination. We may monitor use to enforce these Terms and report illegal activities to authorities. ## Payments Payments settle on-chain over x402 on Base. Each call is paid at the moment of the call in USDC; there is no account, no stored balance, no credits, and kenoodl never custodies your funds. On-chain settlements are final by nature and are public on the Base network. There is no card, no payment processor, and no chargeback mechanism in the loop. We may change pricing at any time; the price is disclosed in the 402 response before any code is sent. Taxes are your responsibility. ## Limitation of Liability TO THE FULLEST EXTENT PERMITTED BY LAW, WE AND OUR AFFILIATES, PROVIDERS, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, AND LICENSORS WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA, GOODWILL, BUSINESS OPPORTUNITIES, OR USE. OUR TOTAL LIABILITY WILL NOT EXCEED THE GREATER OF $100 OR THE FEES YOU PAID US IN THE 12 MONTHS PRECEDING THE CLAIM. SOME JURISDICTIONS DO NOT ALLOW THESE LIMITATIONS, SO THEY MAY NOT APPLY. THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. ## Indemnification You agree to indemnify, defend, and hold harmless us, our affiliates, providers, officers, directors, employees, agents, and licensors from any claims, damages, losses, liabilities, costs, and expenses (including reasonable attorneys' fees) arising from: (a) your use of the Service; (b) your violation of these Terms or applicable laws; (c) your User Content or Outputs; (d) infringement of third-party rights; or (e) disputes with third parties. ## Disputes and Governing Law You and we agree to waive the right to a jury trial or participation in class actions, collective actions, or representative actions. Any disputes will be resolved through binding arbitration in Wichita, Kansas, under the American Arbitration Association rules, administered by a single arbitrator. You may opt for small claims court in your county of residence for qualifying claims. Governing law is the State of Delaware, without regard to conflicts of law principles. For users outside the U.S., these Terms do not affect mandatory rights under local laws, but you agree to U.S. jurisdiction for disputes and consent to data transfer to the U.S. ## Force Majeure We are not liable for delays or failures due to events beyond our reasonable control, including acts of God, natural disasters, wars, terrorism, riots, embargoes, fire, floods, accidents, pandemics, strikes, shortages, cyber-attacks, or failures of third-party providers. ## Changes and Termination We may modify these Terms or discontinue the Service at any time without notice. Continued use after changes constitutes acceptance. Upon termination, you must cease use; surviving sections include Licenses, Disclaimers, Liability, Indemnification, Disputes, and any accrued obligations. ## Miscellaneous If any provision is invalid, the rest remain enforceable. No waiver of breaches. These Terms are the entire agreement. We may assign these Terms; you may not without consent. Contact: info@kenoodl.com or KENOODL, LLC, PO Box 49412, Wichita, KS 67202. By using kenoodl, you agree. --- --- title: Acceptable Use Policy url: https://kenoodl.com/acceptable-use --- # Acceptable Use Policy Effective February 6, 2026 This Acceptable Use Policy ("AUP") applies to your use of kenoodl and our Service. It is incorporated into our Terms of Service. Violations may result in suspension, termination, or legal action. We may update this AUP at any time; continued use means acceptance. ## Fair Use We reserve the right to implement usage limits to maintain service quality. Circumventing any limits, whether directly, through the API, or through agents or automated systems, violates this AUP. Attempting to bypass limits or abuse the system may result in access being blocked. ## General Rules Use the Service responsibly and lawfully. Do not: - Use for illegal activities or to promote harm (e.g., violence, terrorism, hate speech, discrimination). - Generate or distribute harmful content (e.g., child exploitation, self-harm, graphic violence, or explicit sexual material). - Engage in fraud, deception, or scams (e.g., phishing, impersonation, misinformation campaigns). - Spam, harass, or bully others. - Interfere with the Service (e.g., DDoS, overloading, hacking, reverse engineering, or circumventing usage limits). - Use automated tools to scrape, crawl, or extract data without permission. Note: legitimate use of our API by agents paying per call over x402 is permitted and encouraged; this prohibition targets unauthorized scraping outside the API. - Violate third-party rights (e.g., IP infringement, privacy invasion, defamation). - Use for high-risk activities (e.g., automated decisions in healthcare, finance, legal, safety-critical systems, or weapons). - Develop competing AI or models using our Service or outputs. - Submit sensitive PII, confidential info, or proprietary data in prompts. - Bypass safety features or generate prohibited content (e.g., malware, exploits). ## API and Agent Use If you access the Service through our API (including via AI agents or other automated systems): pay per call over x402 on Base; you are responsible for all activity and all charges under the calls you or your agents make, including content submitted by agents; respect rate limits and do not attempt to circumvent quotas; all API content is subject to the same rules as web content. ## Content Guidelines User Content and Outputs must not: promote illegal goods or services; incite violence, extremism, or radicalization; spread misinformation or deepfakes harming individuals or society; exploit vulnerable groups; or violate laws (e.g., export controls, sanctions). We may monitor and review content for compliance and report to authorities if needed. ## Enforcement We assess violations case-by-case. Consequences: warnings, limits, suspension, termination, or legal referrals. No liability for enforcement actions. ## Report Violations info@kenoodl.com By using kenoodl, you agree to this AUP. --- --- title: Europe Specific Terms url: https://kenoodl.com/eu-terms --- # Europe Specific Terms Effective February 6, 2026 If you reside in the European Economic Area, United Kingdom, or Switzerland (collectively, "Europe"), these Europe Specific Terms ("EST") supplement our Terms of Service and Privacy Policy. In case of conflict, EST prevail for European users. We comply with GDPR, UK GDPR, and Swiss data laws. ## Service Operations Any usage limits involve no personal data collection or tracking; purely operational with no privacy impact. ## Data Controller KENOODL, LLC is the data controller for your personal data. Contact: info@kenoodl.com or PO Box 49412, Wichita, KS 67202, USA. EU representative information available upon request. ## Legal Basis for Processing - Contract: to provide the Service (e.g., execute submitted code, return the verdict, handle x402-paid API requests). - Consent: for optional features (withdrawable anytime). - Legitimate Interests: security and improvement (anonymized data), balanced against your rights. - Legal Obligation: compliance or requests. ## Your Rights Under GDPR/UK GDPR you may access, rectify, erase, restrict, and port data; object to processing; withdraw consent (no retroactive effect); and lodge complaints with authorities (e.g., ICO in the UK). Requests: info@kenoodl.com (free, respond in 1 month; verify ID). ## International Transfers Data to the U.S. under adequacy decisions or Standard Contractual Clauses. Contact for details. ## Retention Session-only; deleted immediately post-use. Logs: up to 30 days for security. ## Automated Decisions No automated decisions with legal effects; a verdict on code is advisory, whether accessed directly or via our API by agents or automated systems. When agents access the Service through our API, the same processing applies: the code is executed in an isolated, ephemeral sandbox and the verdict is returned, and the code is not stored on our servers. Where a verdict requires interpreting a plain-language claim, the code and claim may be processed by a third-party model provider whose terms prohibit training on inputs. Request metadata (timestamps, verdict, cost) is logged for billing and rate limiting under our legitimate interest basis. ## Changes Notified via the Service if material. By using kenoodl, you agree. --- --- title: Cookie Policy url: https://kenoodl.com/cookies --- # Cookie Policy Effective January 13, 2026 KENOODL, LLC uses no cookies for tracking or analytics in kenoodl (the "Service"). This Policy explains our use of local storage technologies. By using the Service, you consent to these practices. See our Privacy Policy for more. ## Service Operations Any usage limits involve no cookies or tracking; purely operational with no privacy impact. ## What We Use kenoodl sets no tracking cookies. The only browser storage is PWA caching (service workers for offline access of essential static files only). There is no account, no login, and no session tokens. No third-party cookies, ads, or analytics. No data shared for profiling. ## Why We Use Them Strictly necessary for Service operation, e.g., maintaining sessions without servers. ## Your Choices Disable in browser settings (may break the Service). Opt-out requests: info@kenoodl.com (minimal impact since no tracking). ## Changes Updates posted; continued use means acceptance. ## Contact info@kenoodl.com or PO Box 49412, Wichita, KS 67202. --- --- title: Brand Guidance url: https://kenoodl.com/brand-guidance --- # Brand Guidance Effective January 13, 2026 Guidelines for using kenoodl branding. For press inquiries, contact info@kenoodl.com. ## User References Users may reference kenoodl in feedback and reviews; fair use is welcome, but do not imply endorsement or partnership. ## Name and Style "kenoodl" is always lowercase, even at the start of a sentence. The legal entity is KENOODL, LLC. ## Logos and Marks The kenoodl logo (the OO mark) and KENOODL wordmark are trademarks; use only with permission. No modifications (color, size, distortion). ## Colors - Near Black: #111111 (background) - Off White: #F5F5F5 (primary text) - Gold: #D4A520 (interactive: buttons, links, hover states) - Octopus Blue: #5BA4C9 (structural: logo mark, section labels, card titles) Gold for anything a user or agent clicks. Octopus blue for structural identity, the OO mark, headings, labels. The blue is inspired by the blue-ringed octopus. ## Usage Rules - No implying endorsement or partnership without agreement. - Use in fair reporting or reviews OK; no commercial exploitation. - Attribute: "kenoodl by KENOODL, LLC". - No confusingly similar marks or domains. ## Violations May result in legal action. Report misuse: info@kenoodl.com.