> ## Documentation Index > Fetch the complete documentation index at: https://docs.aide.gg/llms.txt > Use this file to discover all available pages before exploring further. # Risks > What using AIde actually risks, what your teacher can see, and what you control ## Read This Before You Rely On It AIde completes DeltaMath assignments. At most schools, submitting that work as your own violates the academic integrity policy you agreed to at enrollment. That's not a technicality and we're not going to bury it three pages deep. The consequences, if they come, land on you and not on us, as laid out in our [Terms of Service](https://docs.aide.gg/terms-of-service). Depending on your school that can mean a zero on the assignment, a failing grade in the course, a note in your file, or a conversation with an administrator. We don't get to soften that, and any tool that tells you otherwise is selling you something. We're not saying this to talk you out of it. [Our position on why AIde exists](/why-aide-exists) hasn't changed, and we're not interested in judging your reasons. But a real choice requires real information, and "your time is yours to allocate" only means something if you know what you're allocating it against. **Everything on this page is about DeltaMath automation.** [AIde Chat](/plans#ai-chat-and-models) is a different situation entirely. Asking an AI to explain a concept, check your reasoning, or answer a question that has nothing to do with school is the same thing adults do at work all day, and it doesn't put anything at stake. The risk here comes from what gets submitted, not from what gets asked. If you're using chat to actually understand the material, or for something outside class altogether, none of the rest of this applies to you. Worth one caveat: some schools now have AI policies covering assistance and not just submission. Yours might. Check just to make sure. ## What Your Teacher Can Actually See DeltaMath gives teachers analytics on every student. The relevant one is timing: **DeltaMath records how long each problem took you, and your teacher can view that data per problem.** It sits in their dashboard alongside your scores and attempt history. Whether any given teacher looks is a different question. Most are managing 30+ students and grading on top of teaching, and reviewing per-problem timing is not part of a normal workflow. But the data exists, it's attached to your account, and it doesn't expire. AIde at default speed completes problems faster than a person physically can. If a teacher does look at your timing data, that is what they will see. This is the single thing most worth understanding before you use AIde on graded work. ## What You Control AIde's timing behavior is yours to set. Every control below is a dial you turn, and where you leave it is up to you. * [**Speed Regulator**](/limits#speed-regulator) sets how quickly AIde moves through an assignment. Available on Plus and Plus with AI, with the full range on Pro. * [**Parallel Completion Regulator**](/limits#parallel-completion-regulator) controls how many sub-assignments run at once. Pro only. * [**Single Assignment Mode**](/limits#single-assignment-mode) limits AIde to exactly the sub-assignment you paste instead of the whole parent. These exist because pacing should be your decision rather than a side effect of our infrastructure. What settings make sense for your situation depends on your class, your teacher, and your own judgment about your work. We don't have that context and we're not going to pretend we do. ## What We Can't Promise We can't promise you won't be caught. No configuration makes automated work indistinguishable from your own, and any product claiming to guarantee that is lying to you. There are signals we don't control, ones we don't know about, and ones DeltaMath could add tomorrow without telling anybody. Teachers also catch things for reasons that have nothing to do with data, like a student who can't reproduce the work in class. The simplest one has nothing to do with software at all: a teacher walking past your desk and seeing AIde open. No setting we ship does anything about a person standing behind you. If you're using AIde on school hardware or a school network during class, that's a risk you're managing yourself, and it's usually the one that actually gets people. That's the old way, though. The modern version is GoGuardian, Securly, Lightspeed, and the rest of the classroom monitoring stack, which is basically surveillance software wearing a tie. If your district runs one, a teacher doesn't need to walk anywhere. They can see your open tabs from their desk in real time, get flagged automatically on keywords, and pull your browsing history up afterward. Nothing we build touches that, because it runs on your device and your district's network, not on ours. There's also the question of whether AIde loads at all. School networks filter aggressively, and their block lists change without warning. We work to stay reachable, but we can't promise you'll be able to open AIde from a school connection on any given day, and we won't pretend otherwise. As AIde gets more visible, the odds of ending up on those lists go up rather than down. That's the honest trajectory, and it's worth factoring in if school is the only place you'd be using it. Treat every setting as risk reduction, never risk elimination. If the consequence of being caught is one you can't accept, the honest answer is that no tool can make that risk zero, and you should weigh that before you paste the URL. ## Making The Call You know your class, your teacher, and what's actually at stake for you better than we ever will. That's the whole premise AIde is built on. So: know what your school's policy says, know that the timing data exists, know which controls you have, and know that none of it comes with a guarantee. Then decide. It's your call, and it always was. Have a question this page doesn't answer? Reach out through the app. We'd rather tell you something uncomfortable than have you find it out from a dean.