diff --git a/.agents/skills/seo-audit/SKILL.md b/.agents/skills/seo-audit/SKILL.md
new file mode 100644
index 0000000..3a160d6
--- /dev/null
+++ b/.agents/skills/seo-audit/SKILL.md
@@ -0,0 +1,412 @@
+---
+name: seo-audit
+description: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
+metadata:
+ version: 1.1.0
+---
+
+# SEO Audit
+
+You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Before auditing, understand:
+
+1. **Site Context**
+ - What type of site? (SaaS, e-commerce, blog, etc.)
+ - What's the primary business goal for SEO?
+ - What keywords/topics are priorities?
+
+2. **Current State**
+ - Any known issues or concerns?
+ - Current organic traffic level?
+ - Recent changes or migrations?
+
+3. **Scope**
+ - Full site audit or specific pages?
+ - Technical + on-page, or one focus area?
+ - Access to Search Console / analytics?
+
+---
+
+## Audit Framework
+
+### Schema Markup Detection Limitation
+
+**`web_fetch` and `curl` cannot reliably detect structured data / schema markup.**
+
+Many CMS plugins (AIOSEO, Yoast, RankMath) inject JSON-LD via client-side JavaScript — it won't appear in static HTML or `web_fetch` output (which strips `
@@ -79,6 +95,10 @@
How it works
Sign in with Google, write a few things you're grateful for each day, and watch your mindset shift over time. Your entries are encrypted before they leave your device.
+ A private space for gratitude and reflection. No feeds. No noise. Just you and your thoughts.
+
+
+
What is it?
+
+ Grateful Journal is a free, end-to-end encrypted daily journal focused on gratitude.
+ You write a few things you're grateful for each day, and over time you build a private
+ record of the good in your life — visible only to you.
+
+
+
Features
+
+
End-to-end encrypted — your entries are encrypted before leaving your device. We cannot read them.
+
No ads, no tracking — we don't sell your data or show you ads.
+
Works offline — installable as a PWA on Android, iOS, and desktop.
+
Daily prompts — gentle nudges to keep your practice consistent.
+
History view — browse past entries and reflect on how far you've come.
+
Free to use — no subscription, no paywall.
+
+
+
Why gratitude?
+
+ Research consistently shows that a regular gratitude practice improves mood, reduces stress,
+ and builds resilience. Grateful Journal gives you the simplest possible tool to build that habit —
+ without distractions or social pressure.
+
+
+
Privacy first
+
+ We built Grateful Journal because we believe your inner thoughts deserve a private space.
+ Read our full Privacy Policy to understand exactly how your data is protected.
+
+
+
+
+
+ )
+}
diff --git a/src/pages/PrivacyPage.tsx b/src/pages/PrivacyPage.tsx
new file mode 100644
index 0000000..4b6e21c
--- /dev/null
+++ b/src/pages/PrivacyPage.tsx
@@ -0,0 +1,62 @@
+import { Link } from 'react-router-dom'
+
+export default function PrivacyPage() {
+ return (
+
+
+ 🌱 Grateful Journal
+
+
+
+
Privacy Policy
+
Last updated: April 8, 2026
+
+
+ Grateful Journal is built on a simple promise: your journal entries are yours alone.
+ We designed the app so that we cannot read your entries even if we wanted to.
+
+
+
What we collect
+
+
Account info — your name and email address via Google Sign-In, used solely to identify your account.
+
Journal entries — stored encrypted in our database. We do not have access to the content of your entries.
+
Usage data — no analytics, no tracking pixels, no third-party advertising SDKs.
+
+
+
Encryption
+
+ Your journal entries are end-to-end encrypted. They are encrypted on your device before being sent to our servers.
+ We store only the encrypted ciphertext — decryption happens locally in your browser using your account key.
+
+
+
Data sharing
+
+ We do not sell, share, or rent your personal data to any third party.
+ We use Firebase (Google) for authentication only.
+
+
+
Data deletion
+
+ You can delete your account and all associated data at any time from the Settings page.
+ Deletion is permanent and irreversible.
+
+
+
Cookies
+
+ We use a single session cookie to keep you signed in. No advertising or tracking cookies are used.
+
+
+
Contact
+
+ Questions about this policy? Reach us at the contact details on our About page.
+