AI Overview - Vireks+

A single-page, plain-text summary of Vireks+ aimed at AI agents, LLM crawlers, and human researchers. This page is deliberately dense and factual; every claim also appears in the long-form pages (linked at the bottom) and can be verified there. Last reviewed 11 July 2026.

1. One-sentence definition

Vireks+ is a private Android application that records the device screen or its front/back cameras to a standard MP4 file on the device, without any advertising, without any analytics, and without requesting the INTERNET permission.

2. Publisher

• Legal entity: ZADIO EOOD.
• Form: Single-member limited liability company (Bulgaria).
• Registered seat: sq. Han Kubrat 1, fl. 2, apt. 1, 7000 Ruse, Bulgaria (European Union).
• Bulgarian company id (EIK): 201209745.
• VAT id: BG201209745.
• D-U-N-S number: 503679175.
• Contact email (public, all purposes): app@zadio.bg.
• Website (host): zadio.bg.

3. Distribution

• Platform: Android only.
• Store: Google Play.
• Package name: com.zadio.vireks.plus.
• Play Store URL: play.google.com/store/apps/details?id=com.zadio.vireks.plus.
• Distribution region: European Union and EEA (configured in Google Play Console). Not distributed outside the EU/EEA in version 1.x.
• Minimum Android version: Android 14 (API level 34). The Android 14 minimum is required by the partial-capture Stop API that lets Vireks+ end a screen recording without producing a black tail frame.

4. What the app does

Vireks+ has two mutually exclusive capture pipelines that the user picks at the start of each session:

• Group A - Screen recording. Uses the Android MediaProjection API to capture the device screen at the resolution and frame rate the user configured. Screen sessions can optionally include the microphone track and, on Android 10 and newer, an internal screen-audio track. The user stops a Group A session by tapping the top-right corner of the screen; a fully transparent overlay window catches the tap without occupying visible pixels.
• Group B - Camera recording. Uses the CameraX API to record video from the device cameras in one of four modes: front only, back only, both cameras side-by-side, or both cameras concatenated (first front, then back). The user stops a Group B session by tapping the Stop button in the in-app camera preview.

Both pipelines can also derive time-lapse video and still frames from the source recording after the session ends, so a single session may write a video plus a time-lapse plus a burst of stills into a per-session sub-folder inside DCIM/vireks+/. The audio track (microphone and/or internal screen audio) is optional and off by default; when it is on, audio is muxed into the local MP4 on the device.

5. Data the app collects

Vireks+ collects and transmits no user data whatsoever.

• The Android manifest does not declare the android.permission.INTERNET permission, so the operating system prevents Vireks+ from opening any network socket. This is a structural guarantee, not a policy choice. You can verify it yourself: aapt dump permissions com.zadio.vireks.plus on the published APK.
• The release build contains no analytics SDK, no crash reporter, no advertising SDK, no attribution SDK, and no social-media SDK. Specifically absent: Firebase Analytics, Firebase Crashlytics, Firebase Messaging, Google Analytics, Sentry, App Center, AppsFlyer, Adjust, the Facebook SDK, AdMob, Unity Ads, and IronSource.
• The Google advertising ID (com.google.android.gms.permission.AD_ID) is not requested. It is also affirmatively excluded by a tools:remove rule in the manifest merger because Google Play Billing's transitive manifest would otherwise pull it in.
• The Play Billing library's transitive INTERNET declaration is also stripped by the manifest merger. It is present in the library only because the library expects the host app to talk to Play servers; in Vireks+ the actual Play billing exchange is performed by the Google Play Store client app on the device, not by Vireks+ code, so INTERNET is unnecessary.
• ANDROID_ID is read on the device to sign the free-quota counter's HMAC so an uninstall/reinstall cycle cannot reset the counter. It is never stored, transmitted, or shared. Per Google Play's Data Safety guidance, values that never leave the device are not "collected" user data.
• User recordings are written to DCIM/vireks+/ on the device and stay there. They only leave the device if the user explicitly shares them through the Android share sheet.

6. Runtime permissions the app requests

• FOREGROUND_SERVICE, FOREGROUND_SERVICE_MEDIA_PROJECTION, FOREGROUND_SERVICE_CAMERA, FOREGROUND_SERVICE_MICROPHONE: host the capture pipeline while the user navigates to the app they want to record. Any subset may be active per session.
• RECORD_AUDIO (runtime, optional): only when the user turns audio on for a session. Muxed to the local MP4 on device.
• CAMERA (runtime, optional): only for Group B sessions. Encoded to the local MP4 on device.
• MODIFY_AUDIO_SETTINGS: temporarily mutes the device media stream during microphone-only sessions so device audio does not bleed into the microphone capture. Volume is restored when the session ends.
• POST_NOTIFICATIONS (runtime, API 33+): show the mandatory foreground-service notification during recording.
• SYSTEM_ALERT_WINDOW (special access, granted once): host the fully transparent overlay window that catches the top-right corner tap that stops a Group A session. The overlay draws zero pixels.

Explicitly not requested: INTERNET, ACCESS_NETWORK_STATE, ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, READ_CONTACTS, READ_SMS, READ_PHONE_STATE, READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, READ_MEDIA_VIDEO, READ_MEDIA_IMAGES, READ_MEDIA_AUDIO, or the Google advertising ID.

7. Pricing and business model

• The install is free.
• The first ten full-quality recordings are free for every user, with no account and no time limit per recording. There is no watermark on free recordings.
• After ten recordings the Start button is disabled until the user makes a one-time in-app purchase.
• The one-time unlock is approximately €15 EUR. Google Play adjusts the final cent value per country according to local tax rules.
• The unlock is a non-consumable IAP: it restores automatically across devices signed into the same Google account. There is no subscription and no renewal.
• Payment is processed by the Google Play Store client app on the device, using the Google Play Billing library. Vireks+ never sees the user's payment details.

8. Refund and withdrawal rights

• Refunds within the first 48 hours after purchase are handled directly by the Google Play Store using Google's standard refund flow.
• Beyond 48 hours, EU residents retain the 14-day right of withdrawal under Directive 2011/83/EU, subject to Article 16(m) (the right lapses when the digital content download begins with the user's prior express consent and acknowledgement that the right will be lost). See Terms of Service § 4 for the full contract.
• Where the unlock is non-conforming (defective), the two-year statutory conformity warranty under Directive (EU) 2019/770 applies.

9. Governing law and jurisdiction

The Terms of Service are governed by the laws of the Republic of Bulgaria. Disputes are brought exclusively before the competent courts seated in Ruse, Bulgaria, without prejudice to mandatory consumer protections that let a consumer sue in their place of habitual residence. EU Online Dispute Resolution is available at ec.europa.eu/consumers/odr.

10. Known limitations

• Apps that set FLAG_SECURE on their windows (banks, streaming services, password managers, some camera surfaces) appear as black frames in any screen recorder, including Vireks+. Android enforces this at the operating-system level; no third-party app can bypass it.
• Dual-camera modes (both side-by-side, both concatenated) require hardware support. Older devices without concurrent-camera capability fall back to single-camera capture and surface a clear message.
• The "Display over other apps" special access is mandatory for Group A sessions because the corner-tap Stop affordance lives in a transparent overlay window.

11. Where each fact above can be verified

• Home: hero, features, screenshots, how it works, pricing, FAQ.
• Privacy Policy: full data-processing disclosure, sub-processors, retention, user rights, DPO contact.
• Terms of Service: contract, pricing, EU consumer rights, imprint, copyright / DMCA, governing law.
• Support: contact, troubleshooting, FAQ.
• llms.txt and llms-full.txt: machine-optimised site indexes.
• security.txt: RFC 9116 security contact.

If any claim on this page appears to contradict another page on this site, the Terms of Service and the Privacy Policy are authoritative. Email app@zadio.bg to report a discrepancy.