RJS Native Upload Privacy

Data accessed and why

The tool reads owner-selected local files and their metadata. With authorization, it accesses Google Drive account identity and storage information, existing file and folder metadata, and file contents needed for reconciliation and verification. Local records may contain filenames, folder locations, sizes, timestamps, cryptographic hashes, Drive file identifiers and transfer status.

Full Google Drive access is requested to reconcile earlier archive files as well as new copies. That Google permission is broader than the supplied copy-only workflow: it can permit viewing, creating, editing and deleting Drive files. The program limits its transfer work to the operator's predetermined archive targets.

Where data goes

Originals travel directly from the operator's Mac to the selected Google Drive account. Verification can retrieve stored bytes back to the Mac. Metadata companions and receipts are kept locally and, where the operator selects, in private archive folders in Drive.

The tool has no application server receiving archive content. Google processes the authorized requests and stores the selected copies under its own terms. These web pages do not receive originals, Google authorization credentials or transfer logs.

Credentials and access

Google sign-in uses Google's authorization flow. OAuth credentials and the local client configuration remain on the operator's Mac, where the local code uses them to communicate directly with Google. They are not embedded in these pages or sent to a separate application server.

Sharing and permitted use

Google data is used for the archive copying, reconciliation and verification described here. The uploader does not sell data, use it for advertising, train AI models, call an external AI API or automatically send archive content to another person. It does not automatically grant collaborators access or make Drive files public.

The use and transfer of Google API data is limited to these purposes and is subject to the Google API Services User Data Policy, including its Limited Use requirements.

Retention and deletion

Retention is controlled by the operator. Source originals are never automatically deleted by this uploader. Local journals, credentials, logs and metadata sidecars remain until the operator manages or removes them. Drive copies remain in the selected account until the operator manages or deletes them through his account.

Revoking access

The operator can stop the local program and remove its connection in Google Account security settings. Revocation prevents future authorized access; it does not automatically delete existing Drive copies or local configuration. Local credentials can be removed separately on the Mac.

These informational pages

The uploader information provided here includes no sign-in form or archive upload form. The local uploader has no advertising or analytics integration. These pages are served within the River Jade Smithy storefront, whose hosting platform and installed storefront features may process ordinary browsing data under their own privacy and cookie practices. That browsing activity is separate from the local archive transfer.

Questions and changes

Contact Travis Huffaker through the support contact shown in this app's Google authorization information. Changes to this policy will be reflected on this page with an updated date.