Privacy policy

1. Data the connection accesses

After Google authorization, Eyos Storage can access file contents and file metadata, including names, identifiers, sizes, folder structure, and modification times. It can also request storage usage information. It stores OAuth credentials and tokens needed to maintain the authorized connection.

The requested Google Drive permission allows reading, creating, updating, organizing, and deleting files. The server mount is configured to display a dedicated VPS folder. That folder setting limits what the mount shows; the Google permission itself covers Drive more broadly.

2. How the data is used

Data is used to list folders, read or stream media, upload files, maintain a local file cache, and carry out file changes requested by the owner or their authorized server applications. The connection does not sell Google user data, use it for advertising, or use it to train general-purpose AI models.

Google API data is used only to provide this storage connection, in accordance with the Google API Services User Data Policy, including its Limited Use requirements.

3. Storage and access

Original files are stored in Google Drive. Files being read or written may also be cached on the private server. OAuth credentials and tokens are stored in access-restricted files on that server. Operational logs may include filenames and transfer or error information.

Google API traffic uses HTTPS. The server owner controls access to the server and its files. Google and the server’s hosting infrastructure process data as needed to operate the connection. Eyos Storage does not automatically publish files or grant other people access to them.

4. Retention and deletion

Files remain in Google Drive until the owner changes or deletes them, subject to Google’s trash and retention behavior. Local cached files are removed according to cache settings; open files and pending uploads may remain longer. Tokens remain on the server until removed or replaced, and logs remain until rotated or deleted.

The owner can stop the connection and remove its saved credentials, local cached copies, and logs. Deleting a file through the connected storage can also delete or move the corresponding file to trash in Google Drive.

5. Disconnecting Google Drive

Access can be revoked through Google Account connections. Revocation prevents future authorized API access once existing access tokens are no longer valid. It does not automatically remove files already stored in Drive or cached on the server; those copies can be removed separately by the owner.

6. This website

This public website does not sign visitors in, request Google Drive access, or display Drive files. It uses no advertising, analytics scripts, or tracking cookies. Hosting infrastructure may process basic request information, such as IP addresses, requested pages, and errors, to serve and secure the website.

7. Contact and updates

For privacy, access, or deletion requests, contact the app owner at eyosiastamirat20@gmail.com.

Changes to these practices will be reflected on this page with an updated effective date. Additional consent will be requested before Google user data is used for a new purpose that requires it.