Privacy Policy

Last updated: 19 August 2026

VAS Content Assistant is a personal tool operated by one individual for his own social media accounts. This policy describes what data it handles and why. It is written to be accurate rather than broad: it does not claim practices that do not exist.

1. Whose data is processed

In normal operation the assistant processes data belonging to its own owner's accounts only. It does not collect data about other people's accounts, and it is not used to build profiles of other users.

Content that other people have made public on the owner's own posts — for example the text of a comment left on one of his videos, together with its public author name — is visible to the assistant when it reads that post's comments, in the same way it is visible to anyone viewing the post.

2. What data may be processed

CategoryExamplesWhy
Profile identifiers TikTok open_id, union_id To identify which authorized account a request belongs to
Profile information Display name, username, avatar URL, bio, verified status, profile link To confirm the correct account is connected and label saved data
Account statistics Follower count, following count, total likes, video count To let the owner track how his own account develops over time
Public video metadata and counters Video ID, title, description, creation time, duration, cover image and share URL, view / like / comment / share counts To let the owner review how his own videos perform
Comment content on the owner's own posts Comment text and public author display name So the owner can read and consider responses to his own content
Content the owner uploads Video files, titles, descriptions, thumbnails and captions that the owner creates and chooses to send to a platform To let the owner publish or draft his own content through the platform's official API instead of by hand
OAuth tokens Access token, refresh token, granted scopes To maintain authorized access without repeated logins

Uploading is always initiated by the owner for his own content. The assistant does not upload, publish, or modify anything on its own initiative, and it does not post to any account other than the owner's own authorized accounts.

3. Where data is stored

All of the above is stored locally, on the owner's own computer. There is no server, no hosted database, and no cloud backend operated by this application. This website is a set of static pages and does not receive, collect, or store any data from visitors.

4. Credentials and tokens

API credentials and OAuth tokens are kept in local files with restricted file permissions, outside of any code repository. They are never published, never committed to version control, never included in reports or exports, and never shared with anyone.

5. What is not done with the data

6. Retention

Data is kept only as long as it is useful for the owner's own review of his own accounts, and no longer than necessary for that purpose. Because the value of these statistics comes from comparing them over time, historical snapshots of the owner's own metrics may be kept. Tokens are kept only while the authorization remains active, and are deleted when access is revoked or the tool stops being used.

7. Revoking access

Authorization can be withdrawn at any time by the account holder, directly on the platform and without contacting us:

Revocation takes effect immediately and permanently ends the assistant's access.

8. Requesting deletion

To request deletion of data relating to you, write to akhvatkin@gmail.com. Because the data is held in local files rather than in a hosted service, deletion is performed directly on those files. Requests are answered within 30 days.

9. Children

This tool is not directed at children and is not intended for use by anyone under the age required by the relevant platform's own terms.

10. Changes

This policy may be updated. The date at the top of this page reflects the most recent revision.

11. Contact

akhvatkin@gmail.com