Usage data
What usage data the dashsquad apps and the HQ send, what they never send, and how to turn it off.
The dashsquad apps send a small, fixed set of usage events. These events tell us which features people use. They never contain what you say to your agents or what your agents do.
The web app, Desktop and the iOS app send usage events when you are signed in to a dashsquad account. The HQ sends usage events about work that your agents do without you, for example routine runs. The Android app does not send usage events.
What the apps send
The apps send the events to the dashsquad control plane. The control plane sends them to PostHog Cloud EU (Frankfurt).
| Event | Extra data |
|---|---|
app_opened, signed_in, signed_out | None |
screen_viewed | The screen, from a fixed list |
gateway_paired, gateway_removed | None |
conversation_started | None |
message_sent | The input type (text, voice or dictation) and the number of attachments |
turn_finished | The result (done, error or cancelled), the duration and the number of tool calls |
turn_stopped | None |
voice_mode_started | None |
voice_mode_ended | The duration |
agent_created, agent_deleted | None |
question_answered | None |
effort_changed | The effort level set for a conversation (default, low, medium, high or extra high) |
setup_step | The step of the Desktop setup wizard (account, HQ, phone, AI provider or done) and the result (ok, skipped, later or failed) |
chat_archived, chat_restored | The control that you used: the sidebar button, the menu, the shortcut, the archived-chat bar or Undo |
Not all apps send all events. For example, only the iOS app sends the voice mode events.
Events from the HQ
The HQ sends these events only when it is paired with your dashsquad account. It sends them also when you do not use an app. The control plane links each event to the account that paired the HQ.
| Event | Extra data |
|---|---|
agent_message_sent | The result (delivered, queued or refused). For a refused message, the reason, from a fixed list |
agent_thread_paused | The reason (message limit, hop limit or user) |
goal_created | Who created the goal (you or an agent) |
goal_finished | The end state (completed, cancelled or limit reached) |
routine_created | Who created the routine (you or an agent) and the schedule type (daily, weekdays, weekly, interval, once or cron) |
routine_run | The result (ran, quiet, skipped or failed). For a skipped run, the reason, from a fixed list |
turn_failed | The reason (cancelled, interrupted, or the type of provider failure: auth, permission, model unavailable, rate limit, quota, network or other) and what started the turn (you, a notification, a parent agent, an agent, a routine, a wake-up, a goal or a new chat from an agent). Never the error text, the model, the agent or an ID |
unattended_limit_reached | The type of daily limit (cost in USD or tokens) |
Each event also has the platform (web, desktop, iOS or HQ), the release channel, the app or HQ version and a timestamp.
Each event has a pseudonymous account ID. This ID is a one-way keyed hash of your account ID. PostHog does not get your account ID, name, email address or IP address. The data is about your account, not about one person. PostHog keeps usage events for up to 7 years. To delete the usage events of your account, send an email to hello@dashsquad.ai.
What the apps never send
- The text of your conversations and prompts
- Files and file names
- Agent names
- The text of messages between agents
- Goal objectives and the titles of goals and routines
- API keys and tokens
- Screen recordings
- Crash reports
Turn off usage data
Usage data is on by default. The setting is for your full account. When you turn it off on one device, it is off on all your devices. The server ignores events from an account that has usage data off. This includes the events from your HQ.
When you turn usage data on again, the control plane sends one analytics_opted_in event to PostHog. This event has only the pseudonymous account ID.
- Sign in to the web app.
- Open the Devices screen. The setting is also on the screen where you select your HQ.
- In Usage data, clear Share usage data.
Desktop shows the Usage data section only when you are signed in. When you are not signed in, Desktop sends no usage events.
If usage data is off on the dashsquad server, the apps do not show the setting. Then the apps send no usage data.
Feature flags
dashsquad can turn some features on or off for an account. To do this, the control plane asks PostHog about your pseudonymous account ID. If usage data is off, the control plane decides on its own server. It sends nothing about your account to PostHog.
The website
The website https://www.dashsquad.ai counts page views. It stores nothing in cookies or local storage. A page view has the page address and the address of the page you came from. When you leave a page, the website records that you left and how far you scrolled.
The website is configured to send page views from your browser directly to PostHog Cloud EU. These requests do not pass through a dashsquad analytics proxy.
The website removes the query part and the fragment of each recorded address. It keeps campaign tags such as utm_source and utm_campaign. It replaces ad click IDs such as gclid with <masked>. It removes search terms from search engines.
When you join the waitlist, dashsquad sends one anonymous waitlist_signed_up event to PostHog. The event has a random ID. It does not contain your email address.
The website does not use feature flags and does not load settings from PostHog. It does not record clicks, session recordings, heatmaps or page performance. For more information, read the privacy policy.