Introduction
This Privacy Policy applies to Druid Recorder, an Android screen-recording application developed by Druid Apps Studio. It describes how version 1.1.0 (version code 2) of Druid Recorder accesses, processes, stores, and transfers information.
This app-specific policy is listed in the Druid Apps Privacy Policy hub. It applies to the production Android application with package ID com.druidapps.screenrecorder.
Information and data collection
Druid Recorder does not require a user account. The current version does not automatically collect your name, email address, phone number, postal address, account or profile information, payment information, location, contacts, calendar, SMS, call logs, installed-app list, advertising ID, Android ID, or another persistent device identifier. If you deliberately email support through your external email app, the contact information and content you send are handled as described under Support email.
There is no Druid Apps Studio account system or backend connected to the app. Druid Recorder processes recording settings and user-created screen, audio, facecam, watermark, filename, annotation, and marker content locally on your device. Druid Apps Studio does not automatically collect or receive that content.
Content can leave your device when you deliberately share or open a recording with another app or start the optional local browser-transfer feature described below.
Screen recording
Druid Recorder uses Android MediaProjection for screen recording. Entire-screen capture is supported on Android 10 and later; single-app capture uses Android's picker on Android 14 and later. Android displays a system consent prompt for every recording session, and the MediaProjection grant is not retained for future sessions.
Screen frames are encoded locally. New completed recordings are stored as MP4 files in Android shared media storage under Movies/Druid Recorder. The app can also show app-owned recordings previously saved under Movies/Druid Screen Recorder for compatibility; it does not move, duplicate, or upload those legacy files automatically. Druid Apps Studio does not automatically receive or remotely access recorded screen content.
Recording can continue through an Android foreground service while the Druid Recorder app screen is not visible. Android displays recording controls according to the permissions and system behavior available on your device.
Audio recording
Audio recording is optional. The current version supports recording with no audio, microphone audio, supported device or internal playback audio, or a mix of microphone and device audio.
Android's RECORD_AUDIO permission is requested only when you select a non-silent audio mode. Android also requires this permission for playback-audio capture. Audio is encoded inside the same local video recording; Druid Recorder does not automatically create or upload a separate audio file.
Audio leaves your device only when you explicitly share or transfer the resulting recording. If you mute the microphone during an active recording, microphone sound is prevented from being written into the resulting mix, although the active microphone capture source remains open during that session. Pausing recording also keeps active audio capture routes open while excluding paused samples from the saved video. Stopping recording releases those capture routes.
Camera and facecam
Camera access is optional. Druid Recorder requests the camera permission when facecam is enabled and needed for your chosen recording session. Facecam and annotation overlays are supported only in entire-screen capture; single-app capture disables them.
Facecam uses Android CameraX Preview. The app does not create a separate camera video or still image. The visible facecam image becomes part of the screen recording, so those camera pixels remain inside the completed local MP4.
Camera content leaves your device only when you explicitly share or transfer the recording that contains it.
Android permissions
Druid Recorder uses Android permissions needed for its implemented features. Depending on the features you choose, these include foreground-service permissions for recording and media processing; the media-projection foreground-service permission; optional microphone, camera, and notification permissions; optional Display over other apps access; optional Do Not Disturb access; Internet and network-state access for local browser transfer; and wake-lock functionality when you enable the relevant setting.
Display over other apps supports optional floating controls, annotations, facecam and the keep-screen-awake overlay. A background countdown can use an existing overlay grant; the app does not request this access solely for countdown. Do Not Disturb access is used only for the optional recording-related DND feature and does not read notification contents.
FOREGROUND_SERVICEand the media-projection, microphone, camera and media-processing service types keep the chosen recording or processing operation visible to Android. Microphone and camera types are used only when those inputs are active; media processing supports post-recording watermark work on applicable Android versions.RECORD_AUDIOandCAMERAsupport optional audio and facecam;POST_NOTIFICATIONSsupports visible recording and saved-recording notifications.SYSTEM_ALERT_WINDOWandACCESS_NOTIFICATION_POLICYsupport the optional overlay and Do Not Disturb tools;WAKE_LOCKsupports keeping the screen awake.INTERNETandACCESS_NETWORK_STATEsupport the user-started local HTTPS transfer session. They do not enable an app telemetry or cloud-upload service.
Android requests MediaProjection consent separately for every recording session. Druid Recorder does not request broad storage or media-read access, location, contacts, SMS, phone or accessibility-service permissions. Notification permission enables recording controls and saved-recording notifications; denying it does not remove the app's in-app recording controls.
File and media storage
New completed recordings and edited copies are stored in Android shared MediaStore under Movies/Druid Recorder. Druid Recorder lists recordings owned by the application, including app-owned recordings found in the legacy Movies/Druid Screen Recorder directory, and does not enumerate unrelated user videos.
The current and legacy directories are shown together with duplicate media URIs removed; existing files are not automatically moved, renamed or duplicated. App settings, recording-recovery state and marker metadata are stored locally in app-private storage. Temporary files can be created in private app storage or cache while editing, watermarking, or processing video.
You can optionally choose an image watermark through Android's system document picker. Druid Recorder receives access only to the image you select and can retain that document grant for the selected watermark. The image is processed locally and is not automatically uploaded to Druid Apps Studio.
Local Wi-Fi and browser transfer
Druid Recorder includes an optional local browser-transfer feature. It starts only when you explicitly choose to start browser transfer. Your phone then temporarily runs a local HTTPS server over an eligible private Wi-Fi or Ethernet network. The app reads the active local network state and private IPv4 address to create the transfer address; it does not use that address to infer your location or send it to Druid Apps Studio.
The transfer URL contains a random secret token. A browser that can reach your phone and has the complete URL can view the recording filenames and file sizes included in that transfer session and download requested recordings. Recording files travel directly between your phone and the browser; Druid Apps Studio does not receive them. Starting the server by itself does not upload a recording—a browser must connect and request it.
The current implementation uses TLS 1.2 or TLS 1.3. Its temporary TLS identity uses a device-held Android Keystore key and a self-signed session certificate. Druid Recorder displays a certificate fingerprint that you can compare in the browser.
The transfer has no user account or client certificate. Possession of the complete secret transfer URL grants access to that session for a device capable of reaching your phone. Share the URL only with intended recipients, use the feature only on a trusted local network, and stop the transfer when you finish.
The session exposes an app-owned recording list fixed when the transfer starts; it has download endpoints, not an upload endpoint. The local server closes when you stop it, leave the relevant screen, lose or change the network, encounter an error, the app process ends, or leave the session inactive for approximately 15 minutes. An authorized active download keeps the idle timer from expiring. The temporary key is removed during normal cleanup; abandoned session keys are removed when transfer next starts. Because the certificate is self-signed, a browser may display a certificate warning; verify the displayed fingerprint before deciding whether to connect.
Support email
The Support option opens your device's normal email application with the Druid Apps Studio support address. Druid Recorder does not read or send the message itself. If you choose to send an email, Druid Apps Studio and its email provider receive the email address, message, and attachments you include so the request can be answered.
Support correspondence is retained only as long as reasonably needed to respond, maintain support history, prevent abuse, or meet legal obligations. You can ask about deletion of support correspondence by emailing support@druidapps.com, subject to any required retention.
Analytics
The current version of Druid Recorder does not use an analytics service and does not transmit app-usage events to Druid Apps Studio or an analytics provider.
Crash reporting
The current version does not integrate a remote crash-reporting or diagnostic service. The app may write diagnostic information to Android's local system log. Android, Google Play, or the device manufacturer may separately process platform-level diagnostics according to their own settings and privacy policies. Druid Recorder does not contain code that sends those local logs to Druid Apps Studio.
Advertising
The current version does not display ads, does not contain an advertising SDK, and does not access Android's advertising identifier.
Third-party services
Druid Recorder uses Kotlin and standard Android and AndroidX Jetpack libraries, including Jetpack Compose, DataStore, Media3, CameraX and Kotlin Coroutines, for its user interface, local data storage, media processing, and camera preview. These production dependencies do not add an analytics, advertising, attribution, authentication, billing, remote crash-reporting, remote-configuration, or Druid Apps cloud-storage service.
If you choose an external share target, browser, video player, gallery, document provider, cloud application, or another external app, that third party handles the selected information under its own privacy practices.
Data retention
Completed recordings and edited copies remain in Android shared media storage until you or another authorized application deletes them. Druid Recorder does not impose an automatic expiration period on saved recordings.
App settings and marker metadata remain in private app storage until they are changed, app data is cleared, or the app is uninstalled. Temporary processing and cache files are normally deleted after their purpose is complete, although temporary files can remain after abnormal termination until Android or the app later removes them.
Druid Apps Studio does not retain remote copies because the current application does not upload recordings or user data to a Druid-operated service.
If you contact support by email, support correspondence is retained as described in the Support email section.
Data deletion
You can delete recordings from Druid Recorder or through another authorized gallery or media application. Clearing Druid Recorder's application data or uninstalling the app normally removes app-private settings, metadata, and cache. Published recordings stored in shared media storage may remain after uninstall.
Recordings or copies already shared, transferred, or downloaded to another application or device must be deleted separately from that destination. There is no Druid-hosted user account or remote app-data store requiring an online account-deletion mechanism. Support-email deletion enquiries can be sent to the contact address below.
Children's privacy
Druid Recorder does not collect a user's age and does not currently implement an age gate, children's mode, or child-specific functionality.
Security
Druid Recorder relies on Android's application sandbox and Android media and storage controls for local information. Application-private cloud backup and device-to-device backup are disabled, and Android cleartext networking is disabled. Saved shared-media recordings do not have additional app-managed encryption at rest; Android's device and storage protections apply.
For local browser transfer, the current implementation uses TLS 1.2 or TLS 1.3, random secret transfer URLs, a temporary device-held cryptographic key, a self-signed session certificate, and a displayed certificate fingerprint.
Possession of the complete browser-transfer URL grants access to that session for devices that can reach your phone. Keep the URL private, use a trusted local network, and stop the transfer when you finish. These safeguards reduce risk but cannot guarantee absolute security.
External links and external apps
The Privacy Policy option opens https://druidapps.com/privacy/druid-recorder/ in your normal browser, and Support opens an external email app addressed to support@druidapps.com. The current Android app does not contain an embedded WebView that loads a Druid website. Android features such as sharing, open-with, document selection, and browser transfer can involve external applications and services chosen by you. Those third parties operate under their own privacy practices.
Changes to this Privacy Policy
This Privacy Policy may be updated if Druid Recorder's permissions, SDKs, features, storage behavior, or data practices change. The effective and last-updated dates on this page identify the current version of the policy.
Effective date:
Last updated:
Contact
For questions about this Privacy Policy or Druid Recorder's privacy practices, contact:
Druid Apps Studio
support@druidapps.com