Your data, clearly explained.

Who operates Yield

Yield is operated by Yield Intelligence Labs, Colorado, United States. Leonard Industries is the product’s parent brand. Contact support@yieldintelligencelabs.com for privacy questions or requests. This notice covers the Yield website and business application.

Information we handle

We handle account information such as your email address, name, business membership and role; uploaded CSVs and their processed Parquet and preview copies; business context; questions, answers, result tables, source references and query details; private preferences and response ratings; support request subjects, categories, descriptions, replies, related request references, contact details, and status history. For API integrations we handle key labels, permissions, hashed credentials, last-use times and operational audit events. Service providers also process technical information such as IP addresses, request identifiers and security events. Do not upload highly sensitive data, including health records, payment-card details, government IDs or passwords.

Why we use it

We use this information to authenticate members, provide business workspaces and data analysis, maintain conversations and explicit preferences, enforce permissions and usage limits, provide support and protect the service. We do not sell uploaded business records or use them for advertising. The public site does not use marketing analytics, advertising trackers or session replay.

AWS and OpenAI

AWS hosts our application, identity, database, file storage and operational services in us-east-1. OpenAI’s API generates answers and conversation summaries. Requests may include your question, recent conversation and older-turn summaries, business context, private preferences, selected dataset schemas and bounded query results. We do not upload the original CSV or Parquet files to OpenAI. Sending bounded results can still disclose individual records. We do not promise that every service provider processes data exclusively in the United States.

AI retention and training

We request that OpenAI not store Responses API application state, including when summarizing older conversation turns. This is not a zero-retention guarantee: OpenAI describes separate abuse-monitoring retention, normally up to 30 days with stated exceptions. OpenAI says API data is not used for model training unless its customer opts in. Yield has not enabled optional training or evaluation sharing for its project. No independent zero-data-retention approval is claimed. Yield’s private memory updates prompt context, not model weights.

OpenAI API data controls ↗

Product inquiries, integrations and consultations

If you contact us through the public inquiry or Yield Integrations form, we store your name, email, business details, stated needs, any optional data/integration information you provide and your plan interest. Authorized employees use these details, inquiry history, internal notes and contact status to respond and arrange consultations. Public contact details are unverified. General leads and integration requests have separate employee follow-up records; submitting either form does not create an account, subscription or project order. Repeat inquiries attach to the same email address without exposing previous information publicly. We use Cloudflare Turnstile to deter automated abuse; Cloudflare processes technical signals for that check. Our abuse counters keep short-lived keyed identifiers rather than raw IP addresses. Lead records are removed after 12 months without a new inquiry, employee note or status change, or sooner after a verified deletion request. Temporary retry/deletion blocks remain for up to 24 hours and deletion case receipts for 30 days. Notification metadata may remain for up to 90 days, subject to cleanup; already-delivered email copies are separate. We notify our team rather than automatically emailing the unverified visitor, and do not send inquiry content to AI or add visitors to marketing campaigns.

Customer support

Support tickets are private to the requester within the selected business and authorized Yield employees. Other business members, including business admins, do not automatically see them. We store requests and replies to provide support and retain open and closed history until verified account or business deletion. Employees use a separate, restricted sign-in to manage support. Notification emails contain a request reference and sign-in link rather than the ticket text. Notification delivery records and employee access audit events are retained for 90 days, short-lived delivery feedback for up to 24 hours, and notification queues may retain operational email metadata for up to 14 days. Already-delivered emails remain subject to the recipient and mail provider retention policies. Email replies are handled manually and do not automatically become ticket replies. Do not include passwords, access keys, or sensitive records in support requests. The support workflow does not send ticket content to an AI assistant.

Support diagnostics

When enabled, restricted employee support diagnostics record request references, business names and business/member identifiers, predefined operation and error codes, status, timing and application version. These records help us investigate reported failures without copying prompts, answers, uploaded values, filenames, private memory, credentials or ticket conversations. Diagnostic events are retained for 90 days and removed with verified account or business deletion. Employee access is audited. This is operational support information, not advertising tracking or session replay; missing events do not prove that a request succeeded.

Subscriptions and payments

Stripe processes subscription payments and receives the billing information you enter in its payment fields. Yield stores subscription identifiers, plan and payment status, period dates and operational billing records. Yield does not receive full card numbers or security codes. Stripe may use essential payment and fraud-prevention technologies in checkout. After paid access ends, business content remains recoverable read-only for 30 days before safe cleanup, with notices beforehand. Independent member accounts and required billing records remain. Financial record retention is separate from deletion of uploaded business content.

Who can access what

Authorized business members can query their business’s ready datasets. Owners/Admins manage membership, and Owners/Admins and Data Managers manage datasets and shared context. Each member’s conversation, explicit private preferences and ratings are private to that member within that business through the application. Authorized operators and infrastructure providers can have administrative access for operating, supporting and securing the service; this is not end-to-end encrypted storage.

External AI connections, when enabled

Yield MCP is an optional connection to an external AI application. Each authorized member signs in to Yield and consents to access for one business and either all ready datasets, including future datasets, or a fixed selection. Shared business context is a separate permission, off by default. The connected application and its AI provider receive returned schemas and query results; their terms, privacy practices and retention apply to those copies. Private Yield chats and member memory are not provided. Business owners can restrict members and revoke connections; revocation stops new requests but cannot retract previously returned information. We store hashed authorization credentials, consent and connection metadata, query counters and sanitized operational events. Detailed MCP usage and access events are retained for 90 days; verified deletion removes credentials and identifying member links while anonymous allowance totals remain. Your external AI subscription is separate from Yield MCP.

Partner and service connections, when enabled

A customer Owner/Admin can separately approve a named partner delegation and its dataset scope. Managing customer uploads does not automatically permit reading customer records. Personal MCP credentials follow current membership or delegation; unattended service credentials belong to the business and can remain valid when their creator leaves, until the owner revokes their grant or access expires. Shared business context is a separate approval. MCP uses separate credentials from the ingestion API. Revocation stops new authorized requests but cannot recall information already returned to an external application. Selected Yield employees manage restricted operations and commercial metadata; their CMS does not expose private chats, member memory, dataset rows or credential secrets. Operational support records are kept for 90 days; necessary anonymous usage/accounting totals and contract/invoice records are separate.

Retention and your controls

While a dataset is in Yield, we keep its active snapshot and up to four previous successful snapshots so you can restore one. You can delete a dataset from the Data screen at any time. It becomes unavailable to future chats and queries immediately; stored file versions are removed after any active upload or query releases its reference. Saved conversations remain until you clear them. Private memory remains until you reset it separately, and clearing chat also removes its ratings. API audit records are kept for 90 days, and upload retry records for at least 24 hours until processing finishes. Core application logs are configured for 14 days and S3 access logs for 30 days. Some AWS-managed deployment and edge logs have no explicit expiry configured, so we cannot give a fixed retention period for those logs. Usage details are kept for 90 days; account deletion removes their member link, while anonymous allowance totals remain for accounting and limits. Deletion case receipts are kept for 30 days and temporary replay blocks for up to 24 hours, subject to scheduled cleanup. These settings do not guarantee immediate physical erasure. Provider retention is separate.

Deletion requests

You can delete individual datasets from the Data screen whenever you choose; this does not delete your account or other members’ data. To delete your account or business, email support@yieldintelligencelabs.com. We verify your identity and authority and complete valid requests within 30 days. Account deletion removes your identity, sessions, private conversations, memory, ratings, and membership links, but leaves shared business data for other members. Business deletion requires an Owner/Admin and removes the business’s datasets, conversations, and retained file versions after active processing and queries finish; other members’ independent accounts remain. If you are the sole owner, transfer ownership or explicitly request business deletion first. Once deletion completes, we remove the requested customer content from Yield’s active service. Limited usage, security, and deletion records remain for the periods described above; AWS-managed logs may not have a fixed expiry, and provider retention is separate.

Cookies and website choices

The app uses essential, host-scoped authentication and session-binding cookies. Theme preferences are stored in your browser. A limited dataset-list cache is held in session storage and expires within 30 minutes. Marketing pages do not read application cookies or business data. Website hosting and Google Workspace email services process requests and correspondence. Do not send sensitive uploads or passwords in a support email.

Requests and changes

Contact the support address to request access, correction or deletion, or to ask about this notice. We verify the request before disclosing information. We will update this notice when our practices change.