Use of Google Drive with Adinton involves visiting our authentication server (website) as part of the authentication (OAuth) flow. Note that no backup data or other data from your files goes to our servers – this all remains on google drive. So, when you see the Google permission authorisation screen, it is asking you about what the app will be able to do.
The authentication procedure will cause:
- Your IP address to be logged in our webserver logs. No further processing of these logs is carried out. These logs are kept for 6 months and then automatically deleted. We carry out no further processing on them. They are not shared with any third party.
- (If authentication succeeds) your Google account identifier to be stored in the authentication server’s database, so that the necessary authentication token can be given to your site if it requests it again. We carry out no further processing on them. They are not shared with any third party.
Terms of services
1. Your Content
Adinton allows you to upload statistics data content. As described in Adinton GDrive Terms of Service, your content remains your. We do not claim ownership in any of your content, including any text, data, information and files that you upload or store in your Drive account. The privacy settings of your files depends on the folder or drive they are in. All you can do with shared content is not managed by Adinton. We will not use your content for marketing purposes or promotional campaigns.
2. Program Policies
We may review content to determine whether it is working fine. We create a folder in your Drive named “Adinton” to upload statistics files in it. So we don’t review your own content in this folder, we only read/write adinton files. Adinton files are created with this nomenclature for every type: alert-(alertId) where alertId is an internal identifier variable, per example: alert-5eeb529a0ea2ff1e72611b69 audience-(audienceId) where audienceId is an internal identifier variable, per example: audience-5eeb529a0ea2ff1e72611b69