Privacy Policy
Effective Date: February 1, 2026
OCWProject ("we", "our", or "the Service") is an educational content distribution platform operating across multiple school‑specific subdomains. This Privacy Policy describes how we collect, use, disclose, and safeguard information in connection with your use of the Service.
1. Information We Collect
We collect information in the following ways:
- Google OAuth Account Information: When you sign in using Google OAuth, we receive basic account information such as your name, email address, and profile photo.
- Google Drive Import Data: If you choose to import files from Google Drive, we access file metadata and content only for the specific files you explicitly select for upload.
- User‑Submitted Content: Content you voluntarily upload to OCWProject, including academic notes and educational materials.
We do not access, scan, or monitor your entire Google Drive, and no background or continuous Drive access occurs.
2. How We Use Information
Information obtained through Google OAuth and Google APIs is used strictly to:
- Authenticate users and manage accounts
- Enforce user roles and permissions
- Enable approved writers to import and upload content they explicitly select
- Operate and provide core Service functionality
Google user data is not used for advertising, marketing, behavioral profiling, or personalized ad targeting.
3. Uploaded Content vs. Google User Data
Information obtained via Google OAuth or Google Drive APIs remains classified as Google user data and is subject to Google’s Limited Use requirements until a user takes an affirmative action to upload content to the Service.
Once a user explicitly selects and uploads content to OCWProject, that content becomes platform‑hosted user‑submitted content and is no longer treated as Google API data.
OCWProject may use uploaded user‑submitted content in accordance with its Terms of Service, including for operating, maintaining, improving, researching, and developing the Service, as well as for the development and training of machine learning or artificial intelligence models. Google OAuth and Google Drive API data itself is not used for these purposes.
4. Google OAuth & Drive API Access Justification
OCWProject uses Google OAuth to provide secure authentication and limited Google Drive read‑only access to allow approved writers to import files they already control.
- Access is limited to files explicitly selected by the user
- No write, delete, or organizational permissions are requested
- No automated or background Drive access occurs
OCWProject does not modify, delete, or manage user files within Google Drive.
5. Google API Services User Data Policy Compliance
OCWProject’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- Google user data is used only to provide user‑requested functionality
- Google user data is not sold
- Google user data is not shared with third parties except as necessary to operate the Service or comply with law
- Google user data is not used for advertising or AI model training
6. User Roles and Access Controls
- Only vetted and approved writers may upload content
- General users may view content only
- Access controls are enforced at the application level
7. Data Storage and Security
We implement reasonable administrative, technical, and physical safeguards designed to protect information against unauthorized access, disclosure, alteration, or destruction. However, no method of transmission or storage is completely secure.
8. Data Retention and Deletion
- Users may delete uploaded content through the Service where functionality is provided
- Users may revoke Google OAuth access at any time via their Google Account settings
- After OAuth revocation, OCWProject no longer accesses Google user data
- Certain information may be retained as required by law, security needs, or legitimate business purposes
9. Subdomains
This Privacy Policy applies to all OCWProject‑operated subdomains unless otherwise stated.
10. Changes to This Policy
We may update this Privacy Policy from time to time. Changes become effective when posted with a revised effective date.
11. Contact Information
For questions or concerns regarding this Privacy Policy, contact: