Privacy policy
Updated 8 September 2026
Roost is an internal operating workspace for company records, tasks, knowledge, integrations and supervised automation. This policy describes how information is handled when you use Roost or connect an external account.
Operator and contact
The operator is Patryk Wróblewski (LuckySparrow). For privacy questions, access requests, correction or deletion requests, contact luckysparroww@gmail.com. Workspace members can also contact their workspace administrator.
Information processed
- Account details such as your name, email address, profile preferences and workspace membership. Roost stores password hashes rather than plaintext passwords.
- Company records that authorized users enter or import, including tasks, notes, documents, relationships and operational history.
- Connection credentials and OAuth tokens needed to access services you connect. Integration secrets are encrypted at rest.
- Technical and audit information used to operate the service, enforce access permissions, diagnose failures and record changes.
Google Drive, Docs and Sheets
When you connect Google, Roost requests permission to work with Drive files, Google Docs and Google Sheets. Drive permission enables work with existing files in the folders selected for synchronization, including reading content, creating and editing files, changing names, moving files and placing files in or restoring them from the trash.
Roost stores selected folder and file metadata and, for supported document types, content snapshots, extracted text and summaries. These support search, workspace knowledge and synchronization. Selecting folders in Roost limits its synchronization scope; it does not narrow the Google account permission itself.
When authorized users or configured agents make supported changes in Roost, those changes may be written back to Google. Changes made in Google may update the corresponding Roost records.
ClickUp
A connected ClickUp account lets Roost synchronize selected lists, tasks and supported comments. Task names, descriptions, statuses, dates, priorities and identifiers may be stored locally. Supported changes can be written back to ClickUp, and signed notifications from ClickUp update Roost.
Use and sharing
Information is used to provide the workspace functions you request, maintain synchronization, support approved workflows and protect the service. It is available to authorized workspace members and to external services or agents enabled and authorized for that workspace. Hosting and infrastructure services process information as needed to run Roost.
Agent integrations can receive workspace context, including connected document content, when authorized for their work. Administrators are responsible for enabling appropriate tools and access. Roost does not sell Google user data, use it for advertising, or use it to train general-purpose AI models.
Roost's handling of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements. Transfers to enabled tools must follow those same restrictions.
Storage, retention and removal
Workspace records, content snapshots and audit history remain stored while needed for workspace operations, security and applicable obligations. Disconnecting an integration stops future authorized access but does not automatically erase previously imported records or delete files in the provider account. Contact the operator or workspace administrator to request removal of stored data. Older copies may remain in backups until the applicable backup retention cycle completes.
You can revoke Roost's Google access in your Google Account connections. You can also disable integrations in Roost settings. Requests concerning access, correction, deletion or restrictions on processing are handled in accordance with applicable requirements.
Browser storage and security
Roost uses browser storage for sign-in state, interface preferences and temporary OAuth state. Access controls separate workspaces and enforce membership roles. Credentials, accounts and approved agent tools should be protected by their users and administrators.
Changes to this policy
The current policy is published at this address with its update date. Material changes to how connected data is used must be disclosed before that new use takes place.