1. Who operates this application
Settlio Research Archive (the "application") is a private research tool operated by Settlio (the "operator"). It is not offered to the public. The only Google account that signs in to it is the operator's own.
2. What Google data the application accesses
The application requests one Google OAuth scope:
https://www.googleapis.com/auth/drive.file: create files in Google Drive, and see, edit and delete only the files that this application created.
With this scope the application cannot list, open, read or change any other file in the operator's Google Drive. It does not request access to Gmail, Contacts, Calendar or any other Google service.
3. How the data is used
The application uploads research reports and supporting files that it generated itself on the operator's server to a folder in the operator's Google Drive. It then reads those uploaded files' checksums back, to confirm the copies are complete. That is the only use of Google Drive.
The application does not use data obtained through Google APIs for advertising. It does not sell it, does not share it with third parties, and does not use it to train artificial-intelligence or machine-learning models.
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.
4. What is stored, and where
- Files uploaded to Google Drive remain in the operator's own Google Drive, under the operator's Google account.
- The OAuth credentials (the access and refresh tokens Google issues) are stored in one configuration file on the operator's server. Only one server user account and the server's administrator can read it.
- The application keeps local logs of each upload: file names, sizes, timings and checksums. They do not contain the Google credentials.
5. Security
- All communication with Google APIs uses HTTPS.
- Access to Google Drive is limited by the
drive.filescope described above. - The credentials file can be read only by the server user that runs the application and by the server's administrator.
6. Retention and deletion
- Files the application uploads stay in the operator's Google Drive until the operator deletes them. The application never deletes files. It may replace a file it uploaded earlier, if that file's content has changed.
- The operator can revoke the application's access at any time. Go to the Google Account third-party connections page, select the application and remove access. After revocation the stored tokens no longer work, and the operator deletes the configuration file from the server.
- Revoking access does not delete files that were already uploaded. Those stay in the operator's Drive until the operator removes them.
7. This website
This website is static. It uses no cookies, no analytics and no third-party scripts. Its hosting provider (Cloudflare) processes standard technical request data, such as IP addresses, to deliver the pages.
8. Changes
If this policy changes, the updated version is published on this page with a new effective date.
9. Contact
Questions about this policy: arunmuthusamy8888@gmail.com