Audit `src/components/Analytics.tsx` for privacy-compliant defaults

[Codex723]

Summary

Confirm analytics only load after consent is granted via CookieBanner.tsx, and document what's tracked in a privacy-facing doc.

Difficulty

Good First Issue — estimated effort: ~1-3 hours. Labels: frontend, security, good-first-issue, good-first-issue

Where to Work

• src/components/Analytics.tsx
• CookieBanner.tsx

How to Approach This

1. Locate the relevant page under src/app/(app)/ or component under src/components/.
2. Match the existing Tailwind utility-class conventions already used in that file — don't introduce a new styling approach.
3. If adding new interactive state, prefer local useState/useEffect consistent with how nearby components in the file already manage state.
4. Test the change at both desktop and mobile breakpoints (e.g. Chrome DevTools responsive mode) before opening a PR.
5. Run npm run lint and npm run build locally to confirm no type or lint errors were introduced.
6. If you added a new reusable piece of UI, consider whether it belongs in src/components/ instead of being page-local.

Acceptance Criteria

• Behavior/UI described above is implemented in the file(s) listed under "Files Likely Affected".
• Verified visually at both desktop and mobile widths.
• Keyboard accessible where interactive (tab order, visible focus state) if applicable.
• No new TypeScript, lint, or build errors (npm run lint, npm run build).
• Existing tests still pass; new tests added if this issue includes a testing component.

Notes for Contributors

Comment on this issue before starting so it can be assigned to you and duplicate work is avoided. If the described approach doesn't quite fit once you're in the code (e.g. the file has moved, or there's a cleaner way to do it), that's fine — leave a comment explaining the deviation in your PR description rather than silently changing scope.

[OmniZlatoon]

📋 Grainlify Application

@OmniZlatoon has applied to work on this issue as part of the Grainlify program.

I CAN DELIVER MAINTAINER! PLEASE ASSIGN AND SEE IT WORK

Hi maintainer sir, I'm called Junior Brown , a full-stack and smart contract engineer building on Stellar. I specialize in designing and shipping scalable, secure systems end-to-end, from Soroban smart contracts to production-ready backend infrastructure and user-facing applications.

I’ve worked on complex architectures involving automated agents, cross-chain logic, and data indexing, focusing on reliability, performance, and clean standards. My approach is very product-driven: I don’t just build contracts, I build complete systems that solve real user problems and can scale in production.

I’m especially interested in infrastructure, security, and automation creating tools and frameworks that make it easier for other developers to build safely and efficiently on Stellar.

---

Repo Maintainers: To accept this application, review their application or assign @OmniZlatoon to this issue.

[Vyacheslav-Tomashevskiy]

Opened #518.

The consent-gating logic in Analytics.tsx was already correct - the actual gap was that nothing documented what's tracked, and the consent check had no test/failure-mode coverage. Details on both fixes are in the PR description.

/claim