But the deeper colonial injustice is epistemic . When a community’s oral histories, local language documents, or indigenous knowledge are stored on Google Drive, they are ingested into servers overwhelmingly located in the Global North (Iowa, Belgium, Singapore—but owned by US entities). They become subject to US law (the Patriot Act, the CLOUD Act). They are scanned by models trained on English and Mandarin data. The metadata—who shared what with whom, at what time—is a goldmine for surveillance capitalism. The injustice is that the Global South subsidizes Google’s AI training with its data, pays for the bandwidth to upload it, and receives no dividend, no control, and no guarantee that the data won't be used to automate the very systems that marginalize them. You can delete a file from Google Drive. But "delete" is a euphemism. In Google's infrastructure, "delete" typically means "remove from user interface and mark for eventual garbage collection." Residual copies persist on backup tapes, disaster recovery systems, and forensic caches for months. Meanwhile, any file you have ever shared remains—because the recipient may have downloaded it, printed it, or re-shared it. Google does not and cannot claw back copies.
The injustice is preemptive, opaque, and unreviewable . There is no cross-examination, no right to present context, no human with discretion until after the damage is done. This is the digital equivalent of a police officer seizing your filing cabinet based on a secret tip from an unaccountable informant. Worse, because Google Drive is integrated with Gmail, Google Photos, and Chrome, a single flag can trigger a cascading "death by algorithm"—losing your email, your calendar, your phone’s backups, all because a single file’s hash matched a prohibited list. You are guilty until proven silent. Google Drive's promise is frictionless collaboration. Its reality is a new hierarchy of power. Consider the "Share" button. The owner of a file can grant "View," "Comment," or "Edit" access. But the owner can also, at any moment and for any reason, revoke that access. In a workplace, a manager can lock a junior employee out of a presentation minutes before a client meeting—not because of performance, but because of a petty dispute. In a family, a parent can delete a shared photo album as a punishment. In a political collective, a coordinator can erase the group's entire archive when they defect. injustice google drive
To fight these injustices is not to abandon cloud storage—that is impossible for most. It is to practice digital hygiene as resistance : end-to-end encryption before upload, using Drive as a transient shuttle rather than a permanent archive, diversifying storage across decentralized protocols (IPFS, Arweave), and demanding legal frameworks that recognize algorithmic acts as state action. The first step is to stop seeing Google Drive as a neutral folder in the sky. It is a contested territory. And the silent arbiters have already written the rules. Your move is to read them, then decide whether to play—or to build a different game entirely. But the deeper colonial injustice is epistemic
The injustice is that the right to erasure —a legal principle in the EU's GDPR—collides with the technical reality of distributed systems. You can ask Google to forget your file. Google can agree. But the person you shared it with last year, who saved a copy to their own Drive? They now own your data forever. The tool gave you the illusion of withdrawal without the mechanism. This is the injustice of the digital Panopticon: you can close your eyes, but the watchers keep their recordings. None of these injustices are accidents. They are the logical outcomes of a business model that profits from lock-in, scale, and data extraction. Google Drive is not a public utility; it is a landlord, a judge, a colonial administrator, and a forgetful god rolled into a blue-and-white icon. They are scanned by models trained on English
Injustice is often imagined as a spectacle: a gavel falling on the innocent, a line crossed by a tyrant, a resource hoarded while a neighbor starves. But in the 21st century, the most pervasive injustices are silent, procedural, and embedded in the architecture of our digital tools. Google Drive—a ubiquitous, seemingly benevolent utility for storage and collaboration—is a potent case study. Its injustices are not bugs; they are features of a system where ownership, access, and memory are leased, not granted. 1. The Injustice of Ephemeral Ownership (You Don't Own Your Files) When you save a file to your local hard drive, you possess a physical (if magnetic) artifact. When you upload that same file to Google Drive, you initiate a complex legal and technical transformation. According to Google's Terms of Service, you retain your intellectual property rights. However, by uploading, you grant Google a "worldwide, royalty-free, and non-exclusive license" to host, reproduce, distribute, modify, and publicly display your content for the purpose of operating, promoting, and improving their services.
The injustice is one of unilateral, irreversible power . Collaboration on Google Drive is not a partnership; it is a tenancy-at-will. The owner holds the deed. Everyone else holds a revocable pass. There is no "shared ownership" model, no smart contract for joint control, no escrow for critical files. The tool itself incentivizes a feudal structure: one lord, many vassals. The injustice deepens when that lord leaves a company or dies—their Drive content is often deleted after a grace period, taking collective knowledge with it. Google Drive offers 15 GB of free storage. That number seems generous until you realize it is shared across Drive, Gmail, and Google Photos. For a user in San Francisco with gigabit fiber, 15 GB is trivial. For a user in rural India or Nigeria, where connectivity is slow, intermittent, and expensive, that 15 GB represents a significant investment of time and data allowance to upload. Moreover, Google’s compression algorithms (e.g., for photos) degrade quality more aggressively for free tiers—a subtle tax on the poor.
The injustice here is one of latent expropriation . Your grandmother's scanned photos, your startup's financial model, your novel’s only draft—all become data inputs for Google's machine learning models. While anonymized, the boundary between "operating the service" (e.g., generating thumbnails, enabling OCR) and "improving the service" (e.g., training image recognition on your private wedding photos) is deliberately opaque. The injustice is not theft but structural dependency : you cannot opt out of this license without leaving the platform. In a world where collaboration expects Drive links, opting out is exile. Perhaps the most visceral injustice occurs when Google Drive’s automated content moderation systems flag a file as violating its "acceptable use policy." These systems are not courts; they are pattern-matching black boxes. A medical student sharing de-identified histology slides of fetal tissue. A historian storing Nazi-era propaganda for analysis. A parent backing up bath-time photos flagged for "sexual content." In each case, the user receives a terse notice: "This file violates our terms of service." Access is revoked. The account may be suspended. The appeal process is a form—often answered by an algorithm.