Privacy Policy

Effective date: September 13, 2026

TrueFrame Studio is designed to minimize collection of personal data and keep creator control over connected services.

1. Information used by the software

Depending on the features you use, TrueFrame Studio may process product names, product descriptions, reference images, generated images, generated videos, review status, publishing history, API configuration, and authorization tokens required to communicate with services you choose to connect.

2. Local storage

The current Chrome-extension version may store settings and workflow data locally in the browser on your device, including configured API credentials. Anyone with access to your Chrome profile or device may potentially access locally stored information, so you should secure your device and browser profile.

3. Third-party services

When you use AI generation or publishing features, relevant data is sent to the third-party service you selected. For example, prompts and reference media may be sent to Google AI services, while approved video and authorization data may be sent to TikTok. Those providers process data under their own privacy policies and terms.

4. TikTok data

If you connect TikTok, TrueFrame Studio may receive an OAuth access token and limited account information necessary for the permissions you approve. Requested permissions may include basic account information and content posting permissions. TrueFrame Studio does not require your TikTok password.

5. How information is used

to create and manage product-content projects;
to generate posters and videos through selected AI providers;
to review, queue, download, or publish approved media;
to maintain user-selected application settings and workflow history;
to diagnose technical errors and improve the product.

6. Data selling and advertising

TrueFrame Studio does not sell personal data to advertisers. The application does not require advertising profiling to provide its core creator workflow.

7. Credential protection

API keys, client secrets, access tokens, and refresh tokens should be treated as confidential. Do not publish or share them. Future versions may move sensitive OAuth credentials to a secure backend where required by a provider's security rules.

8. Retention and deletion

Local application data remains on the device until the user clears it, removes the extension, or deletes the relevant project data. Data held by third-party providers is subject to their own retention practices. Users can revoke connected app access from the relevant third-party account settings.

9. Security

Reasonable technical safeguards are used in the software design, but no software or network transmission can be guaranteed completely secure.

10. Children's privacy

TrueFrame Studio is intended for users who are legally able to manage the connected creator and developer accounts required by the relevant platforms. It is not designed to knowingly collect personal information from children.

11. Changes to this policy

This Privacy Policy may be updated as TrueFrame Studio adds new integrations or storage methods. Material updates will be reflected by changing the effective date above.

12. Contact

For privacy questions or requests, use the TrueFrame Studio Support page.