Privacy & security
Last updated: 8 November 2026
Roadmap Slides is built by Crosstown Tech, a software studio based in Toronto, Canada. It turns work you already track into roadmap slides. This page says exactly what it reads, what it keeps, and for how long.
What Roadmap Slides reads
From Microsoft Planner
Signing in with Microsoft uses Microsoft's identity platform (Entra ID) and is also the Planner connection. Roadmap Slides requests these scopes and no others:
Tasks.Read— tasks, buckets and plan details from the plans you can already see. Read-only by design; there is noTasks.ReadWrite.User.Read— your own directory id, and your organization's name, so the connection can be labelled.User.ReadBasic.All—idanddisplayNamefor the people tasks are assigned to, so an item can show a person's name.https://globaldisco.crm.dynamics.com/user_impersonation— the gateway Microsoft requires to reach Planner premium plans, which live in Dataverse. Only premium plans are read through it. If your organization has no premium plans, nothing is read here.offline_access— a refresh token, so a scheduled refresh can run while you are signed out.
Basic and premium plans are read through the same connection. When you create a roadmap, the app lists the plans you can see; only the plans you pick are copied.
Trying it before you sign in
On the try-it page (roadmap.crosstowntech.com/demo) you can edit the example
roadmap, type your own items or import an Excel or CSV file before signing in. That draft is
kept in your browser (its local storage) and is not sent to Roadmap Slides.
When you sign in, the draft is saved to your account as a roadmap and removed from the
browser. Until then, clearing your browser's site data deletes it.
From an Excel or CSV file
An uploaded .xlsx, .xls or .csv file is read
in your browser. The file itself is never uploaded. Only the rows you import,
in the columns you keep, are sent to Roadmap Slides and stored as the roadmap's items. After
the import the roadmap has no link to the file.
From Jira, if you sign in with Atlassian
The sign-in screen may also offer Atlassian. That sign-in uses Atlassian's OAuth 2.0 (3LO)
and requests three scopes and no others: read:jira-work (issues, their fields
and projects), read:jira-user (display names, read at the time of use) and
offline_access (a refresh token). Roadmaps from Jira are not offered in the app
today; the grant only signs you in and records the Jira site it reaches.
Signing in with Google
A Google sign-in asks for the scope openid and nothing else — not
email, not profile — and no token is kept from it. No data is read
from Google.
Access is read-only. No write scope is requested on any source, so Roadmap Slides cannot create, change or delete anything in your Planner plans or your Jira site.
Refreshes run automatically. Besides reading when you open a roadmap, a background schedule reads the plans you picked again: at least once a day for an account used in the last 30 days, and more often while you are actively using it. An account left unused longer than that gets a weekly check that its token still works, with no data read, for a while, and then nothing until you use it again.
What it stores
| What | Why |
|---|---|
| Tasks from the Planner plans you picked — title, plan, bucket, labels, progress, priority, start and due dates, checklist counts, assignments (as directory ids) and, for premium plans, parent task, sprint and effort — plus the plan names | The slides are drawn from stored items, so they open quickly |
| Your roadmaps: name, presentation style, your own columns, each slide's settings (layout, rows, filters, titles, "What this means" points) | That is the roadmap |
| Everything you type or import into a roadmap — slide titles, statuses, initiatives, outcomes, notes, items and milestones you add, and every row imported from a sheet. If an imported sheet holds names (for example an Owner column), or you type a name, those names are stored | Your edits are stored beside the Planner data, so a refresh never overwrites them |
| People on Planner tasks, as directory ids only | To show who work belongs to |
| Your identity, as an account id only — Microsoft, Atlassian or Google, whichever you signed in with | To recognise you when you sign in again |
| Connection details — your Microsoft tenant id, your organization's display name and the granted scopes; for an Atlassian sign-in, the site's id, URL, name and time zone | To read the right tenant or site |
| Sign-in tokens for that connection, encrypted | To refresh data without asking you to sign in again |
Names of people
For tasks synced from Planner, Roadmap Slides stores people only as the directory id Microsoft issues. Names on screen and on your slides are looked up from Microsoft Graph with your own token when you open a roadmap, held in your browser's memory while the tab is open, and not written to the database.
Data you bring in yourself is different: a name in an imported sheet, or one you type into a roadmap, is stored with the roadmap like any other value you enter.
Files you download
PowerPoint and PNG files are made in your browser from the slide on screen and saved straight to your device. They are not stored by Roadmap Slides.
Where it is stored
Application data is held on Convex Cloud, in the United States. The app's front end and these pages are hosted on Vercel, which holds no customer data. The app carries no advertising trackers. These marketing pages count visits with PostHog, without cookies.
Product analytics
We count how the app is used (for example, that a roadmap was created or slides were exported) with PostHog, at the organization level. No names, email addresses or content you enter are sent, and no cookies are set.
Credentials and sessions
- Microsoft and Atlassian tokens are held server-side and are never sent to your browser. They are stored encrypted at rest (AES-256-GCM) in the application database.
- Your browser session holds a random secret. The server stores only a SHA-256 hash of it, so reading the database does not let anyone sign in as you. Signing out revokes the session on the server. A session lasts at most 30 days.
- No password is ever created or handled. Sign-in is Microsoft's, Atlassian's or Google's.
Who can see what
Each person who signs in gets their own workspace, and every stored record is keyed to it. Nothing queries across that boundary. Every read from Planner runs with your token, so Roadmap Slides can only hold plans you can already open. Two people in the same organization who can see different plans get different data.
Sub-processors
- Convex — application database and scheduled jobs (United States).
- Microsoft — the source of Planner data (and Dataverse for premium plans), and an identity provider.
- Atlassian — an identity provider.
- Google — sign-in only.
- Vercel — hosts the app's front end and these pages; no customer data is stored there.
- PostHog — cookieless visit counts on these pages and organization-level usage counts in the app (United States).
No data is sold, shared with advertisers, or used to train models.
Retention and deletion
Data is kept while you use Roadmap Slides so your roadmaps have something to draw. Deleting a roadmap in the app removes it at once, with its slides and everything you typed or imported into it. Tasks already copied from its Planner plans stay in your workspace, and keep being refreshed, until the workspace is deleted.
To have your workspace and everything in it deleted — roadmaps, slides, your edits, synced items, connections and tokens — email support@crosstowntech.com from the address on the account you signed in with; it will be deleted within 30 days. You can also revoke Roadmap Slides' access at any time from My Account → Privacy → Apps and services in Microsoft 365, or from your Atlassian account settings, which stops all further reading 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 the Microsoft tenant (organization) you signed in with.