Data and permissions
Understand local data, authentication, AI requests and deletion
On this page
Stored locally
The extension uses browser IndexedDB for workflows, comment templates, execution logs, processed-post/comment records, collected users and groups. Collected data may include public profile links, identifiers and display information; public visibility does not authorize every downstream use. Chrome local storage also holds settings, user information and the Redaily login session.
Sent outside the browser
- Authentication, subscription checks and feedback contact the Redaily server. Server records include accounts, subscriptions and submitted feedback.
- AI requests send post titles, descriptions and relevant visible comments. Reply requests also include the target comment and context. The server calls models through OpenRouter; current code uses DeepSeek models with fallback configuration. Generation is not entirely local.
- Text you submit as feedback goes to the server. Remove passwords, sessions, third-party personal information and unrelated page content first.
- Payment and hosting services may process transaction and request records. Refer to the actual checkout service and privacy policy.
Requested extension permissions
| Permission | Current use |
|---|---|
| storage | Local settings and login state |
| alarms | Local task triggers and update checks |
| webNavigation | Navigation failure detection during page opening |
| cookies | Reading and synchronizing the Redaily auth_session cookie |
| declarativeNetRequest | Modifying or blocking selected network requests |
| HTTPS host access | The manifest declares https://*/*, broader than the two target sites, plus local development addresses |
The current background code also installs header-modification and blocking rules for Xiaohongshu shield/webprofile requests. These capabilities do not establish platform approval or guarantee freedom from detection, restrictions or bans. Review permissions in Chrome's extension details. Disabling or uninstalling the extension stops its subsequent execution.
Deletion and stopping processing
Stop workflows and schedules first. Settings provides a database reset that clears extension tables and restores initial data; this is separate from signing out or clearing authentication state. Delete downloaded CSV/JSON files separately. Remove published comments or follows on the target platform: deleting local logs does not undo those actions.
The website offers account deletion, and support can assist. Server account deletion, payment records, service logs, backups and AI-provider retention have different scopes; one delete action does not establish immediate deletion of every third-party copy. Provider retention and deletion also depend on their policies and configuration. Contact support about the required scope before sharing sensitive data.
Further reading
Privacy policy, AI comments, Contact and feedback.
Applies to extension 3.5.3. Reviewed on September 17, 2026.
For help, use Contact and feedback with your extension version, browser version, workflow type and a redacted error message.