Alphred

Privacy policy

How Alphred handles information across the Computer Agent, website, accounts and public sharing.

Who is responsible and what this notice covers

Nelson Bazzard operates Alphred. For privacy questions or requests, contact nelsonbazzard@gmail.com. Alphred is currently operated under that name, not by an incorporated company.

This notice covers the Alphred Computer Agent desktop application, alphred.ai, account verification and recovery, and public file sharing, to the extent each service is made available to you. It does not cover the separate Private Agent product. Features depend on your version, permissions, connected accounts and selected providers. Describing a feature does not promise availability or a release date.

Conversations, local storage and our access

Alphred does not operate a server-side conversation or ordinary library database. Conversation history, local memories and indexes, projects, settings and ordinary library records are kept on your computer. Model responses return to the app and can be saved locally. Local storage does not mean that cloud AI processing takes place on your device.

We do not use your conversations, prompts, files or generated outputs to train our own AI models. We do not provide a staff review workflow for your local conversations or hold a server-side chat archive for staff to read. Our account database is for authentication and account administration, including account status and any enabled plan, credit or subscription records. It is not a store of your chats.

Public sharing is a separate exception: the service hosts the file copy you explicitly upload and the metadata needed to deliver and manage it. Information you voluntarily send to support is also received by us. Avoid sending full conversations or sensitive files where a redacted explanation will suffice.

The app uses an encrypted local vault for protected records and credentials. Original files, exports, working folders, browser data, downloaded content and operating-system backups are not all brought under that vault. Local encryption is not end-to-end encryption of cloud model requests or public share links.

What cloud AI requests contain

A cloud task sends information needed for the task to the selected model service. Depending on the feature, this can include your prompt, relevant conversation history, instructions and memories, file content, images, screenshots, browser or connected-app content, tool descriptions, tool results and outputs used in later steps.

Commands and their outputs, filenames, code and information returned by connected apps can become model context. An agent can obtain context while carrying out your task, not only from attachments you select. We do not promise that each request is automatically stripped of personal information or secrets.

Parallel subagents can receive delegated instructions and relevant context, make additional model requests, use available tools and return results to the coordinating agent. They are additional processing for your task, not independent human reviewers.

Alphred supports cloud requests through DeepInfra and Z.ai, and Qwen Cloud for supported realtime voice and media analysis. Which provider receives information depends on the feature and configuration. User-configured endpoints or local models can change who receives a request. Selecting a local model does not make other enabled cloud features local.

Model retention and training

Alphred does not retain a server-side conversation archive for review or training and does not use your task content to train its own models. These statements do not mean that no data is transmitted to a model service, website or connected app you use.

Provider retention, caching, security logging, abuse monitoring and training restrictions depend on the actual provider, endpoint and account terms. This notice does not assert that zero-data retention has already been enabled for every provider. Any zero-data-retention commitment must apply to the specific configured service and its contractual exceptions.

Deleting a local conversation does not itself request deletion by an AI provider, connected app or recipient. Contact us about processing arranged by Alphred; providers of accounts and endpoints you independently configure may also need to handle your request.

Computer use, terminal access and background tasks

Using the permissions and tools available to a task, the agent can inspect screen or browser content, operate interfaces, run commands, access files and interact with applications. This can expose personal information in your screen, files or command output, including information about other people.

Approval prompts, per-chat grants and auto-approval settings affect which actions run without another prompt. Alphred includes broader auto-approval options for terminal commands, computer control, files and email. There is no guarantee of a separate prompt before every read, transmission or change.

Scheduled or continuing work can process information while a task runs even when you are not actively typing. Review access and pause or cancel tasks you no longer intend. Disabling one feature does not stop all other work or reverse completed actions.

Voice, microphones and screen viewing

Voice typing can use the on-device Moonshine engine or a configured transcription endpoint. Audio is sent to a remote transcription endpoint when one is selected. Realtime cloud voice uses the configured Qwen Cloud service and can transmit microphone audio, conversation context and tool results.

When screen viewing is enabled for a voice session, screen frames can be sent for model processing. The app has a screen-viewing permission setting; voice is not necessarily audio-only. Media you make available to analysis features can also be sent to the relevant provider.

You can stop recording or voice sessions and manage operating-system permissions. Obtain appropriate permission before recording other people. Transcripts and task outputs may remain in your local conversation after a session ends.

Connected apps, websites and search

A connection gives Alphred access according to the credentials or OAuth scopes you authorise. Depending on the app and task, this can include emails, calendars, documents, repositories, files, contacts, messages and account identifiers. Tool responses can be passed to the selected model as task context.

Connections can support creating, editing, sending, uploading or deleting content as well as reading it. The third-party service and its recipients receive those operations. Search queries are sent to the selected search service, including Exa where configured. Websites visited receive ordinary connection and browsing information.

Connector secrets are stored using the local credential vault. Disconnecting removes the stored credentials from Alphred; it does not guarantee provider-side revocation or erase earlier copies or model context. Revoke access in the provider security settings where needed. Browser website sessions are separate from API connections.

Information we handle

When you visit, our hosting and security providers process information needed to serve and protect the website, including your IP address, browser/device information, requested pages and technical request or error information.

If you use an account link, Supabase processes account identifiers, your email address and the authentication information needed to verify the email or reset the password. Authentication links can contain sensitive, temporary session information; do not forward them.

If you send an enquiry, we receive your email address and the information you choose to include. Do not send passwords, secret keys or unrelated personal information.

If you create a public share through Alphred, we process the uploaded file copy, its name, type and size, owner and share identifiers, and operational sharing records. Viewing a shared file also sends ordinary delivery requests to our infrastructure. Local conversations and the ordinary library are not stored in our Supabase account database.

Why we use information

We process authentication and account records, requested task content, connected-service responses and sharing information to provide services you request. Where applicable, this is necessary to perform our contract with you or take steps you request before a contract. Optional capabilities operate according to your instructions, settings and permissions.

We rely on legitimate interests to deliver and secure the website, prevent abuse, resolve technical problems and answer enquiries. These interests are running a reliable service while limiting unnecessary collection. We may also process information to meet applicable legal obligations.

We do not treat visiting the website or acknowledging a privacy notice as consent to marketing. If we introduce an optional activity requiring consent, we will explain it and obtain any required consent separately.

Public share links

Anyone holding a working share link can view or download its uploaded copy without an Alphred account. Links can be forwarded. Share only information you have permission to disclose.

Stopping sharing or deleting the online account removes access through our sharing service. It cannot recall downloaded copies, screenshots or forwarded content. Editing or deleting your local original does not automatically update or revoke a hosted snapshot. Public sharing is not end-to-end encrypted sharing.

Providers and processing locations

Netlify hosts the website; Supabase provides authentication and account services; Cloudflare provides public-sharing infrastructure and object storage. Cloud AI processing uses configured providers, including the DeepInfra, Z.ai and Qwen Cloud integrations described above. Search services, connected apps and websites receive information required for the operations you use. Independently connected services may act under their own privacy terms rather than solely on our behalf.

Supabase is configured in Ireland and shared object storage in Western Europe. This is not a promise that all processing stays in the UK or EEA. Cloud inference, voice, search and connected services can process data elsewhere. Applicable transfer safeguards depend on the provider and arrangement; contact us for information relevant to your use. A Supabase region setting does not determine where AI processing occurs.

We do not sell personal information. We may disclose information we hold where legally required or reasonably necessary to address fraud, abuse, security incidents or legal claims. This does not give us a server-side copy of conversations stored only on your device.

Retention and deletion

Local records persist according to your use of the app and deletion controls. Deleting a conversation may not remove a separately saved memory, library item, exported file, browser record, backup or third-party copy. Review these separately. We cannot recover or erase local-only conversations through our account database because they are not stored there.

Account administration information is kept while the account is active and removed through the online account-deletion process. Shared copies remain until sharing is stopped, the online account is deleted, or removal is necessary for legal or service-protection reasons. Links do not currently have an automatic expiry guarantee.

Enquiries and technical information are retained for as long as needed to respond, operate and secure the service, resolve disputes and meet applicable legal obligations. Infrastructure backup and log retention can differ from active-service deletion; deletion is not a promise that every backup copy is erased instantly.

Deleting an online account does not delete your local desktop files. Removing the desktop app does not automatically stop a hosted share.

Your rights

Where applicable, you can request access, correction, erasure, restriction and portability of personal information. You may object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting processing that was lawful before withdrawal.

Email nelsonbazzard@gmail.com to make a request. We may need proportionate information to verify your identity. You may complain to the UK Information Commissioner’s Office at ico.org.uk/make-a-complaint/ or the relevant authority where you live or work. You do not have to contact us first.

Storage, security and changes

We do not add advertising or analytics cookies to this website. Account flows use session information necessary to complete authentication. Hosting providers process requests needed for delivery and security. Any future non-essential tracking will be handled separately, with consent where required.

We use access controls, a protected local vault and encrypted network connections where supported. No device or service guarantees complete security. Device permissions, accessible local files, chosen endpoints and connected-account security affect exposure. The app can create technical diagnostic records; redact information before sending it for support.

We do not use the account service to make solely automated eligibility decisions about you with legal or similarly significant effects. Agent actions can nevertheless have real consequences. The service is not designed to make consequential decisions about others without appropriate human oversight. Alphred is not directed at children.

We will update this notice when the website or its processing changes and identify material changes where appropriate. Last updated: 19 October 2026.