AI Subscription Tracker by Digital Research Group — Team Handoff

Production site: https://tracker.digitalresearchgroup.com
Product owner: Digital Research Group (https://digitalresearchgroup.com)

1. Open sales-page.html first for the product overview and screenshots. Primary download CTAs open the lead modal and delivery page; local preview mode does not transmit or retain the entered email.
2. Download or unzip AI-Subscription-Tracker.zip.
3. Move “AI Subscription Tracker.app” to Applications.
4. If macOS blocks the unsigned local build, Control-click the app and choose Open.
5. On first launch, choose Set up first account, Try sample workspace, or save the non-secret setup draft for later.
6. Add one account per subscription. Use distinct labels such as “Claude · Personal” and “Claude · Work”. The label can be left blank; the app supplies a provider + Personal label and keeps any provider-detected plan metadata separate from an optional override.
7. For multiple accounts at the same provider, use distinct labels such as “Claude · Personal”, “Claude · Work”, and “Claude · Family”. A separate browser profile per account is useful when visiting provider sites, but the browser profile does not connect that account to the tracker. Add each account one at a time and keep the label aligned with the account you are viewing.
8. OpenAI is the only live provider connector in this release. It requires an organization Admin API key and automatically reads provider-reported project metadata and rate-limit ceilings. Claude, Gemini, and Grok provider pages are reference links only; choose Manual tracking for those subscriptions. The tracker never imports browser credentials, copies session tokens, or invokes Claude Code/Nimbalyst authentication.
9. Use Smart refresh from an account card or enable it in Settings. It keeps the last good snapshot during outages and marks credentials that need attention. Sign out removes only a tracker-stored OpenAI API key from macOS Keychain; it never signs out of a provider website or another app.
10. If Claude Code or Nimbalyst needs recovery, sign back into the intended Claude account in Nimbalyst/Claude Code itself. Do not use an older tracker build's Claude Plan Authenticate or Logout action. See docs/provider-integration-risk-audit.md for the independent connector review and recovery notes.
11. Verify downloaded archives against SHA256SUMS.txt when distributing the handoff.

See docs/provider-metadata-extraction.md for the provider-by-provider metadata contract and its safety boundaries.

The app stores credentials in macOS Keychain and keeps account metadata and snapshots locally.
Never share an API key in the sales page, archive, or team chat. Rotate any key that has ever been stored outside Keychain before using the app.

For public deployment, configure a first-party HTTPS lead endpoint in lead-config.js. The static preview intentionally does not claim that a lead was recorded.
The current landing audit is docs/landing-page-ux-audit-final.md; docs/landing-page-ux-audit.md is retained as the historical baseline.
AWS and GitHub deployment operations are documented in docs/deployment-operations.md.