Last Updated: July 2, 2026
TL;DR: CourseSpeed does not collect, store, or transmit any personal information. All data stays on your device. Period.
CourseSpeed does NOT collect:
The following data is stored exclusively on your device using Chrome's local storage API:
| Data | Purpose |
|---|---|
| Playback speed preference | Remember your preferred learning speed |
| Skip forward/back duration | Configure rewind and fast-forward seconds |
| Learning statistics | Local watch time and time-saved calculations |
| Chapter bookmarks | Timestamp markers you create during courses |
| UI theme preference | Light/dark/auto display setting |
| Premium subscription status | Verify premium feature access locally |
| Welcome guide flag | Track whether onboarding was shown |
None of this data is transmitted to any server.
When you purchase a CourseSpeed Premium subscription, payment processing is handled entirely by Creem (creem.io). We do not receive or store your payment card details. Creem's privacy policy applies to all payment data.
CourseSpeed does not include Google Analytics, crash reporting, telemetry, advertising pixels, or any third-party scripts.
| Permission | Why Required |
|---|---|
activeTab | Access video playback controls on the current learning tab |
storage | Save your preferences locally on your device |
| Host permissions | Inject playback controls on supported learning platforms only |
chrome://extensions/ → CourseSpeed → Clear dataCourseSpeed is not directed at children under 13. We do not knowingly collect any data from anyone.
Under the EU General Data Protection Regulation: we process no personal data. All functionality operates locally in your browser. No lawful basis is required because no processing occurs.
Under the California Privacy Rights Act: we do not collect, sell, or share personal information. No opt-out is needed because no data collection occurs.
Updates will be reflected on this page and in the Chrome Web Store listing.
For privacy-related inquiries, contact us at support@joycraft.dev or open an issue on our GitHub repository.