WebReg2Cal Privacy Policy
This page is the official privacy policy for the WebReg2Cal Chrome extension.
1. Scope
Last Updated: March 26, 2026
Effective Date: March 26, 2026
WebReg2Cal converts a user-provided WebReg schedule into calendar events. This policy explains what data is processed, why it is processed, and your choices.
2. Data We Process
- Schedule content you provide: Class names, dates, times, locations, and related schedule text from pasted input or uploaded screenshots.
- Google authorization tokens: Temporary OAuth tokens from Google when you choose to connect Google Calendar.
We do not collect unrelated personal data such as browsing history, health information, financial information, or user communications.
3. How Data Is Used
- To parse your schedule and generate calendar events.
- To create events in your Google Calendar only after you choose to authorize access.
- To extract text from an uploaded screenshot using OCR when you choose the screenshot flow.
4. Third-Party Services
- OCR provider:
https://api.ocr.space/ receives uploaded screenshot images only for text extraction.
- Google OAuth and Calendar API:
https://accounts.google.com/ and https://www.googleapis.com/ are used only for sign-in and creating calendar events that you requested.
5. Storage, Retention, and Sharing
- WebReg2Cal does not operate a backend server to store your schedule or calendar data.
- Processing primarily occurs locally in the extension, except calls required for OCR and Google Calendar integration initiated by you.
- We do not sell user data and do not share user data for advertising purposes.
6. Consent and User Choice
- Using OCR is optional and only happens when you upload a screenshot.
- Google Calendar access is optional and only happens when you explicitly authorize it.
- You can use WebReg2Cal in local/export workflows without connecting Google Calendar.
- You can revoke Google access at any time in your Google Account permissions settings.
7. Permissions Used
identity: Required for secure Google OAuth sign-in when you choose calendar sync.
https://api.ocr.space/*: Required to process screenshot text when you use OCR.
https://www.googleapis.com/* and https://accounts.google.com/*: Required for Google OAuth and event creation.
8. Changes to This Policy
We may update this policy when product behavior changes. The updated date at the top of this page reflects the latest revision.
9. Contact
Email: mvppvm42@gmail.com
WebReg2Cal privacy policy.
Last updated: March 26, 2026