12 min read
NOTE: This is a long piece. I won't be (too) offended if you skip right to the conclusion. END NOTE
When people write about the story of inBloom, they generally note that Louisiana was the first state to stop using inBloom. The story is usually told with the exit as Louisiana's decision, made in response to parental outrage over data sharing.
The question of whether or not inBloom was storing Social Security numbers (SSNs) of students raised many initial questions, and the initial responses did little to address these concerns.
From looking at how inBloom's language around SSNs evolved over time, it seems like they started from a place of "we really don't want any SSNs" and ended up at "we won't store SSNs, period."
Shortly after the inBloom launch, I looked at the inBloom data model. This didn't tell us much, as it appeared that inBloom would defer to the student identifier supplied by the state, which may or may not be a SSN.
On April 1, 2013 - the day I wrote this post, inBloom's FAQ included the following language on SSNs:
inBloom discourages storing social security numbers in its data service, but legally school districts and state may record student social security numbers. inBloom prohibits storage of social security numbers in the data store unless agreed to by both inBloom and the state/district on a case-by-case basis.
As of https://www.inbloom.org/faq">June 6th, 2013, that language had been changed to read:
inBloom does not and will not accept social security numbers (SSNs) as unique student identifiers. No SSNs are currently in the data store. In the past, our policy has been to prohibit the use of SSNs as unique identifier unless the state or district applied for a waiver to that policy. No such waivers were ever issued, and going forward inBloom will prohibit the use of SSNs under any circumstances and will not offer waivers.
The current version of the inBloom FAQ includes no references to SSNs at all, and instead highlights that inBloom operates under FERPA.
It's both interesting and informative to track this evolution alongside a couple of letters from inBloom's CEO, Iwan Streichenberger. At the outset, however, I must highlight that neither of these letters are retrieved from the inBloom website. The first, undated letter, was sent out to inBloom partners in spring of 2013, and was retrieved from the Jefferson County, CO, Schools website. The second letter, dated June 17, 2013, was retrieved from Jason France's Crazy Crawfish blog. I'm attaching copies of both letters to this post in case the linked versions disappear. Both of these letters look real; both have been publicly available for months, and the authenticity of both letters has not been challenged, but in the interest of being excessively cautious I want to be clear about where I found these letters.
In the first undated letter - written to inBloom partners shortly after the public announcement that Louisiana was pausing data storage with inBloom on April 24th - Streichenberger provides some background information:
Louisiana was a Phase 2 state in the inBloom consortium, which means it was on a slower implementation track than Phase 1 states. A few months ago, the team in Louisiana saw an opportunity to move more quickly to use the shared services for some key initiatives.
We'll return to these "key initiatives" in Louisiana shortly. The letter continues:
The pause also supports Louisianaâs efforts to transition from using Social Security numbers (SSNs) to randomized student I.D. numbers, in keeping with inBloomâs requirements and with industry best practices. Our team has been working with Louisiana on this issue, and we look forward to continuing to support their efforts in this regard.
It's worth noting that, as highlighted in this letter written in 2013, Louisiana is still using SSNs to identify students. This is particularly problematic given that, in 2009, Louisiana was given a 4 million dollar federal grant to develop a statewide data system. Moreover, the terms of the program under which the grant was given explicitly require that all students have anonymized unique identifiers. Yet, despite this influx of federal money, Louisiana was still using SSNs for student identifiers.
The theme of SSNs being used as student identifiers is picked up in the second letter, written by Streichenberger to John White, the Louisiana state superintendent of education. In this letter, Streichenberger is informing White that inBloom will no longer work with Louisiana.
During the course of planning for implementation in Louisiana, the inBloom team engaged in discussions with state personnel regarding how the state might transition from the use of SSNs to randomized student I.D. numbers. As we worked through this issue and to support the state's Course Choice program, it came to inBloom's attention that Louisiana was nevertheless uploading student SSNs to its secure storage space on the inBloom system.
We acknowledge that discussions were held regarding whether Louisiana could receive a waiver in accordance with the language in the contract. As you know, however, that matter was discussed and rejected, and inBloom did not issue a waiver for Louisiana. Consistent with best practices and based on our recent experiences, we have since changed our policies to prohibit even a temporary waiver, so that no SSNs are uploaded to inBloom's system.
This excerpt highlights five key points:
-
Confirms Louisiana is using SSNs for student identifiers;
-
inBloom gave good advice: DON'T USE SSNs!
-
As discussed above, inBloom changed their SSN policy while working with Louisiana
-
Louisiana ignored inBloom's recommendations, and were fired as a result. The fact that inBloom needed to sever the relationship also calls into question White's claim (from April 2013) that data sharing with inBloom was paused.
-
inBloom was slated to be used used for Louisiana's Course Choice program.
The connection between Course Choice and inBloom is rarely explored in any detail. Later in this post, we'll look at this further. But before we get there, let's take a glance at what part of John White's world looked like in April 2013.

As of http://www.louisianacoursechoice.net/">April 5th, 2013, LouisianaCourseChoice.net is dead to the world. John White and Bobby Jindal are pushing choice as an option. Despite a May state Supreme Court ruling that the funding mechanisms for school choice aren't constitutional, White finds the money anyways. However, the Course Choice system - as it currently stands - uses social security numbers. Whether that's a peculiarity of the Course Choice system or of Louisiana's educational records - which have not yet transitioned to randomly generated IDs - is unclear, but time is running short, and the site needs to launch. If Course Choice isn't live in time to support students leaving public schools by August 2013, it will not be good. The Course Choice system needs the dataset, the Course Choice system needs to go live, so uploading data into the datastore while explicitly ignoring the privacy advice of one of your tech parters seems like a good idea - because hey - what are the Social Security numbers of all the kids in a state among friends?
The irony here is that it sounds like inBloom gave White sound advice, and White - for whatever reason - ignored it. Politically, the only palatable option White has is to claim that he pulled out of collaborating with inBloom because he listened to privacy concerns. Conversely, inBloom can't burn a client by publicly stating that the client ignored technical advice and uploaded sensitive student data, and that the client was fired as a result. This leaves us with the story that we have: that Louisiana started the exodus of inBloom partners nationwide.
However, the role the Louisiana Course Choice program and web site also merit attention. The reason that inBloom dumped White centered around the need for SSNs in the Course Choice site. It's completely unclear whether the site still uses student SSNs and provides them to course vendors or not. This points to the elephant in the room around state-level longitudinal data systems: it's currently a zero-sum game. There are a small number of options, and if a state isn't using one, it's using another. Course Choice went live with another system (likely delivered, supported, and possibly hosted by another vendor) serving data, with the same weak privacy practices. Because of the focus on inBloom, the systemic questions that would actually protect student data (starting with "Why are SSNs being used as identifiers in 2013?") remain unanswered.
Additionally, the Course Choice site contains a small text-based link in the top right corner of the site: "Created by Agilix." This press release from March 2, 2013 highlights the connections between Course Choice, Agilix, inBloom, and John White's vision of how they work together.
John White, Superintendent of Louisiana Schools, says, âBy connecting to IBDS (inBloom Data Standard), Agilix opens a lot of doors for our Course Choice product not only for registration but also for detailed analysis of student performance. We expect this will assist greatly in tracking and reporting results of Course Choice adoption to state authorities.â
If you follow education technology, you can see Agilix popping up in reform centers nationwide. Tom Vander Ark praises Buzz, an Agilix-developed system currently in use in Michigan's Education Achievement Authority. Not everybody is as excited about Buzz as Vander Ark, though. In a piece from Michigan Public Radio, State Representative Ellen Cogen Lipton describes conversations she had with students in schools using Buzz.
"They said, 'Buzz is a joke, it's not challenging, it's demeaning.' I asked them if they liked their school better now or before and they said, 'Before.' When I asked why, one student said, 'Look around this room. Do you see any books? I really miss my books,'" Cogen Lipton said.
We also see Agilix-developed software in use within KIPP schools. Agilix is also developing partnerships with textbook companies to market Common Core aligned products to districts and states.
The example of Agilix shows how companies can thrive in the current educational climate. Agilix has had a series of projects with entities that receive public money. In Louisiana, Agilix worked on a system to streamline registration for courses outside the public school system. In Michigan, Agilix worked with schools receiving public money to develop and beta test learning software.
This is all legal, but we need to recognize and call this out for what it is: a private entity received public money to bootstrap the development of a proprietary product that is then sold to public entities and paid for with yet more public money.
This Is Why It Doesn't Matter Whether Louisiana Left inBloom, or Vice Versa
With the focus on inBloom, we conveniently lose sight of the context within which these discussions occur. As noted in this post, Louisiana moved ahead without inBloom, but with the same ineffective data management strategies. Companies like Agilix capitalize on the opportunities within the educational landscape, and larger questions about data collection and privacy go unaddressed. Agilix highlights that it works well with Chromebooks. However, a school using Chromebooks puts student data into Google's ecosystem, and into the hands of any developers whose apps are used within that ecosystem - and no one is talking coherently about the rights of students with regards to their work living in these systems.
But taking another step back, current education policy ensures that we will always have a pool of schools that are deemed failing. The "solution" to these "failing" schools often involve experiments with school closure, staffing schools with less experienced educators like Teach For America recruits, firing principals, firing teachers, and experimenting with technology. One rationale frequently cited for this experimental churn in our most vulnerable schools is that conditions are so bad, that "we have to do something." However, it's worth asking whether the experimental churn fuels the problems it's intended to solve.
There is no denying, however, that school turnaround is good business. Because a "failing" school is defined as the lowest performing 5% as measured on standardized tests, it should surprise absolutely no one that businesses plans exist that depend on the manufactured need to "turn around" these failing schools.
Fortunately, Agilix (and companies like them) are here to help:
Compass Learning, Inc., Agilix Labs, Inc. and School Improvement Network announced today a joint effort to help improve the five percent of historically lowest-performing public schools in the state of Michigan.
This is why the names don't matter. inBloom, Agilix, Pearson, InfiniteCampus, Clever - if all of these organizations went away tomorrow, a new group would crop up to take their place because federal education policy creates the need for them. Federal education policy simultaneously defines a pool of vulnerable schools, and creates the conditions that allows these schools to be fodder for the latest technological or policy fad.
The problems with our conversations about student privacy mirror some of the problems of our conversations about education. Both sets of conversations position the student as an object to be observed, rather than as an informed agent making rational choices. Until we get our heads around the reality that students are the reason our education system exists - and back up that rhetoric by ensuring students have a controlling voice in the collection of, use of, and reflections on any data arising from their education - we'll continue to miss the point.
#inBloom, #EAA, #JohnWhite, #Agilix, #educationpolicy, #educationreform, #studentrights, #ProposalNotes