How HistoryShowcase uses data

Updated October 19, 2026.

HistoryShowcase is operated by Rocket Alumni Solutions. This page explains in plain language how the app handles data today. Rocket Alumni Solutions’ Privacy Policy and Terms of Service are the governing policies and agreement.

School accounts

Each person creates their own account with an email address and a password. Accounts are handled by Supabase, an authentication service. Supabase keeps your account record: your email address, your password credential, and when you confirmed your email and signed in. Supabase sends account emails, such as confirmation and password reset links.

• Your password goes from your browser to Supabase. HistoryShowcase’s own servers never receive it.
• You confirm your email address from a link before you can sign in.
• Your sign-in session stays in your browser tab’s memory and ends when you close or reload the tab. While an email link is pending, the browser keeps one single-use code in its site storage so the link can finish.
• Rocket Alumni Solutions staff sign in separately, with their Rocket Google account through Auth0. Staff email addresses cannot create school accounts.

School content

The app stores your profile and the schools you belong to, your sites’ stories, photos and other media, imported archives, published releases and display status. Each person’s role on a site (owner, publisher, editor or viewer) decides what they can change. Site owners manage who has access.

Publishing and offline copies

Drafts and original uploads are private to people with access to the site and to Rocket Alumni Solutions support administrators. When someone with publishing access publishes, that release becomes public: anyone with the site’s link can view it. Displays can save a published release for offline use. Publish only material you have permission to share publicly, including any consent your school needs for student names, photos or other personal information. Some files, such as imported archive media, videos and GIFs, can keep their original camera and location details. Review them before you publish.

Archiving a site removes it from the public lookup. It does not erase copies that people or displays have already downloaded, and old published file addresses can keep working until they are removed from hosting and the content delivery network.

Where data is stored and how long it is kept

• School content and media are stored with Amazon Web Services (AWS) in the United States. Private requests are checked against your signed-in identity and your role on the site.
• School content and media stay until they are deleted by an authorized request. Database recovery history is kept for 35 days, and earlier versions of stored files are kept for recovery. Deleting data also has to cover those earlier copies; turning off an account on its own does not erase it.
• Administrator audit records are kept for 365 days. Display check-in records and server logs are kept for 30 days. Expired records are removed automatically, which can take some time.
• A paired display stores a limited display credential and, if you choose to save offline, a copy of the published site on that device.

Diagnostics and embedded videos

The app records request references, response status and timing to keep it working. Rate limits use hashed identifiers. If the page hits an error, the browser reports only a fixed error category and whether it happened in the workspace or on a display. It does not send page content, full addresses, sign-in tokens or error messages. Paired displays report when they last checked in, which release they show and how far an offline save has progressed. There is no advertising or analytics SDK in the app. YouTube and Vimeo videos that a school embeds load from those services under their own policies.

Questions and requests

For access, correction, account deletion, removing media or exporting a school’s content, email support@rocketalumnisolutions.com. Rocket Alumni Solutions checks the requester’s identity and their authority for the school before sharing or deleting data. School content may involve other contributors, so moving or deleting it needs the school’s decision.