Privacy & security
Last updated: 15 November 2026
Recurring Work Items for Azure DevOps is built by Crosstown Tech, a software studio based in Toronto, Canada. It copies a work item on a schedule, with its tasks, into the right sprint. This page says exactly what it reads, what it keeps, and for how long.
What it reads
In your browser, as you
The extension's pages run inside Azure DevOps and use your own Azure DevOps session, with the
two scopes the extension declares: vso.work_write (work items) and
vso.project (projects, teams and sprints). They read the work item you open,
its child tasks, your team's sprints and the people in the project, so you can set up a
schedule.
When a page first loads, it sends your Azure DevOps session token to our backend once. The backend asks Azure DevOps who you are and which organization you are in — your user id, display name and sign-in email — and does not keep the token.
On a schedule, with the connected Microsoft sign-in
Copies have to appear on time when nobody is online. So one person in the organization selects Connect and signs in with Microsoft (Entra ID). The app requests these scopes and no others:
Azure DevOps user_impersonation— act in Azure DevOps as the person who connected: read the original work item and its tasks, read sprints, create the copies.offline_access— a refresh token, so scheduled runs work while that person is signed out.openidandprofile— the signed-in account's name and directory, to confirm it belongs to the organization.
Copies are created as the person who connected, so Azure DevOps shows them as the creator. The connection can do only what that person can already do in Azure DevOps.
What it stores
| What | Why |
|---|---|
| Your organization's id and name | To keep each organization's schedules apart |
| Each schedule: the project, the original work item's id, title and type, the team, the repeat rule, the sprint choice, the people taking turns (as their Azure DevOps sign-in names), the time zone, and when it runs next | That is the schedule |
| A history of runs: when, whether a copy was created, skipped or failed, the new work item's id, the assignee, the sprint name, and why a run failed | The history you see on the Recurring page |
| People who opened the app in your organization: Azure DevOps user id, display name, sign-in email, first and last visit | To count usage per organization and to reach the right person about support or billing |
| The connection: who connected (Azure DevOps user id and name), your Entra tenant id, the refresh token, encrypted, and when it was made | To run schedules while nobody is online |
Work item content is not stored. Descriptions, field values, tags, comments and child tasks are read from Azure DevOps when a copy is made and written straight into the new work item.
Where it is stored
Application data is held on Convex Cloud, in the United States. The extension's pages are packaged inside the extension and served by Azure DevOps. The app carries no advertising trackers. These web pages count visits with PostHog, without cookies.
Product analytics
We count how the app is used — for example, that a schedule was saved or a copy was created now — with PostHog, at the organization level. Events carry the organization's name; no names, email addresses or work item content are sent. No cookies are set and no sessions are recorded.
Credentials and sessions
- The Microsoft refresh token is held server-side and never sent to your browser. It is stored encrypted at rest (AES-256-GCM) and replaced with a new one each time it is used.
- Your session with the backend is a signed token that expires after 8 hours. It is not stored.
- No password is ever created or handled. Sign-in is Azure DevOps' and Microsoft's.
Who can see what
Every stored record is keyed to one Azure DevOps organization, and the backend serves a request only for the organization the caller's own Azure DevOps session belongs to. People in your organization who can open the extension see your organization's schedules.
Sub-processors
- Convex — application database and scheduled runs (United States).
- Microsoft — Azure DevOps, where work items are read and created, and the identity provider (Entra ID).
- PostHog — cookieless visit counts on these pages and organization-level usage counts in the app (United States).
- Vercel — hosts these pages; no customer data is stored there.
No data is sold, shared with advertisers, or used to train models.
Retention and deletion
Stop repeating on a schedule deletes it at once, with its run history. Everything else is kept while your organization uses the app.
To have everything for your organization deleted — schedules, history, the people list, the connection and its token — email support@crosstowntech.com from an address in that organization; it will be deleted within 30 days. Uninstalling the extension, or revoking Recurring Work Items in My Account → Privacy → Apps and services for the account that connected, stops all further access immediately.
Changes
If this page changes materially, the date at the top changes with it. Continued use after a change means the updated page applies.
Contact
Crosstown Tech — support@crosstowntech.com. For privacy requests, please include your Azure DevOps organization name.