SSS GOOGLE DRIVE CONNECTOR
Privacy policy
A personal connection, with a clear account of its intended data use.
Effective November 5, 2026
1. Who operates this project
Beasley Corp is the project name for the owner-operated SSS Google Drive Connector, a personal-use workflow for Snowblind Smart Server (SSS). Questions about privacy, access or deletion can be sent to hunterbdt@gmail.com. This is not a public file-hosting service.
2. This website and the connector are separate
This static website publishes project information and policies. It contains no Google sign-in, forms, analytics scripts, advertising, embedded third-party content or application cookies. It does not receive Drive files or OAuth tokens. When hosted on Cloudflare Pages, Cloudflare may process request information such as IP addresses, browser details and request timestamps to deliver and operate the website, under its privacy policy. This is not a promise that hosting produces no logs or cookies.
3. Google access and data involved
The intended connector uses rclone and the owner's Google OAuth authorization with https://www.googleapis.com/auth/drive.readonly. This scope permits reading metadata and reading, downloading or exporting accessible Drive file contents. Metadata can include file names, identifiers, folder structure, types, sizes and modification times. It does not grant permission to upload, modify or delete files in Google Drive.
This is broad read access across the authorized account's accessible Drive files; it is not limited by OAuth to selected Beasley Corp folders. Any rclone folder selection or filtering must be configured separately. The owner should check the actual consent grant and rclone configuration before use.
4. Purpose, storage and recipients
The permitted purpose is to bring the owner's authorized documents and research into an owner-managed personal archive on SSS. If configured, local copies and derived search indexes may be created there. These are intended uses, not confirmation that copying or indexing has been enabled.
Google processes authentication and API requests. rclone runs in the owner's configured environment, communicates with Google and normally stores reusable OAuth tokens in its configuration; exact storage depends on setup. Downloaded files reside in the configured destination. Logs may contain file names, paths, timestamps or errors, depending on logging settings.
This policy does not permit selling Google user data, using it for advertising, sharing it publicly, or using it to train generalized AI models. Sending Drive contents to external AI or other downstream services is outside the described workflow and requires a separate review and updated disclosure before it is enabled. The public website has no code that transfers Drive data to such services.
5. Retention, deletion and stopping access
No automated retention period or deletion schedule has been verified. Any copied files, indexes, logs and backups may remain in the owner's environment until the owner removes them. Tokens may remain in the rclone configuration until removed or invalidated.
The owner can stop scheduled jobs, remove the connector's access in Google Account connections, and remove the corresponding rclone configuration and tokens. Revoking Google access stops future authorized access but does not erase already downloaded copies. Local copies, derived indexes, logs and any backups must be reviewed and deleted separately. For assistance or a deletion request, email hunterbdt@gmail.com; no automatic completion or fixed response time is promised.
6. What has and has not been verified
These pages do not verify the live connector, its granted scopes, server network exposure, encryption at rest, access controls, token protection, backups, audit logging or deletion procedures. No certification, security audit or implemented server safeguard is claimed. The owner is responsible for configuring and checking the actual environment. This website provides no public route or login to SSS.
7. Changes and questions
This policy should be updated before material changes to the described handling of data. The effective date above identifies this version. Contact hunterbdt@gmail.com with privacy questions. See also the terms of service.