On this pageVisibility basics

Trust and privacy

Trust

Stride is designed to make learning useful while giving people clear choices about identity and visibility. Use the product labels and your organization's guidance together.

AvailableLast reviewed: Sep 29, 2026Audience: Everyone, Manager, Client Admin, Technical/Integration Owner

Visibility basics

Public in Stride means visible to peers in your organization where the product says so; it does not mean visible on the internet. Profile and contribution visibility depend on the specific control and surface, and the product may withhold identity or metrics when the relevant privacy rule applies.

  • A signed-in user sees only the organization-scoped experiences and peer surfaces available to that account.
  • A profile, leaderboard row, forum post, challenge submission, and Success Story can each have different identity behavior.

Share with care

  • Do not enter passwords or information you are not authorized to share.
  • Use Profile → Privacy Controls to review identity choices.
  • Ask your Client Admin how your organization expects shared learning information to be used.
  • If you are unsure whether something belongs in a shared space, leave it out and ask first.

Read and acknowledge the current privacy notice

When your organization has a current notice that needs acknowledgment, Stride shows it at the applicable onboarding, survey, or authenticated dashboard checkpoint. Read the displayed notice and choose Acknowledge and continue; a successful acknowledgment clears that gate.

  • Profile Preferences also provides a read-only View privacy notice action for the current published notice.
  • If no notice has been published, the viewer shows an empty state; if the source is unavailable, it shows an error instead of inventing notice text.
  1. Wait for the current notice to load and read the notice body shown by Stride.
  2. Choose Acknowledge and continue once you understand the notice.
  3. If the notice cannot load or the acknowledgment cannot be recorded, choose Try again; an error does not silently clear the gate.

Manager and reporting boundaries

Managers see the active direct reports assigned to them in manager surfaces; that relationship does not grant broad access to every organization member. Reporting favors aggregate views and minimum cohort thresholds, and personal privacy choices still apply. A manager relationship is not a promise that every individual metric or identity will be shown.

  • An empty assigned team is a valid result; Stride does not substitute the whole organization or sample people.
  • If an individual value is withheld, use the aggregate or team-level context that the product actually displays.
  • Ask your Client Admin when a manager scope or reporting view is unclear.

Export or remove your data

You can request a copy of your data through your Client Admin, who can export a full copy of what Stride holds about your account. A deactivated account is permanently erased after a period of inactivity your organization configures, or never, if your organization has not set one.

  • Ask your Client Admin to request an export or ask about your organization's deactivated-account handling.
  • An export and an erasure are separate organization-level actions; neither happens automatically just because you ask a question in BYTE or elsewhere.

Message history

Message history has its own visibility and deletion windows. Read the Messages guide to understand when older messages leave the conversation, when deletion becomes due, and how an organization hold affects deletion.

64 public articles available