1. Who we are
Whyglint Studio is a content creation and publishing software project. In this policy, “Whyglint Studio,” “we” and “our” refer to the operator of the Whyglint Studio software and this official public website.
2. Scope of this policy
This policy covers two distinct surfaces:
- The public website, which provides product information, this Privacy Policy, the Terms of Service and contact information.
- The desktop application, which is designed primarily to run locally on the user’s computer for content creation, review and supported publishing workflows.
The public website does not provide the application’s creation or publishing runtime and does not connect to the user’s local installation.
3. Information handled by the application
Depending on the features a user chooses, the local application may handle:
- topics, scripts, prompts, uploaded media and generated content;
- voice, visual, subtitle, music and output settings;
- video files and publication metadata such as titles, descriptions, tags, visibility choices and platform-specific options;
- local task and publishing history, including status and sanitized error information;
- account identifiers and authorization information needed for user-approved integrations.
These categories describe information processed by the user’s local installation. They do not mean that Whyglint Studio operates a central server that receives or stores all such data.
4. Information handled by this public website
This static website does not include account registration, advertising trackers, marketing pixels or analytics scripts, and it does not set non-essential cookies. It does not contain a contact form or application backend.
The hosting provider may process ordinary technical request information—such as IP address, browser information, requested URL and timestamps—to deliver and protect the site under the provider’s own policies. Whyglint Studio does not use this site to access files, settings or credentials from the desktop application.
5. Connected accounts and OAuth
When a user chooses to connect a supported account, such as a social platform account, Whyglint Studio uses that platform’s official authorization mechanism. The authorization page is provided by the platform, and the user decides whether to grant the requested permissions.
Authorization tokens and related account information are used only to perform the connected features the user requests, such as identifying an account, preparing a publication, uploading content or checking publication status. Available permissions, review requirements and functionality are controlled by each platform and may change.
Whyglint Studio is not endorsed by, sponsored by or an official partner of any third-party platform merely because it supports an integration.
6. Local credential and data storage
The desktop application stores project information, settings, generated media and operational history locally. When technically applicable, sensitive API credentials, OAuth client secrets and authorization tokens are stored through the secure credential storage provided by the operating system. The publishing component is designed without a plaintext fallback for OAuth material when secure storage is unavailable.
Users are responsible for protecting access to their computer, operating-system account, local files and backups. Removing the application does not necessarily remove data held separately by the operating system or by a connected third-party service.
7. Third-party services
Some features can use services selected, configured or authorized by the user. These may include:
- social and publishing platforms;
- text-to-speech and voice providers;
- media search, stock media or media-processing providers;
- language, generation or other API providers.
When a feature requires an external service, the information needed for that request is transmitted to the selected provider. That provider processes the information under its own terms, privacy policy, retention practices and account settings. Users should review those policies before enabling a service.
9. Data retention
Public website: the site itself does not maintain user accounts or a marketing database. Technical hosting logs, if any, are controlled by the hosting provider and its retention settings.
Desktop application: local content, settings and history remain on the user’s device until the user removes them, clears the relevant application data or deletes the installation. Locally stored credentials remain until they are disconnected, removed through the application or deleted from the operating system’s credential storage.
Third-party services: content or account data sent to a chosen provider is retained according to that provider’s policy and the user’s account settings.
10. User choices and revocation
Users can stop using an external provider, disconnect a supported account in Whyglint Studio, remove locally stored credentials, or revoke application access from the connected platform’s security or application settings. Revocation may not delete content already published or data that a provider must retain under its own rules.
11. Security
Whyglint Studio uses local processing and operating-system credential storage to reduce unnecessary exposure of sensitive information. No method of storage, transmission or software operation is completely secure, so absolute security cannot be guaranteed. Users should keep their operating system, application dependencies and connected accounts protected and up to date.
12. Changes to this policy
This policy may be updated when the software, website, integrations or applicable requirements change. The “Last updated” date will be revised when material changes are published. Continued use after an update is subject to the revised policy.
13. Contact
Questions about this Privacy Policy or privacy practices can be sent through the contact information on the Contact page. Do not include API keys, OAuth tokens, client secrets or other sensitive credentials in a message.