Skip to content
YAKKL
ProductHow it worksComparePricingDownloadFounder's Program
Get started
← All legal documents
Privacy

YAKKL Privacy Policy

How YAKKL collects, uses, discloses, retains, and protects personal data.

Version 1.2 Effective October 10, 2026 Updated October 26, 2026

This Privacy Policy explains how YAKKL, Inc. ("YAKKL," "we," "us," or "our") collects, uses, discloses, and protects personal data when we act as a controller or business for YAKKL websites, individual accounts, self-service Services, sales, marketing, support, billing, security, and our own business operations.

This Policy does not govern personal data in Customer Data that YAKKL processes solely on behalf of a business customer as its processor or service provider. That processing is governed by the customer's agreement and YAKKL Data Processing Addendum ("DPA"). If your employer or another organization provides your YAKKL workspace, consult that organization; its administrators may control your account, settings, Content, and activity records.

"Services" means YAKKL software, applications, websites, AI development and orchestration features, Ari features, APIs, cloud storage, model routing, managed execution, BYOK/custom-endpoint capabilities, deployment, hosting, support, and related services.

Contents

  1. 1. Data paths matter
  2. 2. Personal data we collect
  3. 3. How we use personal data
  4. 4. De-identified Usage Data
  5. 5. Legal bases for processing
  6. 6. How we disclose personal data
  7. 7. AI providers and changing vendors
  8. 8. Retention and deletion
  9. 9. Cookies and website technologies
  10. 10. Security
  11. 11. International data transfers
  12. 12. Your rights and choices
  13. 13. Children
  14. 14. Third-party services and public content
  15. 15. Changes
  16. 16. Contact

1. Data paths matter

YAKKL is designed to support multiple data paths:

  • Local use. Content stored and processed only on your device or environment is not collected by YAKKL. The application may separately send operational telemetry, diagnostics, and usage data described in Section 2.B; that data is designed to exclude Content. Paid YAKKL software also confirms its license with YAKKL's license service as described in Section 2.D; that check does not include Content.
  • Direct BYOK. BYOK defaults to direct routing unless you select another supported route. When a customer-controlled client sends a request directly to a customer-selected provider using customer credentials, the request and response payloads (prompts, Content, and completions) travel from the client to that provider, and YAKKL does not receive those payloads merely because the YAKKL client initiated the connection. Operational telemetry, diagnostics, and usage data described in Section 2.B may still be sent to YAKKL and are designed to exclude Content.
  • Custom endpoint. If you choose your own endpoint, its operator controls the data it receives under its terms.
  • YAKKL cloud or managed routing. When you enable YAKKL cloud storage, logs, retrieval, managed execution, or hosting, YAKKL and applicable service providers process the data required for those features.
  • Hybrid use. A workflow may combine these paths. Settings, product notices, usage records, or documentation identify the applicable path at a level reasonably sufficient for your choices.

2. Personal data we collect

The data collected depends on the Services and settings you use.

A. Data you provide

  • Account and profile data: name, username, email address, authentication method, organization, role, preferences, and account identifiers.
  • Billing data: billing name, email address, billing address, phone number if you give one to the payment processor, plan, price, purchases, invoices, payment status, tax information, and transaction identifiers. You enter payment-card or bank details on the payment processor's page; YAKKL does not receive the full card number or security code. The processor tells YAKKL the card brand, last four digits, issuing country, card type (credit, debit, or prepaid), a processor-generated identifier for the card, the results of its security-code, address, postal-code, and 3-D Secure checks, and its fraud-risk assessment of the payment.
  • Customer Content: prompts, responses, messages, source code, repository content, files, plans, artifacts, uploads, feedback, hosted content, and other material you choose to send to YAKKL-controlled cloud or managed Services. Customer Content may contain personal data.
  • Support and communications: messages, attachments, call or meeting records where disclosed, survey responses, security reports, and other communications. YAKKL keeps a record of each email it sends you about a purchase, subscription, license, payment, refund, dispute, or support request, including the full text and whether it was delivered. Messages sent through the contact form are kept together with the name and email address you gave and the IP address, country, and browser they were sent from.
  • Sales and business contacts: employer, title, business contact details, purchasing interests, and relationship records.
  • Marketing choices: subscriptions, consent records, event registrations, and communication preferences.

B. Data generated through the Services

  • Actions and tool records: tool calls, commands, file or repository operations, approvals, deployments, integrations, third-party service interactions, results, timestamps, and audit records for cloud or managed features.
  • Usage and metering data: features used, model/provider selected, execution mode, request timing, approximate input/output or work measurements, CU consumption, retries, cache behavior, latency, errors, and reconciliation records.
  • Logs and diagnostics: IP address, device and application information, operating system, browser, version, crash data, performance, security events, and error logs.
  • Security and fraud-prevention signals: device and connection characteristics and interaction signals collected during sign-up, sign-in, and checkout (such as challenge responses and input timing and movement patterns) used solely to detect automated activity, fraud, and unauthorized purchases, and retained only as long as needed for those purposes.
  • Cloud workspace data: conversation history, plans, indexes, embeddings, caches, artifacts, workspace membership, permissions, and retention settings when enabled.
  • Hosted-service data: domains, deployment configuration, content, traffic records, and security logs when you use hosting.

C. Data from others

We may receive data from identity providers, model or infrastructure providers, integrations you connect, business-account administrators, payment processors, analytics and communications providers, security vendors, public sources, and business partners. The data depends on the connection and your settings.

D. Purchase, license, and delivery records

When you buy and use paid YAKKL software, YAKKL keeps the records below. They show what was bought, what was agreed to, that the software was delivered, and that the license was used.

  • Checkout records. When you start a purchase on a YAKKL website: the date and time; your IP address and the country derived from it; your browser's user-agent and language setting; the email address you entered, if any; the plan, billing interval, and price; and the legal documents you were shown and accepted, recorded by name, version, and a cryptographic hash of the exact text. A checkout that is started but not completed is also recorded.
  • Payment and subscription events. Notices from the payment processor about each payment, renewal, failed payment, invoice, cancellation (including any reason or comment you gave), refund, payment dispute, and fraud warning from a card issuer, with the processor's identifiers for the customer, subscription, invoice, and charge.
  • License records. A license identifier tied to your subscription and email address, its status, and how many devices it is active on. YAKKL stores a one-way hash of your activation code, not the code itself.
  • Activation records. When you activate a license in YAKKL software, the software sends your activation code, a device identifier, the public half of a signing key the software creates on your device for this purpose, the operating system and processor type, the YAKKL version, whether you used the desktop application or the command line, and the legal documents you accepted in the software (name, version, and hash). YAKKL records these with the date and time, your IP address, and the country derived from it. The device identifier is a one-way SHA-256 digest computed on your device from its host name, operating-system user name, operating system, processor type, and machine identifier. Those underlying values, and the private half of the signing key, are not sent to YAKKL.
  • License checks. While a license is active, a YAKKL background service on your device contacts the license service about once a day, whether or not the YAKKL application is open. Each check sends the license key stored on the device, the device identifier, the operating system and processor type, the YAKKL version, and whether the application was opened since the previous check. Each check is signed with the device's signing key and encrypted to the license service. YAKKL records the date and time, IP address, and derived country of the most recent check for each device, a count of checks, and one dated entry per device per day, marked as either a day the application was opened or a background check only. A license check does not include prompts, responses, source code, files, repository names, commands, or any other Content. The check is also how the software learns that a subscription has ended or a license has been suspended or revoked; when that happens the software removes the license key from the device and stops running paid features.
  • Download and delivery records. When you open the personal download page linked from your purchase confirmation, or download an installer from it: the date and time, IP address, derived country, browser user-agent, and the version and platform downloaded.
  • Dispute responses. If a charge is disputed, YAKKL emails you a personal link. When that link is opened, and when you use the page to cancel your subscription or to tell us the dispute was a mistake, YAKKL records the date and time, IP address, derived country, browser user-agent, what you chose, and the exact statement shown to you if you confirmed the dispute was a mistake.

The license key, the device's signing key, and a small activation record (license identifier, activation date, accepted document versions, the time and result of the last license check, and when the application was last opened) are stored in files on your device. They are removed from the device when you deactivate it.

3. How we use personal data

We use personal data to:

  • provide, personalize, maintain, route, secure, and support the Services;
  • authenticate users; administer accounts, workspaces, subscriptions, seats, and permissions;
  • process payments, CU usage, reconciliation, taxes, and invoices;
  • issue, activate, verify, renew, suspend, and revoke licenses, and apply device limits;
  • deliver software, purchase confirmations, renewal and payment notices, and other transactional messages;
  • keep records showing that a purchase was authorized, which terms were accepted, and that the software was delivered and used, and present those records when a charge is disputed or reported as fraudulent;
  • execute instructions, tool calls, deployments, storage, retrieval, and hosting selected by users;
  • detect, investigate, and prevent fraud, abuse, security incidents, and policy violations;
  • diagnose failures, improve reliability, allocate capacity, and understand feature and model usage;
  • communicate about transactions, security, legal changes, support, and Service updates;
  • send marketing where permitted and honor preferences;
  • comply with law, enforce agreements, establish or defend legal claims, and respond to lawful process;
  • protect people, YAKKL, customers, and third parties; and
  • conduct corporate transactions, diligence, accounting, audit, and business administration.

No AI training. YAKKL does not use Customer Content or Output to train AI models and does not authorize third parties to do so on YAKKL's behalf. Product analytics and de-identified Usage Data do not include Customer Content.

Limited personnel access. YAKKL personnel do not inspect Customer Content as part of ordinary product analytics. Personnel access is limited to support you request, security or abuse investigation, legal compliance, or operation of a managed feature that cannot be provided through automated processing alone. Access must be authorized and appropriately logged or recorded.

Automatic license suspension. When a card issuer tells YAKKL's payment processor that a charge is disputed, YAKKL's systems automatically suspend the affected license and pause further billing on that subscription while the dispute is open, as described in the Subscription and Credit Unit Terms, and email you a link to cancel the subscription or to tell us the dispute was a mistake. If the dispute is decided against YAKKL, the license is revoked and the subscription is cancelled. You may ask for a person to review the suspension by writing to support@yakkl.com.

4. De-identified Usage Data

YAKKL may aggregate or de-identify Usage Data so it cannot reasonably identify you, a user, or an organization. YAKKL may own, retain, and use that data for feature analytics, model-selection statistics, traffic, capacity, reliability, security, routing, product planning, and billing operations. YAKKL will not attempt to re-identify it except to test and improve de-identification safeguards or as required by law.

When de-identifying data, YAKKL applies reasonable technical and organizational measures appropriate to the data and re-identification risk.

5. Legal bases for processing

Where a legal basis is required, we process personal data as follows:

  • Contract: to provide requested Services, administer accounts, process purchases, issue and verify licenses, deliver software and transactional messages, and perform our agreements.
  • Legitimate interests: to secure and improve the Services, prevent abuse, prevent payment fraud and unauthorized use of licenses, keep and present evidence that a disputed charge was authorized and the software was delivered, support customers, manage the business, communicate about related Services, and establish or defend claims, balanced against individual rights.
  • Consent: for optional cookies, certain marketing, and other processing where consent is requested. Consent may be withdrawn prospectively.
  • Legal obligation: to comply with tax, accounting, sanctions, regulatory, law-enforcement, and other legal duties.
  • Vital interests or public interest: when necessary to address an emergency or another legally recognized public-interest basis.

6. How we disclose personal data

We may disclose personal data to:

  • Service providers and subprocessors supporting AI model execution, cloud infrastructure, hosting, storage, security, identity, analytics, support, communications, payment processing, tax, compliance, and IT. The service-provider register identifies current providers and their purposes. The email delivery provider receives the recipient address and content of each message YAKKL sends, and the database and hosting providers store the records described in Section 2.
  • Payment processors, card networks, and card issuers. When you start a purchase, YAKKL sends its payment processor the email address you entered, the plan and price, a checkout reference, the versions of the legal documents you accepted, and the country the purchase came from; you give the processor your payment and billing details directly. If a charge is disputed or reported as fraudulent, YAKKL may give the processor (which passes it to the card network and the card issuer) your name, email address, billing address, the IP address used for the purchase, the terms you accepted and when, the messages exchanged with you, and your download, activation, and license-check records, and anything you did from the dispute link YAKKL emailed you, as evidence that the charge was authorized and the software was delivered.
  • Customer-selected third parties when you direct a BYOK request, custom endpoint, integration, deployment, repository operation, communication, or other Action.
  • Business-account administrators who can manage the workspace and may access Content, activity, settings, billing, and account information according to their permissions.
  • Other users and the public when you share, collaborate, publish, deploy, host, or make Content public.
  • Professional advisers and transaction parties for legal, accounting, audit, insurance, financing, merger, acquisition, reorganization, bankruptcy, or asset-sale purposes under appropriate duties.
  • Authorities and other parties when reasonably necessary to comply with law or lawful process; protect rights, safety, and security; investigate fraud or abuse; or enforce agreements.

YAKKL does not sell personal data and does not share personal data for cross-context behavioral advertising. YAKKL does not use personal data for targeted advertising or place third-party advertisements in the Services. Before changing these practices, YAKKL will update this Policy and provide legally required choices.

7. AI providers and changing vendors

YAKKL maintains a service-provider register identifying current YAKKL-controlled service providers/subprocessors, their purpose, processing location where relevant, and update date.

For direct BYOK and custom endpoints, you select the recipient. Its own terms, retention, safety review, and privacy practices apply. YAKKL cannot control or guarantee those practices.

For YAKKL-managed routing, applicable providers act under YAKKL's commercial and data-processing arrangements where required. Providers may use automated safety classifiers. Content flagged for suspected abuse may be retained and reviewed by authorized personnel for the limited time reasonably necessary to investigate, secure the Services, enforce policy, or comply with law. Abuse review does not permit model training.

8. Retention and deletion

YAKKL retains personal data only as long as reasonably necessary for the purposes described, considering the Service and plan selected; customer settings and deletion requests; sensitivity and risk; security, fraud, and abuse needs; legal, accounting, tax, and contractual requirements; backups; disputes; and limitation periods.

  • Customer Content stored only on your device remains until you delete it.
  • Customer Content stored in YAKKL cloud follows the retention period shown for the plan, workspace, or feature. You may delete eligible Content through available controls at any time.
  • A plan downgrade may shorten future retention. YAKKL will provide reasonable notice or export opportunity where practicable.
  • Detailed purchase, subscription, invoice, payment, refund, and financial dispute records, together with the customer and transaction identifiers needed to interpret them, are retained for as long as needed for ongoing accounting, tax, audit, and historical business analysis, including year-over-year comparisons. YAKKL does not automatically delete these accounting records based on age or replace them with only summary totals. This includes raw payment-processor notices, reconciliation records, records of the terms you accepted, your license record, and messages documenting purchases, payments, refunds, or financial disputes.
  • License activation, license-check, download, download-page, and dispute-link interaction records, including the IP addresses in them, are kept for 24 months after they are recorded. The record of a device is kept while the device is active on a current subscription and for 24 months after it is deactivated or the subscription ends. Financial records of a disputed charge, its outcome, and any related refund remain part of the accounting records described above.
  • Records of a checkout that was started but not completed are deleted after 90 days. Non-billing support messages from someone who has not made a purchase are deleted after 24 months. Non-billing support messages from a customer are kept for three years after the last subscription ends or the last invoice, payment, refund, or dispute on the account, whichever is later, and for at least three years after the message was recorded. Messages documenting accounting matters remain part of the accounting records described above.
  • YAKKL deletes records subject to the fixed periods above on a weekly schedule once the period has passed. A record is kept longer while a payment dispute on the account is open, or where YAKKL is required to preserve it for a legal claim, a tax or regulatory inquiry, or another legal obligation. YAKKL keeps a log of each deletion run that records what kind of records were deleted, how many, and when, without the deleted data.
  • Deleted data may remain for a limited time in encrypted backups, security records, legal holds, billing records, or incident evidence before deletion or de-identification.
  • De-identified Usage Data that is no longer personal data may be retained indefinitely.

The cloud retention period for your plan is shown in the Service and included in the applicable order. Changes to those periods apply prospectively and remain subject to this Policy.

9. Cookies and website technologies

YAKKL uses essential technologies to operate, secure, and remember choices on its sites. With consent where required, YAKKL may use analytics technologies to understand site use. Where consent is required, YAKKL will not enable analytics technologies until you give consent. The Cookie Notice and consent center describe current categories and vendors.

Payment, email signup, anti-abuse, and content-delivery providers may process data when you choose the relevant service even if they are not advertising or analytics cookies.

10. Security

YAKKL uses reasonable administrative, technical, and organizational safeguards appropriate to the nature and risk of personal data. No system is completely secure. You are responsible for protecting devices, accounts, credentials, BYOK keys, custom endpoints, repositories, permissions, and backups under your control.

Report suspected vulnerabilities to security@yakkl.com. Do not send credentials or unnecessary personal data in a report.

11. International data transfers

YAKKL is based in the United States and may process data in the United States and other countries where YAKKL or its service providers operate. Laws in those countries may differ from your location.

Where required, YAKKL uses recognized transfer mechanisms such as adequacy decisions, the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum or other lawful UK mechanism, and supplementary safeguards. Business-customer transfers are addressed in the DPA.

12. Your rights and choices

Depending on where you live and applicable law, you may have rights to:

  • know or access personal data and processing information;
  • receive a portable copy;
  • correct inaccurate personal data;
  • delete personal data;
  • object to or restrict processing;
  • withdraw consent;
  • opt out of sale, sharing, or targeted advertising;
  • limit certain uses of sensitive personal data;
  • not be subject to solely automated decisions with legal or similarly significant effects;
  • appeal a denied privacy request; and
  • lodge a complaint with a data-protection authority.

YAKKL will not discriminate against you for exercising applicable rights. Submit a request to privacy@yakkl.com or through available account controls. We may confirm identity and authority. An authorized agent may submit a request where law permits. If we deny a request, you may appeal by replying with "Privacy Appeal."

Some data may be exempt, and certain data must be retained for security, billing, legal, or other lawful reasons. For example, YAKKL keeps purchase, terms-acceptance, license, and communication records for the periods in Section 8 even after a deletion request, where it needs them to comply with tax and accounting law or to respond to a payment dispute or legal claim. If YAKKL processes data only for a business customer, direct your request to that customer; YAKKL will assist as required by the DPA.

You may unsubscribe from marketing emails using the link in the message. Account, security, billing, and legal communications may continue. Cookie choices may be changed through the consent center.

13. Children

The Services are not directed to people under 18, and YAKKL does not knowingly collect personal data from children through the Services. Contact privacy@yakkl.com if you believe a child provided personal data.

14. Third-party services and public content

This Policy does not govern independent third-party services, customer-selected providers, custom endpoints, integrations, websites, or public repositories. Review their policies before sending data. Information you publish or share publicly may be copied and retained by others beyond YAKKL's control.

15. Changes

YAKKL may update this Policy as Services, data practices, vendors, or law change. We will update the effective date and provide additional notice for material changes where required. We will request consent before materially different processing when law requires it.

16. Contact

  • Privacy questions and rights: privacy@yakkl.com
  • Support: support@yakkl.com
  • Legal notices: legal@yakkl.com
  • Security reports: security@yakkl.com

YAKKL, Inc.

Thank you. We look forward to keeping you updated.
Your subscription could not be saved. Please try again.

Launches, pricing windows, and platform updates. No spam.

YAKKL

Discipline for AI-written code.

X GitHub TikTok

YAKKL

Product Orchestration Compare harnesses Download Security

Buy

Pricing Credit Units Founder's Program Get Orchestrator

Company

About Security Contact Brand & press

Resources

Blog FAQ Support Media Legal

© 2026 YAKKL, Inc. All rights reserved.

YAKKL® is a registered trademark of LambdaStack, LLC, used under license by YAKKL, Inc.