<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Gabe Cunningham on Medium]]></title>
        <description><![CDATA[Stories by Gabe Cunningham on Medium]]></description>
        <link>https://medium.com/@gabecunn?source=rss-dcf5ea44cc58------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WC28ZxDlnrUx55peAXxO8Q.jpeg</url>
            <title>Stories by Gabe Cunningham on Medium</title>
            <link>https://medium.com/@gabecunn?source=rss-dcf5ea44cc58------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:16:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gabecunn/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Welcoming Cindy Heredia to Fontinalis as a Summer Associate]]></title>
            <link>https://medium.com/fontinalis-partners-perspectives/welcoming-cindy-heredia-to-fontinalis-as-a-summer-associate-3636bd1fd112?source=rss-dcf5ea44cc58------2</link>
            <guid isPermaLink="false">https://medium.com/p/3636bd1fd112</guid>
            <dc:creator><![CDATA[Gabe Cunningham]]></dc:creator>
            <pubDate>Mon, 13 Jun 2022 19:02:28 GMT</pubDate>
            <atom:updated>2022-06-13T19:02:28.076Z</atom:updated>
            <content:encoded><![CDATA[<p>Please join us in welcoming <a href="https://fontinalis.com/team/#cindy-heredia">Cindy Heredia</a>, who recently joined Fontinalis as a Summer Associate out of Boston.</p><p>Cindy currently leads MIT’s Driverless team (!) and is also entering the second year of her MBA program at MIT Sloan School of Management. She did a pre-MBA internship on TuSimple’s Corporate Development team and also served on the board of TransitMatters, a public transit advocacy organization. After graduating with a bachelor’s degree in Economics from Mount Holyoke College, Cindy launched her investment career at MFS covering public automotive, industrial, and mobility technology companies.</p><p>Beyond the breadth of these professional accomplishments in mobility, what also really resonated with the Fontinalis team is Cindy’s passion about the fundamental connection between mobility and greater access to employment, education, and opportunity.</p><p>We are lucky to have such a tremendous rising star in mobility join us for the summer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*N49ageJYHqpd7dA3LgYdlA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3636bd1fd112" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fontinalis-partners-perspectives/welcoming-cindy-heredia-to-fontinalis-as-a-summer-associate-3636bd1fd112">Welcoming Cindy Heredia to Fontinalis as a Summer Associate</a> was originally published in <a href="https://medium.com/fontinalis-partners-perspectives">The Next Mobility Leap</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome Amy Dai, Fontinalis’ Next Associate!]]></title>
            <link>https://medium.com/fontinalis-partners-perspectives/welcome-amy-dai-fontinalis-next-associate-a878c3395a67?source=rss-dcf5ea44cc58------2</link>
            <guid isPermaLink="false">https://medium.com/p/a878c3395a67</guid>
            <dc:creator><![CDATA[Gabe Cunningham]]></dc:creator>
            <pubDate>Tue, 10 May 2022 18:19:24 GMT</pubDate>
            <atom:updated>2022-05-10T18:30:21.359Z</atom:updated>
            <content:encoded><![CDATA[<p>We are thrilled to announce the most recent addition to the Fontinalis team, <a href="https://fontinalis.com/team/#amy-dai">Amy Dai</a>, who will be joining the firm out of Boston as an Associate.</p><p>Amy has deep roots in sustainability and impact, most recently working as an investor at Builders Vision family office and previous principal investing experience in renewable energy infrastructure at Macquarie’s Green Investment Group. She has a strong creative streak as well, having spent time as an Imagineer in R&amp;D at Walt Disney and majoring in Business Administration &amp; Cinematic Arts at University of Southern California (USC). She even has been a longtime Mobility Matters reader and spent a summer at Volvo Cars Tech Fund.</p><p>As the mobility world increasingly intersects with major sustainability shifts that need to occur in the next decade and beyond, Amy will play a critical role in advising our portfolio companies and shaping our investment strategy.</p><p>We saw firsthand through the interview process Amy’s perceptive investment judgment, passion for impact, and empathy for founders. We look forward to you meeting her!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cdkzb3z5RTusnYRFJ_fKNQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a878c3395a67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fontinalis-partners-perspectives/welcome-amy-dai-fontinalis-next-associate-a878c3395a67">Welcome Amy Dai, Fontinalis’ Next Associate!</a> was originally published in <a href="https://medium.com/fontinalis-partners-perspectives">The Next Mobility Leap</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fontinalis is hiring an Associate!]]></title>
            <link>https://medium.com/fontinalis-partners-perspectives/fontinalis-is-hiring-an-associate-b2f904011988?source=rss-dcf5ea44cc58------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2f904011988</guid>
            <dc:creator><![CDATA[Gabe Cunningham]]></dc:creator>
            <pubDate>Thu, 17 Feb 2022 20:16:54 GMT</pubDate>
            <atom:updated>2022-02-17T20:16:54.471Z</atom:updated>
            <content:encoded><![CDATA[<p>Fontinalis Partners is hiring an <strong>Associate, </strong>who will be an integral part of our investment team. The position will be based in either Boston or Detroit.</p><p><strong>About Fontinalis: </strong>Fontinalis is an early-stage venture capital firm broadly focused on “mobility” (efficient movement of all forms). Our investment focus also includes a wide range of “enabling technologies” with major applications in mobility. Fontinalis has been particularly active in themes such as electrification, autonomous vehicles, supply chain and logistics, sensors, semiconductors, rideshare/delivery, robotics, insurtech, space, and additive manufacturing. We are constantly looking to identify what new areas of technology are coming “around the curve” with big implications for the mobility sector.</p><p><strong>Key Responsibilities: </strong>We are looking for an Associate who is scrappy, hungry, curious, and appreciates that founders go on a crazy rollercoaster ride, willing their companies into existence. As venture capital investors we are there to support them on this journey. As an Associate you will be on the front lines sourcing opportunities, developing hunches and investment theses as we try to identify founders building iconic companies as early as possible, managing our dealflow pipeline, diligencing investments, speaking with founders (sometimes when the “company” is just an idea on a napkin), and supporting portfolio companies with hiring / customer discovery / go-to-market strategy. You will also update quarterly/annual investor reports, conduct valuation and cap table analyses, and prepare investment memos.</p><p><strong>General Requirements: </strong>Applicants should have 1–4 years of full-time work experience, be comfortable in Excel, be able to communicate with empathy, clarity, and decisiveness, and have a passion for the impact that technology can have on the way the world moves. We imagine this position could be filled by a variety of backgrounds (including folks who are founders / product leads / engineers / investors / investment bankers / management consultants / startup operators / etc).</p><p><strong>Impact:</strong> Former Associates / Investors at Fontinalis have gone on to start a seed stage venture firm, work as a product manager in web3, co-found a micro-mobility startup, work in product management at a large social media consumer internet company, and been promoted to Principals at the firm. We think this role is an exciting launching pad into the world of technology and startups for highly motivated individuals.</p><p>Fontinalis is an equal opportunity employer and we actively encourage candidates from all backgrounds and life experiences to apply.</p><p><strong>To Apply:</strong> Please email <a href="/service/mailto:hiring@fontinalis.com">hiring@fontinalis.com</a> with the subject line ‘Associate Application — Your Name’ by <strong>5pm EST on 3/16/2022</strong>.</p><p>Please answer the following questions in your email:</p><ol><li>What is an area of technology that Fontinalis has not invested in that you believe has significant potential to impact mobility? (200–400 words)</li><li>What should we know about you? (200–400 words)</li><li>Link to your LinkedIn and/or any other relevant links.</li><li>Please attach a resume.</li><li>Indicate preference for Boston/Detroit/Either.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FEc3w6yEOUIBYxo1HKXbHA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2f904011988" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fontinalis-partners-perspectives/fontinalis-is-hiring-an-associate-b2f904011988">Fontinalis is hiring an Associate!</a> was originally published in <a href="https://medium.com/fontinalis-partners-perspectives">The Next Mobility Leap</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bringing Privacy Research to Open Data: What Cities Should Know]]></title>
            <link>https://medium.com/@gabecunn/bringing-privacy-research-to-open-data-what-cities-should-know-81d2470927?source=rss-dcf5ea44cc58------2</link>
            <guid isPermaLink="false">https://medium.com/p/81d2470927</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[smart-cities]]></category>
            <category><![CDATA[open-data]]></category>
            <dc:creator><![CDATA[Gabe Cunningham]]></dc:creator>
            <pubDate>Fri, 22 Jan 2016 19:53:58 GMT</pubDate>
            <atom:updated>2016-01-22T19:58:16.609Z</atom:updated>
            <content:encoded><![CDATA[<p>Launching a municipal open data portal requires careful navigation of numerous privacy laws and sensitive data sets. Yet today cities lack accessible best practices and as a result have had to deal with privacy issues independently, in a disjointed and non-standardized manner. Without best practices to turn to, multiple major cities have accidentally released non-public information or faced pressure for unwittingly revealing sensitive citizen information.</p><p>City officials are also largely disconnected from de-identification research by leading privacy computer scientists, leaving open data groups unable to fully assess the risks and rewards of disclosure. Thus, while most open data events include a statement along the lines of “it is essential that we address privacy considerations,” the mechanics of doing so are still largely unexplored.</p><h4><strong>The privacy concerns of poor open data stewardship are not merely theoretical.</strong></h4><p>Cities from Minneapolis to New York City have exposed non-public information as a result of imperfect privacy practices or have been surprised by the detailed inferences enabled by open data. Additionally, a <a href="http://www.pewinternet.org/2015/04/21/open-government-data/">2015 Pew Research study</a> revealed varying levels of comfort with government-enabled online access to restaurant health and safety records (82%), criminal records of individual citizens (62%), real estate transactions (54%), and mortgages of individual homeowners (22%).</p><p><strong>Today, the intersection of open data and privacy is characterized by a few key challenges:</strong></p><h3><strong>1) Removing identifying information from datasets can be difficult:</strong></h3><p>The primary approach to data privacy for cities, de-identification, involves selecting identifiers that could be used to re-identify individuals and then removing this data or generalizing it (ie. redacting the last 2 digits of the street address, or modifying the date of birth to only show the birth year). This process may appear simple at first glance, yet successful de-identification requires careful consideration of each data record and format. While cities are typically able to identify blatant personally identifiable information (PII) such as names, they can fail to adequately address other less apparent identifiers. The mistakes detailed below, where sensitive information was accidentally released as a result of latent identifiers, highlight the challenging mechanics of privacy protection:</p><ul><li><strong>Unique Identifiers:</strong> Transport for London’s bike share data <a href="http://qz.com/199209/londons-bike-share-program-unwittingly-revealed-its-cyclists-movements-for-the-world-to-see/">included customer identifier numbers</a>, enabling a researcher to trace the movement of individual users.</li><li><strong>Incomplete Redaction: </strong>Minneapolis f<a href="http://www.citypages.com/news/minneapolis-accidently-published-private-information-on-sexual-misconduct-cases-6543532">ailed to redact the addresses of 1,300 locations of sexual assault</a> in a crime open data release.</li><li><strong>Text Fields:</strong> the IRS released Form 990 returns that <a href="http://www.nextgov.com/cybersecurity/2013/07/irs-mistakenly-exposed-thousands-social-security-numbers/66230/">included social security numbers</a>.</li><li><strong>Reverse Geocoding:</strong> Four major cities released <a href="https://medium.com/@gabecunn/493f88e725ba">crime data with address-based (X,Y) coordinates</a>, thus revealing the location of sensitive crime incidents including sexual assaults and rapes.</li></ul><h3><strong>2) “Scrubbing” datasets of identifying information does not guarantee anonymity</strong></h3><p>One fascinating example of the limits of de-identification is the New York City taxi data. This data set received a great deal of attention when <a href="https://medium.com/@vijayp/of-taxis-and-rainbows-f6bc289679a1#.2z0yphk0b">Vijay Pandurangan found</a> that the driver’s license number and taxi number were improperly anonymized. However, <strong>even if the identifiers had been removed, the dataset would have still leaked sensitive information</strong>: due to the time-stamped pick-up and drop-off location data, a researcher was able to demonstrate that <a href="http://research.neustar.biz/author/atockar/">the dataset could be used to track the destination (and tipping habits) of celebrities and map frequent trips to a Hell’s Kitchen gentlemen’s club</a>. Other high-profile examples of datasets being re-identified without identifiers include <a href="http://www.cs.pomona.edu/~sara/classes/cs190-fall12/k-anonymity.pdf">health records</a> using a combination of sex, zip code, and birth date, <a href="https://w2.eff.org/Privacy/AOL/exhibit_d.pdf">web searches</a> using unique queries, and <a href="http://arxiv.org/abs/cs/0610105">Netflix rating data</a> using pubic IMDB ratings. Location information is particularly sensitive, as <a href="http://www.nature.com/articles/srep01376?ial=1">Yves-Alexandre de Montjoye et al. found </a>that 95% of mobility traces are re-identifiable given four time-stamped locations. Given the right secondary information, it can be possible to identify individuals in a dataset even when all explicit identifiers have been removed.</p><blockquote>There is no known effective method to anonymize location data, and no evidence that it’s meaningfully achievable. (<a href="http://randomwalker.info/publications/no-silver-bullet-de-identification.pdf">Arvind Naranayan &amp; Ed Felten</a>)</blockquote><blockquote>Better yet, we need a new word for privacy-motivated data manipulation that connotes only effort, not success. I propose “scrub.” Unlike “anonymize” or “deidentify,” it conjures only effort. (<a href="http://paulohm.com/classes/techpriv13/reading/wednesday/OhmBrokenPromisesofPrivacy.pdf">Paul Ohm</a>)</blockquote><blockquote>Data privacy is a hard problem. Data custodians face a choice between roughly three alternatives: sticking with the old habit of de-identification and hoping for the best; turning to emerging technologies like differential privacy that involve some trade-offs in utility and convenience; and using legal agreements to limit the flow and use of sensitive data. These solutions aren’t fully satisfactory, either individually or in combination, nor is any one approach the best in all circumstances. (<a href="http://randomwalker.info/publications/no-silver-bullet-de-identification.pdf">Arvind Naranayan &amp; Ed Felten</a>)</blockquote><blockquote>The best way to move data release policy past the alleged failures of anonymization is to focus on the process of minimizing risk, not preventing harm. (<a href="http://lsr.nellco.org/cgi/viewcontent.cgi?article=1534&amp;context=nyu_plltwp">Ira Rubenstein &amp; Woodrow Hartzog</a>)</blockquote><p>It is important that the open data community is at least aware of the inconvenient truths about the limits of PII-based anonymization. Rather than living in fear about the next privacy mishap they can take ownership of the risks, rewards, and privacy policy choices inherent in their stewardship of public data. At the very least, it would be helpful for cities to coalesce around certain privacy standards for common data types. These type of efforts could lower the hurdles to publishing data, ensure that small cities trying to launch open data portals don’t have to reinvent the wheel for their own privacy management processes, and enable valuable cross-city comparisons.</p><h3><strong>3) Smart Cities will generate more data and intensify the need for city governments to think about privacy:</strong></h3><p>With the proliferation of Smart City sensors, cities will hold increasing types and volumes of data. Will these data types be public records? Will they be released online via open data portals? Future cities will possess sensitive datasets that also present tremendous value for private companies, citizens, researchers, and governments. City officials will have to determine how to maximize the value in their datasets while avoiding damaging privacy blow-ups. We can start by bridging the gap between privacy researchers and open data practitioners to develop best practices in open data privacy management.</p><p>Interested in the intersection of open data, privacy, and smart cities? Get in touch — I’d love to hear your thoughts!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81d2470927" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crime Open Data & Reverse Geocoding]]></title>
            <link>https://medium.com/@gabecunn/crime-open-data-reverse-geocoding-493f88e725ba?source=rss-dcf5ea44cc58------2</link>
            <guid isPermaLink="false">https://medium.com/p/493f88e725ba</guid>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[smart-cities]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Gabe Cunningham]]></dc:creator>
            <pubDate>Fri, 22 Jan 2016 19:53:32 GMT</pubDate>
            <atom:updated>2016-01-22T19:58:11.371Z</atom:updated>
            <content:encoded><![CDATA[<h4>Crime Data is High Value But Also Sensitive</h4><p>Crime open data is often the most-downloaded dataset in municipal open data portals, with numerous cities recording tens of thousands of downloads. Public safety data provides critical information about communities for citizens and was rated the #1 very important data category in the <a href="http://discover.socrata.com/rs/socrata/images/%5BSocrata%5D%202014%20Open%20Data%20Benchmark%20Report.pdf">2014 Socrata Open Data Benchmark study</a>. At the same time, crime datasets include sensitive information about victims, including the location of reported incidents such as sexual assault, rape, and juvenile crimes. Given the sensitivity of these crimes types, state laws often shield the personally identifiable information (PII) of victims (including addresses) from public disclosure.</p><h4>Cities Can Accidentally ‘Leak’ PII via Reverse Geocoding</h4><p>I found that four major U.S. cities accidentally ‘leaked’ the addresses of sensitive crime incidents in 2013–2014. These cities redacted the text addresses of crime incidents but still included (X,Y) coordinates that were based on the original addresses, thus accidentally ‘leaking’ the addresses of crime victims. Most other cities had recognized the sensitivity of the coordinates and instead reported the same (X,Y) coordinates for each incident within a 100-block. <strong>I worked with each of the four cities to remove the address-based coordinates from their datasets for sensitive crimes, but the fact that this occurred in a few major cities is indicative of a broader need for real engagement with the mechanics of privacy for open data.</strong></p><h4>How It Happened</h4><p>Most cities redact the text addresses of all incidents in crime open data (i.e. 1234 Alice Ave becomes 12XX Alice Ave) due to the sensitive nature of the data. Redaction grants public access to the general location of crimes without indicating the exact address. I discovered that four cities were accidentally exposing identifying crime incident records when I downloaded the crime open data, sorted the crime data by the 100-block field, and then noticed that there were a variety of (X,Y) coordinates associated with the same 100-block. I notified four cities about this issue based on the characteristics of their data, and each city addressed the situation by shifting to non-address-based coordinates.</p><h3><strong>If the location field is based on the original addresses, the city can accidentally leak the addresses of crime victims.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*RndULGYBwKV3gELfMX2ZqA.png" /></figure><h4>Reverse Geocoding</h4><p>Address-based coordinates are re-identifiable due to <a href="https://en.wikipedia.org/wiki/Reverse_geocoding"><strong>reverse geocoding</strong></a>, which involves taking spatial coordinates such as longitude and latitude and revealing the associated street address. This process is called reverse geocoding because this is the opposite of traditional geocoding, which takes an address and returns a unique geospatial location. Rather than reporting address-based coordinates for sensitive incidents, cities can instead use hundred-block coordinates (or some other aggregated location), geomask coordinates, or remove the coordinates entirely.</p><h4>The Road Forward</h4><p>Distinguishing between address-based coordinates and hundred-block coordinates may seem to be an issue of semantics, but it is actually necessary for responsible data stewardship. Open data privacy remains a topic that is often discussed, but there have been limited efforts to bridge the gap between municipal open data decision-makers and leading privacy researchers. I hope that this incident (and others I will discuss in a <a href="https://medium.com/@gabecunn/81d2470927">follow-up post</a>) highlights the need for improved best practices in open data privacy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=493f88e725ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>