Ваша приватность важна.

1. Introduction & Scope

Welcome to IlmFun, operated by CHERRY SOFTWARES LLC ("Company", "we", "us", or "our"). We are committed to safeguarding the privacy and personal data of our users, students, educators, creators, and academy administrators.

This Privacy Policy explains how we collect, store, use, process, and protect your information when you access or use:

• The official website at ilmfun.com and associated subdomains (including api.ilmfun.com).
• The IlmFun desktop applications (for Microsoft Windows 10 & 11, including built-in Stream Studio).
• The IlmFun mobile applications (for Android and iOS).
• All related APIs, WebSocket hubs, real-time communication stages, and digital services provided by IlmFun.

2. Information We Collect

We collect only the minimum necessary information required to provide reliable educational services, authenticate users, facilitate real-time classes, and operate secure academy workspaces.

A. Account Information

When you register an account on IlmFun, we collect:

• Identity Data: Display name, unique username, and email address.
• Security Credentials: Passwords are cryptographically salted and hashed using state-of-the-art one-way hashing algorithms (Argon2 / Bcrypt). We never store or have access to plaintext passwords.
• Profile Customization: Optional profile avatar picture, custom biography, and timezone settings.

B. Third-Party Sign-In & Optional Creator Integrations

If you choose to authenticate using Google Sign-In (openid, profile, email) or Gilos single sign-on, we receive authorized basic profile information from the identity provider, including your verified email address, full name, profile picture URL, and third-party user ID. We use this data solely to create or link your IlmFun account. If you additionally choose to link a YouTube channel inside the Windows desktop Stream Studio, we process YouTube API data strictly under the dedicated protections described in Section 5 below.

C. Educational & Community Communications

• Academy Interactions: Channels joined, messages posted, homework submissions, study notes, and file attachments.
• Educator Verification: Educational credentials, certificates, or identity verification documentation submitted by teachers applying for verified status.
• Direct Messages: 1-on-1 and group direct messages sent between connected study partners.

D. Technical & Operational Telemetry

To maintain connectivity and troubleshoot connection issues during live sessions, we collect:

• IP address and approximate geolocation (city/country level).
• Operating system type and architecture (e.g. Windows 11 x64, Android 14).
• App version and build number.
• Connection diagnostics (packet loss, audio bitrate, WebRTC connection latency).

3. Device & Hardware Permissions

Depending on your platform (Windows, Android, or iOS), IlmFun requests specific operating system permissions. These permissions are strictly utilized for educational and communication features:

4. Real-time Audio, Video & WebRTC (LiveKit)

Live audio and video interactions within IlmFun academies are powered by LiveKit's secure WebRTC Selective Forwarding Unit (SFU) infrastructure.

Educational Lesson Archiving: If a verified instructor or academy administrator elects to record a scheduled lecture or masterclass for students who could not attend live, all participants receive an immediate visual and auditory indicator confirming that the session is being recorded. Recordings are stored encrypted in Cloudflare R2 storage and are accessible only to authorized academy members.

5. YouTube Data API v3, Google OAuth Sensitive Scopes & Limited Use Disclosure (Windows Desktop)

The IlmFun for Windows Desktop client includes an optional built-in Stream Studio that enables educators and community creators to broadcast live video directly to their own YouTube channel using YouTube API Services (YouTube Data API v3). Connecting a YouTube account is 100% optional and is never required to use IlmFun on desktop, mobile, or web.

By choosing to connect your YouTube account within IlmFun Desktop, you agree to be bound by the YouTube Terms of Service, and acknowledge that Google's processing of your account data is governed by the Google Privacy Policy.

A. Requested Google OAuth Sensitive Scopes & Strict Operational Purpose

When—and only when—you explicitly click "Connect YouTube Account" inside IlmFun Stream Studio on Windows, IlmFun initiates a user-consented Google OAuth 2.0 Authorization Code flow with S256 PKCE and requests the following two sensitive YouTube scopes alongside basic sign-in identity (openid, profile, email):

B. How Your YouTube Credentials & Data Are Secured, Stored & Protected

• PKCE OAuth 2.0 & TLS 1.3 Transport: Authorization codes are exchanged exclusively over TLS 1.3 using RFC 7636 Proof Key for Code Exchange (S256) and cryptographic anti-CSRF state validation via loopback redirect.
• Hardware-Backed Local Encryption (Windows DPAPI): On your Windows device, short-lived OAuth access tokens and refresh tokens are encrypted at rest using the operating system's native Windows Data Protection API (DPAPI) secure storage—never in plaintext configuration files.
• Encrypted Server Refresh Vault (AES-256-GCM): To maintain seamless studio connectivity across sessions, your OAuth refresh credential stored on IlmFun's backend is encrypted at rest using authenticated AES-256-GCM encryption alongside your connected channel's display profile (channel ID, title, handle, avatar URL, subscriber count) and, while you are actively live, the public watch URL and stream title you choose to share with channel participants.
• Zero Persistent Storage of Stream Keys & Live Chat: Your YouTube RTMP stream ingestion key and YouTube Live Chat messages are processed exclusively in volatile memory (RAM) on your Windows desktop client during an active broadcast session. They are never logged, archived, or persisted in IlmFun databases.
• Zero Ads, Data Brokering, or AI Training: Data obtained through YouTube API Services and Google OAuth scopes is never sold, licensed, shared with advertisers or data brokers, used for targeted advertising or creditworthiness evaluation, or used to train artificial intelligence or machine-learning models. Human personnel cannot read your encrypted tokens or RTMP keys and never access Google user data unless explicitly requested by you for support, required to investigate a security incident, or mandated by law.

C. Disconnecting YouTube & Revoking OAuth Access

You retain complete control over your Google and YouTube connection and may revoke access at any time through any of the following methods:

• One-Click In-App Disconnect: Open Stream Studio → YouTube Live → Disconnect on Windows Desktop. This immediately purges local DPAPI-encrypted tokens from your PC, permanently deletes your server-side YouTubeConnection vault record, and sends an immediate cryptographic token revocation request to Google (https://oauth2.googleapis.com/revoke).
• Google Security Permissions Page: You may independently review and revoke IlmFun's access at any time directly from your Google Account at https://security.google.com/settings/security/permissions.
• IlmFun Account Deletion: Deleting your IlmFun account permanently purges any linked YouTube connection metadata and encrypted tokens alongside your account records.

6. In-App Economy & Financial Transactions ("Emeralds")

IlmFun features an in-app virtual currency known as "Emeralds". Emeralds are utilized to enroll in premium educational lessons, reserve seats in specialized masterclasses, and support verified instructors.

• Payment Processing: When purchasing Emeralds, payments are processed directly through authorized third-party billing providers (such as Google Play In-App Billing or Apple In-App Purchase). CHERRY SOFTWARES LLC does not collect, process, or store credit card numbers, bank account numbers, or CVVs.
• Transaction Logs: We maintain records of Emerald balances, purchase receipts, lesson enrollment history, and educator transfers to ensure account integrity and prevent fraud.

7. How We Use Information

We process your data exclusively for legitimate business and educational purposes:

• Service Delivery: To operate academies, channels, live voice stages, optional creator live streams, homework submissions, and messaging.
• Account Administration: To authenticate your identity, manage permissions, and enforce academy roles (Owner, Administrator, Teacher, Student).
• Safety & Moderation: To detect, investigate, and prevent harassment, hate speech, spam, automated bot abuse, and unauthorized intrusions.
• Platform Reliability: To monitor system uptime, analyze crash logs, and optimize WebRTC media performance.
• Customer Communication: To send critical service alerts, security notices, and respond to support inquiries.

8. Cloud Infrastructure & Third-Party API Services

We partner with world-class, security-compliant infrastructure and API providers to deliver high availability and data protection:

• Cloudflare Inc. (Cloudflare R2): Encrypted global object storage for avatars, attachments, assignments, and educational assets.
• LiveKit: Secure WebRTC audio and video streaming infrastructure.
• Google LLC (Google OAuth 2.0, YouTube Data API v3 & Firebase Cloud Messaging): Push notification delivery (FCM), Google Sign-In authentication, and optional user-authorized desktop YouTube Live broadcasting via YouTube API Services.
• Vultr / Dedicated Cloud Hosting: Hardened application and database hosting with network firewalls and TLS 1.3 encryption.

9. Data Sharing & Disclosure

Your information is only shared in the following limited circumstances:

• Academy Members: Users who share an academy with you can see your display name, username, avatar, roles, status, and—if you actively broadcast an external live stream into a voice or stage channel—the public watch link and broadcast title you choose to display.
• Service Subprocessors: Technical vendors listed in Section 8 who process data strictly under our contractual instructions and applicable API user data policies.
• Legal & Law Enforcement: If required by valid subpoena, court order, or binding legal process, or when necessary to protect personal safety or investigate urgent threats.

10. Data Retention & Account Deletion (GDPR & CCPA)

We retain personal data only for as long as your account remains active or as needed to provide you with educational services.

Your Right to Delete:

You have the absolute right to delete your account and personal data at any time:

• In-App Deletion: Navigate to User Settings → My Account → Delete Account within the desktop or mobile client.
• Email Request: Send an email from your registered address to privacy@ilmfun.com with the subject "Account Deletion Request".

Upon receiving a deletion request, your authentication credentials, linked OAuth tokens, personal identifiers, and private profile data will be permanently purged within 30 days. Public or academy-level chat messages are anonymized to maintain educational continuity for enrolled students.

11. Children's Privacy (COPPA & Under-Age Protection)

IlmFun is designed as an educational collaboration platform. In compliance with the Children's Online Privacy Protection Act (COPPA) and international child safety standards:

• Our general consumer service is intended for users aged 13 and older (or the minimum legal age in your jurisdiction).
• If an educational institution, school, or academy utilizes IlmFun for younger students, the institution or academy is responsible for obtaining verifiable parental consent in accordance with COPPA and local regulations.
• If we discover that personal data from a child under 13 was collected without verified consent, we take immediate steps to delete the account and associated records.

12. Security Safeguards

CHERRY SOFTWARES LLC implements industry-standard administrative, physical, and technical safeguards:

• Encryption in Transit: 100% of web traffic, REST API calls, Google/YouTube API requests, and WebSocket connections use TLS 1.3 encryption.
• Encryption at Rest: Database backups and Cloudflare R2 object storage are encrypted using AES-256; OAuth refresh vaults use authenticated AES-256-GCM encryption; and desktop OAuth credentials are protected locally via Windows DPAPI.
• Authentication Security: High-entropy cryptographic hashing for passwords, PKCE S256 verification for desktop OAuth flows, rate-limiting on sensitive endpoints, and automated bot mitigation.

13. Your Rights & Contact Information

Depending on your location (including under GDPR, UK GDPR, and CCPA/CPRA), you have the right to access, rectify, export, or restrict processing of your personal data.