console.blog() is a personal blog platform. This policy explains what data we collect, how we use it, and your rights regarding your information.
Information We Collect
Account Information
When you create an account, we collect:
- Email address
- Name (display name)
- Profile picture (if provided or from OAuth provider)
- Username
Authentication Data
If you sign in with GitHub or Google, we receive basic profile information from these services. We do not have access to your passwords on these platforms.
Content You Create
- Blog posts and drafts
- Comments
- Profile information (bio, social links)
Local Storage
We use browser local storage to remember:
- Theme preference (dark/light mode)
- Reading history and streak data
- Search history
- Draft content (auto-save)
This data stays on your device and is not sent to our servers.
How We Use Your Information
- To provide and maintain the blog platform
- To authenticate your account
- To display your posts and profile to other users
- To send notifications about activity on your content
- To send password reset emails (if using email/password login)
- To send newsletter updates (if subscribed)
Data Sharing
We do not sell your personal information. We may share data with:
- Service providers: Hosting (Vercel), database (Turso), image storage (Cloudinary), email delivery (Resend)
- OAuth providers: GitHub and Google for authentication
Cookies
We use essential cookies for authentication (session management). We do not use tracking or advertising cookies.
Your Rights
- Access your data through your profile and dashboard
- Edit or delete your posts and comments
- Delete your account (contact us via the support page)
- Clear local storage data through your browser settings
Data Retention
We retain your data as long as your account is active. Deleted posts are soft-deleted and permanently removed after 30 days. If you delete your account, your data will be removed within 30 days.
Security
We implement security measures including encrypted connections (HTTPS), secure password hashing, rate limiting, and input sanitization. However, no system is completely secure.
Changes to This Policy
We may update this policy from time to time. Significant changes will be communicated through the platform.
Contact
Questions about this policy? Reach out through our support page.