Plays — Privacy Notice

Last updated: October 8, 2026

This notice covers Plays by Moat8, the public AI workflow library and its AI guide at moat8.space/workflows. Moat8 LLC operates Plays. The separate Moat8 Data Vault Privacy Policy covers the Vault application and connected accounts; its conversation-retention and model-training commitments must not be assumed to apply to Plays.

What you share with the AI guide

When you send a message, Plays sends your message, the recent conversation supplied by the page, any selected business activities and industry, relevant public workflow instructions, and any company website context to NVIDIA's hosted language-model API. The request passes through the Plays application hosted on Railway. You do not need a Vault account to use this guide.

If you provide a company website, the application may read public pages on that website and send selected text, page titles and source URLs to the model to help explain possible workflows. These are public observations, not verified knowledge of the company's internal processes. The visited website receives an ordinary server request. Plays does not sign in to that website or connect to your private company systems.

Plays does not receive your Vault session cookie or authorization through the site's workflow proxy, and it has no connection to your Vault's files, sources or credentials. Anything you type or paste into Plays is nevertheless sent to the model as described above. Do not include credentials, private documents or personal information you are not authorized to share; the guide does not provide the Vault help assistant's credential-masking guarantee.

Providers and their handling of messages

Railway hosts the Plays application; NVIDIA processes model requests and generates replies. Provider-side handling is governed by the applicable service agreements and provider policies. NVIDIA's standard API Trial Terms permit use of submitted and generated content to improve products, including AI models. This notice does not promise zero retention or a no-training arrangement with NVIDIA. See NVIDIA's Privacy Policy and Railway's Privacy Policy.

Browser state, caching and operational logs

The page keeps its chat history and current company context in browser memory. The Plays application does not write a conversation-history database. Saved workflow identifiers and selected activities are kept in this browser's local storage; you can remove them through the library controls or your browser's site-data settings.

The server temporarily caches public website research in process memory to avoid repeated fetching. Application logs record operational information such as request identifiers, timing, error codes and rate-limit events, without recording chat text, model answers, company URLs or source-page contents in those log events. Network addresses are used to enforce usage limits. Hosting and model-provider logging and retention are separate from application logging; the Vault's thirty-day conversation-deletion rule does not apply here, and no provider-specific deletion period is promised by this notice.

Library usage measurement

Plays measures library use only after you choose to accept optional analytics. If you accept, it records page views and selected actions such as workflow saves, skill previews or downloads, and guide requests, together with timestamps, public workflow identifiers, page categories, the site's canonical hostname and broad acquisition categories. The Plays server forwards these limited events to PostHog in the EU. Analytics events do not include chat messages or replies, search text, company URLs, URL query strings, full referring URLs, credentials, visitor IP addresses, geographic enrichment or browser fingerprints. We do not create person profiles or make session recordings.

Analytics uses local storage, not cookies. Your choice lasts for up to 90 days. If you accept, a random visitor identifier is stored in this browser and expires with that choice; a random session identifier changes after 30 minutes of inactivity or a maximum of 24 hours. These identifiers let us count consenting browsers and their visits and actions; they do not tell us a visitor's name or account. Clearing browser site data or using a different browser changes how visits are counted. Earlier aggregate events used a separate random identifier for each event and did not support unique-visitor counts.

Before acceptance, after declining or withdrawing consent, or when the browser sends Do Not Track or Global Privacy Control, Plays sends no library analytics events and clears any analytics identifiers. You can change your choice through Analytics settings in the library footer. Plays does not use the landing page's analytics cookie. The landing website's analytics settings and the Vault's account-linked analytics are described separately in the Vault Privacy Policy.

Questions and choices

You can browse workflows without submitting a chat message or a company website. Clear browser site data to remove locally saved selections. For questions about Plays data handling or a data request, contact legal@moat8.ai and identify Plays as the product; do not send passwords or API keys.

Moat8 LLC, 30 N. Gould St, Ste R, Sheridan, WY 82801, USA.