Privacy & security
Last updated: 9 November 2026
Mentoring Programs is built by Crosstown Tech, a software studio in Toronto, Canada. It helps a program owner run a mentoring program, either on the web at mentoring.crosstowntech.com, with messages sent by email, or inside a Microsoft Teams team, with messages sent by the app's bot. This page says exactly what the app collects, who can see it, where it is kept and how to remove it.
The short version
- Every message goes to one person: an email, or a private chat with the bot in Teams. Nothing about a pair is posted in a channel.
- The program owner sees whether pairs are meeting and the mood tap. The owner never sees the note a pair writes about what they worked on.
- From calendars, the app keeps one fact: "these two people met on this date". Never titles, descriptions or other meetings.
- Anyone can see or delete their data: write to support, use the unsubscribe option your email app shows for our messages, or in Teams ask the bot "What do you have on me?" or say "Delete me".
What the app collects
From Microsoft Teams
When the app is added to a team, Teams tells it who is in that team. The app stores, for each
member: display name, email address, the Microsoft Entra object id, the Teams user id the bot
needs to send a private message, and whether the person is a team owner, member or guest. The
role comes from the TeamMember.Read.Group permission, which applies only to the
team the app was added to and is granted by that team's owner when adding it.
From Microsoft sign-in (web)
Program owners, and participants when they sign up through a link, sign in with their work Microsoft account. The app stores their display name, email address and Microsoft Entra ids. The browser keeps the sign-in so the person stays signed in. Personal Microsoft accounts are not accepted, and a sign-up link only works for people in the program owner's organization.
From the sign-up form
Only what the person types or picks: department, years of experience (as a band such as "3–5"), the goals they want to work on or the skills they offer, how many mentees a mentor can take, an optional note, and answers to up to five questions the program owner adds. The form (a card in Teams, a page on the web) shows a link to this page before any of it is collected.
While the program runs
- Pairings, and when each pair started and ended.
- Check-in answers: whether the pair met, the mood tap, and an optional note about what you worked on.
- Meeting dates, from check-ins or from calendars (below).
- Closing-survey answers: progress (1–5), whether you'd recommend the program, and an optional quote, which is anonymous unless you tick "use my name".
- A log of the messages the app sent (emails or Teams cards), so the owner can resend one that failed. When an owner emails a sign-up link to someone, that address is in the log too; owners can send these only to addresses at their own organization's email domain.
- An audit log of owner and admin actions (create, match, re-match, close, export, delete).
Who sees what
- You see everything about yourself.
- Your partner sees your name, department, experience band and your goals or skills — not your other answers or your mood.
- The program owner (and up to two co-owners) sees sign-up answers, pairings, whether pairs met, meeting counts and moods per pair. Not the notes.
- App admins — people with the Microsoft 365 Global Administrator or Teams Administrator role, and anyone they appoint — see the list of programs in the company and can change owners, archive or delete programs.
Microsoft permissions
The app asks for the least it can work with, and nothing that needs an administrator to start:
- Sign-in (on the web, or Teams single sign-on) — your name, email and Microsoft ids. Some organizations let only an administrator approve new apps; the sign-in page then offers a one-click approval link to send them.
TeamMember.Read.Group— the roster of the one team the app is in, to know who is an owner.TeamsTab.Read.GroupandChannelSettings.Read.Group— to find which channel of that team has the Mentoring tab, so the owner's alerts open it. It looks through the team's channel tabs for its own and keeps only the ids of the channels that have it. It does not read messages or files.Calendars.ReadBasic(optional) — for meeting tracking. Microsoft's default settings require an administrator to approve it once for the company; the program owner gets a link to send them. Without it, the app asks "Did you meet?" instead.
Calendar access, precisely
With approval, the app reads — for mentoring pairs only — the start time, attendee list and cancelled flag of calendar events from roughly the last five weeks, from one member of the pair. If the other member of the pair is an attendee, it records the date. It does not request or store event titles, descriptions, locations or any other meeting. The access token that allows this is encrypted at rest (AES-256-GCM).
The app never writes to calendars. "Book 30 min" opens Outlook's or Teams' own new-meeting screen for you to send.
Emails and their links
On the web, intros, check-ins, nudges, surveys and owner alerts are sent by email from
mentoring@notifications.crosstowntech.com. Each email's buttons lead to a page that
answers it for you without signing in. Those links are personal and expire (after 180 days, or
21 days for owner alerts): if you forward an email, the person you forward it to can answer it
as you. An answer, once given, can't be changed from the same link.
Where the data lives
Program data is stored with Convex (database and backend) in the United States. The web app and the owner's tab are served by Vercel. Emails are sent through Resend (United States), which receives each recipient's address and the message. Messages between Teams and the app pass through Microsoft Azure Bot Service. We count how the app is used (for example, that someone signed in, a program was created, pairs were launched or an invite was shared) with PostHog (United States), at the organization level: each event names the organization by its email domain or Microsoft tenant id. PostHog also receives the page address (with private links removed), the browser type and, until we anonymise it in PostHog's settings, the visitor's IP address. The browser keeps an anonymous id for this in its local storage. No names, email addresses or answers are sent, and no cookies are set. All traffic is encrypted in transit. Organizations that need data kept in Canada can contact us before starting.
How long it is kept, and deleting it
- Deleting your data — "Delete me" in the bot chat in Teams, the leave-and-delete page behind the unsubscribe option of our emails, or a request to support@crosstowntech.com — removes you from every program in your organization, closes your pairs (your partner gets a kind note), and erases your answers, check-ins, notes, survey answers, the messages sent to you and any calendar access. A placeholder named "Deleted participant" remains so the program's totals still add up.
- Archiving a program keeps its data for the report. An app admin can delete a program, which erases everything about it except the audit-log entry that it was deleted.
- Removing the app from a team pauses its programs. Their data is deleted 30 days later.
- Programs with no activity for 60 days are archived automatically.
- Usage counts in PostHog name an organization, not a person, so deleting your data does not change them. They are kept under PostHog's standard retention.
What we don't do
- No advertising, no selling or sharing data, no training AI models on it.
- No reading of chats or mailboxes. The bot is not in the pair's own chat and cannot see it, and the app never reads anyone's email.
Contact
Questions or requests: support@crosstowntech.com. Crosstown Tech handles personal information in line with Canada's Personal Information Protection and Electronic Documents Act (PIPEDA).