Privacy Policy
Last Updated: December 2025
1. Introduction
DevUEFN (“we,” “our,” or “us”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, store, and delete user information when you use our platform, including authentication via Google OAuth and access to YouTube API Services. DevUEFN is maintained by a solo developer and not a team.
2. Information We Collect
Personal Information
When you register for an account or authenticate via Google, we may collect:
- Email address
- Username
- Profile information
Additionally, we may receive limited account info from Discord or GitHub when you authenticate via those services, but we do not store this information—it remains on Google’s side and is not visible to us.
Usage Data
We automatically collect information about your interaction with our service:
- Watched videos and watch history
- Liked videos and preferences
3. How We Use Your Information
We use the collected information to:
- Authenticate users via Google OAuth
- Provide and maintain our ad-free video service
- Personalize your learning experience
- Recommend relevant UEFN tutorials
- Improve our platform and services
- Communicate with you about updates
4. Data Sharing and Disclosure
We do not sell your personal information to third parties. We may share information in the following circumstances:
- Service Providers: With trusted third parties who assist in operating our platform
- Legal Requirements: When required by law or to protect our rights
- Business Transfers: In connection with a merger or acquisition
5. Data Retention
We retain Google user data only for as long as necessary to provide our services. Account data is stored while your account is active. Inactive accounts may be periodically removed. OAuth access tokens are stored securely and refreshed only when required.
6. Data Deletion
Users may request deletion of their data at any time. To request deletion:
- Contact us at devUEFN@gmail.com and request account and data deletion
After deletion:
- Your account information will be permanently removed
- OAuth tokens will be revoked
- Any stored Google user data will be deleted from our systems
7. YouTube API Services
DevUEFN uses YouTube API Services to display UEFN tutorial content. By using our service, you agree to be bound by the YouTube Terms of Service and Google's Privacy Policy. We do not store any data received from these services beyond what is necessary for account authentication and platform functionality.
8. Data Security
We implement reasonable technical and administrative measures to protect your personal information. However, no method of transmission or storage over the Internet can be guaranteed 100% secure. OAuth tokens and other authentication data are stored securely and only as needed.
9. Cookies and Tracking
We use cookies and similar technologies to enhance your experience, analyze usage, and provide personalized content. You can control cookie settings through your browser. Essential authentication cookies may be required for service access.
10. Children's Privacy
Our service is not intended for children under 13. We do not knowingly collect information from children under 13. If you believe we have collected information from a child, please contact us immediately to request deletion of that information.
11. International Data Transfers
Your information may be transferred to and processed in countries other than your own. We ensure appropriate safeguards are in place for international data transfers and comply with applicable privacy regulations.
12. Changes to This Policy
We may update this Privacy Policy periodically. Changes will be posted on this page with an updated "Last Updated" date. Significant changes affecting data retention or deletion will be communicated where required.
13. Contact Us
If you have questions about this Privacy Policy, or if you wish to request deletion of your Google, Discord, or GitHub data, contact us at:
Email: devUEFN@gmail.com
Note: Discord and GitHub account information obtained via OAuth is not stored on our side; we only receive it through Google's authentication process.