Add to ChromeCookie Sync copies the logins you choose from Chrome to your rtrvr Cloud browser. Use it when a Cloud task needs a site you're already signed in to, such as Instagram. Cookie Sync is available on paid plans.
Profile-Based Isolation
Cookie Sync is scoped to the current Chrome profile. Each profile has its own cookie store, and sync only reads from the profile where the extension is running. Use separate profiles for separate accounts.
Profile "Work" → syncs work Gmail cookies → deviceId: device-work
Profile "Personal" → syncs personal Gmail cookies → deviceId: device-personal
Profile "Client" → syncs client portal cookies → deviceId: device-clientHow It Works
- 01
Sign in to the site in the Chrome profile where you use the rtrvr extension. Sign in to rtrvr with the same account on the website and extension.
- 02
Click the cookie icon at the bottom of the extension to open Cookie Sync.
- 03
If Cookie Sync says cookie access is off, click Allow cookie access. Then search for the site, such as instagram.com, and select it from the suggestions or click Add.
- 04
Adding the first site starts syncing and turns on auto-sync. Check the site's last-sync time and sign-in status. Use Sync all now to refresh it manually.
- 05
On rtrvr.ai/cloud, check the Cookies panel, then choose an option under From the cloud in Routing and start your task.
Watch Cookie Sync from 2:18, or start at 0:00 to see the same Instagram task routed through Chrome first. See Run in your Chrome or in Cloud for the routing steps.
Saving to Google Sheets uses a separate connection. Follow the Connectors guide to grant Google Drive file access.
Auto-Sync Scheduling
Keep Auto-sync all sites on to refresh the sites in your sync list. Choose an interval from 15 minutes to 24 hours. A selected site also syncs again after you sign in to it. Keep Chrome open for these updates; Cloud uses the last saved login when Chrome is closed.
Domain Selection
Use Search or type a domain… to find sites in your current Chrome profile. Select a suggestion to add it. If the site doesn't appear, open it in Chrome and sign in, then try again. Only sites you add are synced; Auto-sync all sites refers to that list.
You can also ask in chat: "sync my cookies for linkedin.com to the cloud" or "make my scheduled run work on app.example.com". The agent adds the site and syncs it now. The first time, Chrome's cookies permission has to be granted by a click — the chat shows a Grant permission button and the run continues the moment you press it; adding a new site also asks for a one-time confirmation, because it turns on the recurring sync. The reply says whether a login was found for the site ("is linkedin.com synced?" reads the same status).
Cloud Storage
Cookies are stored at a Firebase path unique to your account and device:
user_cookies/{userId}/{deviceId}/{domain}
Example: user_cookies/abc123/device-work/linkedin_comSecurity & Privacy
- 01
Cookies are stored in your private Firebase path — no other users can access them
- 02
The "cookies" permission is optional and can be revoked anytime
- 03
You choose exactly which domains to sync — no automatic collection
- 04
Clear Cloud Data deletes cookies uploaded by this Chrome profile. Logins saved by another device or directly in Cloud stay; remove those in the website's Cookies panel.
- 05
Revoke Permission disables Cookie Sync and removes Chrome's cookies permission.
Troubleshooting
- 01
Verify cookies are synced: check "last synced" timestamps in the domain list
- 02
Re-sync manually: click the refresh icon to force an immediate upload
- 03
Check the right profile: make sure you're syncing from the profile where you're logged in
- 04
Session expired: log back into the site in your browser, then re-sync
- 05
Check the saved login in the website's Cookies panel. If you use several Chrome profiles, sync from the one signed in to the account you want.