trust · early access

Data and privacy

This page describes the current technical data flow. It is not the final privacy policy or a substitute for the provider policies that apply to Claude Code, Codex, and local Grok compatibility.

Technical disclosure updated August 15, 2026

Manifoldone remains early access. A final privacy notice identifying the operating legal entity, retention periods, subprocessors, transfer terms, and applicable rights is a required gate before broad public launch.

Local-session boundary

the working tree and files unless you deliberately publish an artifact or static page;
local session history and desktop runtime state;
provider credentials and isolated provider profiles;
terminal processes, terminal contents, and local diagnostic logs.

Remote Host credential and checkpoint boundary

Cloud provider credentials are stored in an envelope-encrypted Vault. They are not stored in plaintext database columns, general logs, or Git checkpoints. At execution time, the selected credential is materialized only into that isolated runtime's dedicated provider-profile home. This is not a claim that credentials never leave the Mac: the encrypted Vault is a connected Manifoldone service and the provider CLI communicates with its provider.

Cloud Git checkpoints are encrypted before object storage. A successful checkpoint defines the transcript and Git boundary that can be restored; a failed checkpoint is shown as a recovery problem and is not counted as durable success. The private beta does not promise uninterrupted execution or that work loss is impossible.

Collaboration identity boundary

An approved workspace member may review shared transcript, artifact, and diff data and submit the next turn to the same server-side Agent. Each command stores the human requester separately from the Remote Host execution identity and is serialized with other turns. The provider credential is never returned to the collaborator client. Shared execution is unavailable for provider identities whose terms do not permit this delegated model; viewers remain read-only.

What an agent provider receives

Manifoldone launches the provider CLI on your machine. Prompts and any context that CLI chooses or you authorize are sent to that provider under its account terms and privacy policy. “Runs locally” describes execution ownership; it does not mean the selected AI provider receives no data.

What connected Manifoldone services process

sign-in identity and profile fields;
projects, membership, roles, presence, and notifications;
shared session events, comments, and control messages needed by authorized collaborators;
artifacts, attachments, or static pages that you explicitly upload;
operational request metadata required to secure and run the service.

Optional product improvement events

Product analytics are off by default on every desktop, web, and mobile-web client. A signed-in user can opt in from that client's Settings and turn sharing off again at any time. Consent does not automatically carry to a different client. The product accepts only a fixed event name plus provider, operating system, app version, a fixed outcome category, coarse duration bucket, local/cloud execution mode, desktop/web/mobile-web client surface, work-surface category, and, for shared-workspace events, the project ID. The service stores the event time and associates the event with the signed-in Manifoldone user so that user can delete it; this is pseudonymous account data, not anonymous data.

The product-event endpoint rejects arbitrary properties. It does not accept prompts, responses, code, workspace names, repository paths, branch names or file paths, terminal contents, session IDs, account tokens, or provider credentials. A project ID is accepted only after checking that the signed-in user belongs to that project.

A signed-in user can delete all stored product improvement events from the same Settings section. Turning analytics off stops future product events; it does not delete account or collaboration data.

Design-partner requests

The early-access form stores the contact name, work email, team-size range, selected providers and operating systems, handoff description, optional timezone, and limited campaign attribution supplied in the page URL. We use it only to evaluate, contact, and onboard design partners. It is separate from optional in-product analytics. You can request correction or deletion through the contact address below.

Support requests

The support form stores an email address, fixed issue category, message, and optional provider, platform, and app version. Do not submit source code, prompts, terminal output, credentials, or tokens. We use the request only to investigate and respond to the reported issue.

Website measurement

The marketing site uses Vercel Web Analytics for aggregate page and referral measurement. Desktop product analytics use the separate opt-in path described above.

Account and deletion requests

Signed-in users can permanently delete an account from the web profile. To prevent deleting a workspace out from under collaborators, deletion is blocked while the user owns a project with other members; request an ownership transfer or remove those collaborators first. Product improvement events also have their own delete action in desktop Settings.

Use the support request form or contact hello@manifoldone.com. Do not email provider credentials, environment variables, private code, or complete terminal logs.