Privacy policy

This policy describes what laya-model.com stores, the cookies the site and its vendors use, and how to reach the operator. It was last updated on 8 October 2026.

laya-model.com is an independent community site. It hosts a prepaid decide API, a tools playground, and notes for running the Apache-2.0 Laya weights yourself. It is not an official Convai product, and it is not affiliated with Convai Innovations, NandhaKishorM, or TypeSafe. It is not the LayaAir game engine. Questions about this policy go to support@laya-model.com or the contact page.

Information we collect

Sign-in uses Google. There is no email and password form. When you register, we store the account email, name, profile image URL, and Google subject identifier. We keep those fields so we can attach API keys, the prepaid balance, and the monthly grant to the same account. We do not receive your Google password.

API keys use the laya_ prefix. The full secret is shown once, when you create it. After that we store a SHA-256 hash and a short prefix so the account page can list the key. We cannot show the secret again. You can revoke a key on the account page. Calls made with a revoked key are rejected.

Decide calls that bill an account write a usage row. That row stores the route, the input-token count, the cost, and the time. We do not put the prompt text, the state body, or the question text into the usage ledger. The text of a live call is sent to the upstream inference host so it can return choice, score, and noul answers. Do not send secrets you cannot share with that host. The browser does not call the upstream directly. The server holds the inference key.

Anonymous free runs are counted with a cookie named laya_anon. The value is a random id. It is not tied to a Google account. The cookie is HttpOnly, SameSite=Lax, and kept for up to a year so the free-run counter survives a refresh. The default allowance is one successful anonymous decide call. That number can be changed with the server setting ANON_FREE_RUNS.

Card payments are processed by Creem, or by Stripe if this deploy is switched to Stripe. We store the order id, the pack id, the amount, the provider, and whether the order was paid. We do not store your card number, card expiry, or card security code. The browser return URL after checkout does not add credits. A paid notification on the server webhook does, after the signature matches.

Cookies we set

Besides laya_anon, a signed-in session uses an Auth.js session cookie. The session is a signed token that keeps the account page logged in. It is not your API key. Signing out of the browser ends that session on this device. Revoking a key is separate, and is done on the account page.

We use these cookies to run the product: to know which account is signed in, to enforce the anonymous free run, and to keep a request on the same session while you create a key or start checkout. We do not use them to read the contents of a decide request.

Analytics

This site uses Google Analytics 4 (GA4). The measurement id is the value configured for the site. When that setting is left unset, the tag falls back to G-NYHT3H3EYP. The GA4 tag loads from the root layout and sends a page view on the first load and again when you move between pages in the browser. GA4 uses cookies, including cookies named like _ga, to distinguish browsers and to measure traffic.

We also send a small set of product events: view_home, click_playground, run_live, run_demo, copy_install, click_github, and click_hf. Those events record that a control was used. They do not include the text of a decide request, an API key, or a payment card number. run_live records whether the call returned ok. It does not record the ticket you pasted.

Plausible is optional. It loads only when NEXT_PUBLIC_PLAUSIBLE_DOMAIN is set. The script we use is the standard Plausible script, which does not set a cookie. If it is enabled, it receives the same event names as GA4. If the variable is blank, Plausible stays off.

You can block GA4 with your browser, with a content blocker, or with the Google Analytics opt-out add-on published by Google. Blocking analytics does not block the decide API. The API uses the session cookie or the laya_ key, not the analytics cookie.

Advertising cookies

This site may show advertisements. Third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website and other websites.

Google's use of advertising cookies enables it and its partners to serve ads to users based on their visit to this site and other sites on the Internet. Those cookies can record that a browser was here and can use that fact, together with earlier visits, to choose and measure ads. We do not send the text of a decide request, an API key, or a card number to an ad vendor as part of that process.

You can opt out of personalized advertising by visiting Google's Ads Settings. You can also opt out of some third-party vendors' use of cookies for personalized advertising at www.aboutads.info. Those pages are run by Google and by the Digital Advertising Alliance, not by this site. Opting out of personalized ads does not turn off the decide API, and it does not by itself delete the account data described above.

When a Google AdSense publisher id is configured on the server, this site publishes an ads.txt file that names Google as an authorized seller of the site's ad space. Until that id is set, /ads.txt is not published. Advertising cookies are a function of the ads a vendor serves. They are separate from the laya_anon cookie and from the sign-in session.

How we use and share information

We use account data to sign you in, to issue and check API keys, to apply the monthly input-token grant, to meter prepaid calls, and to credit a pack after a paid checkout. We use the usage rows to show recent calls on the account page and to enforce rate limits and the hourly and daily input-token caps. We use analytics to see which pages and controls are used. We use advertising cookies, as described above, to allow vendors including Google to serve and measure ads.

We do not sell your personal information. We share it with the processors that perform the functions above: Google, for sign-in, GA4, and advertising; the inference host that answers a decide call; and Creem or Stripe, for card checkout. A decide request is sent to that inference host. The usage ledger on this site does not keep a copy of the prompt.

We keep account, key, and usage rows for as long as the account exists so the product can bill and can show history. There is no self-serve delete button. Email support@laya-model.com if you want the stored profile, keys, and usage rows removed. Revoke keys on the account page in the meantime. Payment records may be kept as needed for the charge that already happened. We do not keep card numbers in any case, because we never receive them.

Children

The site is a developer tool for routing and labeling text. It is not directed at children, and we do not knowingly collect personal information from children. If you believe a child has signed in with Google and created an account here, email us and we will delete the rows we store.

Contact

Operator contact: support@laya-model.com. The contact page explains what to include and what not to send. The about page describes what this site operates. The terms cover the prepaid API. This policy may be updated as the product changes. The date at the top is the latest revision.

Privacy · Laya AI