Skip to main content
These channels are operated by Juno through its own provider accounts — no permissions are requested from your organization. This page covers what data flows through them and what IT may want to allowlist.

​
Email

  • Provider — Juno sends transactional email through SendGrid.
  • Default sender — notifications@sg.junojourney.com. A custom sender address on your own domain can be configured with your admin.
  • Data sent — recipient name and email address, and the notification content (for example, an assignment title and a link back to Juno).
  • Allowlisting — to ensure delivery, allow the sg.junojourney.com sending domain in your mail filtering. Juno’s sending domain is authenticated with SPF and DKIM.

​
SMS

  • Provider — Juno sends SMS through Twilio, only for organizations that enable SMS notifications.
  • Data sent — recipient phone number and a short notification text with a link back to Juno.
  • Phone numbers are used solely for notification delivery.

​
Browser push

  • Provider — Juno sends web push notifications to learners’ browsers through Firebase Cloud Messaging. Juno has no mobile app. Push reaches a learner’s browser through a service worker that Juno registers, including a browser on a phone or tablet.
  • Data sent — an opaque browser token, the notification title and body, and a link back to Juno.
  • A token identifies one browser on one device, not a person’s identity outside Juno. Juno keeps a separate token for a browser on a phone or tablet.

​
What we do with the data

Recipient details are used only to deliver the notification. Learners control which channels they receive in their notification preferences, and admins control which channels are enabled for the organization.

​
Revoking or disabling

Each channel can be disabled organization-wide from Juno’s notification settings, and individual learners can opt out of channels in their own preferences.
Last modified on October 6, 2026