Why Google Sheets?
rtrvr.ai uses Google Sheets as a "memory layer" for complex workflows. When you run multi-tab automations, each tab operates as an independent sub-agent that needs to read inputs and write results. Sheets provide a structured way to orchestrate these parallel operations.
Google Drive: drive.file Scope
We use Google's most restrictive Drive scope: drive.file. This is the smallest permission available and gives us access ONLY to files we create or files you explicitly select through the Google Drive Picker.
| Allowed | Not Allowed |
|---|---|
| Create new Google Sheets for workflow outputs | Browse or search your Drive |
| Access Sheets you explicitly select via file picker | Access your existing documents |
| Write results to Sheets rtrvr.ai created | Read files you haven't explicitly shared |
| — | Access shared drives or team files |
Local Actions
rtrvr.ai is built on a local-first architecture. The agent runs primarily in YOUR browser using Chrome Extension APIs. Your credentials never leave your machine — we use your existing logged-in sessions and never ask for passwords or store login tokens.
Data Retention
- We don't store Sheet data — it lives in YOUR Google account
- Task artifacts are retained only for workflow replay purposes
- Execution logs are automatically deleted after one week
- Logs are retained only for debugging and customer support
AI & Training Data
Your data is NOT used to train AI models. Our contract with Google explicitly forbids training on inference data, and rtrvr.ai does not perform any model training. Your workflows are processed and results returned — nothing more.
Best Practice: Dedicated Chrome Profile
For maximum peace of mind, use a dedicated Chrome profile for rtrvr.ai. This provides complete isolation from your main browsing and work accounts.
- Click your profile icon in Chrome (top right)
- Click "Add" to create a new profile
- Name it "rtrvr.ai Automation"
- Install the extension in this profile only