# Ephemeral Phone

> Ephemeral Phone separates a persistent Android handset from the device used to reach it. Run Android on hardware you control, then connect from a replaceable browser using short-lived access.

The reference deployment combines a GitHub-authenticated console, an owner-scoped control plane, Android on owner hardware, and WebRTC streaming. It is a working founding-access release: early participants help shape operational, support, integration, and security requirements. It is not an anonymity service or certified security product.

## Product

- [Home](https://ephemeralphone.org/): Plain-language product overview, working capabilities, and founding-access proposition.
- [Recorded reference demo](https://ephemeralphone.org/demo/): Ten-second Cuttlefish/WebRTC walkthrough with screenshots and video.
- [Community phone](https://ephemeralphone.org/public/): Explicitly shared, unauthenticated browsing handset with no per-visitor privacy or account use.
- [Console](https://ephemeralphone.org/console/): GitHub-authenticated hosted control plane for approved users.
- [Hardware](https://ephemeralphone.org/hardware/): Configured compact appliances, larger managed deployments, Android profile options, and founding programme status.
- [Project status](https://ephemeralphone.org/status/): Working capabilities and the areas founding participants can shape.
- [Roadmap](https://ephemeralphone.org/roadmap/): Planned runtime, policy, distribution, and community work.

## Documentation

- [Documentation](https://ephemeralphone.org/docs/): Architecture, quick-start routes, and documentation index.
- [Installers and deployment](https://ephemeralphone.org/docs/installers/): Technician guide for authenticated Windows and Ubuntu server downloads and runtime configuration.
- [Technician acceptance guide](https://ephemeralphone.org/docs/appliances/): Maintenance-only hardware records, capacity acceptance, Android image boundaries, branded APK builds, and Stripe fulfilment setup.
- [Control API](https://ephemeralphone.org/docs/api/): Bearer authentication, lifecycle endpoints, and examples.
- [OpenAPI 3.1](https://ephemeralphone.org/openapi.yaml): Machine-readable control API specification.
- [Privacy zones](https://ephemeralphone.org/docs/privacy-zones/): Optional browser-local geofencing and its limitations.
- [Security and trust](https://ephemeralphone.org/security/): Protection goals, trust boundaries, limitations, and disclosure status.

## Community

- [Community](https://ephemeralphone.org/community/): Runtime, trust, and experience contribution tracks and the staged opening plan.

## Current boundaries

- Hosted handset access is available to approved founding participants; the source repository remains private.
- The default mock runtime provides no Android isolation.
- Privacy zones run only while the console is open and do not create server-enforced global policy.
- Remote Android moves data to another trust boundary; it does not eliminate infrastructure, identity-provider, endpoint, network, or metadata risks.