Safety
How we keep kids safe on Vibe Cōdr Academy.
Our Commitment to Kid Safety
Vibe Cōdr Academy was built from the ground up with child safety as a core design principle — not an afterthought. Every feature, every interaction, and every line of code has been evaluated through the lens of protecting the kids who use our platform.
We believe that kids should be able to explore coding creatively in an environment that their parents and teachers can trust completely. Below is a detailed explanation of every safety measure we have in place.
Two-Layer Content Filtering
Every message in Vibe Cōdr Academy passes through two independent content filters — one on the way in and one on the way out.
Layer 1: Input Filtering
Before a child's message is ever sent to the AI, it is screened for inappropriate content. This includes profanity, slurs, sexual language, violent content, hate speech, and attempts to manipulate or "jailbreak" the AI. If a message is flagged, it is blocked immediately — it never reaches the AI. The child sees a friendly message explaining that their message could not be sent, and the attempt is logged for the parent or teacher to review.
Layer 2: Output Filtering
After the AI generates a response, it passes through a second filter before being shown to the child. This catches any inappropriate content that the AI might generate despite our system-level instructions. If the AI's response is flagged, it is replaced with a safe fallback message.
Both filters are continuously updated to address new patterns and edge cases. While no filter is perfect, the two-layer approach significantly reduces the risk of inappropriate content reaching a child.
Personal Information (PII) Protection
Children sometimes unknowingly share personal information in conversation. Our PII detection system automatically identifies and blocks the following types of personal information before they reach the AI:
- Phone numbers
- Email addresses
- Physical addresses
- Social Security numbers
Our PII detection uses word-boundary matching to minimize false positives while still catching real attempts to share personal information. When PII is detected, the message is blocked and the child is shown a friendly reminder not to share personal information. The attempt is logged for the parent or teacher.
Sandboxed Code Execution
All projects on Vibe Cōdr Academy run inside a sandboxed iframe. This means that the code your child creates — or that the AI generates — is completely isolated from the rest of the browser and the device.
The sandbox prevents code from:
- ×Accessing the device's camera or microphone
- ×Reading the device's GPS or geolocation data
- ×Accessing the local file system
- ×Navigating the parent page or opening new windows
- ×Reading cookies or session data from the main application
- ×Making network requests to external servers
JavaScript execution is allowed within the sandbox so that interactive projects (such as games and animations) work correctly, but it cannot escape the sandbox boundary. Kids can code freely and creatively with no risk to your devices.
No Social Features or Direct Contact
Vibe Cōdr Academy has no social features. There is no way for one user to contact or communicate with another user. Specifically:
- No direct messages or private messaging of any kind
- No chat rooms or group chats
- No friend requests or follower systems
- No commenting on showcase projects
- No user profiles visible to other users (beyond the display name and avatar on published showcase projects)
- No forums or discussion boards
The only interaction between users is the ability to view and upvote projects published to the Project Showcase. This is a deliberate design decision to eliminate any avenue for inappropriate contact between users or between an adult and a child who is not their own.
Full Adult Visibility
We give parents and teachers complete transparency into what their kids are doing on the platform. Your adult dashboard provides the following for each child account:
Message History
Every message between your child and Crackers 🦜 is stored and accessible from your dashboard. You can read the full context of each conversation at any time.
Project Review
See every project your child has saved, including the HTML, CSS, and JavaScript code and a live preview. Track which projects have been published to the Showcase.
Blocked Content Log
When a message is blocked by our content filter, you see the exact content that was attempted, when it happened, and why it was flagged. This gives you an opportunity to have a conversation with your child if needed.
Time Tracking
See exactly how long each child spends in the coding editor — daily, weekly, and monthly. Our heartbeat system pauses when the browser tab is hidden, so the numbers reflect actual active time.
COPPA Compliance
Vibe Cōdr Academy complies with the Children's Online Privacy Protection Act (COPPA), which governs the collection of personal information from children under 13 in the United States.
Our COPPA compliance measures include:
- Child accounts can only be created by a parent or guardian — children cannot sign up on their own.
- We collect minimal data from children: a username (display name), a password, projects, conversations, and usage statistics. We do not collect a child's real name, email, phone number, or physical address.
- Parents and guardians have the right to review all information collected from their child, request deletion of that information, and refuse further collection by deleting the child account.
- We do not sell children's personal information. We do not share children's personal information with third parties for marketing or advertising purposes.
- We do not use tracking cookies or third-party analytics on children's accounts.
For complete details on our data practices, see our Privacy Policy.
How to Report a Safety Concern
If you encounter any safety concern while using Vibe Cōdr Academy — whether it involves content that should have been filtered, a potential vulnerability, or any other issue related to child safety — please contact us immediately.
Report a Safety Concern
Email: info@deaconhill.com
Please include as much detail as possible, including the child account username (display name), the approximate date and time of the incident, and a description of what occurred. We treat all safety reports as high priority and will respond promptly.
Safety Summary
| Content filtering | Two layers — input and output — blocking profanity, sexual content, hate speech, violence, and jailbreak attempts |
| PII protection | Automatic detection and blocking of phone numbers, emails, addresses, and SSNs |
| Code execution | Sandboxed iframe with no access to camera, microphone, geolocation, or file system |
| Social features | None — no DMs, chats, comments, friend requests, or contact between users |
| Adult visibility | Full access to message history, projects, blocked content log, and time tracking per child |
| Tracking cookies | None — only essential authentication session cookies |
| COPPA compliance | Full compliance — parental consent required, minimal data collection, parental review and deletion rights |