Your data / The evidence trail
Privacy Policy
Effective date: November 20, 2026 (2026-11-20)
Dijital Dedektif Studio is a single-creator tool for making educational code-forensics videos and posting to the creator’s own account. This policy covers the tool and this static listing site. Contact the operator at chemicalpeaces@gmail.com.
TikTok data and permissions
Login Kit authorization requests video.publish (Direct Post video publishing) and user.info.basic (basic profile access). The current publisher queries TikTok’s creator-info endpoint for account information, including the creator username and available privacy options. It does not separately query the user-profile endpoint or request followers, messages, contacts, or viewing history.
The local OAuth helper receives an authorization code at http://127.0.0.1:8080/callback and exchanges it for tokens. The publisher uses access and refresh tokens, receives upload instructions and a publish ID, and checks processing status and any returned post IDs. Video files, titles, hashtags, and posting settings are sent to TikTok to publish the creator’s content.
Why data is used
Authorization data enables authenticated API calls. Creator information determines permitted posting privacy and forms publication links. Publish IDs, status results, and publication links support retries, reporting, and avoiding duplicate completed publications. Script history helps avoid repeated topics.
Storage and retention
- Credentials are supplied through environment variables, a local
.envfile, or GitHub Actions secrets. The authorization helper prints the refresh token for the creator to store securely; it does not save it automatically. - Rotated TikTok refresh tokens are written to
TIKTOK_TOKEN_FILE, default.secrets/tiktok-token.json, with owner-only file permissions (0600). The scheduled workflow can update the GitHub Actions refresh-token secret. Access tokens and creator-info responses are held in process memory; signed upload URLs are not written to state or receipts. - The default SQLite database,
state/autopilot.db, retains scripts, job checkpoints, events, errors, timestamps, and publication links. Token-free receipts retain publish IDs. Generated media and reports are stored in local artifact and report directories. - The scheduled workflow persists the database and token-free receipts in the
autopilot-statebranch, caches media for resuming work, and uploads rendered MP4 artifacts with a seven-day retention setting. GitHub controls cache eviction. Reports also go to Actions summaries, a repository issue, and an optional configured webhook. - There is no automatic expiry for local tokens, local media, database history, receipts, or reports. They remain until the creator deletes them, replaces credentials, or the hosting provider removes them under its policies. Repository history and backups may retain copies after ordinary file deletion; these must be addressed separately when removing data.
Keep credentials out of source control. State, artifacts, and reports can expose content or account links if the creator makes their repository or outputs public.
No sale; limited service-provider disclosure
We do not sell personal data or share it for advertising. Data is disclosed only as needed for the configured services below, at the creator’s direction, or where legally required. TikTok tokens and creator-info responses are not used as inputs to the script, speech, or image-generation services.
- TikTok: authorization, creator information, video upload, posting metadata, and processing status.
- Google Gemini: script-generation prompts, channel configuration, and previous script titles.
- Microsoft Edge-TTS: narration text and voice selection for speech synthesis.
- Pollinations and optional Pexels: image prompts or search queries for visuals; locally generated cards are the final fallback.
- Optional YouTube / Google APIs: separate creator authorization and video upload with titles, descriptions, tags, and privacy settings when YouTube publishing is configured.
- Optional rendering worker: media and rendering inputs are sent to the creator-configured worker instead of rendering locally.
- GitHub and optional report webhook: scheduled execution, secrets, state, media cache, artifacts, and operational reports as described above.
Each provider processes the data it receives under its own terms and privacy policies. This static site has no application analytics, tracking scripts, cookies, or external embedded assets. Its hosting provider may process ordinary request information such as IP addresses and access logs.
Revoking access and deleting data
Remove this app’s access in TikTok settings under the connected-app permissions (typically Settings and privacy → Security & permissions → Apps and services permissions; labels may vary). Stop scheduled runs, delete the local TikTok token file and any copies, and remove TIKTOK_REFRESH_TOKEN from local environment or .env files and GitHub Actions secrets. Revocation does not automatically erase local records or already posted videos; manage published posts in TikTok.
For deletion requests, email chemicalpeaces@gmail.com with the account or records concerned, but never include passwords or tokens. We may request enough information to verify ownership and will delete data under our control, subject to legal obligations. Creator-controlled local files, repository history, caches, artifacts, reports, backups, and provider-held copies may require separate removal by the creator or relevant provider.
Children
This tool is not intended for children under 13 or anyone below the applicable minimum age for TikTok or developer services. We do not knowingly collect children’s data. Contact us if you believe a child’s data has been provided.
Changes and contact
Updates will be posted on this page with a revised effective date. Questions about this policy or data handling: chemicalpeaces@gmail.com.