"Bring Your Own Devices": A Cautionary Tale for Public Employees During Investigatory Searches
Bibliographic record
Abstract
The advancement of technology-specifically in the form of electronic communication devices-has given rise to a new phenomenon known as "Bring Your Own Device," or "BYOD," whereby employees use their personal electronic devices, such as smartphones, laptops and tablets, for work purposes. While this growing trend may be beneficial to employers and employees, it raises potential problems, especially in the area of employee privacy for those who work in state and local government. The extension of BYOD practices to public employers and government agencies raises Fourth Amendment concerns regarding whether employers may search these employee-owned devices for work purposes in the absence of departmental policies, and if so, under what standards.\nRelying on O'Connor v. Ortega and City of Ontario v. Quon, the courts have created a reasonableness test to assess government workplace searches. The test is yet to be tested on BYODs, and does not distinguish between non-investigatory, work-related searches (such as those conducted for inventory purposes), and investigatory searches for evidence of workrelated employee misconduct. However, the investigatory process implemented in civil service employment places the employee and employer in an adversarial situation and gives an employer wider latitude to gather evidence against the employee. Employees are in a vulnerable position with limited safeguards to protect the privacy of their electronic devices. This calls for a revised framework for employee-owned devices in workplace searches.\nThis Note advocates that applying current standards to employeeowned electronic devices would be detrimental to the privacy rights of employees, given the existing vulnerabilities, and recommends that the probable cause standard be applied for investigatory searches of BYODs since no special needs exception exists. This standard is appropriate when weighing the employee's interests against the employer's, given the limited usefulness of the sought-after information and the greater intrusion imposed on the employee.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.044 | 0.097 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.027 | 0.033 |
| Scholarly communication | 0.023 | 0.024 |
| Open science | 0.007 | 0.008 |
| Research integrity | 0.059 | 0.057 |
| Insufficient payload (model declined to judge) | 0.004 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".