How do I install acct?

Run `npm install -g acct-sh`, then `acct` for the command list. Create a profile with `acct init` (--id, --user, --email, --name, --bind). Add a shell hook with eval "$(acct hook zsh)".

Does acct replace gh auth switch?

Yes for directory-scoped work. acct injects GH_TOKEN from the OS keychain for the bound profile and does not call gh auth switch. Git HTTPS uses git-credential-acct; identity uses includeIf.

Where are tokens stored?

In the OS keychain via @napi-rs/keyring (macOS Keychain, Windows Credential Manager, Linux Secret Service / libsecret). CI hosts may set ACCT_SECRET_BACKEND=file for an explicit plaintext secrets.json opt-in.

How do I diagnose conflicts?

Run `acct doctor` (add --online to verify ambient GH_TOKEN against the cwd profile). It scans credential helpers, install blocks, orphan bindings, sticky tokens, and keyring availability.

Legal

Privacy policy

Last updated 13 August 2026. This notice describes the acct website at acct-web.vercel.app.

Who we are

acct is an open-source CLI (npm: acct-sh) maintained by Abdullah Ahmed. This website is the public product page for that tool. There are no user accounts on the site and we do not operate a backend that stores visitor profiles.

What this policy covers

It covers visits to this website, including pages such as the homepage, this policy, and public files like /llms.txt. It does not replace the privacy notices of third-party sites we link to (GitHub, npm, Vercel).

The acct CLI runs on your machine. Tokens stay in your OS keychain (or an explicit local file backend you opt into). The CLI source does not include usage telemetry or a phone-home channel to us. When you use GitHub through gh or git, that traffic is between you and GitHub under GitHub's privacy statement.

Information we collect

We do not run first-party analytics, ads, or a newsletter. The site has no login, no contact form, and no cookies that we set to identify you. Copying an install command uses the browser clipboard on your device only.

This site is hosted on Vercel. Vercel's Privacy Notice states that when people visit a customer website, Vercel processes traffic metadata such as IP address, coarse location derived from IP (city/country, not precise geolocation), user-agent / system configuration, and request logs in order to operate, secure, and deliver the site. We do not have a separate visitor database on top of that hosting.

To render the Releases section, our servers (not your browser) fetch public data from GitHub (the GitHub API and the raw changelog) and from the npm registry. Those requests identify the website as the client. They do not send your name or email to those services as part of a site account we run.

Cookies and similar technologies

We do not use advertising cookies, a cookie-consent banner, or third-party analytics tags (no Google Analytics, Meta pixel, or similar). Essential hosting and security behavior is controlled by Vercel. You can block cookies in your browser; the marketing pages do not depend on them to function.

Why we process this information

Where data-protection law (including the GDPR) applies, hosting and security logs are processed as needed to operate and protect the site — typically legitimate interests in delivering a public documentation/marketing page and keeping it available. We do not use that information to profile you for ads.

Sharing

We do not sell personal information and we do not share it for cross-context behavioral advertising. Infrastructure providers that necessarily see request data to host the site include Vercel (and the cloud providers in Vercel's subprocessors list). Outbound links to GitHub and npm are those companies' services, governed by their policies.

Retention and location

We do not keep a first-party store of visitor accounts. Hosting logs follow Vercel's retention for the platform. Vercel delivers the site over a global edge network; processing may occur in the United States and other regions where Vercel and its subprocessors operate. Vercel publishes a Data Processing Addendum and is listed under the EU–U.S. Data Privacy Framework.

Your rights

Depending on where you live, you may have rights to access, correct, delete, or restrict personal data, to object to certain processing, and to lodge a complaint with a supervisory authority. Because we do not run user accounts, there is often nothing in a first-party database to access or delete. For hosting logs held by Vercel, we can look into a request if you write to us with enough detail to identify the relevant traffic; some log data is only available to the hosting provider.

If you are in the EEA, UK, or Switzerland, you can also contact your local data protection authority. If you are in California, we do not sell or share personal information as those terms are used in the CPRA, and we do not use sensitive personal information to infer characteristics about you.

Children

This site is for developers. It is not directed at children under 16, and we do not knowingly collect personal information from children.

Changes

If we add accounts, analytics, or other collection, we will update this page and the date above. Material changes will be reflected here before they apply to new collection.

Contact

Privacy questions: open an issue on the acct GitHub repository. That is the contact channel published for this project.