O8 Artifacts
O8 Artifacts Privacy
How O8 LLC handles Google Drive information for its own artifact workflows. This page covers the O8 Artifacts connection, rather than every O8 product or conversation.
Information accessed and used
The connection uses the Google authorization you grant to check the approved folder, create generated work files, inspect file metadata and permissions, and retrieve registered originals for permitted review. Metadata can include file names, identifiers, file types, sizes, revisions and checksums.
Google's drive.file permission limits access to files used with the application. O8 also checks the approved destination and the caller's current assignment and tool access. The artifact workflow requires private files and rejects destinations or originals with unapproved sharing.
Processing and storage
Generated artifacts and retained original revisions are stored in Google Drive. O8 keeps file references, integrity information, creator and assignment references, publication status and review evidence in private operational records. These records help verify which original was reviewed and recover an interrupted operation.
An authorized AI review may transmit an original file's contents, an extracted report or a preview to the AI provider configured for that review. This processing is part of inspecting the assigned work. Google authorization credentials are kept in protected application credential storage and are not supplied as model inputs. Short-lived Drive access tokens remain in application memory.
Retention and your choices
The workflow retains registered originals, their exact revisions and supporting evidence. It has no automatic deletion schedule for those artifacts or records. Retention and removal require an authorized operation; completing a review does not itself authorize deletion.
You can remove the application's authorization through your Google Account's connections settings. Revocation prevents further authorized Drive access. It does not recall information already processed or delete files, copies, review evidence or operational records. Removing a Drive file also does not remove O8's separate records.
Use the contact details accompanying these pages to ask about access, retention or deletion. Describe the relevant artifact or connection without sending passwords, authorization codes or tokens. A request must be checked against your authority and any required preservation of the work and its evidence.
These information pages
These pages are publicly readable. Access to the O8 application and its artifact files requires separate authorization.
These pages contain no analytics scripts, advertising scripts or submission forms. They do not connect to your Drive. Google consent and authorized artifact operations take place separately.
Contact
O8 LLC
admin@o8.chat