Bucko Privacy Notice

Effective date: September 24, 2026.

Bucko is operated by Studio Yeehaw LLC (“Studio Yeehaw,” “we,” “us”). Questions or privacy requests: mitch@studioyeehaw.com.

What Bucko handles

Depending on the features you use, Bucko may handle:

• Account and session information, contact details, your Bucko address, assistant settings, profile details, saved instructions, schedules, and proactive-update preferences.
• Messages and files you send to Bucko through supported channels, including message text, attachments, and delivery metadata needed to provide the service.
• Memory you ask Bucko to save, and memory inferred from repeated ordinary interactions when learning is enabled. Memories can include facts, preferences, conditions, audience settings, source references, and correction or deletion records.
• Data from connected services that you authorize, including Gmail messages and metadata, Google Calendar events and calendar metadata, and Google Drive files or metadata, when needed for a requested feature. Bucko uses the connected account selected for that action.
• Billing and subscription information handled through the payment provider. Bucko receives the account and subscription information needed to manage access and billing status; payment card details are handled by the payment provider.
• Technical, security, and operational records needed to authenticate requests, prevent abuse, deliver messages, run scheduled work, troubleshoot failures, and maintain the service.

How Bucko uses information

Bucko uses this information to provide conversations, memory, connected-service searches and actions, drafts, schedules, reminders, account support, billing, security, and service operations that you request or enable. Bucko may use public web information when a requested feature requires it, such as meeting preparation.

Bucko does not treat a connected account as permission for every action. Connected-service access is limited by the account, feature, and authorization available for that action. Actions that affect an external service may require your approval.

Google user data

When you connect Google services, Bucko accesses only the Google data needed for the feature you use and the permissions you authorize. Gmail, Calendar, and Drive access can include reading messages, events, files, and related metadata; write access is used only for features and actions that require it and that you authorize.

Bucko uses Google user data to provide the user-facing Bucko features described in this notice. Bucko does not sell Google user data or use it for advertising. Bucko does not use Google user data for credit, lending, insurance, employment, housing, or similar eligibility decisions. Bucko does not transfer Google user data to third parties except service providers acting to provide the requested Bucko feature, comply with law, protect the service, or as part of a business transfer with appropriate protections.

AI and browser processing

Bucko sends prompts and relevant user-provided context to AI model providers through Vercel AI Gateway. The current code names OpenAI models, and the relevant context can include the current conversation, recalled Bucko memory, and data needed for the requested task. These providers may retain service records under their applicable agreements and privacy terms.

For an approved browser task, Bucko may use Kernel/OnKernel browser infrastructure. Pages and task data needed for that task may be processed by that provider. This processing is limited to the browser task you approve.

Service providers

Bucko uses infrastructure and providers needed to operate the service, which may include Vercel, Neon/PostgreSQL, Redis, private object storage, Hindsight memory storage, Composio for connected Google accounts, Resend for email, Photon for iMessage, and Stripe for billing. Providers process information only for the services they provide to Bucko and under their own terms and privacy notices where applicable.

Memory, storage, and retention

Bucko stores account, session, preference, schedule, billing, and memory records in systems with different lifecycles. We keep records while needed to provide Bucko, handle account requests, secure the service, and meet applicable legal obligations. Retention can differ among operational logs, backups, billing records, and service providers. Runtime state and provider-managed workflow state may have separate lifecycles. Memory is stored in canonical application records and a retrieval index; corrections and forget actions create or apply deletion and revision records so old memory is not used in normal recall.

You can ask Bucko to correct or forget a memory, and the account controls provide reset and deletion actions where available. Account deletion starts cleanup of account-linked application data. A deletion request removes account-linked active records through a retryable cleanup process. Some billing, security, backup, workflow, and provider records may remain for their applicable retention periods or legal obligations.

Sharing and audience controls

Bucko keeps personal memory scoped to the account that may read it. Group and household information is shared only when the source, audience, authority, and current membership permit it. A group membership or a person's name alone does not grant access. Bucko does not use a private conversation or a surprise detail to broaden an audience without the required evidence and authority.

Security

Bucko uses access controls, authenticated provider callbacks, scoped account and audience checks, and revision and authority checks for memory. No online service can guarantee absolute security. If you believe your account or data is at risk, contact us at mitch@studioyeehaw.com.

Your choices

You can disconnect connected accounts, limit or disable learning and inferred memory where the product provides that control, correct or forget saved memories, pause or remove schedules, and request account deletion. You may also contact us to ask what account-linked information is held or to request correction or deletion. We may need to verify account ownership before fulfilling a request.

Changes and contact

We may update this notice when Bucko’s data practices change. We will post the updated notice and update the effective date. For questions or requests, contact mitch@studioyeehaw.com.

Google Limited Use

Bucko’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide or improve user-facing features that are prominent in Bucko, as permitted by the user; it is not used for advertising or to train generalized AI models. Human access is limited to user consent, security, legal compliance, or aggregated internal operations as permitted by Google’s policy.