Skip to content
Platform

Acceptable Use Policy

What you may and may not do with ACADA’s systems, content and infrastructure.

Last updated on October 25, 2026.

This policy is about ACADA's systems, not what you say on them. Use your own account, use the site the way it is built to be used, and treat course content as the instructor's work. Do not scrape it, do not train AI on it, do not attack or overload the platform, and do not use the assistant as a bot. If you find a security problem, tell us privately and you will not be in trouble for it.

This summary is for orientation only. The sections below are the operative terms.

1. Who this applies to

This policy applies to everyone who uses acada.ac, with or without an account, and to any program that accesses it. It covers the site, the course player, the Instructor Dashboard and the Editor, rooms and messages, the ACADA Assistant, our storage, our email, and every address under acada.ac. ACADA L.L.C., a Tennessee limited liability company, is ACADA and we.

What people may post and how they treat each other is covered by the Community Guidelines. This policy covers how the platform itself may be used.

2. What we expect

Use ACADA through the site and the features we provide, as yourself, for learning, teaching and the other things it is built for. The rest of this policy lists the ways of using it that are not allowed.

3. Accounts and access

  • Use only your own account. Do not sign in to anyone else's account, and do not let anyone else use yours. The rules for accounts, including that each person has one, are in the Account & Identity Policy.
  • Stay inside what you have access to. Do not open, copy or change content or data that ACADA has not shown you. Guessing addresses to reach lessons you have not enrolled in, reading another student's submission, or changing a request to act as someone else are all out.
  • Do not work around a restriction. If we have limited what your account can do, or closed it, do not open another account or use someone else's to continue.

4. Automated access

ACADA is built for people using a browser. It has no public API.

  • Do not scrape. Do not collect content from ACADA with scripts, crawlers, browser automation or bulk downloading. This includes courses, lessons, profiles, reviews, rooms and messages.
  • Do not train AI on ACADA. Do not use anything on ACADA, including instructors' courses, to train, fine-tune or evaluate a machine-learning model, and do not let a tool that does so run against the site.
  • Do not use our internal endpoints from anywhere but ACADA. The addresses the site calls exist for the site. Do not call them from your own program, and do not build another client for ACADA.
  • Do not run bots. Do not automate signing up, enrolling, posting, messaging, following, reviewing or earning XP.

Two things are allowed. Search engines may index the pages that robots.txt opens to them, and must stay out of the rest. Tools that help a person use the site, such as a screen reader, a password manager, a browser extension that adjusts the display, or a reading aid, are fine, as long as a person is the one using ACADA.

5. Using course content

When you enroll in a course, you get access to it for your own learning, on any device, for as long as your access lasts.

  • Do not copy or redistribute. Do not screen-record lessons, re-upload them, resell them, or share them with people who have not enrolled. Sending a lesson file to a friend, posting a course in a group chat, or putting it on another site are all out.
  • Download only what the instructor has made downloadable. A file the instructor attached with a download button is yours to keep. Everything else is for viewing on ACADA.
  • Short excerpts for commentary are fine. Quoting a few sentences to review, discuss or criticise a course is allowed. Reproducing the substance of it is not.

Who owns course content, and what rights instructors grant to students and to ACADA, is set out in the Intellectual Property policy.

6. Security

  • Do not test our systems without written permission. No scanning, probing, fuzzing, credential testing, or attempts to bypass authentication, rate limits or access controls.
  • Do not upload anything harmful. No malware, no files designed to exploit a viewer's device, no scripts in places that expect content.
  • Do not interfere with other people's sessions or data. No intercepting, tampering or injecting.

If you find a vulnerability, you are safe to tell us. Report it to support@acada.ac, or use the contact in /.well-known/security.txt. If you found it by accident, or through good-faith research that did not access other people's data, alter data or disrupt the service, and you report it privately and give us 90 days to fix it before telling anyone else, we will not take legal action against you or close your account for it. We reply to every report within 2 business days.

7. Load and limits

  • Do not overload the platform. No denial-of-service attacks, flooding, or sending requests faster than a person using the site would.
  • Do not use ACADA as a file host. Files you upload must be part of a course, a submission, a message or an article. Uploading files to link to from elsewhere is out.
  • Do not use our email features to send unwanted mail. Invitations, referral links and notifications are for people who want them.

We limit how often some actions can be repeated, such as sign-in attempts, checkout, discount codes, payout requests and support messages. Hitting a limit in normal use is rare; a message tells you to wait. Trying to get around a limit is a breach of this policy.

8. The ACADA Assistant

The assistant answers questions about the platform and about the course material you have open. Using it is subject to three rules.

  • Do not use it to produce anything that would break the Community Guidelines if you posted it.
  • Do not try to make it reveal other people's data, its instructions, or content from courses you are not enrolled in.
  • Do not automate it. It is for the person at the keyboard.

Each account can send the assistant 8 messages a minute and 60 messages a day. Its answers can be wrong; check anything you rely on. What the assistant is and is not, as advice, is set out in the Educational Disclaimer.

9. How we enforce this

For most breaches, we follow the same steps as the Community Guidelines: a written warning that says what happened, then restrictions on the account, then closure if it continues. The full process, and how to appeal, is in the Account Enforcement & Appeals policy.

We close the account at once, without a warning, for attacking the platform, running fraud or bot tooling, or accessing other people's accounts or data. We may also block the network address or device involved.

Where an attack, fraud tooling or deliberate overloading causes us cost, we may recover that cost from the person responsible. Where the conduct is a crime, we report it to law enforcement and give them what they lawfully ask for.

10. Reporting a violation

To report scraping, a bot, an attack or any other misuse of ACADA's systems, write to support@acada.ac. To report a security vulnerability, use the same address or the contact in /.well-known/security.txt, and read section 6 first.

11. Changes to this policy

When we change this policy, we change the date shown at the top. If a change adds a rule or a consequence, we post a notice in the app at least 14 days before it takes effect.

12. Related policies