Alby company primary-source snapshot

Fetched: 2026-08-07 UTC

1) Official homepage

Selected excerpts from the official site:

All you need to use bitcoin as everyday money online, in apps and in person.

Self-custody in the cloud

Access your wallet directly in any browser while keeping full control over your keys.

Connect web, desktop and mobile apps to your Alby Hub … Define app permissions and set daily, weekly, monthly or yearly budgets for the apps you connect to.

Additional signals from the homepage:

The public pitch is not just browser wallet; it is a broader hosted-plus-self-custodial stack around Alby Hub, app connectivity, lightning addresses, and developer tooling
The site explicitly pushes Alby Cloud and self-custody-in-the-cloud as part of the first-party operating shell
Support, guides, developer portal, and open-source repos all sit under one branded operator boundary

2) Terms of service

Source: https://getalby.com/terms-of-service

Selected excerpts from the terms:

These terms of service … constitute a legally binding agreement … between you … and Alby Inc.

Alby Inc. is a company incorporated in USA, with its registered office in Dover, 8 The Green STE A, Dover, DE 19901, United States …

Alby provides you with the following services: access to Alby Account, access to Alby Online Communities, access to Alby Cloud, access to Alby API, access to Distribution of Lightning Channels.

Alby offers the following products: Alby Browser Extension, Alby Hub, Alby Go.

Alby acts solely as a distributor of lightning channels … Alby is not an LSP and does not offer services of an LSP.

Additional signals from the terms:

The terms are unusually useful for taxonomy because they explicitly separate the account, cloud, API, and channel-distribution services from the Browser Extension / Hub / Go product surfaces
The company boundary matters because one named operator is deciding account eligibility, service access, cloud terms, and channel-distribution packaging
The channel-distribution language also makes it clear that Alby is packaging third-party Lightning service-provider access rather than merely shipping neutral local software

3) Privacy policy

Source: https://getalby.com/privacy-policy

Selected excerpts from the privacy policy:

Alby is the controller responsible for the processing of your data … Alby Inc. 8 The Green STE A, Dover, DE 19901, United States.

Communication data, transaction data, lightning node authentication data are processed.

We store log files to determine service disruptions and for security reasons … for a period of 60 days …

We involve external service providers with tasks such as sales and marketing services, contract management, payment handling, programming, data hosting.

Additional signals from the privacy policy:

The privacy policy confirms that the company boundary is also the data-controller boundary for account, transaction, and node-authentication workflows
The note is useful because Alby is not only a client-side app; it operates account, notification, dashboard, and cloud-linked services that create observability and retention questions
External provider usage and controller language make the company layer analytically distinct from the open-source product artifacts

4) Hub/account linking FAQ

Source: https://guides.getalby.com/user-guide/alby-hub/faq/why-do-i-need-to-link-my-alby-account.md

Selected excerpts from the guides:

your Alby Account becomes the wallet interface for your Alby Hub

Some of those functionalities include: A lightning address … Payment notifications and reports … Seamless association with the Alby Browser Extension … APIs for developers … Quicker and comprehensive support

Alby cannot see the transactions that go directly through your node using NWC connections with your Hub. However, if your Alby Account is linked, transactions will be visible on your dashboard at getalby.com.

Additional signals from the linking FAQ:

Linking is the cleanest first-party source showing where optional self-custody turns back into a company-run dashboard, support, notification, and identity shell
The company note is useful because the same user can stay self-custodial at the wallet layer while still inheriting a first-party account, lightning-address, and support boundary
The transactions visible on your dashboard line is a strong reminder that the operator boundary matters even when the wallet rhetoric emphasizes sovereignty

5) Developer OAuth, webhooks, and NWC relay docs

Sources:

Selected excerpts from the developer docs:

Login to your account on getalby.com and create a new API client here: https://getalby.com/oauth_clients

Authorization URI https://getalby.com/oauth

Token URI https://api.getalby.com/oauth/token

Want to use webhooks for your own Alby account? create a webhook in our developer dashboard

That’s why Alby is offering a professionally operated relay specialized on NWC events.

Public unauthorized requests to our main relay are subject to rate limiting … Wallet service providers … should reach out and ask us to set up a dedicated relay service.

Additional signals from the developer docs:

The company directly operates the OAuth client-issuance path, authorization/token endpoints, webhook dashboard, and one important default NWC relay surface
This is exactly the sort of control surface that disappears if Alby is treated only as an open protocol or wallet UX brand
Partner-specific dedicated relay setup shows that the operator relationship can become infrastructure policy rather than merely public documentation

Notes

This pass did not surface a classic Alby company whitepaper or litepaper.
The strongest primary materials were the homepage, terms, privacy policy, Hub/account-linking guide, and the developer OAuth / webhook / relay docs.
Alby is best treated as a named operating shell around wallet connectivity, app-session permissions, cloud hosting, identity, and developer-facing payment infrastructure rather than only as a browser wallet or NWC-adjacent protocol label.

Cowrie Research

Explorer

alby-company-primary-sources-2026-08-07