Docs: Add how to disable id/anon ID storage to docs

[DavidWells]

There seems to be confusion about the anonId and how to not persisting user data. We should add to the docs somewhere that if you're using the Analytics Core library, no IDs anonymous or otherwise are persisted.

E.g.

import { Analytics, EVENTS, CONSTANTS } from '@analytics/core'
import storage from '@analytics/storage-utils'

// See ../packages/analytics-core for source code
export default function analyticsLib(opts = {}) {
  // const defaultSettings = { storage } // no storage now
  return Analytics({
    ...defaultSettings,
    ...opts
  })
}

export { analyticsLib as init }
export { analyticsLib as Analytics }
export { EVENTS, CONSTANTS }

See more in https://github.com/DavidWells/analytics/issues/345

The docs live in https://github.com/DavidWells/analytics/tree/master/site/main/source dir. Maybe add a new file or update one where this might make sense

@claude

[claude[bot]]

Claude finished @DavidWells's task in 2m 1s —— View job • claude/issue-466-20250619_010447 • Create PR ➔

---

Documentation Update for Disabling ID Storage

I've successfully added comprehensive documentation to address the issue about disabling ID/anonymous ID storage.

Todo List:

• [x] Read repository setup instructions (CLAUDE.md) - No CLAUDE.md found
• [x] Explore documentation structure in site/main/source
• [x] Review existing documentation to find best placement
• [x] Create or update documentation with clear examples
• [x] Commit changes to branch
• [x] Provide PR creation link

✅ Completed

Created a new tutorial at site/main/source/tutorials/disabling-id-storage.md that provides:

• Clear explanation of how to use @analytics/core to disable ID storage
• Code examples showing the difference between storage-enabled and storage-disabled configurations
• Privacy considerations including GDPR compliance benefits
• Implications of disabling storage (both benefits and limitations)
• Custom storage configuration options for fine-grained control
• Plugin considerations for privacy-focused setups
• Testing guidance to verify storage is disabled
• Use case recommendations for when to disable storage

The documentation directly addresses the confusion mentioned in the issue about anonId persistence and provides practical examples for privacy-compliant analytics implementations.

---

[github-actions[bot]]

📋 Claude Code execution complete

ℹ️ Analysis only (no code changes)

📊 Execution Info: Issue #466 | Unknown (401 files) | @DavidWells

🚀 Automated management executed:

---

💡 Example commands for Claude:

🔍 Analysis & Review:

• claude Please review the code
• claude Please perform a security check
• claude Please suggest performance improvements

🛠️ Tasks & Implementation:

• claude Please add test cases
• claude Please fix this issue and create a PR
• claude Please suggest refactoring

📚 Management & Operations:

• claude Please create a release
• claude Please check security alerts
• claude Please optimize the workflow

📋 Issue Specific:

• claude Please investigate the root cause of this issue
• claude Please propose multiple solutions

🔄 Rerun: You can run again anytime with claude [your instructions]