Last updated: September 9, 2026 · Version 2026-09-09
This Privacy Policy is issued by SwayForm LLC ("SwayForm," "we," "us," or "our"), based in Atlanta, Georgia. It explains how we collect, use, store, and share information across the SwayForm website (swayform.net), the Learning Portal (learning.swayform.net), our administrative tools, and the S1 robot platform.
If you are a student, parent, guardian, or school employee, please also read the Student & Children's Privacy Notice, which covers COPPA, FERPA, and Georgia student-data law in more detail and controls over this policy for anything specific to student data. Schools should also see the School Data Agreement, and anyone interested in our security practices should see the Security page. Retention and deletion specifics live on the Data Retention & Deletion Policy page. Physical safety and acceptable use of S1 hardware is covered separately by the Robot Safety and Acceptable Use Policy.
On this page
This policy covers every SwayForm-operated surface a school, family, student, or visitor might interact with:
SwayForm is currently in a pilot development stage — we do not yet process commercial purchases through this website, and some sections below describe both what is true today and how a feature will be handled once it exists. Where that distinction matters, we say so explicitly rather than describing a feature we have not built yet.
S1's core processing — motion control, ROS 2 nodes, and camera/sensor processing — runs locally on its onboard computer. S1 connects to the school's Wi-Fi (for the Learning Portal, classroom accounts, and updates), but does not require a cloud connection to operate.
The optional cloud simulation subscription (see For Schools) is a separate, opt-in service — it is not required for S1 to operate. Enabling it requires separate disclosure and consent before it is turned on.
SwayForm does not use facial recognition, voiceprint recognition, or gesture-based biometric identification, and does not create biometric identifiers (as defined by applicable law, including the amended COPPA Rule) from classroom images, video, or sensor data. This is true even though S1's camera and depth sensor are technically capable of supporting such features in the future.
If SwayForm ever adds a biometric-recognition feature, it will be a separate, clearly disclosed, opt-in feature requiring its own authorization process — never a silent addition to an existing product.
SwayForm does not send Student Data (defined below), classroom video, audio, or student-written code to third-party AI services to train general-purpose AI models. We may use properly de-identified or aggregated information (for example, anonymized feature-usage counts) to understand how our products are used, diagnose performance issues, and improve our educational products — but we will not attempt to re-identify properly de-identified Student Data.
"Student Data" means personal information about a K-12 student that is collected or generated in connection with SwayForm's products, including but not limited to: name, school-affiliated or personal email address, school name, account identifiers, class or robot-seat assignments, lesson progress, activity logs, code or projects a student creates, and any information provided by the school on the student's behalf.
A school's authorization does not make the school solely responsible for compliance with COPPA or other student-privacy laws. SwayForm maintains its own obligations as an operator under COPPA and other applicable law regardless of any school consent or authorization it relies on.
See the Student & Children's Privacy Notice for the full COPPA notice, including what is collected from children under 13, parental and school review/deletion rights, and how to make a request.
| Category | What we collect | Why |
|---|---|---|
| Account & profile | Name, email address, school name, account role (admin, student, or general member) | Create and operate your Learning Portal account; identify which school and robot you belong to |
| Lesson progress | Which activities are completed, current activity/step | Save and display your learning progress across sessions |
| Code you write (editor drafts) | Program files as you write and edit them in the Learning Portal editor | Let you write and edit programs — stored locally in your browser, not on SwayForm's servers |
| Code submitted to run on a robot | The submitted program and the resulting output when you send code to the "Run on Robot" approval queue | Let an instructor review and approve it and let it execute on the robot — stored on SwayForm's servers only while queued/running and for a limited period afterward (see Data Retention & Deletion Policy); visible only to your own school's instructors/admins |
| Session data | A signed, HTTP-only session cookie | Keep you signed in; expires automatically |
| Terms acceptance record | Your email, the policy version you accepted, and a timestamp | Maintain proof that you agreed to the Terms of Use and this Privacy Policy |
| Contact & sales inquiries | Name, email, organization, role, and message you submit | Respond to your inquiry |
| Hosting logs | IP address, request timestamps, and other standard technical data logged by our hosting provider | Security, abuse prevention, and reliability |
| Analytics and cookies | None in dedicated use as of this update | If and when analytics or advertising cookies are added, this row and the rest of this policy will be updated first to disclose what is collected and why |
We do not currently operate any live video, audio, or biometric data pipeline from S1 to our servers — see Section 2.
The Learning Portal uses Google Identity Services ("Sign in with Google") rather than a username/password system. When you sign in this way, Google provides us with a signed token containing your email address, whether that email is verified, your display name, and your profile picture — nothing more. We do not request any additional Google permissions (such as access to your Drive, Calendar, or contacts), and we never receive your Google password.
SwayForm uses a small number of service providers ("subprocessors") to operate the website and Learning Portal. Each may use the information it receives only to provide its contracted service to SwayForm, and must protect it accordingly.
| Provider | Purpose | What it may receive |
|---|---|---|
| Vercel | Website and Learning Portal hosting | Standard hosting/request logs (IP address, timestamps) |
| Neon | Database hosting | Account, profile, school, and lesson-progress data described in Section 5 |
| Sign-in / authentication | The sign-in token described in Section 6 | |
| Web3Forms | Delivers contact-form submissions to SwayForm by email | Whatever you type into the Contact or Contact Sales form |
This is a complete list of subprocessors currently receiving any data as of the date of this policy. If SwayForm adds a new subprocessor that will receive Student Data or other personal information, we will update this table before that subprocessor begins receiving data.
SwayForm does not sell personal information of any kind — student or otherwise — and does not share it with third parties for their own marketing purposes. We do not use website visitor or Learning Portal account information for targeted or behavioral advertising, and we will not add contact-form submitters to a marketing mailing list.
Full detail, including how to request deletion, is on the Data Retention & Deletion Policy page. In summary:
| Data | Retention |
|---|---|
| Account profile & lesson progress | While the account or school relationship is active; purged within 30 days of a verified deletion request or account closure |
| An entire school's data (school leaves the platform, or requests full deletion) | Completed within 45 days of a verified request from an authorized school representative |
| Contact-form submissions | Up to 12 months, or sooner once your inquiry is resolved |
| Hosting/security logs | Up to 12 months |
| Terms acceptance records | Retained for the life of the account, plus 3 years, as proof of consent |
| Backups | Roll off within 30 days after the underlying data is purged from live systems |
| Code you write in the Learning Portal editor or on robot hardware | Stored locally on your device/browser or the robot's own storage, not on SwayForm's servers — SwayForm cannot delete what it does not hold, so you and your school are responsible for local copies |
We maintain administrative, technical, and organizational safeguards designed to protect the information described in this policy, including access controls, encrypted connections, and least-privilege access to production data. Full detail is on the Security page. No system can be guaranteed to be 100% secure, and we do not claim otherwise. If we become aware of a security incident affecting your personal information, we will investigate and provide notifications required by applicable law and any agreement we have with your school.
If SwayForm is involved in a merger, acquisition, financing, or sale of assets, personal information may be transferred as part of that transaction. Any successor will remain subject to the commitments in this policy with respect to information collected before the transfer, including the student-data protections described here and in the Student & Children's Privacy Notice.
We will update the version number and "Last updated" date at the top of this page whenever this policy changes. For material changes — particularly anything affecting Student Data, camera/video handling, or retention — we will provide advance notice (for example, to school administrators on file) before the change takes effect where practical.
Questions, access requests, or deletion requests can be sent to contact@swayform.net. SwayForm LLC is based in Atlanta, Georgia.