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

Ouverte
#10,534 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
1/5
Temps estimé
Moins d'une heure
Accessibilité débutants
1/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
javascript, typescript
Domaine
authentication

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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!

Langage dominant
TypeScript
Étoiles
1.8k
Forks
492
Merge moyen
1 j 7 h
PR mergées (30 j)
357

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de clerk/javascript

Toutes les issues de clerk/javascript

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.