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

未关闭
#10,534 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
1/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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!

主要语言
TypeScript
星标
1.8k
派生
492
平均合并
1 天 7 小时
30 天内合并 PR
357

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

clerk/javascript 的其他 Issue

查看 clerk/javascript 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。