Alia
How It WorksPlansAbout Us
Log In
Platform TermsGoogle Integration AppGoogle OAuth AppZoom ConnectorEntry PackagesSAT Platform TrialSubscription TrialSMS MessagingSecurity
Platform TermsGoogle Integration AppGoogle OAuth AppZoom ConnectorEntry PackagesSAT Platform TrialSubscription TrialSMS MessagingSecurity

Alia Education

Security

Last modified: October 20, 2026

Alia Education serves tutors, counselors, students, and families. We handle student records, session information, and data from the Google, Zoom, and messaging accounts our users connect. This page explains who is responsible for protecting that information, how we protect it, and how to report a security concern.

Security Leadership

Terry Conlon, Chief Technology Officer, is Alia Education's security lead and is accountable for the security of the Alia platform, including the Alia website, the Alia Dashboard, the SAT practice platform, Eve (Alia's AI assistant), and the infrastructure that runs them.

In this role, Terry is responsible for:

  • Security architecture and engineering decisions across the platform
  • Access control for production systems, data, and third-party integrations
  • Reviewing code and infrastructure changes before they reach production
  • Vulnerability management, including triage of reports received through this page
  • Incident response and notification of affected users
  • Security testing of Alia's own systems

Contact: [email protected]

Infrastructure and Data Protection

  • Hosting: Alia's services run on Amazon Web Services. Application services run in private network subnets with no public IP addresses, and only reach the internet through managed load balancers and gateways.
  • Encryption: Data is encrypted in transit with TLS and encrypted at rest in our database and file storage. Encryption keys are managed in AWS Key Management Service with automatic key rotation.
  • Secrets: Production credentials and API keys are stored in AWS Secrets Manager and injected at runtime. They are never committed to source code, and automated checks block commits that contain private keys or cloud credentials.
  • File storage: Stored files are private by default, with public access blocked at the storage level.
  • Separate environments: Staging and production run in separate environments, and testing uses a separate database so that production data is not used for development.

Access Control

  • Access to production systems is limited to the people who need it to operate the platform, and is granted and revoked by the security lead.
  • Within the product, users see only the students, sessions, and records they are authorized for.
  • Third-party integrations such as Google, Zoom, and Stripe use OAuth or scoped credentials, and request only the permissions the feature needs. Users can disconnect an integration at any time.
  • Eve, Alia's AI assistant, can use a tool only when that tool has been granted to the user. Its read access and write access use separate credentials, actions that change data require the user's explicit approval, and tool calls are recorded in an audit log.

Secure Development

  • Every change is made on a separate branch and goes through a pull request and automated tests before it is merged.
  • Changes are deployed to staging before production through an automated pipeline, and infrastructure is defined as code so that it is reviewed like any other change.
  • Third-party dependencies are pinned with lockfiles and upgraded deliberately, with each upgrade reviewed and tested like any other change.
  • Production errors are reported to the engineering team automatically, and service health is monitored continuously.

Incident Response

The security lead coordinates the response to any suspected security incident: containing it, investigating the cause, fixing the underlying problem, and recording what happened. If an incident affects personal information, we notify affected users and any relevant authorities as required by law.

Reporting a Vulnerability

If you believe you have found a security vulnerability in any Alia Education website, application, or service, please email [email protected] with the subject line "Security Vulnerability Report". Please include:

  • A description of the issue and its potential impact
  • The affected URL, page, or feature
  • Steps to reproduce the issue

We aim to acknowledge reports within three business days and will keep you informed as we investigate and fix the issue.

When researching, please:

  • Do not access, change, or delete data that does not belong to you
  • Do not degrade or disrupt our services, and do not use social engineering or physical attacks
  • Give us reasonable time to fix the issue before disclosing it publicly

We will not pursue legal action against anyone who reports a vulnerability in good faith and follows these guidelines.

Contact

Terry Conlon
Chief Technology Officer and Security Lead, Alia Education
[email protected]

Book a call with one of our experts

Get Started

Alia

  • How It Works
  • Eve
  • Roadmap
  • Plans
  • About Us
  • Contact

Resources

  • Test Prep
  • Partnerships
  • Newsletter

Company

  • Careers
  • Security

Legal

  • Terms
  • Privacy

© 2026 Alia Education. All rights reserved.

XInstagramYouTubeLinkedIn