Legal
Privacy Policy
EFFECTIVE NOVEMBER 21, 2026
Carini Systems (“we,” “us”) provides Introduction to Mechatronics, a hands-on Arduino curriculum that schools, teachers, homeschool families and individual learners use through a school’s learning management system (LMS), through Google sign-in, or directly. This policy explains what information we receive, what we keep, and what we never do. It covers our website at carinisystems.com and the course service at learn.carinisystems.com.
- We do not store student names, email addresses or student work on our servers.
- Students’ answers, photos and circuits are saved only in the student’s own browser.
- We never sell information, show ads, or use information to build profiles.
- We use no cookies, advertising trackers or analytics services on our website or in the course.
Our website (carinisystems.com)
Our website does not use cookies, analytics or advertising. Its “Request my quote” and “Join the waitlist” forms do not store anything on the website; they open your own email app with a message to us filled in. When you email us, we receive what you choose to send, such as your name, school, role and email address, and we use it only to answer you, prepare quotes, and tell you when homeschool and individual plans open. You can ask us to remove you from the waitlist at any time. The website is hosted by Cloudflare and loads its fonts from Google Fonts, which, like any web service, receive technical information such as your IP address when the page loads.
Information the course service receives
When a lesson opens from a school’s LMS (Canvas, Schoology, Moodle and others)
The school’s LMS sends a signed message that includes the person’s name, an LMS user ID, their role (for example, student or teacher), the course, and which school’s connection is in use. We use it to check the school’s license, to show the right version of the lesson (student or teacher), and to fill in the student’s name on the page. We do not store the name or the user ID. We turn the user ID into a one-way code that keeps students’ saved work separate on shared computers; it cannot be turned back into the ID.
When someone signs in with Google
For schools that use Google Classroom, and for homeschool families and individual learners, people sign in with a Google account. For students and lesson access we ask Google only for basic sign-in information: name, email address and Google account ID, plus the school’s Google Workspace domain when the account belongs to a school. We use it to check the license and to show the right lesson pages, and we do not store it.
When a teacher sets up Google Classroom
A licensed teacher may choose to let the service add the course to one of their Google Classroom classes. With the teacher’s permission, Google gives the service temporary access that lets it list the teacher’s classes (class names, sections and IDs) and add a topic, a course overview and assignments to the class the teacher picks. This access is held only in our server’s memory for up to 15 minutes and is discarded after the setup runs. The service does not read rosters, student submissions or grades, and does not change anything else in Classroom.
Lesson page links
After a sign-in or LMS launch, the service creates an encrypted link to the lesson that expires after 8 hours. The link carries the person’s name (so it can appear on the page), their role, the one-way code and the school name. It cannot be read or changed by others and stops working when it expires.
What we keep
| What | Why | How long |
|---|---|---|
| Usage log: the date and time, school name, role (student or teacher) and lesson number of each lesson opened. No names, emails or IDs. | License records and understanding which lessons schools use | Up to 3 years |
| License records: the school or customer name, license dates, LMS connection details, and the email addresses of licensed teachers or individual customers. | To provide what was purchased and to contact customers about their license | For the license term and up to 3 years after |
| Emails you send us, including quote requests and waitlist sign-ups. | Answering you, quotes and waitlist notices | As long as needed for that purpose, or until you ask us to delete them |
| Purchase and billing records (quotes, invoices, purchase orders, contact details of the person who ordered). | Accounting and tax law | As long as the law requires |
| Technical messages from our server (for example, errors). They do not include names or email addresses. | Fixing problems | Overwritten on a rolling basis as new messages are written |
Information that stays on the student’s device
Students type answers, add photos and video links, and build circuits in the Virtual Arduino. All of this is saved in the student’s own web browser on their device (browser storage), not on our servers. When a student exports a PDF, the file is saved to their device for them to upload to their teacher’s LMS or Google Classroom; it is not sent to us. A student can erase their saved work with the lesson’s “Start over” button or by clearing their browser’s site data.
How we use information
We use information only to provide, secure and support the curriculum service for the school, teacher or customer who licensed it, and to keep required business records. We do not sell or rent information, use it for advertising, build profiles of students, or use student information for any purpose other than providing the service.
Who else handles information
- Cloudflare hosts our website and carries traffic to and from the course service, protecting both from attacks. Like any network provider, it processes technical information such as IP addresses.
- The school’s LMS provider and, when used, Google handle sign-in under the school’s or user’s own agreements with them.
- Our email provider stores the emails you send us.
We may also disclose information if the law requires it, or to protect the safety of students or others. Lessons include links to outside websites, such as retailers that sell the electronic parts; those sites have their own privacy policies.
Google user data
Carini Systems’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to sign people in, check their license, and, for teachers who request it, add course materials to their Google Classroom class. We do not use Google user data for advertising, do not sell it, do not let people read it except where needed for security, legal compliance or with the user’s permission, and do not use it to train artificial intelligence models.
Students, schools and parents
- Schools (FERPA). When a school uses the service, we act as a “school official” with a legitimate educational interest, use student information only for the school, and follow the school’s direction. If a school has signed a student data privacy agreement with us, that agreement controls where it differs from this policy.
- Children under 13 (COPPA). The service is designed for use under a school’s direction, and the school may consent on parents’ behalf for educational use. We collect only the minimum needed to open a lesson, and we do not store it. In homeschool accounts, the parent is the account holder.
- Questions and requests. Parents, students and schools may ask what information we have, ask for corrections, or ask us to delete information. Because student work stays on the student’s device, most requests can be handled by the school or by clearing the browser’s saved data; for anything else, contact us and we will respond within 30 days.
Security
All connections use encryption (HTTPS). LMS launches and Google sign-ins are verified with digital signatures before any lesson opens, lesson links are encrypted and expire, students cannot open teacher materials, and our server runs in an access-controlled environment. No system is perfectly secure; if we learn of a security incident affecting a school’s information, we will notify the school without unreasonable delay and as the law and any agreement with the school require.
Cookies and tracking
Neither our website nor the course service uses cookies, advertising, analytics or tracking tools. Lesson pages use browser storage only to save the student’s own work on their device. Inside the course, fonts are served from our own server, so students’ browsers make no calls to Google Fonts.
Changes to this policy
If we change this policy, we will post the new version here with a new effective date. If a change materially affects how we handle student information, we will notify licensed schools before it takes effect.
Contact
Carini Systems, Virginia, United States
Email: carinisystems@protonmail.com