Connect with us

News

Amazon employees demand stoppage of facial recognition contract with law enforcement

Published

8 years ago

on

Amazon workers have penned a letter to Jeff Bezos calling on the CEO to immediately cancel the access of law enforcement agencies to its Rekognition facial recognition system. The employees’ letter comes on the heels of several Amazon shareholders who have also asked the e-commerce giant to stop selling Rekognition to the police.

As could be seen in the letter to the CEO, Amazon’s employees stated that they do not agree to have their work used for purposes that could target marginalized groups. The letter also cited the United States government’s practice of separating children away from their parents at the border as a key reason why Amazon should cancel its contract with law enforcement agencies. Amazon workers further called for the removal of Palantir, a data-mining company, from the client list of Amazon Web Services (AWS). Palantir, a company founded by Peter Thiel, currently has a contract with ICE and is actively involved in the agency’s deportation and detention programs. 

Rekognition is, at its core, an API for deep learning-based analysis to detect, track, and analyze people and objects in videos. In Amazon’s advertisement for the service on YouTube, the company could be seen promoting Rekognition’s facial tracking capabilities such as smart home monitoring, celebrity detection in videos, and more serious applications such as the recognition and tracking of persons of interest. An investigation conducted by the American Civil Liberties Union earlier this year determined that Amazon actively marketed Rekognition to law enforcement officials, citing the software’s advanced face tracking capabilities. 

The Amazon employees’ initiative against the company’s ties to law enforcement comes on the heels of similar protests in Microsoft and Google.  Earlier this year, Google was beset by a brief exodus of workers and employee protests after it was revealed that the company had aided the Pentagon in its AI-driven Project Maven initiative, which uses artificial intelligence to effectively analyze footage from military drones. While Google stated that the work it has done with the Pentagon was mundane, the company ultimately opted not to renew its Project Maven contract, while also announcing new ethics principles to govern its artificial intelligence work.

Advertisement

Microsoft also found itself in hot water last May after it was revealed that the company has a $19.4 million contract with the United States’ Immigration and Customs Enforcement (ICE). In a letter addressed to CEO Satya Nadella, Microsoft employees stated that they “refuse to be complicit” in ICE’s practice of marginalizing select ethnic groups and actively separating families. In a response to its employees’ protests, Microsoft noted that the company only provides non-surveillance services such as mail, calendar, messaging and document management to the government agency.

The Amazon workers’ full letter to Jeff Bezos could be read in full below.

Dear Jeff,

We are troubled by the recent report from the ACLU exposing our company’s practice of selling AWS Rekognition, a powerful facial recognition technology, to police departments and government agencies. We don’t have to wait to find out how these technologies will be used. We already know that in the midst of historic militarization of police, renewed targeting of Black activists, and the growth of a federal deportation force currently engaged in human rights abuses — this will be another powerful tool for the surveillance state, and ultimately serve to harm the most marginalized. We are not alone in this view: over 40 civil rights organizations signed an open letter in opposition to the governmental use of facial recognition, while over 150,000 individuals signed another petition delivered by the ACLU.

Advertisement

We also know that Palantir runs on AWS. And we know that ICE relies on Palantir to power its detention and deportation programs. Along with much of the world we watched in horror recently as U.S. authorities tore children away from their parents. Since April 19, 2018 the Department of Homeland Security has sent nearly 2,000 children to mass detention centers. This treatment goes against U.N. Refugee Agency guidelines that say children have the right to remain united with their parents, and that asylum-seekers have a legal right to claim asylum. In the face of this immoral U.S. policy, and the U.S.’s increasingly inhumane treatment of refugees and immigrants beyond this specific policy, we are deeply concerned that Amazon is implicated, providing infrastructure and services that enable ICE and DHS.

Technology like ours is playing an increasingly critical role across many sectors of society. What is clear to us is that our development and sales practices have yet to acknowledge the obligation that comes with this. Focusing solely on shareholder value is a race to the bottom, and one that we will not participate in.

We refuse to build the platform that powers ICE, and we refuse to contribute to tools that violate human rights.

As ethically concerned Amazonians, we demand a choice in what we build, and a say in how it is used. We learn from history, and we understand how IBM’s systems were employed in the 1940s to help Hitler. IBM did not take responsibility then, and by the time their role was understood, it was too late. We will not let that happen again. The time to act is now.

Advertisement

We call on you to:

  • Stop selling facial recognition services to law enforcement
  • Stop providing infrastructure to Palantir and any other Amazon partners who enable ICE.
  • Implement strong transparency and accountability measures, that include enumerating which law enforcement agencies and companies supporting law enforcement agencies are using Amazon services, and how.

Our company should not be in the surveillance business; we should not be in the policing business; we should not be in the business of supporting those who monitor and oppress marginalized populations.

Sincerely,

Amazonians

Here’s Amazon’s advertisement for Rekognition.

Advertisement

https://www.youtube.com/watch?v=SNONL4IecHE

Related Topics:

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

News

Tesla Cybercab gets crazy change as mass production begins

Tesla has officially kicked off mass production of its groundbreaking Cybercab robotaxi at Giga Texas, and the first units rolling off the line feature a striking transformation that’s turning heads across the EV community.

Published

3 hours ago

on

April 25, 2026

By

Credit: TechOperator | X

Tesla Cybercab has evidently received a pretty crazy change from an aesthetic standpoint, as the company has made the decision to offer an additional finish on the vehicle as mass production is starting.

Tesla has officially kicked off mass production of its groundbreaking Cybercab robotaxi at Giga Texas, and the first units rolling off the line feature a striking transformation that’s turning heads across the EV community.

VIN Zero—the very first production Cybercab—showcases a vibrant champagne gold exterior with a high-gloss finish, a dramatic departure from the flat, matte-wrapped prototypes that debuted at the 2024 “We, Robot” event.

This glossy sheen is a pretty big pivot from what was initially shown by Tesla. The company has maintained a pretty flat tone in terms of anything related to custom colors or finishes.

A specialized clear coat or process delivers the deep, reflective gloss without conventional painting. The result is a premium, mirror-like shine, and it looks pretty good, and gives the compact two-seater a more luxurious and futuristic presence than the subdued matte prototypes.

Photos shared by Tesla community members reveal VIN Zero in a showroom-like setting at Giga Texas, highlighting refined panel gaps, large aero wheel covers, and the signature no-steering-wheel, no-pedals interior optimized for full autonomy.

Advertisement

The open frunk in some images offers a glimpse of practical storage, while the overall build quality appears more polished than that of test mules.

This glossy evolution aligns with Tesla’s broader production ramp. After the first unit in February 2026, the company has shifted to volume manufacturing, with dozens of units already spotted in outbound lots. CEO Elon Musk and the team aim for hundreds per week, paving the way for unsupervised FSD robotaxi networks that could slash ride costs to pennies per mile.

The Cybercab holds Tesla’s grand ambitions of operating a full-service ride-hailing service without any drivers in its grasp. Tesla has yet to solve autonomy, but is well on its way, and although its timelines are usually a bit off, improvements often come through the Over-the-Air updates to the Full Self-Driving suite.

Advertisement
Continue Reading

News

Tesla confirms Cybercab with no steering wheel enters production

Published

7 hours ago

on

April 25, 2026

By

Tesla has confirmed today that its steering wheel-less and pedal-less Cybercab, the vehicle geared toward launching the company’s autonomous ride-hailing hopes, has officially entered production at its Giga Texas production facility outside of Austin.

The Cybercab is a sleek two-door, two-passenger coupe engineered from the ground up as an electric self-driving vehicle. It features no steering wheel or pedals, relying instead on Tesla’s advanced vision-only Full Self-Driving system powered by multiple cameras and artificial intelligence.

The minimalist cabin centers on a large display screen that serves as the primary interface for passengers, creating an open, futuristic space optimized for comfort during unsupervised rides. A compact 35-kilowatt-hour battery pack delivers exceptional efficiency at 5.5 miles per kilowatt-hour, providing an estimated 200-mile range.

Additional innovations include inductive charging compatibility and a lightweight design that enhances aerodynamics and performance.

Production at Giga Texas builds on earlier prototypes and initial units completed earlier in 2026. The facility, already a hub for Model Y and Cybertruck assembly, now ramps up dedicated lines for the Cybercab.

Advertisement

This shift to volume manufacturing reflects Tesla’s strategy to scale affordable autonomous vehicles rapidly.

By focusing on a dedicated platform rather than adapting existing models, the company aims to keep costs low while prioritizing safety and reliability through continuous AI improvements.

The Cybercab’s debut in production carries broad implications for urban mobility. As the cornerstone of Tesla’s Robotaxi network, it promises on-demand, driverless rides that could slash transportation expenses, reduce traffic accidents caused by human error, and lower emissions through its all-electric powertrain.

Accessibility features, such as space for service animals or assistive devices, further broaden its appeal. Regulators and cities worldwide will soon evaluate its deployment, but the vehicle’s design already addresses key hurdles in scaling unsupervised autonomy.

Advertisement

Challenges persist, including full regulatory clearance and building charging infrastructure. Yet this production launch signals momentum. With Cybercabs poised to roll out in increasing numbers, Tesla edges closer to a future where personal ownership meets shared fleets of intelligent vehicles.

The start of Cybercab production is more than just a new vehicle entering mass manufacturing for Tesla, as it’s a signal autonomy is near. Being developed without manual controls is such a massive sign by Tesla that it trusts its progress on Full Self-Driving.

While the development of that suite continues, Tesla is making a clear cut statement that it is prepared to get its fully autonomous vehicle out in public roads as it prepares to revolutionize passenger travel once and for all.

Advertisement
Continue Reading

News

Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much

There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.

Published

1 day ago

on

April 24, 2026

By

(Photo: Hector Perez/YouTube)

Tesla Full Self-Driving v14.3.2 began rolling out to some owners earlier this week, and there are some notable improvements that came with this update.

There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.

Overall operation saw a handful of slight improvements, especially with parking performance, which has been the most notable difference with the arrival of FSD v14.3. However, there are still some very notable shortcomings, most notably with region-specific signage and navigation.

Tesla Assisted Smart Summon (ASS) improvements

There are noticeable improvements to ASS operation, which has definitely been inconsistent in terms of performance. Tesla wrote in the release notes for v14.3.2:

Advertisement

“Unified the model between Actually Smart Summon, FSD, and Robotaxi for more capable and reliable behavior.”

As recently as this month, I used Summon with no success. It had pulled around the parking lot I was in incorrectly, leaving the range at which Summon can be operated and losing a signal while moving in the middle of the lot.

This caused me to sprint across the lot to retrieve the vehicle:

Unfortunately, Summon was not dependable or accurate enough to use regularly. It appears Tesla might have bridged the gap needed to make it an effective feature, as two tests in parking lots proved that Summon was more responsive and faster to navigate to the location chosen.

Advertisement

It also did so without hesitation, confidently, and at a comfortable speed. I was able to test it twice at different distances:

Advertisement

I plan to test this more thoroughly and regularly through the next few weeks, and I avoided using it in a congested parking lot initially because I have not had overwhelming success with Summon in the past. I wanted to set a low baseline for it to see if it could simply pull up to the place I pinned in the Tesla app.

It was two for two, which is a big improvement because I don’t think I ever had successful Summon attempts back-to-back. It just seems more confident than ever before.

Advertisement

New Disengagement Categories

This is a really good idea from Tesla, but there are some issues with it. The categories you can select are Critical, Comfort, Preference, and Other.

I think the reasons why people choose to take over would be a better way to prompt drivers, like, “Traveling Too Fast,” “Incorrect Maneuver,” “Navigation Error,” would be more beneficial.

I say this because it seems that how we each categorize things might be different. For example, I shared a video of an intervention because the car had navigated to an exit to a parking lot and put its left blinker on, despite left turns not being allowed there.

I disengaged and chose Critical as the reason; it’s not a comfort issue, it’s not a preference, it’s quite literally an illegal turn, and it’s also dangerous because it cuts across several lanes of traffic and is 180 degrees.

Advertisement

Some said I should not have labeled this as Critical, but that’s the description I best characterized the disengagement as.

Advertisement

Categorizing interventions is a good thing, but it’s kind of hard to determine how to label them correctly.

Inconsistency with Regional Traffic Patterns

Tesla Full Self-Driving is pretty inconsistent with how it handles regional or local traffic patterns and road rules. The most frequent example I like to use is that of the “Except Right Turn” stop sign, which has become a notorious sighting on our social media platforms.

In the initial rollout of v14.3, my Model Y successfully navigated through one of these stop signs with no issues. However, testing at two of these stop signs yesterday proved it is still not sure how to read signs and navigate through them properly.

Off camera, I approached another one of these signs and felt the car coming to a stop, so I nudged it forward with the accelerator pedal pressed.

This helped the car go through the sign without stopping, but I could feel the bucking of the vehicle as the car really wanted to stop.

Musk said on the earnings call earlier this week that unsupervised FSD would probably be available in some regions before others, including a state-to-state basis in the U.S.

Advertisement

“It’s difficult to release this like to everyone everywhere all at once because we do want to make sure that they’re not unique situations in a city that particularly complex intersection or — actually, they tend to be places where people get into accidents a lot because they’re just — perhaps there’s — and like I said, an unsafe intersection or bad road markings or a lot of weather challenges. So I think we would release unsupervised gradually to the customer fleet as we feel like a particular geography is confirmed to be safe.”

This could be one of those examples that Tesla just has to figure out.

Highway Operation

Full Self-Driving is already pretty good at routine roadway navigation, so I don’t have too much to report here.

However, I was happy with FSD’s decision-making at several points, including its choice not to pass a slightly slower car and remain in the right lane as we approached the off-ramp:

Advertisement

Better Maneuvering at Stop Signs

Many FSD users report some strange operations at stop signs, especially four-way intersections where there is a stop sign and a line on the road, and they’re not even with one another.

Advertisement

I experienced this quite frequently and found that FSD would actually double stop: once at the stop sign and again at the line.

This created some interesting scenarios for me and I had many cars honk at me when the second stop would happen. Other vehicles that had waved me on to proceed through the intersection would become frustrated at the second stop.

FSD seems to have worked through this particular maneuver:

FSD should know to go to the more appropriate location (whichever provides better visibility), and proceed when it is the car’s turn to move. The double stop really ruined the flow of traffic at times and generally caused some frustration from other drivers.

Advertisement
Continue Reading