Last updated September 8, 2026

InputScout Privacy Policy

VEYAMA LLC operates InputScout. InputScout uses YouTube API Services. This policy explains the information InputScout processes, the services involved, and the choices available to you.

Information InputScout processes

• Account identity: Guest use is stored on your device and does not create a Supabase account. If you explicitly create or sign in to an account with Google or verified email, Supabase processes an account ID, email address, and basic identity information; InputScout does not receive your plaintext password.
• Learner settings: language, self-described level, variety and topic preferences, preferred duration, ability estimates, theme, and profile-setup state. Guest settings remain on the device until a confirmed account import.
• InputScout activity: saved and completed items, resume position, app-tracked input sessions, fit ratings, pairwise comparisons, community quality votes, and reports. Guest activity remains on the device until a confirmed account import. Only signed-in accounts may submit YouTube URLs.
• Catalogue and moderation: public YouTube identifiers and official metadata, editorial evidence, staff actions, operational records, and redacted audit information.
• Support information: messages and identifiers you choose to send when requesting help, access, or deletion.

What InputScout does not claim to collect

InputScout does not import or record your official YouTube watch history. App-tracked input sessions describe activity inside InputScout or time you manually report; they are not YouTube account history. InputScout does not download video, audio, or subtitles.

How information is used

We use InputScout information to provide guest access, preferences, discovery, saved items, progress, difficulty calibration, recommendations, optional account recovery, abuse prevention, catalogue quality, support, security, and audited operations. Personal fit labels are not directly averaged into the global difficulty score.

Website measurement

InputScout does not currently load website analytics on this public site. If privacy-focused measurement is enabled later, this policy will describe the active service and configuration.

Android app measurement

Production Android builds use Google Analytics for Firebase to understand app reliability and which screens are useful. After connected startup and policy acceptance, the app sends an app-ready event and generic screen categories, such as discovery, library, or progress. It does not send account IDs, email addresses, search text, video identifiers, video titles or URLs, playlist identifiers, ratings, or watch history to Analytics. Firebase also collects automatic app and session events, engagement timing, a pseudonymous app-instance identifier, and device/app information such as operating system, app version, language, and approximate location derived from network information. Google says Analytics does not log or store IP addresses. Event-level measurement is associated with the app-instance identifier before it appears in aggregate reports. This measurement can apply to guests as well as signed-in learners; device-local learner records remain separate. Advertising ID collection and ad personalization are disabled. The offline demo and web app do not initialize Firebase Analytics. Google processes this measurement under its Privacy Policy. Contact privacy@inputscout.com for measurement and retention questions; Analytics is not linked to your InputScout account ID, so account deletion does not identify an Analytics installation. Local learner-data reset and account deletion do not delete previously sent Analytics data. Google Analytics property retention settings apply to event/user data separately from standard aggregated reports.

Service providers and third-party content

Supabase provides authentication, database, storage, and Edge Function infrastructure. Vercel hosts the public website and web applications. YouTube and Google provide external video playback, video metadata, and their own platform services. Google Play distributes the Android app. These providers process technical information under their own terms and privacy practices where applicable, including the Google Privacy Policy.

YouTube API Services and playback

InputScout uses YouTube API Services to retrieve official public video and channel metadata and to provide playback through the official YouTube player. InputScout does not request YouTube account scopes, access private YouTube account data, or import your YouTube watch history. Your use of YouTube through InputScout is governed by the YouTube Terms of Service and the Google Privacy Policy.

Videos play through the official YouTube embedded player or open on YouTube. YouTube may process device, network, cookie, account, playback, and advertising information independently. InputScout does not control YouTube advertising or recommendation behavior.

Advertising

InputScout currently has advertising disabled and does not include an advertising SDK. YouTube may still show its own advertising inside the official player. This policy will be updated before InputScout introduces advertising.

Sharing

We do not sell learner data. Information is disclosed to infrastructure providers as necessary to run InputScout, when you direct us to do so, to protect the service and its users, or when legally required. Public community signals are designed to be aggregated or pseudonymous rather than displaying a learner identity.

Retention and deletion

Device-local guest data remains on that device until you reset it, remove the app data, or confirm an import into an account. InputScout account and activity data is retained while needed to provide the service and maintain security and integrity. Stored official YouTube metadata used by the active catalogue is refreshed or rechecked within 30 days, and unavailable videos may be hidden. An account deletion removes or anonymizes covered InputScout data, subject to narrowly retained security, legal, backup, or append-only audit records where legitimately required. See Delete Account for both in-app and external request options.

Guests, account import, and device loss

A guest has no server account and its device-local data may not be recoverable after device loss, app-data removal, or browser-storage clearing. You may explicitly create or sign in to a Google or verified email account and confirm an import of the current guest profile. If the destination already contains learner data, InputScout asks before merging and does not silently replace either profile.

Security and children

We use access controls, role checks, and audit logs. No service can guarantee absolute security. InputScout is not directed to children under 13, and the service does not knowingly request a child’s personal information.

Your choices

You can reset or delete InputScout data from Profile in the app, request deletion without reinstalling, or contact us about privacy questions. If you connect Google sign-in, you can review or revoke that access from the Google security settings page. InputScout does not request private YouTube account scopes, so revoking Google sign-in does not change the public catalogue metadata retrieved through YouTube API Services. Depending on applicable law, additional access, correction, objection, or portability rights may apply.

Contact

Email privacy@inputscout.com for privacy questions or support@inputscout.com for product support.