For the LibVibes Community — sharing your prompt and solution so other librarians can use it. Plain language first, the details below.
LibVibes is a free, static companion site published by TCEA (the Texas Computer Education Association) and maintained by Miguel Guhlin. Most of the site — the prompt library, built examples, use cases, and downloads — is just web pages: it has no accounts, no logins, and collects nothing about you.
This combined Privacy Policy and Terms of Service governs the one part that does involve sending us information: the "Share Yours" submission form and the Community gallery where approved submissions are published. It is meant for adult educators, librarians, and library staff who choose to share a tool they made. If you do not submit anything, none of this applies to you.
You may submit if you are an adult (18 or older) acting on your own behalf or for your school, library, or district, and the work you submit is your own original work or you have the rights and permission to share it.
By submitting, you agree not to send content that is unlawful, harmful, harassing, hateful, discriminatory, deceptive, privacy-invading, malicious, or otherwise inappropriate for a K-12 educational audience. Solutions must be a single self-contained HTML file (or a link to one) with no external trackers, advertising, analytics, cryptominers, or code that collects data from end users.
You and your school or organization retain ownership of the prompt and solution you submit. We do not claim your copyright.
So that we can actually review, host, and showcase your work, you grant TCEA a non-exclusive, royalty-free, worldwide license to store, review, reproduce, adapt for safe display, publish, and distribute your submission as part of LibVibes, with attribution to the name you provide. This license lasts while your submission is published and ends when we remove it at your request or our discretion (allowing reasonable time for caches and backups to clear). You may continue to use and share your own work however you like.
Published community solutions are offered to other educators for free educational use and remixing. If you want a specific open-source license applied to your work, say so in your submission and we will honor it or decline to publish.
To be published, a submission should:
index.html with inline CSS/JS and no external libraries, working offline;No submission goes live automatically. Because submissions are other people's HTML and JavaScript, a TCEA staff member reviews every entry for safety and fit before anything is published. We may approve, request changes, or decline a submission for any reason, and we are under no obligation to publish.
Approved solutions are published at libvibes/community/<name>/ and listed on the Community page with credit to you. We may edit lightly for safety, formatting, or clarity, or remove any published item at any time — for example if a problem is reported, a link breaks, or it no longer fits. You can ask us to take your submission down and we will.
LibVibes and all community submissions are provided "as is," for free, with no warranty of any kind. Community tools are made by individual educators, not certified by TCEA, and may contain bugs or limitations. Review and test any tool yourself before using it with students, and confirm it meets your district's privacy, security, and accessibility requirements.
To the fullest extent allowed by law, TCEA and the maintainer are not liable for any damages arising from submitting to, publishing on, or using LibVibes or any community tool. If you submit work, you confirm you have the right to share it and you agree to defend us against claims that your submission infringes someone else's rights.
We collect only what you type into the submission form. Nothing more, and only when you choose to submit:
| Field | Why we ask |
|---|---|
| Your name | To credit you on the published tool |
| To follow up about your submission (questions, approval, changes) | |
| School / library | Optional context; helps us understand who's building |
| Title, grade band, category, one-line description | To describe and organize your tool in the gallery |
| The starter prompt | The reusable part other librarians remix — published with the tool |
| Your solution (pasted HTML or a link) | The tool itself, which we review and, if approved, host |
Your name, title, description, prompt, and solution are intended to be public if approved. Your email and school are used for contact and context only and are not published.
We do not sell your information, use it for advertising or behavioral profiling, or use it to train artificial-intelligence models.
The submission form is a Google Apps Script web app. When you submit, your entry is recorded in a private Google Sheet and any pasted HTML is saved to a Google Drive folder, both in the maintainer's TCEA-associated Google Workspace account. A notification email may be sent to the maintainer. Access to that Sheet and the review page is password-protected and limited to the maintainer.
The LibVibes website itself is hosted on GitHub Pages (a static file host). Approved community files are stored in the project's public GitHub repository and served as plain web pages.
LibVibes pages may use your browser's localStorage only to remember settings on a tool you're using; that stays on your device and is not sent to us.
The submission form is for adult educators. It is not directed to children, and we ask that you never include student personal information — names, photos, emails, IDs, work samples, or anything identifying a child — in a prompt, description, or solution you submit.
If you build a community tool that students will use, you are responsible for ensuring it complies with FERPA, COPPA, the Texas SCOPE Act, CIPA, and your district's policies before you put it in front of students. If you believe a student's information was submitted or published by mistake, contact us (Section 18) and we will remove it promptly.
Because you choose what to submit, you stay in control. You may, at any time, ask us to:
Email us (Section 18) and we'll acknowledge within a reasonable time and complete removal from the live site promptly, allowing for normal cache and backup clearing.
Submissions are stored in access-controlled Google Workspace, served over HTTPS, and the review page is password-protected. No online service is perfectly secure, but because we collect so little — and no student data — the risk to you is low. If we become aware of a breach affecting submission contact information, we will notify affected submitters and take reasonable steps to address it.
If you are in the United Kingdom, the European Economic Area, or another region with similar data-protection law and you choose to submit, this section applies to you.
The data controller for submission information is TCEA (Texas Computer Education Association), with the LibVibes maintainer, Miguel Guhlin, as point of contact (Section 18).
You have the right to access, rectify, erase, restrict, object to, and port your personal data, and to withdraw consent. You may also lodge a complaint with your local supervisory authority (for example, the UK ICO or your national Data Protection Authority). To exercise any right, contact us (Section 18); we'll respond within one month.
LibVibes is designed to sit comfortably inside school and district privacy requirements because, by design, it collects no student data. The submission form is adult-facing and the rest of the site is static.
District responsibility. If you adopt or self-host a community tool for student use, your district is the controller for any data that tool may collect and is responsible for FERPA/COPPA/SCOPE/CIPA compliance, parental notice or consent, and accessibility in your deployment.
This quick-reference is for district privacy officers and procurement reviewers evaluating LibVibes. Because the product itself processes no student personal information, a full student Data Privacy Agreement is generally not required to browse, copy prompts from, or download LibVibes. The summary below supports your review, and we will sign a reasonable district addendum on request.
| Item | Detail |
|---|---|
| Product | Free static website (prompts, examples, downloads) plus an adult-facing submission form. |
| Student data processed | None. No student accounts, logins, rosters, or records. |
| Data elements collected | Submitter name, email, school, and their submitted prompt/solution (Section 7) — adults only. |
| Subprocessors | Google (Workspace / Apps Script — form storage); GitHub (Pages — static hosting). Google Fonts for typography. |
| Security controls | HTTPS transport; access-controlled Google Workspace; password-protected review page; human safety review of every submission. |
| Retention & deletion | Approved items kept while published; rejected/withdrawn items deleted within ~30 days. Removal on request. |
| Breach notification | Affected submitters notified if submission contact data is exposed (Section 13). |
| Sale / ads / AI training | None. Data is never sold, used for advertising, or used to train AI models. |
If your district requires a signed DPA, NDPA exhibit, or addendum before staff submit work or before you host a community tool for students, contact us (Section 18) and we'll work with you. For tools you self-host, your district's own DPA framework governs that deployment.
LibVibes aims to meet the WCAG 2.1 Level AA baseline. For the core LibVibes pages we maintain, that means:
<details> disclosures);alt text on informative images (decorative images use empty alt);If you hit an accessibility barrier on a LibVibes page, tell us (Section 18) and we'll try to fix it or provide an equivalent alternative.
We may update this policy as LibVibes evolves. Material changes will be reflected by a new version number and effective date at the top of this page. Continuing to submit after a change means you accept the updated terms.
Questions, corrections, or removal requests: contact Miguel Guhlin, TCEA, at mguhlin@tcea.org, or via blog.tcea.org. TCEA · Texas Computer Education Association.