Trust Center

How we protect your institution's data.

Your security, privacy, legal and accessibility offices should be able to evaluate us before the first meeting. This page describes our practices plainly, and we confirm our commitments in writing.

Items marked In v1.0 are decided and being built for the 1.0 release of AdiHub, the Angelsee Data Intelligence Hub; they are not available yet. Everything else describes how AdiHub and Angelsee work today.

Where your data lives

AdiHub and its database run on your institution's own servers, so institutional data stays under your controls. We do not operate a shared, multi-tenant database of institutional data.

  • Installed on your campus servers or in your institution's own cloud.
  • HTTPS only, with TLS 1.2 or 1.3 in the server template we supply. At rest, your data is protected by your servers' storage encryption; AdiHub also encrypts the second-factor secrets it stores.
  • Administrators must use a second factor. Angelsee staff with server access are named in advance, use multi-factor authentication, and lose that access when the work is done.
  • Sign-ins, second-factor events, role changes and sign-in settings changes go to a tamper-evident log in your own database, which your administrators hold.

Source code and ownership

AdiHub comes with source code per subscription, so your security team can audit how every number is produced.

  • In v1.0 You receive the readable source code of the modules you subscribe to, plus the core platform they need to run and to be audited. It arrives separately from the installable package.
  • In v1.0 The source code is licensed under Angelsee's source-available license, for your institution's own use. It may not be resold or redistributed.
  • Your data is always yours, and so is every dashboard your own team builds.
  • Work an Angelsee consultant authors or co-authors with your staff belongs to Angelsee, and your institution receives a perpetual license to use it internally.
  • Sharing a dashboard your team built is always your choice. A shared dashboard carries its definition (layout, charts, filters, metric definitions, description and footnote) and generated sample data, never your data, connection details or user names.
  • Improvements we build for one institution may be added to AdiHub for every institution, never with any institution's data.

Student records and FERPA

FERPA is a law, not a certification, so we describe how we handle education records rather than display a badge.

  • Angelsee holds no education records. They stay on your servers, and we never copy institutional data off them.
  • Angelsee staff work with education records only as a statement of work allows, and we confirm our commitments in writing.
  • In v1.0 Every chart, table, export and drill-down follows each user's role and data scope: university, college or unit, department, or individual.
  • Sample data is generated and labelled on every page and export. Public benchmarks use public federal data, shown with its source and date.

What AdiHub sends to Angelsee

By default, nothing. AdiHub needs no connection to Angelsee to run, and it never sends institutional data to us.

  • Updates arrive as a package file that your team moves to the server and can verify with the checksum file that comes with it.
  • In v1.0 Your subscription is checked offline, from a signed license file on your server.
  • Sign-in and invitation email goes through your institution's own mail relay.
  • In v1.0 One optional exception, dashboard requests to Angelsee. It is off by default, and only an institution administrator can turn it on. The sender sees exactly what will be sent, and every send is logged.
  • In v1.0 A request carries its title, the question it answers, its audience, an estimate of the time it would save, an optional contact, and a sample data template with fictional rows only, screened for real identifiers before it is sent. Nothing else is sent, and the request can be downloaded as a file instead.

Your institution's Hub In v1.0

Each institution configures its own Hub.

  • Its own name (it doesn't have to say Angelsee), with your institution's name, logo and main theme color. Colors are checked for accessible contrast before they are accepted.
  • Its database connection and its own settings, such as the mail relay, sign-in, time zone and fiscal year.
  • A small “Powered by AdiHub” line appears in the footer and on the sign-in page.

Accessibility

Public institutions are expected to meet WCAG 2.1 AA for web content, and every institution benefits from it.

  • AdiHub targets WCAG 2.1 AA, including keyboard use, visible focus, screen-reader names and structure, and sufficient contrast. These basics are on for every user and can't be switched off.
  • Every AdiHub chart has a table view and a CSV download, so no value depends on color or shape alone.
  • In v1.0 Optional display settings that each user can turn on for themselves. All are off by default.
  • Read our full accessibility statement.

Service providers we use

These are the outside services Angelsee uses. AdiHub, installed on your servers, sends them nothing.

  • Amazon Web Services hosts this website.
  • ImprovMX forwards email sent to angelsee.com addresses to our mailbox, which Google hosts.
  • GitHub hosts our code repository. It holds no client data.
  • Twilio sends and receives the text messages people agree to on our contact form.
  • Anthropic provides AI tools that sort and summarise email and form messages sent to us.

Security incidents and vulnerability reports

If we learn of a security incident that affects your institution, we notify you promptly and in writing, with what happened, what it affects and what we are doing about it.

  • Report a vulnerability in AdiHub or this website to security@angelsee.com, with the affected page or version and the steps to reproduce it.
  • Please don't access data that isn't yours or disrupt service while testing. We acknowledge each report and keep you informed until it is resolved.
  • Security fixes ship as patch releases to institutions with an active subscription.

If a subscription ends

Your institution keeps using the version it has installed, under the same internal-use license.

  • It no longer receives updates, security patches, support or new modules.

See where AdiHub fits your institution.

Tell us which offices and systems are involved. We reply within three business days.