Privacy and Admin Visibility

This reference explains, in user-safe language, what other alumni, school admins, authorized staff, and Getaka platform admins may be able to see or do in Eskula. It is meant to build trust without exposing restricted admin operating procedures.

What Other Alumni May See

Other alumni may see your directory profile only when your account and privacy settings allow it. Depending on your settings and school configuration, visible details can include:

• Name and batch year.
• Profile photo and public profile fields.
• Public directory profile details.
• Networking intent tags, when enabled.
• Messaging availability or an explanation when messaging is unavailable.

Other alumni should not see passwords, one-time codes, government ID images, private support notes, private contact details hidden by settings, payment account details, or internal verification notes.

Memory Lane public sharing is more restrictive than ordinary directory visibility. A public Memory Lane page is available only when your account is active, your profile visibility is all_alumni, and you explicitly choose to create a public Memory Lane share link. batch_only, private, deleted, and deletion-pending profiles do not render on anonymous public Memory Lane links.

What School Admins and Authorized Staff May See

Users with the school_admin role and authorized users with the school_staff role manage school records and support alumni users for their own school. Depending on their role and permissions, they may see information needed for support and operations, such as:

• Alumni roster details for their school.
• Claim or activation progress at a high level.
• Profile details needed to correct school records.
• Role assignments such as alumni or batch_representative.
• Donation records needed for school reporting, receipts, and reconciliation.
• Announcement and engagement information needed to operate the school community.

Admin access does not remove privacy rules. Admins cannot use documentation to bypass consent, profile visibility settings, role restrictions, RLS, audit logging, or data-protection requirements.

What Platform Admins May See

Getaka platform_admin users may access operational data when required for provisioning, billing, support, compliance, security, or incident response. Platform access is broader than school admin access, but it should be used for a legitimate operational reason and is subject to audit and internal controls.

What Admins Should Not Do From User Docs

User-facing docs must not teach restricted admin operations. Public or regular user docs must not include:

• CSV import procedures.
• Role-change procedures.
• Identity review or moderation instructions.
• Audit log workflows.
• Donation reconciliation steps.
• Internal support escalation paths.
• Platform operations or incident-response runbooks.

Those procedures belong only in restricted admin or platform documentation.

Your Controls

You can manage your own privacy and account preferences from user settings:

• Use /{schoolSlug}/profile/privacy for profile visibility, consent, data export, and deletion request links.
• Use /{schoolSlug}/profile/notifications for email notification preferences.
• Use /dashboard/profile and /{schoolSlug}/profile/edit to review and update your profile.
• Use /dashboard/donations/history to check donation status and receipt links.
• Use /forgot-password when you need to reset account access.

Changing visibility settings may affect whether classmates can find you in the directory. Some operational records may still be retained when required for receipts, audit, compliance, security, or legal obligations.

Changing profile visibility away from all_alumni disables public Memory Lane rendering. If you want Memory Lane sharing turned off without changing your directory visibility, contact your school or Getaka support until the dedicated sharing toggle is available.

If Something Looks Wrong

Contact your school or Getaka support if you believe your profile, donation, receipt, visibility, or account access is wrong. Include the school name, affected page, approximate time, and a short description.

Do not send passwords, one-time codes, government ID images, full payment account details, or private keys through ordinary support messages.

Screenshot Policy

This MVP reference uses text instructions instead of screenshots. If screenshots are added later, each one must include visible product version or capture date context and must be re-reviewed when the related privacy or admin-visibility workflow changes.