Security and data practices.

The controls in place, and the limits we want you to know.

Our full policies live in the app: Privacy and Terms.

What do we collect?

Your account info, the content you create in Aluma, and only for platforms you connect, the assignment, grade and schedule data your school account exposes.

What do we never do?

We never sell your data, never use private conversations to train models, and never complete or submit schoolwork on your behalf.

Who can see conversations?

You. A small number of Aluma support staff may access a conversation only to investigate a bug or a report you send in, never for browsing or marketing.

How do I delete my data?

Go to Settings to export your data, reset your account or delete it. Or email privacy@aluma.fun.

Data and infrastructure

Hosting and transport

Application hosted on Render, with Cloudflare in front for DNS, CDN and DDoS protection. TLS in transit.
Application data stored in SQLite on an encrypted disk.

Internal analytics

We collect basic product usage data, such as feature usage counts and message volume, to run the Service and understand which parts of the product are working. This is operational analytics, not advertising tracking, and it is not sold or shared with third parties for marketing.

Subprocessors

Anthropic: model inference through the Claude API.
Stripe: payment processing.
Render: application hosting.
Cloudflare: DNS, CDN and DDoS protection.
Resend: transactional email.
School and productivity platforms you connect: scoped to what you authorize.

Connected accounts

Connected school and productivity accounts

Aluma connects to school and productivity platforms in different ways. Each one is described here directly.

Token connectors (Canvas, Schoology, Blackbaud, Notion, Slack, Todoist, Linear, Trello, Asana, ClickUp): you paste a token you create. It's encrypted at rest on Aluma's servers so sync can run, never shown back to you, and deleted when you disconnect.
Sign-in connectors (Google Classroom now; Google Calendar, Microsoft 365, Outlook and OneNote coming soon): you sign in with the provider and grant read-only access. Aluma never sees that password.
Lumi Anywhere school sync (PowerSchool, Blackboard, Moodle, D2L Brightspace, Sakai, Edsby, Edgenuity, ClassDojo, Seesaw, Teachable, Thinkific, TalentLMS, Docebo, and Google Classroom as an option): runs in a tab in your own Chrome. Lumi reads the assignment list and returns only titles, due dates, classes and links.
School passwords: Aluma's servers refuse to store them. If you ask Lumi to sign in for you and choose Remember, the login stays in that Chrome on that computer only. Forget or signing out clears it.
The Lumi Anywhere extension stores an Aluma sign-in token in the browser and sends page content only when you turn on Whole page or Point at part for a message. It never types answers into a page or submits anything.
Encryption: stored tokens use authenticated encryption, and Aluma holds the key so the server can run sync. We don't claim otherwise.
Read-only: syncing is read-only. Aluma does not edit or submit your schoolwork. There is no exception.
You can disconnect any connector at any time.

AI and academic integrity

AI providers and content handling

Tutoring replies are generated using third party model providers, currently Anthropic's Claude API. Your messages are sent to the provider to produce responses, subject to their terms. Aluma does not train its own foundation models.
Aluma does not use your private conversations to train models.

Academic integrity

Aluma is built to coach students through their work, not to complete or submit it for them. Guided walkthroughs start with a diagnostic question, hints are revealed one step at a time, and understanding is checked with follow-up questions rather than accepted on an explanation alone. Aluma does not submit assignments on a student's behalf.

Access and responsibility

Authentication

Passwords are hashed and never stored in plain text.
Sessions use signed cookies with expiry.
Account deletion removes account data from our primary storage.

Support staff access to conversations

A small number of Aluma staff can access individual conversations when needed to investigate a bug report, a support ticket or a safety concern you or a parent raises. Routine, unprompted browsing of student conversations is not part of our process.

Shared responsibility

Aluma is responsible for the platform controls above. Students and families are responsible for the accounts they choose to connect, the content they upload and keeping their login credentials safe.

Deletion and incidents

Deletion timing

Deleting your account removes your data from our primary, live database immediately. Not currently offered: a published fixed timeline for purging data from encrypted backups. Contact us for current status if you need a specific backup deletion timeline for a school or district agreement.

Incident response

We monitor for and respond to security incidents as part of normal operations. Not currently offered: a published formal incident response SLA or notification timeline. Contact us for current status.

Schools and certifications

School data processing agreements

Aluma does not currently have published data processing agreements (DPAs) or state student-data-privacy addenda published for schools and districts. Contact us for current status if your school or district requires one.

Independent security testing

Aluma has not undergone independent third-party penetration testing or security audits at this time. Contact us for current status.

Certifications

Aluma does not currently hold independent security certifications such as SOC 2, ISO 27001 or education-specific approvals. FERPA and COPPA are laws, not certifications a vendor can hold. As the company grows we plan to pursue relevant compliance work and will publish updates here. Contact us for current status.

Reporting a vulnerability

Please report suspected security issues to security@aluma.fun. We aim to acknowledge reports within a few business days.