1. Information We Collect
1.1 Anonymous Video Statistics
We collect aggregate information about which videos are popular among ALL users:
- Video IDs: YouTube's public video identifiers
- Channel names: Public channel names
- Usage counts: How many times (total, all users) a video was used with our extension
Privacy guarantee: This data is completely anonymous. We know "Video X was used 1,000 times" but we do NOT know WHO used it. Similar to YouTube's view count.
1.2 Your Activity (Without Video Context)
We collect information about YOUR usage patterns:
- Random User ID: A UUID generated when you install the extension (not linked to your email)
- Feature usage: Which features you use (generate timestamps, descriptions, titles)
- Success rates: Whether operations succeeded or failed
- Session data: Temporary session IDs for debugging
Privacy guarantee: We do NOT track WHICH videos you use these features on. We only know "User X generated 5 timestamps" but NOT on which videos.
1.3 What We DO NOT Collect
- ❌ Your viewing history: We don't track which videos you watch on YouTube
- ❌ Connection between you and videos: We cannot link your User ID to specific video titles
- ❌ Personal information: Unless you explicitly verify your email for newsletter
1.4 Error Logging (Debugging Only)
When errors occur, we collect additional context to fix bugs:
- Video context: Video ID, title, and channel (only when error happens)
- Error details: Error message, browser information
- Retention: Error logs are kept for 30 days, then automatically deleted
Purpose: This helps us quickly identify and fix issues. For example, if subtitles don't load on a specific video, we need to know which video to reproduce the bug.
2. How We Use Your Information
2.1 Anonymous Video Statistics
We use aggregate video data to:
- Optimize AI prompts: Understand which types of content work best
- Prioritize features: See which features are most popular
- Improve quality: Identify content categories that need better handling
Example: "Educational videos are popular → let's optimize for tutorials"
2.2 Your Activity Data
We use your activity data to:
- Improve UX: Understand how users navigate the extension
- Fix bugs: Identify features that fail frequently
- Measure success: Track if new features improve user experience
Example: "Timestamp generation fails 20% → need to fix this feature"
2.3 Error Logs
We use error logs exclusively for:
- Bug fixing: Reproduce and fix issues
- Technical support: Help users when they report problems
Error logs are NOT used for marketing, profiling, or any other purpose.
3. Data Storage and Security
3.1 Data Separation
Important: We store data in separate databases that CANNOT be linked together.
- video_popularity table: Video statistics WITHOUT user IDs (anonymous)
- analytics table: User activity WITHOUT video context
- error_logs table: Errors WITH full context (debugging only, 30-day retention)
Technical proof: It is impossible in our database schema to query "which videos did User X interact with" (except for error cases).
3.2 Data Retention
- Video statistics: Retained indefinitely (anonymous aggregate data)
- User activity: Retained for 12 months, then automatically deleted
- Error logs: Retained for 30 days, then automatically deleted
3.3 Security Measures
- Encryption in transit: All data transmitted over HTTPS
- Encryption at rest: Database encrypted by Supabase (PostgreSQL with encryption)
- Access control: Row Level Security (RLS) policies enforce data separation
- No third-party sharing: Data never sold or shared with advertisers
4. Third-Party Services
We use the following third-party services:
- DeepSeek AI API: For generating summaries and content
- Cloudflare Workers: For secure data processing
- Supabase: For temporary data storage and analytics
These services have their own privacy policies and security measures.
5. Your Rights
You have the right to:
- Use the extension without providing any personal information
- Uninstall the extension at any time
- Request information about what data we process
- Contact us with privacy concerns
6. Children's Privacy
Our extension is not intended for children under 13. We do not knowingly collect personal information from children under 13.
7. Changes to This Policy
We may update this privacy policy from time to time. We will notify users of any material changes through the extension or our website.
8. Technical Details (For Transparency)
We believe in radical transparency. Here's exactly how our data collection works:
8.1 Database Schema
We use three separate tables:
-- Table 1: video_popularity (anonymous)
video_id | channel_name | view_count
"abc123" | "TechChan" | 1523
// NO user_id column!
-- Table 2: analytics (without video context)
user_id | event_type | success
"uuid-1234" | "generate_timestamps" | true
// NO video_id column!
-- Table 3: error_logs (debugging only)
user_id | video_id | error_message
"uuid-1234" | "abc123" | "Load failed"
// Only for errors, 30-day retention
8.2 What Queries We CAN Run
- ✅ "Which videos are most popular?" (from video_popularity)
- ✅ "How many users generated timestamps today?" (from analytics)
- ✅ "What errors occurred on video X?" (from error_logs)
8.3 What Queries We CANNOT Run
- ❌ "Which videos did User X interact with?" (no link between tables)
- ❌ "What content does User X prefer?" (no video context in analytics)
- ❌ "Build a profile of User X" (impossible without video-user connection)
8.4 Code Transparency
You can verify our data collection by:
- Opening Browser DevTools → Network tab
- Using our extension on a video
- Inspecting requests to
ytdesc.com/api
- You'll see two separate requests:
video-popularity (no userId) and analytics-basic (no videoId)
10. Compliance
This extension complies with:
- Chrome Web Store Developer Program Policies
- General Data Protection Regulation (GDPR) principles
- California Consumer Privacy Act (CCPA) requirements