Steerloom
Privacy notice
Updated 12 November 2026
Steerloom is operated by Martin Aleksandrov. For privacy questions or requests, contact [email protected].
Information we use
- Account information, including your email address, account identifier, and information supplied by your sign-in provider. If you register with a password, Supabase handles the password and stores a password hash.
- Workspace names, memberships, invitations, roles, board connection details, selected board identifiers, and dashboard settings.
- When you connect Jira, Trello or Azure DevOps, the credentials or OAuth tokens needed for read-only access. These are encrypted before storage. Board content is retrieved to calculate reports; imported rows, board history, and conversations are not saved as workspace records.
- When a workspace connects an AI key (optional), the key is encrypted before storage. Questions asked in Steerloom AI are sent with the briefing evidence needed to answer them, such as metrics and, once you allow board reading, the board items the assistant reads to answer (titles, descriptions, comments, assignees, history and links), to the AI service the workspace chose. Board reads are read-only. Conversations are not saved as workspace records.
- Secure session information needed to keep you signed in. Server sessions are encrypted on Render and expire after eight hours.
- Feedback you send with the Feedback button: your message, the page you sent it from, your browser type and, if you give one or are signed in, your email address so we can reply.
- Usage counts: how many people reach each step, such as opening the demo, connecting a board or opening a briefing, whether you answered yes or no when asked if a briefing or the demo was useful, and, if you followed a tagged link such as one in a LinkedIn post, which link it was. A tagged link is remembered in your browser for 30 days so later steps count for it. We count steps only. A person is represented by a one-way code made from their account identifier, never by name or email, and no board content is included. Daily counts are kept for 90 days.
The Steerloom app you install on your own computer asks steerloom.app about once an hour, and when you open a page, whether a newer version exists, and fetches the update command when you ask for it. These requests send no account, board, device or version information; like any web request, they reveal your network's IP address to our hosting providers.
Why we use it
We use this information to create accounts and isolated workspaces, connect boards you authorize, calculate delivery-flow reports, save your dashboard choices, and protect the service. Connecting a board is optional. Steerloom does not request write access to Jira, Trello or Azure DevOps and does not use advertising or third-party analytics trackers; the only usage information is the step counts described above, kept on our own server to see where people get stuck.
Who handles it
Supabase provides account authentication and the workspace database. Render hosts the Steerloom server and its encrypted session file. Resend delivers account emails and the feedback you send. Google processes Google sign-in if you choose it. Atlassian, Trello or Microsoft process requests when you authorize a connection. If a workspace connects an AI key, the AI service it chose (such as Anthropic, OpenAI, Google, xAI or a company endpoint) processes the questions and evidence sent to it, under that workspace's own account with the service. Their own privacy notices also apply to their services.
Retention and your choices
Account and workspace settings are kept while your account or workspace is active. Disconnecting a board removes its saved connection credential and associated dashboards. Signing out ends the browser session; server sessions expire after eight hours. Service providers may retain backups under their own schedules. There is currently no self-service account deletion screen. Contact us to request access, correction, export, or deletion of your information; we will verify your identity before acting. You can also revoke Jira, Trello or Azure DevOps access in the provider's account settings.
Questions and changes
Write to [email protected] about this notice or your data. We will update the date above when this notice changes.