DSB Team Queue
Privacy notice
Updated November 16, 2026
This notice covers DSB Team Queue, the DSB Media Windows companion and Chrome extension used by authorized staff for creator assignments and TikTok message preparation and sending. It does not describe every DSB Media service.
Google information accessed and why
When you choose Connect Google, Google handles account sign-in and file selection in your browser. The app requests only https://www.googleapis.com/auth/drive.file. It receives an authorization code, access token and refresh token to access the selected staff recruiting workbook on your behalf.
The app checks the workbook's identity, tab names and your edit capability. It downloads a workbook export, which can contain other tabs and columns in that workbook, to validate the signed creator release and read creator handles, creator IDs, invitation types, validation times, assignments and message drafts. When you explicitly claim a creator, it attempts to replace that creator's unassigned reservation marker with your entered desk name, then reads the workbook again to confirm the outcome.
This access supports the visible recruiting workflow. The app does not request Gmail, Google Contacts or access to every Drive file. Google authorization does not change the workbook's existing sharing permissions.
TikTok information and local queue records
The extension uses your existing signed-in TikTok browser session to check the sender account, open recipient conversations, prepare drafts and carry out a batch you review and start. It works with sender and recipient usernames, message text, conversation state and delivery indicators. Sign in on TikTok itself; the queue does not ask you to enter your TikTok password into the app.
Your Chrome profile stores queue and draft text, sender and recipient handles, settings, exclusions and delivery history. Delivery records include outcomes and timestamps, and can include failure reasons. Sent and uncertain outcomes help prevent duplicate sends. Clearing them removes that local evidence.
Storage and who can see the information
The Windows companion saves the Google refresh token outside the installed program folder under your local Windows app-data directory. It encrypts that saved grant with Windows Data Protection API (DPAPI), bound to the current Windows user. Access tokens are used by the companion for Google API requests. Workbook exports are processed locally for these operations.
Assignments and other workbook content remain in the Google-hosted staff workbook and are visible according to its existing access settings. Your entered desk name becomes visible there when a reservation succeeds. Messages you send are delivered through TikTok to the selected recipients. Local queue data belongs to the Chrome profile and can be accessed by people with access to that profile or computer. Google and TikTok also process information under their own policies.
The queue's Google-data workflow sends requests to Google for sign-in and workbook operations. It does not implement an advertising, data-sale, analytics-upload or model-training destination for Google user data. These two informational pages contain no analytics scripts, trackers or forms.
Revoking access and removing records
You can revoke the app's Google authorization through your Google Account connections. Your coordinator can separately change your workbook access. Revocation stops future authorized Google access; it does not erase prior workbook edits, TikTok messages or local queue records.
The saved Windows grant and Chrome extension data have no automatic deletion schedule in the current app. To remove the saved grant, close the queue and remove its grant files from %LOCALAPPDATA%\DSB\DMQueueTeam\google. To remove local queue data, remove the extension from the Chrome profile that used it. Removing the program folder alone does not clear those separate stores. Reinstalling or reconnecting can create new local data.
Contact DSB Media for help locating local records or requesting review or removal of DSB-controlled workbook records. Workbook history and TikTok messages are separate from local queue data; removing local data does not delete them. Review existing shared assignments before starting again with cleared delivery history.
Contact
For access, data handling or deletion questions about DSB Team Queue, email dsb@dsbagency.com.