Written security assurance request under 16 CFR 312.8(c) COPPA (ReadyU, readyu.ai)

Abierto
#10,534 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
1/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, typescript

Línea de trabajo

This issue requests a written security assurance and plan guidance from Clerk; it does not identify a code file, test, or repository change to start from. The requester asks for a reply by email and says an identical request was sent to support, so the outcome depends on a response from Clerk rather than a newcomer contribution.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Written security assurance request under 16 CFR § 312.8(c) (COPPA Rule)

We are ReadyU (readyu.ai), a K-12 education platform (NSBMathBlitz, NsbPhysicsBlitz, BioSphere and sibling apps) launching on Clerk Hobby with Clerk Organizations as our auth provider. A large share of our users are children under 13, so Clerk collects and maintains children's personal information (parent email, name, organization membership) on our behalf.

Under the amended COPPA Rule, 16 CFR § 312.8(c), before releasing children's personal information to a service provider the operator "must take reasonable steps to determine that such entities are capable of maintaining the confidentiality, security, and integrity of the information and must obtain written assurances that such entities will employ reasonable measures to maintain the confidentiality, security, and integrity of the information."

We understand Clerk has held SOC 2 Type 2 since 2022 (per https://clerk.com/security.md), and that the SOC 2 report itself is gated to the Business plan ($300/mo) — not available to us on Hobby or Pro. Until we can upgrade, we are requesting a direct written security assurance instead:

  1. A written assurance (letter or email from Clerk) that Clerk will employ reasonable measures to maintain the confidentiality, security, and integrity of the children's personal information it collects and maintains on ReadyU's behalf, sufficient for our § 312.8(c) vendor due-diligence file; and
  2. Guidance on the lowest-cost way for a Hobby-plan customer to obtain that assurance or an equivalent report extract (e.g. an NDA-gated excerpt of the current SOC 2 report via the Drata trust portal at trust.clerk.com).

Please send the written assurance (or a reply) to [email protected] (Yan Deng, owner/operator, ReadyU). Reference: this issue; our production instance is being bootstrapped under the readyu.ai primary domain.

For our compliance file, this issue is the recorded request (channel: public GitHub issue on clerk/javascript, since the § 312.8(c) request needs a trackable written channel). An identical request is being emailed to [email protected].

Thanks!

Lenguaje dominante
TypeScript
Estrellas
1.8k
Forks
492
Merge medio
1 d 7 h
PR fusionados (30 d)
357

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de clerk/javascript

Todos los issues de clerk/javascript

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.