Legal
Ogh Privacy Policy
This policy explains how Ogh accesses, uses, stores, protects, retains, and deletes user data.
Last updated: July 28, 2026
Ogh is a local-first, open-source Android streaming application. Ogh does not operate an account service, advertising service, analytics service, telemetry service, or media relay. Broadcast media is sent directly from the user's device to destinations chosen by the user.
Information Ogh accesses
Ogh accesses the selected screen, camera, microphone, or eligible device audio only after the user selects that feature and grants the Android permission it requires. Manual RTMP credentials are provided directly by the user.
Manual destinations may use RTMP or RTMPS. RTMPS encrypts the stream and credentials in transit; plain RTMP does not. Ogh recommends RTMPS whenever the destination supports it.
Google and YouTube user data
When the user chooses Connect YouTube, Ogh requests the Google OAuth scope https://www.googleapis.com/auth/youtube. Ogh uses this permission only to:
- identify the user's YouTube channel;
- create and configure a YouTube live broadcast and ingestion stream;
- bind the ingestion stream to the broadcast; and
- manage the broadcast lifecycle requested by the user.
Ogh does not use Google user data for advertising, analytics, profiling, credit decisions, or training generalized artificial-intelligence models. Ogh does not sell Google user data or transfer it to an Ogh server or another third party.
Ogh's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Twitch data
When the user connects Twitch, Ogh requests the permission needed to read the user's Twitch ingest stream key immediately before a streaming session. Ogh uses that information only to publish the stream to the user's chosen Twitch channel.
Local storage and security
OAuth access tokens, refresh tokens, connected channel identifiers, and manual streaming credentials are stored only on the user's device. Sensitive values are encrypted with AES-256-GCM using a non-exportable key held by Android Keystore.
Ogh does not place OAuth tokens or stream keys in diagnostics or application logs. Provider ingestion credentials resolved for a session are held in memory and are not written to persistent storage.
Video, audio, pause-image, and stream-metadata preferences are stored in private Android application storage. Ogh excludes its application data from Android cloud backup and device transfer.
Data sharing
Ogh sends data only as required to provide features selected by the user:
- OAuth tokens are sent only to the provider that issued them.
- Broadcast media is sent only to destinations enabled by the user.
- Ogh does not sell user data.
- Ogh does not share user data with advertisers or data brokers.
- Ogh does not transfer user data to an Ogh-operated backend.
Retention and deletion
| Data | Retained until |
|---|---|
| OAuth tokens and channel information | The user disconnects the provider, clears Ogh's app data, or uninstalls Ogh |
| Manual streaming credentials | The user deletes the destination, clears Ogh's app data, or uninstalls Ogh |
| Provider ingestion credentials | End of the streaming session; held in memory only |
| Streaming preferences | The user clears Ogh's app data or uninstalls Ogh |
Disconnecting a provider requests token revocation and then deletes Ogh's local tokens and account information. YouTube users can also revoke Ogh's access independently from their Google Account connections page.
Uninstalling Ogh or selecting Android Settings → Apps → Ogh → Clear data removes all locally stored Ogh data from the device.
User choices and control
- Users may use manual RTMP without connecting Google or Twitch.
- Users choose which capture source and destinations to enable.
- Users may stop capture and streaming at any time.
- Users may disable destinations individually.
- Users may disconnect provider accounts from Ogh.
- Android permissions may be revoked from the device settings.
Changes and contact
Material changes to this policy will be published on this page and documented in the Ogh project history.
For privacy questions, deletion assistance, or support, open an issue in the Ogh GitHub issue tracker. Do not include OAuth tokens, stream keys, or other credentials in a public issue.