1. Scope
This notice applies only to data processed by Regional Task Queue inside Attio. It does not describe the separate Buildrhaus website or other Buildrhaus services.
2. Data the app reads
Regional Task Queue reads only the Attio data needed to assemble the current member's queue and present it in context:
- The active workspace member identifier.
- Incomplete tasks assigned to that member, including task title, deadline, completion state, assignee and linked record identifiers.
- The name and primary location of a linked person or company.
- A linked person's company and that company's primary location when the person has no location.
- Object identifiers needed to distinguish supported people and companies records.
3. Why the data is used
The member identifier limits the queue to tasks assigned to the active member. Linked record locations determine whether a task belongs under AUS, Europe, US or Other. A leading square bracket label in the task title determines its type. Deadlines determine the order within each type.
Names are displayed so the member can recognize the record connected to a task before taking action.
4. Where processing happens
The app runs on Attio hosted App SDK infrastructure and calls only the public Attio REST API for application data. The app token is supplied inside the Attio hosted environment.
Buildrhaus operates no separate data processing backend for Regional Task Queue. The app does not send task or linked record data to an external Buildrhaus service and requires no external account or service connection.
5. The only write
The app can mark a task complete only after the member selects that task and clicks Mark complete. Before the write, it verifies that the task is still incomplete and still assigned to the active member.
The selected task's completion state is the only value changed by the app. Regional Task Queue does not create, delete or edit people or company records. It performs no scheduled processing and makes no background writes.
6. Storage and retention
Regional Task Queue does not add a separate Buildrhaus storage or retention layer for task or record data. It reads current data from Attio when the member opens or refreshes the queue, and the completion change remains in the Attio workspace.
7. Permissions
The app uses User Management read, Records read, Object Configuration read and Tasks read and write. An Attio admin controls whether those permissions are approved for the workspace.
8. Support messages
If you email support, Buildrhaus receives the information you choose to include in that message. Support correspondence is separate from the app's Attio data flow. Include only what is needed to explain the issue and never send API keys or other credentials.
9. Questions
For a privacy question about Regional Task Queue, email support@buildrhaus.com.
Read the Regional Task Queue Terms or return to the Regional Task Queue documentation.