Email: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation

Raw text

Transcribed text as recorded, including headers and formatting fragments.

Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 Page 1 of 15 Message From: [/O=THEFACEBOOK/OU=EXCHANGE ADMINISTRATIVE GROUP Sent: (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN= 2/10/2020 9:45:55 PM To: @fb.com]; @fb.com]; @fb.com]; @fb.com]; @fb.com]; Andrew Bocking @fb.com]; @fb.com]; @fb.com]; Guillermo Spiller @fb.com]; Denise Moreno @fb.com]; @fb.com]; @fb.com] CC: Subject: @fb.com] Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Attachments: image001.png; image002.png; image003.png; image004.png; image005.png; image006.png; image007.png; image008.png; image009.png; image010.png; image011.png; image012.png Just wanted to update this thread - the team is ready to launch the checkpoint (line in green on the earlier plan) globally tomorrow, Feb 11. Pls Imk if questions/concerns. From: @fb.com> Date: Wednesday, December 4, 2019 at 8:14 PM To: Cc: @fb.com>, Andrew Bocking @fb.com>, @fb.com>, @fb.com>, @fb.com>, Guillermo Spiller @fb.com>, @fb.com>, Denise Moreno @fb.com>, @fb.com>, @fb.com> @fb.com> @fb.com>, @fb.com>, Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Our first rev of the modal concept put the confirmation on a second screen which was the same number of steps as the current inline checkbox. Since then, we played with adding a little more friction to the process (while trying to keep the UX simple) by having the user: 1) change the DOB 2) show modal screen with age checkbox 3) confirm age via checkbox 4) submit form again This tweak should show some gains and is worth testing. Check out the design here (FYI It's still WIP and does not have the approved content). Will circle back with timeline after some further team discussions From: @fb.com> Date: Wednesday, December 4, 2019 at 4:12 PM To: Andrew Bocking @fb.com>, @fb.com>, Spiller @fb.com>, @fb.com>, @fb.com> Cc: @fb.com> @fb.com>, @fb.com>, @fb.com>, Guillermo @fb.com>, Denise Moreno @fb.com>, @fb.com>, @fb.com>, Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation + who now manages this space in Ops. HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003183 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 Page 2 of 15 From: Andrew Bocking @fb.com> Date: Monday, December 2, 2019 at 4:48 PM To: @fb.com>, @fb.com>, @fb.com>, @fb.com>, Guillermo Spiller @fb.com>, @fb.com>, Denise Moreno @fb.com>, @fb.com>, @fb.com>, @fb.com>, @fb.com> @fb.com> Cc: Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Thanks for the update! @ - where can we learn more about the confirmation screens + timelines for them? Seems pretty urgent/important given the highlight (+checkbox only mitigating 30%). Andrew From: @fb.com> Date: Monday, December 2, 2019 at 2:41 PM To: @fb.com>, Andrew Bocking @fb.com>, @fb.com>, @fb.com>, Guillermo Spiller @fb.com>, @fb.com>, Denise Moreno @fb.com>, @fb.com>, @fb.com>, @fb.com>, @fb.com> Cc: @fb.com> Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation for Ops Quick status update: Checkbox launched globally to 95% on 11/26 - observed 30% drop in u13 DoB change attempts, which translates into 2.3-3M global annual MAP impact (vs ~3.2-4M earlier) Working team's consensus is to: Launch checkpoint globally this week, pending remaining product/eng work and ops readiness (the capacity now is 2.6k/day, will need to go to 12-16k/day + likely 35 day backlog of 591K accounts) @ Continue to build and test potential confirmation screen designs - based on early design outcomes, Profile team believes the incremental MAP impact would be immaterial @ Pls add on if I missed anything. From: @fb.com> Date: Friday, November 22, 2019 at 11:39 AM To: @fb.com>, Andrew Bocking @fb.com>, @fb.com>, @fb.com>, Denise Moreno @fb.com>, @fb.com>, Guillermo Spiller @fb.com>, @fb.com>, @fb.com>, @fb.com> Cc: @fb.com> Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003184 Decision: Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 Page 3 of 15 • Launch checkbox now, no checkpoint • Follow up on time to build the age confirmation screen@ in parallel • Follow up on data preservation@ • Ensure staffing to handle the volume increase • Next week: share numbers on checkbox impact@ • Week of Dec 2: launch checkpoint globally (pending @ days) From: @fb.com> Date: Friday, November 22, 2019 at 8:37 AM To: Andrew Bocking @fb.com>, Cc: @ @ to provide input - start building 's guidance, likely including all users from the last 35 @fb.com>, @fb.com>, @fb.com>, Denise Moreno @fb.com>, Guillermo Spiller @fb.com> @fb.com>, @fb.com>, @fb.com>, @fb.com> Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Hi Andrew, we rerun the numbers. For FB the rate from checkpointed to appeal clear is ~8.5%, which breaks down as below: Appeal rate: 48% (proportion of checkpointed users who appeal) Appeal clear rate: 17.5% (proportion of appeals successfully cleared) Answering your second question we never looked into whether stuck accounts end up creating a SUMA account. M From: Andrew Bocking @fb.com> Date: Thursday, November 21, 2019 at 5:23 PM To: Cc: @fb.com>, @fb.com>, @fb.com>, @fb.com>, Denise Moreno @fb.com>, Guillermo Spiller @fb.com> @fb.com>, @fb.com>, @fb.com>, @fb.com> Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Thanks - that would be helpful. Have we ever looked into whether those stuck create a SUMA account? From: @fb.com> Sent: Thursday, November 21, 2019 9:19:58 AM To: Cc: @fb.com>; @fb.com>; Andrew Bocking @fb.com>; Denise Moreno @fb.com>; @fb.com>; @fb.com>; Guillermo Spiller @fb.com> @fb.com>; @fb.com>; @fb.com> Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation We did some analysis in the past and we saw a combination of two factors: HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003185 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 Page 4 of 15 1. Very low appeal rate from FB users (i.e. very few users who land in the U13 checkpoint even appeal. We don't see the same behavior for IG accounts in the same checkpoint) 2. Once people appeal, the clear rate is low. The appeal is solely ID-based and has non negligible friction (particularly for teens who we believe are more likely to land in this checkpoint) I can share numbers later on but we need to rerun few queries to make sure they are still up to date. From: @fb.com> Date: Thursday, November 21, 2019 at 4:29 PM To: @fb.com>, @fb.com>, Guillermo Spiller Moreno @fb.com>, Cc: @fb.com>, @fb.com>, Andrew Bocking @fb.com>, @fb.com>, Denise @fb.com> @fb.com>, @fb.com> Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation On #4 and #5, we are hoping to mitigate around half of the impact with this change. 2.6% of age changes on mobile are to u13 vs. 1.3% on www. This is super biased and hard to say how much of this is due to the checkbox, but this is our best way to quickly estimate what kind of impact it would have before running a test. There's three main areas where we could work try to mitigate this impact: 1. Promote the edit birthday feature less. It currently sits right under current work, education, contact info and city, meaning when a user goes to change where they live, work, etc. they have a good chance to see birthday with an edit button. 2. Be more explicit than a checkbox like a confirmation screen, etc. to make sure users are really aware of what they are doing 3. Optimize the checkpoint <- I have not looked into checkpoint clear rate yet, @ could you share some high level understanding of why it's so low? Is it completions or decisions that cause the dropoff? I think the main question is how much do we do before we ship vs. after we ship. We can use the 15 min to discuss. Thanks, From: @fb.com> Date: Thursday, November 21, 2019 at 3:32 PM To: Cc: @fb.com>, @fb.com>, @fb.com>, @fb.com>, Andrew Bocking @fb.com>, Guillermo Spiller @fb.com>, Denise Moreno @fb.com>, @fb.com> @fb.com>, @fb.com> Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Sorry for splitting thread. Was sending from an airplane and I guess my email didn't go through until this morning. Pasting on top of Is much more detailed response to keep everything in the same place. Yes, I believe the primary way you clear a checkpoint is by providing ID. HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003186 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 From: Andrew Bocking @fb.com> Date: Thursday, November 21, 2019 at 10:22 AM To: @fb.com" @fb.com>, Cc: @fb.com>, @fb.com> @fb.com>, @fb.com> @fb.com>, Denise Moreno @fb.com>, Page 5 of 15 @fb.com>, Guillermo Spiller Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Is an ID required in all/most cases? Just wondering why clear rates are so low. From: @fb.com> Sent: Thursday, November 21, 2019 7:20:54 AM To: Andrew Bocking @fb.com>; Cc: @fb.com>; @fb.com> @fb.com>; @fb.com> @fb.com>, @fb.com>, @fb.com>; Guillermo Spiller @fb.com>; Denise Moreno @fb.com>; @fb.com>; @fb.com>; Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation (new) #6 - Who can provide more insights on the actual checkpoint experience? Is it awful for people to get through if they did this accidentally? CO does a quick visual inspection to see if it looks like it's obviously a mistake-described here. After that they are checkpointed and I believe generally have to provide ID to get out. From: @fb.com> Date: Wednesday, November 20, 2019 at 11:38 PM To: Andrew Bocking @fb.com>, Guillermo Spiller @fb.com>, @fb.com>, Denise Moreno @fb.com>, @fb.com> Cc: @fb.com>, @fb.com>, @fb.com" @fb.com> Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Great - we'll set up 15 mins for this group to discuss live. On #6 @fb.com>, @fb.com>, The best estimate for checkpoint pass through rate we have is 7% based on community reported u13 checkpoint (current state) - that's what @ used for MAP impact calcs. The flows are below, and Integrity) - pls chime in, if anything's missing. (who runs this on www checkpoint HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003187 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 Please Verify Your information Cnty Bapand AB As You can see this contact form because you are using the intermel wol. Please make sure that logged out users can see the form as was by tesang property. The current visibility satings on the fom 18: CHECKPOINT Your sxxxxutt has been baked because we need to confirm your age. Please complate the form below withs 28 days to regen apuess to your account, & you don't conform your age within 28 days, you want wit Gelsted. Please keep in mind that you won't be able to access your account without completing vis step. Please providis a photo as seans of an 10 that contiene your age. The D misst made the inhemmation d the account. Once we nonfirm your age, we's detete your from our servers. Learn more about wary we require & and the fileen types of D we accept below. Submitting ID What types of ID does Facebook accept? How do I upload my ID to Facebook? Why am I being asked to upload an ID to Facebook? What happens to my ID after I send it to Facebook? Choose Files No Me chut We may wocrypt and store your ID My up to one year in tripnes and y De. Your will be stored securely and will not be visible to anyone on Facebook # you don't want Panstrouk to use your 10 impressed syntesse for detecting the On, you can 30 days of sexmission or when you surred inde option off Vist the Help Center to kem more stout what heppens to your after you send it to ve Mobile checkpoint Page 6 of 15 HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003188 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 Please Verify Your Information Your account has been locked because we need to confirm your age. Please complete the form below within 28 days to regain access to your account. If you don't confirm your age within 28 days, your account will be deleted. Please keep in mind that you won't be able to access your account without completing this step. First name Ex: John Last name Ex: Smith Date of birth 2019 January 3 Please provide a photo or scan of an ID that confirms your age. The ID must match the information listed on the account. Once we Please provide a photo or scan of an ID that confirms your age. The ID must match the information listed on the account. Once we confirm your age, we'll delete your ID from our servers. Learn more about why we require ID and the different types of ID we accept below. Submitting ID What types of ID does Facebook accept? How do I upload my ID to Facebook? Why am I being asked to upload an ID to Facebook? What happens to my ID after I send it to Facebook? What happens to my ID after I send it to Facebook? Your ID(s) Saved as JPEGs, if possible. You may attach up to 3 files. Choose Files No file chosen We may encrypt and store your ID for up to one year to improve our automated systems for detecting fake IDs. Your ID will be stored securely and will not be visible to anyone on Facebook. If you don't want Facebook to use your ID to improve our automated systems for detecting fake IDs, you can adjust your Identity Confirmation Settings. If you turn this option off, the copy of your ID will be deleted within 30 days of submission or when you turned this option off. Visit the Help Center to learn more about what happens to your ID after you send it to us. From: Andrew Bocking @fb.com> Date: Wednesday, November 20, 2019 at 5:37 PM To: HIGHLY CONFIDENTIAL (COMPETITOR) @fb.com>, Guillermo Spiller @fb.com>, Page 7 of 15 ΜΕΤΑ3047MDL-287-00003189 Cc: Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 @fb.com>, Denise Moreno @fb.com>, @fb.com>, @fb.com>, @fb.com>, @fb.com> Page 8 of 15 @fb.com> @fb.com>, Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Thanks - super helpful! For #4 - @ do we not have any estimates given the comparison to WWW? For #5 - Based on answer to #4, would be good to know @ doing short term? if there's anything else we should consider (new) #6 - Who can provide more insights on the actual checkpoint experience? Is it awful for people to get through if they did this accidentally? If easier we can also discuss live for 15min in the next 2 days. I'd personally rather just get to a good conclusion here on making sure we don't have a bunch of accidental checkpoints and then rollout this change Globally. Andrew From: @fb.com> Date: Wednesday, November 20, 2019 at 5:05 PM To: Andrew Bocking @fb.com>, Guillermo Spiller @fb.com>, @fb.com>, Denise Moreno @fb.com>, Cc: @fb.com>, @fb.com>, @fb.com>, @fb.com> @fb.com> @fb.com>, Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Thanks so much for your quick reactions Andrew! Pls see the responses in line in green below. Happy to set up time for this group to discuss live too. From: Andrew Bocking @fb.com> Date: Wednesday, November 20, 2019 at 4:43 PM To: Cc: @fb.com>, Guillermo Spiller @fb.com>, @fb.com>, Denise Moreno @fb.com>, @fb.com> @fb.com>, @fb.com>, @fb.com>, @fb.com>, @fb.com> Subject: Re: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Hey +@Guillermo @ @Denise to review as well. Thanks for the summary! Questions that may be tough to align on via email: HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003190 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 Page 9 of 15 1. How quickly would this need to ship in US? FYI we're at risk for negative MAP growth in Q4 in US&CA region due to other Integrity classifier launches in September. It's an ongoing bleeding, but there's no specific target date - it's just as soon as possible. And thank you, super helpful perspective. 2. Why are we planning to limit to US in this proposal? The highest legal risk is in the US given COPPA and FTC. The idea was to strike middle ground between mitigating legal risk asap and containing MAP Impact. 3. When does a decision need to be made + when do we need to ship? No specific date for either, but asap for both. 4. Can you better explain the "checkbox" that's on WWW but not on mobile? Is that what triggers the legal requirement for enforcement? I'm unclear on what this checkbox means here... and how it fits into the calculation for the impact to MAP/yr. The checkbox is the extra Ul friction to make sure people don't accidentally change their age to u13. Today, on www you have 2 steps (1.select your DoB 2. Confirm your age via the checkbox), while on mobile it's just 1 step (select your DoB). The proposed Ul change is to add the 2nd step on mobile as well. The overall MAP impact is likely to go down with the introduction of the 2nd step on mobile as it will prevent more people from accidentally changing their DoB to u13 - but we don't know by how much. 5. Why do we think it will take till Q1, 2020 to do anything to make sure people don't do this by accident you said we had ideas here? The 2ns Ul step - the checkbox on mobile and proposed for the immediate launch. Q1 was a high level estimate of how and get stuck?@ what was long it'd take to test the impact of other options (eg moving DoB change setting to another place). Thanks, Andrew From: @fb.com> Date: Wednesday, November 20, 2019 at 4:03 PM To: Andrew Bocking Cc: @fb.com>, @fb.com> @fb.com> @fb.com>, @fb.com>, @fb.com>, @fb.com>, Subject: [AC Priv] Age enforcement - proposed fix to changing DoB on Profile escalation Hi Andrew we would love to get your reaction to our recommended approach to fixing the issue with the profile DoB change flow on FB. The summary is below, the details are here. Thank you so much! Context Currently on FB, when a user attempts to change their age to under 13, a checkbox to confirm the age is shown on www (not on mobile), an error is generated, and the action is logged in the table "edit_birthday" (userid, new age, old age, and the error message are stored for 35 days). No enforcement action is taken. Checkpointing these users could result in ~126k/year in the US (~3.4M/year globally) MAP impact. Proposed Solution 1. Adjust mobile DoB change flow by adding a checkbox to confirm you age after DoB change attempt on mobile (note: www already has the checkbox) and launch it globally now HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003191 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 Page 10 of 15 2. Send to checkpoint those confirming their age is u13 in the US now estimated MAP impact 664/day or 126k/year 3. Test flow options (Profile team), roll out best flow and checkpoint to RoW in Q1'20 Current www flow (has checkbox, no checkpoint) Error whats updating date of birth Under 18 Vorwoman anlee: birthday that indicator your are under 3 years old Please content is far sesistance. Current mobile flow (no checkbox, no checkpoint) HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003192 Case 4:22-md-03047-YGR 10:44 4 > Edit Profile BIRTHDAY Birthday August 19 Birth Year 2014 Document 3007-1 Filed 05/01/26 10:44 4 > Edit Profile You cannot select a birthday that indicates you are under 13 years old. Please contact us for assistance. Birthday August 19 Note: you can only change your birthday a limited number of Birth Year 1992 times. Female Male Custom GENDER Female Male Custom INTERESTED S INTERESTED IN Women Women Men LANGUAGES Men LANGUAGES Proposed mobile flow (add checkbox globally, checkpoint routing TBD) Page 11 of 15 HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003193 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 Page 12 of 15 HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003194 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 m.svcscm.4233.od.facebook.com/ iPhone 5/SE▾ 320 AVOHIHIS X Edit profile Birthday 1 August Birth Year 1981 I confirm my age is 38. Edit profile Page 13 of 15 m.svcscm.4233.od.facebook.com/ 100%▼ Phone 5/SE▾ X Edit profile 100%▼ Please confirm your date of birth by ticking the box above. BIRTHDAY Birthday 1 August Birth Year 1980 Note: you can only change your birthday a limited number of times. GENDER GENDER Female Male Female Male Custom INTERESTED IN Custom HIGHLY CONFIDENTIAL (COMPETITOR) ΜΕΤΑ3047MDL-287-00003195 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 + Edit profile m.svcscm.4233.od.facebook.com X 100%▼ Edit profile Please confirm your date of birth by licking the box above. BIRTHDAY Birthday 1 August Birth Year 1982 I confirm my age is 37. Note: you can only change your birthday a limited number of times. GENDER Female Male Page 14 of 15 Note: There are further optimizations that could add friction to the DoB change process. Testing those would be part of Profile redesign, which is in progress, and in the Profile team's scope. Decision options (B recommended) Options Option A Description Launch checkpoint globally now MAP impact estimated 3.4M/year (18k/day) 2 3 Preys یک Cons Consistency Fastest compliance fix Min additional resource investment Highest immediate growth hit Launch checkpoint in US now, test/adjust the flow and roll out checkpoint globally in Q1'20 126K/year in US (664/day), TBD ROW Contained immediate growth impact Potential for slowdown Option C Test/adjust the flow, launch checkpoint globally in Q1'20 TBD, aim for <3.4M/year globally Potential for lowest MAP impact -Consistency No immediate compliance fix Highest additional resource investment Potential for slowdown 5 In favor "Could live with" Against Policy, Legal (TBC) Profile Integrity is fine with any option. HIGHLY CONFIDENTIAL (COMPETITOR) Legal (TBC), Profile Profile Policy, Legal (TBC) ΜΕΤΑ3047MDL-287-00003196 Case 4:22-md-03047-YGR Document 3007-1 Filed 05/01/26 All Custodians All Paths ΜΕΤΑ3047MDL-287-00003183 Bocking_Andrew; Metadata /Bocking_Andrew/Top of Personal Folders/Inbox Confidentiality Date Sent From HIGHLY CONFIDENTIAL (COMPETITOR) 02/10/2020 9:45 pm @fb.com> Primary Date 02/10/2020 9:45 pm To Page 15 of 15 @fb.c Bocking om>; @fb.co @fb.com piller TODIO.com>; fb.com>; Denise Moreno @fb.com> @fb.com>; @rb.com>; @tb.com> SEMANTIC SEMANTIC SEMANTIC SEMANTIC SEMANTIC DOC TYP E_ALIAS SEMANTIC