SVP Privacy Policy

Last updated: September 16, 2026

SVP ("the Service") is a local-first, single-owner software pipeline developed and operated exclusively by Göktuğ Turhan ("the Developer", "we", "our") to produce and publish original short-form documentary videos. This policy explains what data SVP accesses through the TikTok Content Posting API, how it is used, and how it is protected, in compliance with TikTok's Developer Terms of Service and Developer Data Security Requirements.

Summary: SVP is not a public multi-user application. It connects only to the Developer's own TikTok account, stores tokens only on the Developer's own device, and never collects, sells, or shares data belonging to any other person.

1. TikTok Data Accessed

SVP accesses the following data only after the Developer completes TikTok OAuth authorization for his own account, and only to perform the direct post the Developer explicitly approved:

Data	Purpose
open_id, access token, refresh token	Authenticate the Developer's own account for one Direct Post request
creator_info (nickname, privacy level options, comment/duet/stitch settings, max duration)	Display the account's real posting options before the Developer confirms a privacy level
The video file itself	Uploaded to TikTok as the post content the Developer authored and approved

2. How We Use This Data

Single-purpose use: Data returned by the TikTok API is used solely to complete the specific Direct Post upload the Developer initiated for a specific video file.
No external transmission: API calls go directly from the Developer's own machine to TikTok's official endpoints. SVP has no backend server, so no data ever passes through infrastructure controlled by anyone other than TikTok and the Developer.
No profiling, ads, or AI training: TikTok data is never used to build advertising profiles, train machine learning models, or track any user other than the Developer's own posting activity.
Explicit consent per post: Before any upload, SVP records the Developer's explicit consent for the selected privacy level and the required synthetic-media (AI-generated content) disclosure.

3. Storage, Retention & Deletion

Local storage only: OAuth tokens are stored strictly in an owner-only local file on the Developer's own machine, outside the project's source repository. They are never uploaded to any cloud service.
Publish receipts: After a successful post, SVP writes a local, non-secret receipt (publish ID, privacy level, video hash, timestamp) to keep an audit trail of what was published and when. This receipt contains no personal data about any third party.
Revocation: The Developer can revoke SVP's TikTok access at any time from TikTok account settings ("Manage apps"), which immediately invalidates the stored tokens. Deleting the local token file has the same effect on SVP's side.

4. Data Sharing

SVP does not sell, rent, or share any data with third parties. The only external party any data is ever sent to is TikTok itself, via its official API, to perform the upload the Developer explicitly approved.

5. Synthetic Media Disclosure

Every video SVP publishes to TikTok uses locally synthesized narration. Every such upload sets is_aigc: true and enables TikTok's AI-generated content label, consistent with TikTok's synthetic and manipulated media policy.

6. Children's Privacy

SVP is not directed at children and does not knowingly collect data from anyone other than its own Developer.

7. Changes to This Policy

Material changes to this policy will be reflected on this page with an updated "Last updated" date.

Contact & Developer

Developer: Göktuğ Turhan · Email: goktugturhan74@gmail.com · Website: alazlab.com