1. Who operates the service and whose workspace is used
Kuykendall Industries, LLC operates KI Code. This notice covers MABOS-Code (also called KI Code), its hosted workspace, desktop application, paired runtime and connected-service processing. The main KI Privacy Policy explains shared account, purchase and request handling. Customer identity and organization access are resolved through KI Store; authorized employee access is resolved through KI Portal and the selected company. Product records are associated with those authorized scopes. A customer does not inherit KI's internal development workspace.
2. Information processed and purposes
KI Code processes account and workspace identifiers, product-access information, provider account and resource metadata, connection credentials, and authorization/session records to establish and maintain access.
Copying a selected key from Array. When you choose to copy a provider key, Array shows the selected source account, provider and key, and the server-confirmed destination Code account, workspace and enrolled machine. You can approve a copy from your personal or company Array account into the Code destination you currently control. Approval does not merge those accounts. Code checks the current source and destination authorization, validates the selected provider credential, and stores its own encrypted copy. Provider validation sends the credential to the selected provider; saving a key does not choose a model or generate content. The copied secret travels through the private native handoff and the authenticated Code connection request, not through a prompt, ordinary browser-storage record or capability-map report.
Automatic Warden execution. Connecting your installation while signed in as its owner can establish encrypted installation authorization scoped to your account or company, execution host and repository policy. Tasks receive narrower authorization for their exact task, tools and existing funding limits. Your installed Code harness can receive and finish authorized tasks after the browser closes or its sign-in session expires. Current account, company, membership, repository and provider permissions still apply. This authorization does not renew a browser sign-in or create another provider account.
Task work can include your instructions, conversation history, selected repository files and branches, generated changes, model responses, execution events, command output, database queries and results, checks, and publication or deployment receipts. Persistent task records and project memory, including summaries and context derived from your work, allow you to reopen work, reconnect, inspect what happened and continue across sessions. Memory can operate without a Congress connection. These records are scoped to the relevant account, organization and project; authorized organization administrators may have access under their assigned roles. Security and operation records support access checks, troubleshooting and confirmation of actions whose result was uncertain. KI does not use private code, task content or project memory to train general-purpose models or publish it as help content without separate permission.
Repository content, command output, and database results can contain sensitive information. KI Code does not promise universal redaction of task content. Limit the data you supply and do not place secrets in ordinary task content.
Images, music and media review. Requested media work can include generation prompts, reference images, candidate images or audio, decoded pixels or audio samples, review instructions and results, candidate identifiers and checksums, your selection or revision feedback, and the chosen workspace file. Independent image-generation, music-generation, image-review and audio-review model choices are stored on KI servers with the signed-in owner, organization, preference revision and update time. They are separate from the coding-model choice. Choosing Auto clears the corresponding model pin; changing a choice does not erase earlier task evidence.
3. Where information goes
The hosted application runs on Vercel, with the existing KI identity and application database infrastructure on Supabase. Authorized KI service operation and support can require access to relevant records. Application access remains subject to current identity and workspace authorization.
The selected model route receives the task context needed for inference, which may include conversation, repository content, and tool results. GitHub receives authorized repository operations; Vercel receives authorized deployment operations; Supabase receives authorized project and database operations. Available connections and selected resources determine which of these paths are used. Provider terms and settings govern the providers' own handling, including their retention and any model-training use; this notice does not promise a provider-wide retention or training exclusion. For a provider KI engages to supply the service, KI remains responsible for its own privacy commitments and applicable duties. A provider’s terms do not expand KI’s permitted use of private work. When you connect your own provider account, its applicable agreement and settings also govern that connection.
A conversation can work across multiple repositories you or an authorized agent attach, including repositories added after work begins. Repository identities, branches, source revisions, selected files, generated changes and tool results remain associated with their source repository. Relevant context from those repositories may be supplied to the selected model route and authorized tools to carry out the conversation. Current account, organization, repository and tool permissions continue to govern that processing.
When configured for the relevant workspace, KI Congress and Constellation retrieve related context and preserve bounded task summaries and references, such as repository and commit identities, changed paths, checks, and deployment URLs. Connection status alone does not establish that this context exchange succeeded. A paired runtime processes work on that machine. Model selection and the location where tools execute are separate. A route allowing cloud fallback can send context to a cloud provider; a local-only inference setting does not make hosted account, task, memory or connected-service records local. Authorized background work can continue after the interface disconnects.
Connected models and search. Selected cloud routes may use your connected OpenAI, Anthropic, Google Gemini, xAI, Together AI or other supported provider account. Generation sends the requested prompt and supported reference media to the chosen image or music provider; a selected review model receives the actual candidate media and relevant review instructions. The selected generation and review providers can differ. A paired machine can ask the trusted KI service to use its owner's saved cloud connection and receive the resulting media bytes; that relay does not disclose the saved API key to the machine. Local models process inference on their configured host, while the account and task records described here remain in their existing services. When enabled, Tavily receives the search query as an enhancement to the KI Search operation. Fetched pages and inspected sites receive the network requests needed for the research task.
Suno account connection. If you choose Connect Suno, your browser visits Suno to authorize KI Code. KI requests the scopes api:v0, credits:spend, download, library:read, library:search, library:write, offline_access and profile:read. The requested scopes permit the corresponding account, library, download and credit operations at Suno; they do not by themselves start a song or spend credits. KI stores the resulting encrypted authorization and reads Suno's actual available tool catalogue to establish supported capabilities. The current connection and catalogue checks do not make a music-generation request. Any later supported generation operation requires its own requested task and current access.
4. Credentials and browser storage
Stored integration and model credentials are encrypted by the trusted service. The normal application read responses provide connection metadata or masked indicators rather than the stored secrets. Trusted runtimes use credentials for the corresponding authenticated provider requests; service credentials are not placed in ordinary task prompts or repository files by the connection flow.
KI Code uses authentication, preview-access, and authorization-flow cookies: __Host-ki_code_session, __Host-ki_code_login and __Host-ki_code_flow for customer sign-in, and __Host-ki_code_sso to complete an automatic KI Store customer connection; __Host-ki_code_employee, __Host-ki_code_employee_flow, __Host-ki_code_realm and __Host-ki_code_employee_continuity for company sign-in; __Host-ki_code_github_flow, __Host-ki_code_vercel_flow, __Host-ki_code_supabase_flow, __Host-ki_code_tavily_flow, __Host-ki_code_render_flow and __Host-ki_code_suno_flow while you connect a provider; and __Host-ki_launch_access for preview access. None is used for advertising or cross-site tracking. KI Code also uses browser storage for scoped drafts, selected tasks and projects, file selections, and workspace preferences. Clearing browser storage removes those local copies but does not erase server task records. Cookies used on kuykendall.industries, the KI Store and the KI Portal are listed in the Kuykendall Industries Privacy Policy.
Customer sign-in lasts up to 90 days from the original sign-in and ends after 30 days without activity. The host-only __Host-ki_code_sso cookie lasts up to 10 minutes, binds the connection to this browser and contains an opaque flow reference rather than a provider credential. The connection reuses the existing KI customer identity; the provider refresh credential retains one owner. Signing out or security revocation can end access sooner. Recovery access and sensitive-action confirmation retain their shorter limits.
Optional dictation records audio and transcripts in browser storage for the signed-in identity. Transcription uses the selected local browser or same-computer engine; selecting Send submits the edited text as task input. You can inspect, export or discard saved recordings. Cleanup of sent recordings occurs when their saved-recordings list is opened, according to the chosen retention setting; unsent or failed recordings may remain until discarded. This is separate from hosted conversation or telephone recording. The shared cookie and storage notice describes the account and preview cookies.
Suno authorization storage. The host-only __Host-ki_code_suno_flow cookie lasts up to 10 minutes, uses HttpOnly, Secure and SameSite=Lax, and is cleared when the callback is handled. It holds an opaque browser binding, not a Suno access or refresh token. The matching server flow retains hashed state, browser and sign-in bindings, owner and organization identifiers, connection generation, a return path and an encrypted PKCE verifier and client identifier. Suno access and refresh tokens remain encrypted in the owner's current connection and can be refreshed for authorized use. Normal connection and catalogue responses exclude those tokens. The four media-model preferences are server records, not browser-storage copies.
5. Retention, disconnect, and requests
Project history, task evidence, saved context and memory are retained to continue and support your work, maintain security and satisfy applicable record duties. There is no automatic task-history expiry. Request deletion through the channel below; we assess the relevant records, derived context, provider copies and any legal hold together. An expired session, preview grant, or authorization flow stops its use; expiry does not mean every associated database record is immediately deleted.
Installation and task custody. We retain encrypted installation and task authorizations, their owner, host and task bindings, original sign-in lineage, and issuance or revocation evidence with operation history. These records have no automatic deletion today. Original sign-in records supporting them are excluded from ordinary expired-session cleanup. Natural browser expiry does not end this separately scoped authorization. Code sign-out, underlying account or security revocation, host unpairing and host credential rotation end the applicable execution authority. Stopping a task ends that task's execution; disabling its Warden connection ends the installation's Warden execution. Saved custody may still report retained progress, failure or cancellation after revocation, but cannot start new work or report new success. The privacy request process below includes these retained records.
Retire conversation removes a conversation from your history and prevents reopening or resuming it from that history or an old link. It does not erase the underlying task records, Living Record or Meaning Lattice. The context they retain can still inform other conversations within the relevant authorized account, organization and project scopes. KI Code has no product control to remove that retained memory. Retirement applies to your history; it does not change another authorized person’s history or access.
Before your first completed retirement, the application asks you to acknowledge that distinction. The trusted service retains a record associated with your signed-in account containing the conversation identifier, retirement time and retained-memory acknowledgment. That record lets later retirements skip the notice across reloads and devices. Canceling the first notice records neither retirement nor acknowledgment. Retirement records remain with the retained task records; signing out or clearing browser storage does not remove them. This history action is separate from a privacy request under the process below.
Array copy records and independence. Code retains the selected provider and credential identifier and revision, any selected Anthropic workspace, source and destination account references, enrolled machine, approval and credential digests, hashed source-session references, deadlines and the original copy result. The source account’s bearer credential is not stored in the copy record. A prepared copy is usable for up to five minutes; source approval lasts up to 90 seconds and ends sooner when a bound session or the prepared copy ends. These limits stop new use of the authorization; they are not automatic record-deletion schedules. After a successful copy, locking Array, disconnecting its account map or removing the original wallet key does not delete Code’s saved copy. Remove that connection in Code, and revoke the key with its provider when you want to invalidate the credential everywhere it is used. The original import result can be checked without copying the secret again.
Removing a model key deletes its saved connection; revoke the key at its provider if you want to invalidate it there. Local disconnect removes the usable saved integration credential and invalidates pending authorization attempts. It does not delete task history, scoped context already preserved, or changes made at a provider. Provider revocation is separate. GitHub token revocation may be attempted; a failed attempt is not a confirmed revocation. Optional Vercel or Supabase revocation can affect a broader installation or authorization, as the confirmation explains. Signing out of Code does not sign you out of every KI service. Provider copies and backups are subject to the relevant provider's handling, not an immediate-erasure guarantee from KI Code.
Depending on applicable law, you may have rights to access, correct, delete, or object to processing of personal information. Kuykendall Industries, LLC handles access, correction, deletion, and other privacy requests through the KI contact form or by email at contact@forwarding.kuykendall.industries, identifying the relevant organization and request without including credentials. KI considers identity, authority over the requested records, and applicable preservation duties when handling requests. We respond within the applicable legal period and explain any permitted exception or extension. Disconnecting alone does not submit an erasure request.
Suno and media records. The Suno authorization flow is usable for up to 10 minutes; this validity limit is not an automatic database-deletion schedule. Encrypted Suno tokens remain until the connection is replaced or disconnected, subject to expiry, revocation and current access. Disconnect removes the usable local credential and invalidates pending connection attempts; it does not delete your Suno library, prior provider processing or retained KI task history. Model-preference revisions and media operation evidence retain the account and task retention rules above. Clearing a model pin or disconnecting a provider does not erase previously saved media files.
6. Security and notice changes
KI Code uses HTTPS, current access checks, scoped application authorization, private database permissions, and encrypted credential storage. These measures do not eliminate all risk. Use the designated credential forms and avoid putting secrets in prompts, repository files or ordinary command output. Privacy questions use the KI contact form. This notice and later revisions show their effective dates.
We keep the text of earlier versions; ask through the KI contact form for a copy. This update does not authorize a new secondary use of previously collected private content or change an accepted purchase agreement. Material changes receive appropriate notice and any required consent.
What changed in revision 2 on November 20, 2026, from revision 1:
- Describes the explicit Array provider-key copy, reviewed source and Code destination, current account authorization and provider validation.
- Identifies retained copy records, short approval validity and the independent encrypted connection saved in Code.
- Preserves the separate metadata-only account capability map and existing privacy-request process.
What changed on November 20, 2026, from the version effective November 17, 2026:
- Describes independent server-stored media-model choices, actual candidate processing and review, and authorized paired-machine cloud media requests.
- Describes the optional Suno account connection, requested scopes, temporary authorization cookie, encrypted credentials and capability discovery.
- Lists Tavily, Render and Suno connection cookies and distinguishes flow validity, connection removal and retained task or provider records.
Earlier changes on November 17, 2026, from the version effective November 15, 2026:
- Describes the temporary customer SSO cookie and automatic connection from an existing KI Store identity.
- States the 90-day maximum customer sign-in and 30-day inactivity limit, while retaining revocation and separate installation authority.
Earlier changes on November 15, 2026, from the version effective November 11, 2026:
- Describes separately scoped installation and task authorization for automatic Warden execution after natural browser expiry.
- Explains retained encrypted custody and original sign-in lineage, the exception to expired-session cleanup, and applicable sign-out, revocation, host and Stop controls.
- Retains existing private-content protections, provider responsibilities, privacy requests and accepted agreements.
Earlier changes on November 11, 2026, from the version effective November 7, 2026:
- Explains conversation retirement as a personal history action, with the underlying task records, Living Record, Meaning Lattice and reusable context retained.
- Describes the first-retirement acknowledgment and retained account record so the notice does not repeat across reloads or devices; canceling records no retirement or acknowledgment.
- Describes authorized context from multiple repositories, including repositories added during ongoing work, while keeping source identities and existing account, organization and tool boundaries.
- Preserves the existing privacy request process, private-content protections, provider responsibilities and accepted agreements.

