Privacy Policy
Applies to: the OAuth client named jaeku.kr Drive Client Operator: jaeku.kr · [email protected]
요약 (Korean summary)
이 앱은 데이터를 수집하지 않습니다. Google 인증 토큰은 앱을 인증한 각 컴퓨터의 로컬 파일에만 저장되며(소유자 전용 권한), 외부로 전송되지 않습니다. 운영자 본인 외에 이 앱을 사용하는 사람은 없습니다.
Summary
This application collects nothing, transmits nothing to third parties, and operates no servers. It runs locally and talks only to Google's APIs.
Who uses this application
The operator, and no one else. There is no registration and no other user accounts.
What data the application accesses
When authorized, the application can read and write files in the Google Drive of the account that granted access — that account being the operator's own. It accesses file contents and metadata only as needed to carry out commands the operator runs (listing directories, reading a file, uploading a file).
The application does not access contacts, mail, calendar, or any Google service other than Drive.
What data is stored, and where
| Data | Location | Protection |
|---|---|---|
| OAuth refresh & access token | A local configuration file on each computer where the client has been authorized (typically ~/.config/rclone/rclone.conf; the exact path depends on the operating system) |
Owner-only file and directory permissions |
| Cached file contents | A local cache directory on the same computer | Owner-only permissions |
Nothing is stored anywhere else. There is no database, no hosted backend, and no remote logging.
The client is authorized on more than one computer — at the time of writing, one Linux workstation and one macOS laptop, all used by the operator. The operator may authorize additional machines they use. This does not change anything above: each machine keeps its own local credentials, and no machine sends data anywhere other than Google's APIs.
What data is shared
None. No data is sold, rented, shared, or disclosed to any third party. There is no analytics, telemetry, advertising, or tracking of any kind.
Network traffic goes only between the operator's own machines and Google's APIs.
Retention and deletion
Credentials persist locally on each authorized machine until the operator deletes them or revokes access. Deleting that machine's rclone configuration file removes its stored credentials immediately. Revoking access (below) invalidates the credentials held by every machine at once.
Revoking access
Access can be withdrawn at any time from Google Account permissions. Revoking access invalidates the stored token; the application can then do nothing until re-authorized.
Google API Services User Data Policy
This application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Children
The application is not directed at children and is used only by its operator.
Changes
Material changes to this policy will be published on this page. The page history is the record of changes.