Privacy Policy
Research Result Sync · Last updated 29 August 2026
1. Who this policy covers
Research Result Sync is a private automation tool used by one person: its developer. It is not offered to the public, has no sign-up, and accepts no other users. This policy describes how it handles data belonging to that single user.
2. What data the application accesses
The application accesses files in the developer's own Google Drive through the Google Drive API, using the scope https://www.googleapis.com/auth/drive. It performs three operations, all confined to one folder of that Drive:
- uploading result files produced by scientific computations (JSON logs and PNG figures);
- reading those files back;
- listing the folder to determine which files still need to be copied.
It accesses no other Google service. It does not read email, contacts, calendar, photos, or any file unrelated to the purpose above.
3. What data the application does not collect
The application has no users other than its developer, so it collects, stores, and processes no personal information belonging to any other person. This website sets no cookies, runs no analytics, and serves no advertising.
4. Limited use of Google user data
Research Result Sync's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In particular: data obtained through the Google Drive API is used only to provide the backup function described on the homepage; it is not transferred to any third party; it is not used for advertising, profiling, or market research; it is not sold; and it is not used to train, fine-tune, or evaluate any machine learning or artificial intelligence model. No human reads this data other than the developer, who owns it.
5. How data is stored and transmitted
Result files are held in two places: the developer's own Google Drive, and a virtual private server rented and administered by the developer. All network transmission uses HTTPS/TLS. The OAuth refresh token issued by Google is stored as a file on that server, readable only by the server's administrator account, and is never transmitted to any third party.
6. Sharing
No data is shared with, sold to, or disclosed to any third party. The only parties involved are Google (as the storage provider chosen by the developer) and the developer.
7. Retention and deletion
Result files remain in the developer's Google Drive until the developer deletes them. Copies on the developer's own server are removed by the developer. Authorization can be revoked at any time from the third-party access page of the developer's Google account; once revoked, the application immediately and permanently loses all access to Google Drive.
8. Security
Access to the developer's server is restricted to key-based administrative login. The storage service running on it requires a randomly generated token for every request and confines writes to a single directory. Certificates for all endpoints are issued by a public certificate authority and renewed automatically.
9. Changes to this policy
Any change is published by updating this page and the date shown above.
10. Contact
This application is not offered to the public. Questions may be directed to the developer at the support email registered for this application in the Google Cloud Console.
11. Trademarks
This application is independent and is not affiliated with, endorsed by, or sponsored by Google LLC or by the rclone project. Google Drive and Google are trademarks of Google LLC.