1. Who we are
AssignAI is operated by the AssignAI team ("AssignAI", "we", "us"). This policy explains what personal information we collect through the AssignAI web application (the "Service"), how we use it, who we share it with, and the choices you have. It applies to instructors, students, and anyone who visits the site.
2. Data-flow statement
This table describes every category of data the Service handles today, where it is stored, and who can see it. It is written to match how the software actually works.
| Data | Collected from | Stored in | Sent to | Who can see it |
|---|---|---|---|---|
| Account: email, name, role (instructor or student), a one-way hash of your password, and optional profile fields (a title such as "Dr.", first and last name, a short bio, and a profile photo, stored as a small image in our database). | You, at sign-up and on your profile page. | Google Cloud Firestore (our database). | Nobody outside our hosting providers. | You. Instructors see the name and email of students enrolled in their courses. |
| Course and assignment content: course names and descriptions, instructor contact details shown to students, assignment instructions, learning objectives, step designs, and the AI tutoring settings an instructor chooses. | Instructors. | Google Cloud Firestore. | The AI provider, as context when generating replies (see below). | The instructor, and enrolled students for published assignments (minus hidden grading objectives and system prompts). |
| Learning Assistant conversations: every message a student sends and every reply the assistant gives, with timestamps, which assignment step each message belongs to, turn counts, and whether the assistant judged a step's objective met. | Students, while completing an assignment. Instructors, while previewing their own assignment. | Google Cloud Firestore, filed under an anonymous session ID (see section 3). | The AI provider, to generate each reply and to judge objectives. Sent without the student's name, email, or account. | The student, and the instructor who owns the assignment (in the app and as a CSV or Markdown export). |
| Enrollment: which students joined which course, and when. | Created when a student uses a course invite link. | Google Cloud Firestore. | Nobody. | The course's instructor. |
| Uploaded documents (for example a syllabus an instructor attaches while building an assignment). | Instructors. | Not stored. The file is converted to text in memory and discarded. | Up to the first few thousand characters of the extracted text go to the AI provider as context for the Builder Assistant. | The instructor, during that builder session. |
| Usage analytics: pages viewed, product events (such as "assignment created"), browser and device type, and an opaque user id with your role. No email or name. | Your browser, automatically. | PostHog (analytics provider), servers in the United States. | PostHog. | The AssignAI team. |
| Error reports: technical details when something breaks (stack trace, page, browser), tagged with an opaque user id and role. No email or name, and no message text by default. | Your browser and our servers, automatically. | Sentry (error-monitoring provider). | Sentry. | The AssignAI team. |
| Rate-limit counters: how many AI requests your account has made in the current minute and day. | Generated by the Service. | Google Cloud Firestore. | Nobody. | The AssignAI team. |
| Server logs: request metadata such as IP address, time, and URL, kept briefly by our hosting provider for security and debugging. | Your browser, automatically. | Vercel (hosting provider). | Vercel. | The AssignAI team. |
About the AI provider
Replies from the Learning Assistant and the instructor-side assistants (such as the Builder Assistant) are generated by Anthropic's Claude API, with OpenAI's API as an automatic backup if Anthropic is unavailable or rate-limited. To generate a reply we send the relevant conversation text, the assignment's instructions and objectives, and course context the instructor provided. We use both providers' APIs under their commercial terms, which, as of the effective date, state that API inputs and outputs are not used to train their models. We do not send your email, name, or password to the AI provider (see section 3). If we change providers, we will update this section.
3. Anonymous student IDs
When a student starts an assignment, the Service creates a random identifier (a UUID) for that student and that assignment. The student gets a different identifier for each assignment, and the conversation and progress for that assignment are stored under it.
- What the AI provider receives: the conversation and the assignment context (instructions, objectives, and the course details the instructor provided). Requests do not include the student's name, email, password, or account details.
- Where the link to the student lives: the record that connects each identifier to a student account is kept only in our database on AssignAI's servers. The AI provider has no access to it.
- Who can still see names: the instructor who owns the assignment sees which student each transcript belongs to, as described in section 2.
One limit to know: if a student types identifying details into a message, such as their own name, that text is sent to the AI provider like the rest of the message.
4. How we use information
- To run the Service: authenticate you, deliver assignments, generate assistant replies, and show instructors their students' progress.
- To keep the Service reliable and safe: rate limiting, error monitoring, abuse prevention.
- To understand how the product is used, in aggregate, so we can improve it.
- To respond when you contact us.
We do not sell personal information, do not use it for targeted advertising, and do not use student conversations to train AI models.
5. Students, instructors, and education records
Instructors use AssignAI on behalf of their institution or course. When a student completes an assignment, the resulting transcript and progress data are made available to the instructor who owns that assignment. Instructors are responsible for using that information in line with their institution's policies and applicable education-privacy laws, including the Family Educational Rights and Privacy Act (FERPA) where it applies. Where AssignAI processes education records on an institution's behalf, it does so only for the purposes above and does not disclose them except as described in this policy.
6. Sharing
We share personal information only with:
- Service providers that process it for us under contract: Google Cloud (database), Vercel (hosting), Anthropic and OpenAI (AI replies), PostHog (analytics), Sentry (error monitoring).
- Instructors, for students enrolled in their courses, as described above.
- Authorities, when required by law or to protect the rights and safety of users and the public.
- A successor, if AssignAI is acquired or merged, in which case this policy continues to apply to the transferred data.
7. Cookies and similar technologies
- Strictly necessary: a session cookie that keeps you signed in. The Service cannot work without it.
- Analytics: PostHog stores a small identifier in your browser so we can count visits and understand product usage. It is set only when analytics are enabled for the deployment you are using.
We do not use advertising cookies.
8. Retention and deletion
We keep your account and content for as long as your account exists. Learning Assistant conversations are kept so that students and instructors can revisit them for the duration of the course and afterward. To delete your account, or to ask us to delete specific conversations, contact us from the email address on your account (see Contact); we will act within 30 days. Instructors can also ask us to delete all data for a course. Analytics and error data are kept by those providers under their retention settings. Backups may persist for a limited time after deletion.
9. Your choices and rights
- You can view and update your profile in the app.
- You can request a copy of your data, correction, or deletion by contacting us.
- Students can ask their instructor, or us, which assignments have collected data about them.
- Depending on where you live, you may have additional rights under state or national privacy law. We will honor those rights as required.
10. Security
Passwords are stored only as salted one-way hashes. Data moves between your browser, our servers, and our providers over encrypted connections. Access to production data is limited to the AssignAI team. No system is perfectly secure; if we learn of a breach affecting your information, we will notify you and, where required, your institution and regulators.
11. Children
AssignAI is built for higher education and is not directed at children under 13. We do not knowingly collect information from anyone under 13. If you believe a child has created an account, contact us and we will remove it.
12. International users
The Service is hosted in the United States. If you use it from elsewhere, your information will be transferred to and processed in the United States.
13. Changes
We will post any changes here and update the effective date. For material changes we will also notify signed-in users in the app.
14. Contact
Our privacy contact details will be listed here once this policy is finalized.
See also our Terms of Service.