articulate.

PLAIN LANGUAGE. CLEAR BOUNDARIES.

Privacy notes.

Your account and your local working profile have different jobs. Signing in does not approve a history scan or agent sharing.

Updated November 16, 2026

This website

The homepage explains Articulate and shows fictional preferences. It has no analytics, advertising tracker, local history scanner or account-service call. Fonts and agent icons load from this website.

The separate account connection page communicates with Supabase for sign-in and onboarding. Google and GitHub process authentication when you choose them. No Articulate page asks for your Google or GitHub password or repository access.

GitHub Pages hosts these public browser files and logs visitor IP addresses for security. See GitHub Pages data collection and GitHub’s Privacy Statement. Browser interface code and public service configuration are visible; backend code, private keys and user records are not part of this website.

Sign-in and your introduction

Supabase holds your managed identity, email/provider profile, session and security records. The Articulate account record contains your account ID, creation date, latest sign-in and free-plan status. First-time onboarding asks for your name, work category (company, school, startup or N/A), role, and an organization name when applicable. These explicit details are stored in Supabase with a completion date; completed onboarding is skipped on later sign-ins to the same account.

Work and role labels describe what you tell us. They do not grant administrative access, measure ability or automatically become instructions to an AI agent. Account creation does not authorize uploading local chats, caches, project paths, working profiles or device fingerprints. No payment, marketing signup or Pro trial starts.

Connecting your terminal

The CLI creates a temporary sign-in request. Its browser approval link is private and should not be shared. After sign-in and onboarding, your browser encrypts a minimal Articulate session to a key held by the originating CLI. Supabase temporarily stores the encrypted handoff and hashed verification capabilities, plus the approving account ID. The CLI requires the browser’s one-time code before claiming and verifying that session.

Requests become unclaimable after five minutes. Successful claim, cancellation or deletion of the approving account removes the handoff; expired rows are cleaned on a subsequent login start. No plaintext session token or local activity is stored in the handoff table. Identity-service sessions and security logs are separate from this temporary queue.

The sign-in page uses tab-scoped session storage for OAuth and pairing. GitHub provider tokens are excluded from persisted browser session storage. After preparing a CLI handoff, the page clears its stored login session and stops automatic refresh. The CLI stores the verified Articulate session in your OS credential store. The copy buttons write only the displayed command or code when clicked; this website does not read or upload your clipboard.

The local pilot

The current public npm pilot remains local and does not require this account flow. The new account-connected CLI is in private testing. Installing either does not itself approve scanning or agent sharing. Guided setup asks for supported source/project scope, and each agent needs separate permission.

Selected imported text is screened for known credential patterns and normally expires locally after 30 days. Screening cannot recognize every secret. Reviewed preferences and saved profile data remain until you change or remove them. Cloud-only or deleted agent history may be unavailable.

Raw imported history is not returned through Articulate’s MCP tools. Connected AI providers can process the reviewed summaries and preferences you approve for their connection. Local processing and provider processing are separate.

Removal and retention

Use articulate privacy to inspect/remove managed local data or articulate disconnect for agent connections. Uninstalling a package does not erase saved profiles or original agent histories. In the private account build, sign out separately to remove its OS-stored account credential; erasing the local profile folder does not remove that credential.

Account/profile records remain until account deletion. Deleting an account also removes its onboarding profile, early-tester enrollment, use-summary records and approved handoffs. It does not erase local profiles, uninstall agents or remove every provider log or backup. Hosted account deletion remains in the separate account-management pilot; contact support for help. Managed logs/backups follow Supabase’s retention and privacy practices.

Early-tester enrollment is a separate explicit action. No benefit or Pro trial has been announced. A minimal account-linked use-report database contract exists, but automatic CLI/plugin reporting is not enabled. Sign-in counts are not product usage or proof of learning gains.

Questions and credits

Email hello@i-ops.dev for privacy/account help. Your email provider and ours process the message. Describe issues without credentials, verification codes, raw histories or private project files.

See font and agent-mark credits and browser sign-in software notices.

Back to Articulate ↗