Privacy Policy
This policy describes what information the Affiliate VDO Automation application receives, why it receives it, where it is kept, and how to have it removed. It describes the software as it is actually built today. Where something is intended but not yet enabled, this policy says so rather than describing it as if it were running.
1. What this policy covers
Two separate things:
- This website — the pages you are reading now.
- The application — a program that runs on the computer of the person operating it, and which can be authorised by an account holder to read public figures from their own social accounts.
2. This website
These pages are static files. This site sets no cookies, runs no analytics, embeds no tracking pixel, loads no third-party font, script or stylesheet, and has no form, login or comment box. There is nothing here that asks you for information.
The site is served by a third-party hosting provider. Like any web host, that provider handles the network request your browser makes, and may keep its own operational records of requests it serves — typically things such as an IP address, a timestamp and the page requested. Those records belong to the hosting provider and are governed by that provider's own policies, not by this one.
3. Information received through TikTok authorisation
The TikTok integration is not enabled yet. This section describes what it is intended to receive when it is, so that the description exists before anything is granted rather than after.
If an account holder authorises the application on TikTok, it is intended to receive, for that account only:
- the account identifier TikTok issues to this application for that user, and the basic profile information TikTok returns with it, used to confirm the connection is to the intended account;
- identifiers, links and publication times for that account's own public videos;
- four public engagement counts for those videos: views, likes, comments and shares;
- an authorisation token, issued by TikTok, that lets the application make those read-only requests until the token expires or is withdrawn.
It is not intended to receive private videos, drafts, direct messages, follower lists, information about the people who watched a video, or anything belonging to any other account. Further detail is on the TikTok integration page.
4. Why it is used
For one purpose: to let the person operating the application see how the videos they published actually performed, and to keep a record of that over time so that later work can be informed by it. The information is not used for advertising, is not sold, and is not used to build a profile of anybody else.
5. Where it is kept
Records the application creates are kept in files on the computer where the application runs. There is no shared server holding them and no account on this website that stores them.
When the TikTok integration is enabled, authorisation tokens will be kept apart from the application's own source code and will not be written into its reports or logs. No such token exists today, because the integration is not enabled.
The application does send requests over the internet to the third-party services it is configured to use — for the integration described here, that is TikTok. What a third-party service does with a request it receives is governed by that service's own terms and privacy policy. The application is also designed so that information obtained through TikTok authorisation is used only for the purposes in section 4, and is not passed to the separate services it may use to help produce video content.
6. How long it is kept
Records are kept until the person operating the application deletes them. There is no automatic deletion schedule, and no fixed retention period is claimed here, because none has been set. Authorisation tokens stop working when they expire or when authorisation is withdrawn.
7. Security
The application is built to request only the narrow, read-only permissions it needs, and to avoid storing anything it does not need for the purpose in section 4. When the TikTok integration is enabled, authorisation tokens will be kept out of its source code, reports and logs.
No claim is made here about any particular security certification, standard, audit or accreditation, because none has been obtained. Software running on an ordinary personal computer is only as protected as that computer is.
8. Withdrawing authorisation, and asking for removal
Authorisation can be withdrawn at any time from your own TikTok account settings, using TikTok's own control for the applications you have connected. That control works whether or not this application is running.
To ask for information already recorded about your account to be removed, write to the contact address in section 11. Requests are handled by a person, not by an automated system, and the reply will say what was found and what was done.
9. Third-party services
Information covered by this policy reaches TikTok because TikTok is where it comes from: the application asks TikTok for it. TikTok's handling of your account and your data is governed by TikTok's own policies. This site's hosting provider is described in section 2.
10. Changes to this policy
This policy will change as the application changes — in particular when the TikTok integration stops being intended and starts being enabled. When it changes, the effective date at the top of this page changes with it. Material changes will be described rather than made silently.