Privacy Policy

Information we handle and why

Account and security information includes your username, email address, display name, preferences, password hash, verification and recovery information, configured multifactor or passkey credentials, and session-security records. These records can include your IP address and browser information. We use them to operate and protect accounts, maintain sessions and send account-related messages.

Connected-account information includes provider identifiers, names, email addresses, channel or profile details, protected access and refresh tokens, permission and synchronization status, and imported subscriptions or followed channels. We use it for sign-in, account connections, enabled synchronization and related recommendations. Optional Twitch chat uses a separate permission flow and sends a message when you enable it and submit one.

Activity and technical information includes impressions, clicks, viewing duration, explicit feedback and related content, session, placement, device and diagnostic identifiers. We use it for discovery and recommendations, feedback, diagnostics and abuse prevention. Some activity can wait in browser memory while signed out and be associated with an account after sign-in during that browsing session.

Public platform information includes video and channel metadata and, when available, YouTube comment text, identifiers, author display names, channel and avatar links, publication and update times, and provider like and reply counts. Public YouTube comments are read-only in Veya and do not require a Google connection. This feature does not offer YouTube comment posting, replying, liking or moderation.

Correspondence includes information you choose to send for support or privacy requests. Please provide relevant links instead of unnecessary copies of comment bodies or sensitive documents.

Veya uses public content titles and descriptions to generate similarity representations through AWS Bedrock. Comment text and commenter profiles are not inputs to the comments feature’s analytics or that embedding pipeline.

Service providers and external content

Veya uses Amazon Web Services for hosting, storage, processing and transactional email. Google and YouTube, and Twitch, provide external content and account integrations. Support and privacy correspondence arrives through AWS SES and Amazon WorkMail and is forwarded to the operator’s monitored Google Gmail mailbox.

Veya uses YouTube API Services. Public-comment requests identify the requested video, thread and page; they do not pass your Veya profile or Google authorization token to YouTube for those reads.

Embedded players and externally hosted images make requests from your browser to their providers, which can receive network and device information and use cookies or similar technologies. Embedded content may include advertisements. See the Google Privacy Policy (opens in a new tab) and Twitch Privacy Notice (opens in a new tab). External links take you to their respective services.

We currently use the services described here. The activity processing described above remains part of Veya; this is not a claim that Veya has no analytics.

Cookies, browser storage and retention

Veya uses cookies and browser storage for sessions, preferences and navigation. Current session cookies can last up to seven days; some presentation information is readable by Veya’s browser code. Access tokens are held in memory. A separate functional cookie remembers the accepted policy version for up to one year, without a user identifier or account record. A new policy version asks for acknowledgment on your next app entry. Clearing cookies can require sign-in or acknowledgment again.

Browser storage remembers settings such as theme, sidebar, captions, autoplay and chat preferences, together with temporary navigation and feedback-session information. Clearing it can reset these preferences.

The comments feature does not write comment text or author fields to Veya’s database, persistent browser storage or comments analytics. Provider response pages stay in server memory with a two-minute cache lifetime and periodic cleanup. The database stores aggregate request-usage counters separately.

Loaded browser comment lists use the earliest loaded response’s expiry, thirty minutes after it was fetched. Loading more pages does not extend that deadline. Expired lists clear when the browser runs the expiry check; suspended tabs clear overdue state when they resume. Veya cannot remotely erase a frozen device’s memory. Third-party image caches and copies independently made by others are separate from this application state.

Account, connection and activity records do not all expire automatically. They remain until updated or removed through relevant controls or a deletion request. Signing out or allowing a session cookie to expire does not itself delete the account or previous server-side activity. Veya does not apply one uniform automatic age-based purge to these records.

Operational container logs rotate when configured size limits are reached. Separate database diagnostics and operator-managed backups or exports can remain longer; there is no uniform automatic age-based purge across all those files. Some in-memory diagnostics use shorter limits, which do not govern copies an operator makes.

Manual SQL recovery copies can contain account, connection and activity data as of the backup date. Deleting a live record does not edit an earlier backup. Reviewed manual SQL Server backups are checked hourly for removal from fourteen days old, measured from the later of backup completion and file modification. The newest valid copy is preserved, and cleanup pauses if that copy becomes stale until a replacement is created and verified. Other recovery copies, including operator archives and MySQL binary logs, have separate retention. These recovery safeguards do not override the deletion-request commitment below.

Support and privacy correspondence is managed by the operator across the receiving and forwarded mailboxes. Deletion requests cover Veya-held copies in those mailboxes.

Choices and deletion requests

You can change available preferences, pause supported synchronization and disconnect accounts. Disconnecting removes Veya’s local connection and associated imported subscription or grant records. You can also revoke access through the provider; Google permissions are available at Google account permissions (opens in a new tab).

For questions, complaints, correction, access or deletion requests, or requests that Veya stop accessing or displaying data about you, email inquiries@programmertechnologies.com. Include relevant Veya, video, comment or channel links. A Veya account or new Google authorization is not required for a public-comment request. We may ask for proportionate ownership information where necessary; do not send passwords or unnecessary identity documents.

Programmer Technologies Corporation handles deletion requests promptly and completes them within seven calendar days of receipt. Removing Veya-held copies does not remove the original on YouTube; use YouTube’s own controls for that. Public information still available on YouTube may be retrieved again during normal use. Tell us if your request includes preventing further access or display so we can address that scope and explain the measures taken. Removing a cached copy is not a claim of permanent channel-wide exclusion.

Security, audience and changes

Veya uses controls including HTTPS, hashed account passwords and protected provider tokens.

Veya is a general-audience service and is not directed to children. Children are not a target audience, and Veya does not intend to offer YouTube Kids.

We identify policy updates by effective date and seek renewed agreement before covered data uses that require it. Contact inquiries@programmertechnologies.com with privacy questions or complaints.