Privacy Policy

This policy describes the Destiny 1 Dev Blog documentation website and its local Windows production application, operated by Luke McClellan. Contact the operator at lcmcclellan28@gmail.com with privacy questions or requests.

Website visits

The public documentation pages contain no advertising, analytics scripts, tracking pixels, embedded social feeds or application login. The hosting provider receives information necessary to serve the site, which can include an IP address, requested URL, browser information and technical logs. Hosting access controls may require provider sign-in while the site is private. The operator does not receive your TikTok password through this website.

Data used by the local application

The owner chooses the footage, screenshots, audio, package metadata, project notes, titles and captions used in production. The application creates analysis data, proxies, previews, edits, thumbnails, approval records and publishing history locally. Package metadata can contain sensitive information; it must be reviewed before sharing.

Connecting TikTok provides an app-specific account ID, display name, granted permissions and access/refresh tokens. The application uses these to identify the intended account, transfer an approved clip and reconcile confirmed publication status and share URLs. YouTube account authorization is handled separately.

Storage and security

On Windows, app credentials and platform tokens are encrypted with Windows DPAPI for the signed-in Windows user. They are not returned by the dashboard state API. Footage, project records and generated files are stored on the owner's machine or configured NAS; this policy does not claim they are encrypted by the application. The publisher's dashboard is restricted to loopback hosts.

This documentation site contains no publisher credentials or footage. Account authorization returns to the local application, not this website.

When information leaves the machine

Authorized API requests send account tokens and the information needed for that request to the relevant platform. An approved TikTok inbox transfer sends the selected video to TikTok. The creator chooses the final caption and publication settings inside TikTok. YouTube uploads send the approved video and its configured metadata to Google. Dry-run mode sends no video.

The app does not sell account data, use it for advertising or send source footage to a hosted AI service. It uses local production tools. TikTok, Google, the website host and email provider handle information under their own applicable terms and privacy policies.

Retention and deletion

Local footage and production history remain until the owner removes them. Disconnect removes the local platform token, pending OAuth state and cached account identity; saved app credentials are retained for later connection. Revoke TikTok access additionally requests platform token revocation. Credentials can be removed from the local encrypted vault by the owner. Removing local files or revoking a grant does not delete videos already sent to a platform.

To delete a TikTok draft or post, use TikTok's controls. Delete locally retained footage and project history through the machine or NAS owner. If you contact support, your email and request are used to respond and handle the issue; request deletion through the same contact.

Your choices and rights

You choose whether to connect an account or transfer a clip. You can revoke platform access and request access, correction or deletion of personal information held by the operator. Where applicable, you may have other data-protection rights and a right to complain to your data-protection authority. Contact the operator so the relevant records and request can be identified.

Changes

The operator will update the date and this policy when the application's data practices change. Material changes affecting account access require appropriate notice and any required renewed consent.