In one sentence: King Home Backup Sync is a personal backup client used by a single person — its own author — to copy his own files out of his own Google Drive onto his own computer; it holds no data belonging to any third party, has no other users, and shares nothing with anyone.
Who this policy is from
King Home Backup Sync (“the application”) is written and operated by Christopher King, a private individual in South Africa, for his own personal use. There is no company behind it, no employees and no commercial activity of any kind. The application is not distributed, is not published to any app store, and cannot be installed or signed into by anybody else.
Who uses the application
One person: the author. The application authenticates to exactly one Google Account — the author’s own — and there is no mechanism by which a second account could be added. It has no user registration, no user database, no login page and no public interface. If you are reading this, you are reading the privacy policy of a program used by nobody but the person who wrote it.
What Google user data the application accesses
The application requests read-only access to the author’s own Google Drive. With that access it does two things, and nothing else:
- Lists the contents of one folder in the author’s Drive, in order to identify which backup file is the most recent.
- Downloads that one file — a backup archive that another of the author’s own applications wrote there.
It does not read any other folder, does not open documents, does not read email, contacts, calendar, photos or any other Google service, and does not access any account other than the author’s own.
What the application never does
- It never creates, edits, renames, moves, shares or deletes anything in Google Drive. Its access is read-only.
- It never accesses a Google Account other than the author’s.
- It never transmits Google user data to any third party, server or service.
- It never uses Google user data for advertising, profiling or marketing.
- It never uses Google user data to train, fine-tune or evaluate any artificial-intelligence or machine-learning model.
- It never sells data. There is nothing to sell and nobody to sell it to.
How the data is used and stored
The downloaded backup file is written to a private server in the author’s home in South Africa, and is read there by the author’s own tooling. The file never leaves that machine, and the machine is not reachable from the public internet for this purpose. Copies exist only on other hardware the author owns.
The application also stores an OAuth refresh token so that it can run unattended on a daily schedule. That token is kept in a file readable only by the account that runs the job, on the same private server, and is used for no purpose other than re-authenticating to the author’s own Drive.
How long data is kept
The downloaded backup is kept on the author’s server for as long as it is useful to him, and is overwritten or deleted at his discretion. It is his own data, and no other person’s data is present in it. The OAuth token is kept until the author revokes it, which he can do at any time from his own Google Account security settings, after which the application simply stops working.
Who the data is shared with
Nobody. There are no third-party recipients, no analytics providers, no advertising networks and no subprocessors. No cloud service is involved in handling the downloaded data beyond Google Drive itself, which is where the file already was. The application makes no outbound network connection other than to Google’s own APIs.
Limited Use disclosure
The application’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Data belonging to other people
There is none. The application has one user, reads one account, and processes only that account owner’s own files. This website collects nothing either: both pages are static files with no analytics, no cookies, no tracking and no forms.
Children
The application is used solely by an adult — its author — and is not directed at, available to, or usable by children.
Your rights and control
Because the only person whose data the application touches is its author, the usual rights of access, correction and deletion are exercised by him directly on his own systems. Access can be withdrawn at any moment by revoking the application at myaccount.google.com/permissions. South African data-protection law (POPIA) applies to the operator as a private individual processing his own personal information.
Security
Access is read-only and scoped as narrowly as the task allows. Credentials are stored outside version control and are never committed to any repository. All communication with Google is over encrypted connections. Were the token ever exposed, it would be revoked immediately and reissued.
Changes to this policy
If this policy changes, the date at the top of the page changes with it. Since the application has a single user, who is also its author, there is nobody else to notify.
Contact
Questions about this policy, or about the application’s handling of data, go to christopher234king@gmail.com.