Legal, Privacy & School Safety

Privacy Policy

Dark Labs ("Dark Labs," "we," "us") operates dark-labs.co as a studio portfolio and business website. This Privacy Policy describes how we handle information when you visit our public site or contact us.

This policy applies to dark-labs.co. Educational products are operated separately and may have additional policies.

Information We Collect

Information you provide. If you use our contact form, we may collect your name, email address, message content, and any other details you choose to submit.

Technical information. Our hosting and infrastructure providers may process standard server logs, including IP address, browser type, referring URL, and timestamps. We do not intentionally use Google Analytics or Google Tag Manager on dark-labs.co for marketing analytics.

Search Console. We may use Google Search Console for domain ownership verification and aggregated search performance monitoring. Search Console is not a user-facing tracking product on this site.

How We Use Information

We use contact submissions to respond to inquiries and evaluate potential work. We use server logs for security, troubleshooting, and site reliability. We do not sell personal information.

Cookies and Tracking

dark-labs.co is intended to function as a marketing and portfolio site without third-party advertising trackers. If we add analytics or embedded services in the future, we will update this policy and disclose them here.

Data Retention

Contact form submissions are retained only as long as needed to respond, maintain business records, or meet legal obligations.

Children's Privacy

dark-labs.co is not directed to children under 13. We do not knowingly collect personal information from children on this marketing site. Teacher-facing educational products are not designed for student use. Where those products process student records on behalf of schools, they are governed by separate policies and school agreements.

Your Rights

Depending on your location, you may have rights to access, correct, delete, or restrict certain processing of your personal information. Contact us at [email protected] to make a request.

---

Terms of Service

By accessing dark-labs.co, you agree to these Terms of Service. If you do not agree, please do not use the site.

Use of the Site

You may use this website for lawful purposes only. You may not attempt to disrupt the site, scrape it in a way that impairs service, probe systems without authorization, or use the site to distribute malware or unlawful content.

Portfolio and Content

Project descriptions, images, writing, and other materials on dark-labs.co are provided for informational purposes. Case studies and screenshots are illustrative unless otherwise stated. We do not guarantee that every described capability is available in every deployment.

Third-Party Links

This site links to external services, repositories, and client or product websites. Dark Labs is not responsible for the content, privacy practices, or terms of third-party sites.

No Professional Advice

Information on this site does not constitute legal, security, educational, or procurement advice. Schools, libraries, and businesses should rely on their own counsel and policies when evaluating technology.

Intellectual Property

Unless otherwise noted, content on dark-labs.co is owned by Dark Labs or used with permission. You may not reproduce site assets for commercial use without prior written consent.

Disclaimer of Warranties

The site is provided "as is" without warranties of any kind, express or implied, including fitness for a particular purpose or non-infringement.

Limitation of Liability

To the fullest extent permitted by law, Dark Labs will not be liable for indirect, incidental, special, consequential, or punitive damages arising from use of this site.

Governing Law

These terms are governed by the laws applicable where Dark Labs operates, without regard to conflict-of-law principles.

---

School Safety & CIPA Compatibility

Dark Labs designs AI, automation, and educational technology systems that can be configured for use in school and library environments.

CIPA compliance is certified by eligible schools and libraries as part of their E-Rate obligations. Dark Labs does not certify a school's CIPA compliance. However, our systems can be configured to support CIPA-aligned safety practices, including:

• authenticated access for private educational tools;
• exclusion of private teacher, staff, and admin pages from public search indexing;
• moderation or disabling of user-generated content where appropriate;
• administrative controls for communication, content visibility, and data access;
• restrictions against obscene, pornographic, exploitative, or harmful-to-minors content;
• support for school-managed filtering, monitoring, and acceptable-use policies.

What CIPA Means for Schools

The Children's Internet Protection Act (CIPA) requires eligible schools and libraries receiving E-Rate discounts to adopt an internet safety policy and implement measures to block or filter access to certain harmful content online. Certification is the responsibility of the school or library authority, not individual vendors.

Dark Labs supports procurement and safety review by documenting how our educational products can be deployed in controlled environments. We use language such as CIPA-compatible configuration rather than claiming vendor-side CIPA certification.

Portfolio vs. Educational Products

dark-labs.co is a studio portfolio. It includes work across AI, Web3, games, and commercial technology. Educational deployments are described here for context, but school-facing privacy, security, and student-data commitments for live products are maintained on product-specific sites and in district agreements.

Search Console and Public Indexing

Dark Labs does not use Google Search Console as a user-facing tracking system. Search Console may be used only for domain ownership verification and aggregated search performance monitoring on public marketing pages.

Private application, dashboard, and admin routes should remain authenticated, excluded from public sitemaps, and marked noindex where applicable. robots.txt supports crawl hygiene but is not a security control.

Communications and AI Safety

Where educational products include AI-assisted features, those tools are intended for teacher and staff use only. Deployments should be:

• authenticated and role-based for authorized school personnel;
• moderated or constrained by school policy;
• free of unmoderated open web browsing or image generation unless explicitly approved by the district;
• not deployed as direct student-facing chat, messaging, or social tools.

School administrators, library staff, and procurement reviewers may contact [email protected] for deployment documentation or to request a district review packet.

---

Student Data Practices

This section describes how Dark Labs handles student information when authorized school staff use our educational technology.

Educational products are a teacher-facing platform. It is not directed to students and is not designed for student login or direct student use. Teachers and authorized administrators may use educational products to manage attendance, grading, analytics, and related school operations that can involve student educational records.

dark-labs.co is a public marketing site. We do not publish student personally identifiable information (PII) on public marketing pages, including names, emails, grades, attendance records, school IDs, or classroom screenshots with real data.

Roles and Responsibilities

In typical K-12 deployments, the school or district acts as the primary authority over educational records and student privacy decisions. Dark Labs builds teacher-facing tools that schools configure under their own policies, acceptable-use rules, and vendor agreements.

COPPA

Educational products are not directed to children under 13. COPPA may still be relevant when student information is processed on a school's behalf. Where a school authorizes use of educational products and consent is obtained consistent with COPPA, Dark Labs supports school-directed deployments and can provide notices describing collection and use practices relevant to the product.

FERPA and Educational Records

Where applicable, student educational records processed in educational products should be protected consistent with FERPA expectations and the school's agreements. Access should be limited to authorized school personnel as defined by the district.

Technical Safeguards

For educational products, Dark Labs supports:

• authentication and role-based access for teacher and admin experiences;
• noindex and crawl exclusions for private app, dashboard, and admin routes;
• separation of public marketing content from authenticated product environments;
• administrative controls over visibility, communication, and data access;
• audit-friendly deployment options for district review.

Data Minimization on Public Sites

Our public portfolio avoids real student examples. Marketing copy describes teacher-facing capabilities at a high level without exposing live classroom data.

Live deployments are governed by product terms and district agreements. Contact [email protected] for a current student-data addendum or district security questionnaire.

---

Security

Dark Labs takes a practical security posture across public marketing properties and configurable product deployments.

Public Website

dark-labs.co is a static/marketing site with limited data collection. Contact submissions are handled through controlled server-side endpoints with basic abuse protections.

We do not rely on robots.txt as an access-control mechanism. Private routes on separate product domains or subdomains require authentication and should use noindex headers where appropriate.

Indexing and Crawl Controls

Public portfolio and legal pages may be indexed. The following paths are disallowed in our robots policy for crawl hygiene on properties that use them:

• /app/
• /dashboard/
• /admin/
• /students/
• /api/

These paths are reserved for product environments and are not intended to expose private data through search engines.

Search Console

Google Search Console may be used for DNS/domain verification and aggregated search performance monitoring. We recommend domain verification via DNS TXT rather than adding analytics snippets solely for verification.

Search Console access should be limited to trusted administrators, and stale verification tokens should be removed during periodic access reviews.

Educational Deployments

For school-facing products, supported controls may include:

• authenticated sessions and role-based authorization;
• encrypted transport (HTTPS);
• environment separation between production and non-production systems;
• administrative audit and access controls where required by contract;
• configurable retention and export workflows through district agreements.

Reporting Issues

If you believe you have found a security vulnerability affecting Dark Labs, contact [email protected] with enough detail to reproduce the issue. Please avoid public disclosure until we have had a reasonable opportunity to investigate.