Privacy Policy
At CaptureWorld Blog, we prioritize reader privacy and data transparency. This policy provides detailed disclosure on how we collect, process, and safeguard your account information, reading history, and local AI workspace keys.
1. Information We Collect & Process
Account Identity: When you sign in through Google OAuth 2.0, we store your full display name, verified email address, and profile photo avatar URL to identify your account.
Reading History & Progress: As you scroll through articles, our reading tracker logs your exact scroll depth percentage and scroll position offset (e.g., 45% read) so you can resume reading smoothly whenever you return.
Interactions & Favorites: Saved bookmarks, liked articles, comment history, and topic preferences are tied to your user ID for seamless synchronization across devices.
Client Browser Local Storage: Your personal AI auto-formatting API keys (OpenAI / custom LLM endpoints) and UI state preferences (such as dark mode toggle and Google Translate settings) are saved locally in your browser storage.
2. How We Utilize Your Information
Seamless Article Resume: Utilizing saved scroll positions to automatically scroll to your last read line upon article page load.
Content Curation & Recommendations: Understanding popular reading trends to recommend relevant photography, tech, and cultural stories.
Security & Authentication: Verifying JSON Web Tokens (JWT) on protected API endpoints to prevent unauthorized access or account impersonation.
Editorial Communication: Sending crucial account status notices or opt-in weekly newsletter digests if you explicitly subscribe.
3. Cookies & Session Storage Technologies
Essential Auth Cookies: Secure HTTP-only and Bearer session tokens used strictly to maintain your authenticated sign-in session.
Preference Storage: LocalStorage key-value pairs stored locally on your device for fast theme switching without server roundtrips.
Managing Storage: You are free to clear browser cookies or localStorage items at any time through your browser developer tools or settings.
4. AI & Third-Party Integrations Security
Client-Side AI API Keys: When using the AI Auto-Format tool in the author/admin editor, your API key is fetched directly from your browser's localStorage and passed to the formatting request. We NEVER store or log your private AI keys in database records.
Third-Party Authentication: Sign-in utilizes Google OAuth 2.0 protocol. We never receive or store your Google account password.
No Data Selling: We have a strict anti-monetization policy regarding personal user data. Your email address and reading habits are NEVER sold, rented, or traded to third-party ad networks.
5. Data Retention & Storage Durability
Reading History Retention: Reading history logs are retained as long as your account remains active to power your Reading History dashboard.
Inactive Accounts: Accounts inactive for over 24 consecutive months may be archived or purged automatically to reduce data footprint.
6. Your Comprehensive Privacy Rights
Access & Export: You may view your stored bookmarks, liked articles, and account details directly in the user menu dashboard.
One-Click History Purge: You can delete your entire reading history instantly using the 'Clear History' button on the Reading History page.
Permanent Account Deletion: You have the right to request permanent deletion of your profile, comments, and associated data by contacting our privacy officer.
7. Updates to This Policy
Policy Revisions: We may update this Privacy Policy periodically to reflect new features, AI integrations, or legal compliance standard updates.
Notification of Changes: Any material revisions will be highlighted with an updated 'Effective Date' banner at the top of this document.