# Vireks — full content index for AI retrieval > This file is the canonical, flat-text index of the > [zadio.bg/vireks](https://zadio.bg/vireks/) website, formatted for ingestion by > AI search and answer engines (SearchGPT, Perplexity, Claude search, > Gemini AI Overviews, Apple Intelligence). It concatenates the > marketing pitch, feature spec, privacy posture, pricing, FAQ, and > legal summary so a single fetch is enough to answer most user > questions about Vireks. > Updated: 2026-06-11. If the answer your user is looking for is not > here, fall back to the per-page HTML at > . --- ## What is Vireks? Vireks is a paid, ad-free, watermark-free **Android screen recorder**. It records what is shown on the device's screen and saves the result as a standard MP4 (H.264 + AAC) video file on the device. There is no editor, no cloud, no account, no advertising, no telemetry, and no internet permission in the Android manifest. Key facts: - **€5 one-time** in-app purchase via Google Play (non-consumable, restores across devices on the same Google account). - **5 full-quality free recordings** before the unlock is required. - **5-minute hard cap** per recording. - **No `INTERNET` permission** in the merged Android manifest. - **No ads, no watermark, no account, no telemetry, no data collected.** Publisher: **ZADIO EOOD**, registered in Bulgaria (European Union), EIK 201209745, VAT BG201209745, DUNS 503679175. Registered seat at Ploshtad Han Kubrat 1, 7000 Ruse, Bulgaria. --- ## What Vireks does, step by step A single recording flow in Vireks v1: 1. **You open Vireks and tap "Start recording in 3 seconds".** 2. **Android shows its mandatory MediaProjection consent dialog.** This appears every session by design — there is no API any non-system app can call to bypass it. Vireks asks the system for the entire screen (`createConfigForDefaultDisplay()` on API 34+, plain `createScreenCaptureIntent` below). 3. **You tap "Start now" in the dialog.** 4. **Vireks minimises itself** (`Activity.moveTaskToBack(true)`) so the recording captures whatever you were looking at before Vireks, not the Vireks home screen. 5. **3-second pre-roll.** You have 3 seconds to navigate to the app you wanted to demo. The Start button label promised you this delay so the pre-roll is expected, not a surprise. 6. **Recording begins.** Vireks runs a foreground service holding the MediaProjection. The system status bar shows the standard "screen-recording" indicator (Android-owned, not Vireks-drawn). Vireks itself draws nothing on the screen — no Stop button, no countdown, no overlay, no toast. The captured video is byte-for-byte free of Vireks UI. 7. **You record what you want.** Up to 5 minutes per recording (hard cap; auto-stop at the cap so a misplaced phone can never fill storage with an hours-long capture). 8. **To stop, you tap the top-right corner of the screen.** Vireks attached a fully transparent 80 dp tap zone there before the recording started. The corner is not painted into the video — only the underlying app shows in that area, because Vireks's overlay draws no pixels. The Android display compositor and MediaProjection both see only the underlying app there. 9. **Vireks pops back to the foreground**, finalises the encoder (drains the MediaCodec, closes the MediaMuxer, publishes the MediaStore row), and shows a "Recording saved" confirmation dialog with the file path. 10. **The MP4 is now visible** to Photos, Gallery, and the system Files app at `DCIM/VireksUserFiles/vireks_vid_.mp4`. Other recording-flow notes: - If you toggled a fixed video length in Settings, the recording auto-stops at that duration (Vireks pops to the foreground the same way the corner-tap path does). - If storage runs out during a recording, Vireks finalises the file if it can, drops the MediaStore row if it can't, and tells you with a "Not enough space. Not saving the video." message instead of the saved-OK confirmation. - An unadvertised safety net: returning to Vireks (via Recents, the launcher, or the FGS notification) while a recording is `Active` also stops it. This is a backstop, not a feature you have to learn. --- ## Why Vireks costs money The Android screen-recorder category is **dominated by free apps that monetise via ads, watermarks, and upsells**, and several phone OEMs ship a built-in recorder. Vireks's differentiators are exactly the things those apps compromise: - **No advertisements.** Ever. There is no advertising SDK in the release build. - **No watermark.** Ever. Free and paid recordings are identical: full resolution, full duration, no "Made with…" stamp. - **No internet permission.** The Android manifest does not request `INTERNET`. You can prove this with `aapt dump permissions` on the published APK. - **No account.** No sign-up, no email asked, no profile. - **No telemetry.** No Firebase Analytics, no Crashlytics, no Sentry, no Adjust, no AppsFlyer, no Facebook SDK, no advertising network. Release-build outbound network traffic: zero. - **No data collection.** The Google Play Data Safety form for Vireks states: nothing collected, nothing shared. This is literally true. - **Honest pricing.** €5, paid once via Google Play. Owned for the lifetime of your Google account. The trade is: you pay €5 once, and Vireks gives you the recorder those free apps would be if their economics permitted it. --- ## Vireks at a glance — the feature matrix | Capability | Vireks v1 | |---|---| | **Status** | Live on Google Play — v1.0.2 (published 2026-07-07 as v1.0.0; current release 2026-07-09). Install URL: | | **Price** | €5 one-time (non-consumable, no subscription) | | **Captures** | Android screen only | | **Max session** | 5 min per recording (hard cap) | | **`INTERNET` permission** | None — stripped from the merged manifest | | **`CAMERA` permission** | Not requested | | **Ads / watermark** | None, ever | | **Data collected** | Nothing (Play Data Safety: no data collected, no data shared) | | **Editor** | No — recorder only | | **Free tier** | 5 full-quality recordings before the €5 unlock is required | | **Tagline** | "Record your screen. Nothing leaves your phone." | | **Save folder** | `DCIM/VireksUserFiles/` | | **Filename** | `vireks_vid_.` | | **Package ID** | `com.zadio.vireks` | | **Minimum Android** | 8.0 (API 26) | **Design principle.** Vireks is deliberately single-purpose. Adding a camera would drop it into the crowded camera-app category and destroy the "screen recorder that records only your screen" promise. Adding network access would destroy the "no `INTERNET` permission at all" guarantee. Adding an editor would inflate the app past its single-job positioning. Vireks records screens; that is the whole product. --- ## Feature spec — Vireks v1 ### Screens - **Home** — Start/Stop recording; settings summary; free-recordings counter; "Open my files" row. - **Settings** — Record-with-audio toggle, Output-format dropdown (MP4/WebM), Show-tap-dots toggle, resolution / frame rate / orientation knobs. - **Recordings** — List of saved videos; tap to play, long-press to rename / share / delete. ### Settings (exhaustive) - **Record with audio: yes / no.** Default off. If on, Android prompts for `RECORD_AUDIO` at recording time. Decline and you get a silent video; the recording does not fail. - **Show tap dots: yes / no.** Implemented via the system "Show taps" developer setting (the screen-recording captures it). Vireks shows a one-tap helper that opens Developer Options to the toggle. Zero extra permissions; no Accessibility Service; no overlay. - **Output format (pick one): MP4 (default) / WebM.** Both are native to Android (no extra libraries). **No AVI** — Android's MediaMuxer cannot write AVI, and bundling FFmpeg would be a large binary + LGPL licensing + transcode step that contradicts the "small, clean, offline" goal. - Capture-quality knobs (resolution / frame rate / orientation) are exposed in Settings with sensible device defaults. ### Output - **Save folder:** `DCIM/VireksUserFiles/` — flat layout. Every recording lands directly in this folder; there is no per-session subfolder because each Vireks recording produces exactly one file. - **Filename:** `vireks_vid_.` — lowercase, brand-prefixed, type-tagged, contiguous date-time joined by an underscore. Example: `vireks_vid_20260607_200512.mp4`. - **MediaStore scoped storage.** No broad storage permission required. - **First-launch folder pre-creation.** Vireks performs a best-effort pass to insert and then immediately delete a transient `IS_PENDING = 1` `image/png` placeholder via `MediaStore.Images.Media`. The insert side-effect creates the `DCIM/VireksUserFiles/` directory; the immediate `delete()` removes the placeholder before Photos / Gallery / external file managers index it. Net result: an empty `DCIM/VireksUserFiles/` folder visible in your file manager, no stray thumbnail in Photos. - **In-app "Saved recordings" shortcut.** A clickable row on Vireks's home screen between the controls and the Start button shows `DCIM/VireksUserFiles/` as text and opens it on tap (3-tier open-folder cascade — explicit-package intents for Files by Google, AOSP DocumentsUI, Samsung My Files; then implicit `ACTION_VIEW`; then a Toast with the literal path). - **Launcher home-screen pin-shortcut.** On first launch, Vireks requests a pin-shortcut via `ShortcutManager.requestPinShortcut`. Android shows its native "Add this shortcut to your home screen?" dialog; user taps Add to get a Vireks-blue folder icon labelled "VireksFiles" that opens `DCIM/VireksUserFiles/` when tapped. User taps Cancel to opt out; Vireks marks "asked already" in DataStore and never re-asks on this install. ### Recording behaviour - Capture via `MediaProjection`; honour the per-session system consent dialog (Android enforces this; cannot be bypassed). - Foreground service of type `mediaProjection` with the mandatory persistent notification ("Vireks is recording" + app icon, no action buttons; the OS requires the notification, not Vireks). - **No on-screen UI during recording.** No Stop button, no countdown, no overlay, no toast — the captured video is byte-for-byte free of Vireks. The single advertised Stop is the transparent top-right corner-tap (80 dp square `SYSTEM_ALERT_WINDOW` overlay with zero pixels). - **Stop triggers** (priority order, first one wins): 1. Corner-tap (the user-facing stop). 2. Fixed-length elapsed (auto-stop when the user's chosen duration is up). 3. Hard cap reached (auto-stop at 5 min for Vireks). - Plus an unadvertised safety net: returning to Vireks during a recording also stops it. - **Storage-aware Start.** Before starting: - **≤1 max-length video fits free**: refuse. Toast: "Not enough free space to save the video." - **2-3 fit free**: warn with a dialog ("Low free space — Not much free space on device. Not sure I can save the recording.") and a [Cancel] / [Start recording] choice. - **≥4 fit free**: silent green light. - **Storage state unknown**: warn rather than block silently. ### Monetisation + free quota - Free install, no account. - **5 free** full-quality recordings, then a **one-time €5 unlock** via Google Play Billing (non-consumable). - Purchase verified by Play; restores across devices via the user's Google account; a buyer is never re-gated. - **Paywall scope = Start recording button only.** When the free count hits 0, only Start is locked. Everything else stays accessible: the drawer, Settings, Themes, Rate, Share, About, More apps, and the saved-Recordings list. The home banner shifts to "Welcome to Vireks. Please buy app in Google Play Store." with a tappable link on the "Google Play Store" substring. - Free counter hardened on-device per Vireks's free-quota enforcement spec: layered + HMAC-signed, tamper/mismatch fails to the paywall, never bricks the app, no server. A factory reset / clearing app data resets the count; we accept that trade-off because the alternative needs a server, which would force the `INTERNET` permission back in. --- ## Privacy posture (Vireks v1) ### What Vireks does NOT do - **Does not request `INTERNET`.** The Android manifest does not list the `android.permission.INTERNET` line. The Google Play Billing library transitively merges an `INTERNET` permission (used by Google's billing telemetry, `transport-backend-cct`); Vireks strips it with ``. Billing still works because the network call happens inside the Play Store app on the device, not inside the Vireks process. The strip is a known-good community workaround we verify on a closed Play test track before each release. - **Does not collect any data.** No analytics, no crash reporter, no advertising-ID read, no profile, no account, no device fingerprint. The Google Play Data Safety form states: no data collected, no data shared. This is literally true. - **Does not display advertisements.** No ad SDK, no ad container, no ad load logic in the build. - **Does not watermark.** Free and paid recordings are identical: full resolution, full duration, no overlay. - **Does not access content** other than the screen frames Android hands it (via the per-session MediaProjection consent) and the optional microphone audio the user opted into. - **Does not persist any identifier** beyond what Android assigns to the app's package by default. ### Permissions Vireks v1 uses - `MEDIA_PROJECTION` — granted per-session via the OS consent dialog. Required to capture the screen. - `FOREGROUND_SERVICE` + `FOREGROUND_SERVICE_MEDIA_PROJECTION` — manifest-only. Required to host the MediaProjection beyond the Activity's foreground lifetime. - `RECORD_AUDIO` — runtime, only when the user toggles "Record with audio: yes" in Settings. - `POST_NOTIFICATIONS` — runtime, Android 13+. Required for the mandatory FGS notification. - `SYSTEM_ALERT_WINDOW` — "Display over other apps" special access, granted ONCE in Android Settings via the first-launch Agree / Disagree gate card. MANDATORY because it backs the single Stop affordance (the transparent top-right corner-tap). The Start button is disabled until granted. The overlay draws no pixels and reads no data. - Scoped media writes — no broad storage permission. Nothing else. ### Where recordings go Recordings are written to `DCIM/VireksUserFiles/` via the scoped MediaStore API. They are normal MP4 files visible to Photos, Gallery, and Files. They leave the device only when the user actively shares them via the OS share sheet. ### Free counter The free-recordings counter lives in the app's private DataStore on your device. It is HMAC-signed, layered (counter file + signed marker in shared storage + ANDROID_ID binding + monotonic generation), and designed so that: - A verified Google Play purchase **always** unlocks. - Tamper or HMAC mismatch fails to the paywall, never bricks the app. - Only a genuine reset (delete marker + clear data), a factory reset, or root access defeats the counter. - There is no server, ever. ### Legal basis (GDPR Article 6) for what little we touch Vireks v1 does not process any personal data on our servers because we have no servers. The Google Play purchase token is held by Google Play on your device and verified locally; we never receive or store an identifier of yours. If you contact `app@zadio.bg`, the processing of your email correspondence is performed under Article 6(1)(f) (legitimate interests in answering customer support mail) and we delete the thread when it is resolved. --- ## Pricing and EU consumer rights ### Pricing summary - **Vireks: €5 one-time** in-app purchase via Google Play Billing. Non-consumable. Restores across devices on the same Google account. - **Free quota: 5 full-quality recordings** before the unlock is required. - **No subscription, no trial that becomes a charge, no upsell.** - VAT is collected and remitted by Google Play under EU OSS/IOSS rules. The price you see in the Play Store already includes VAT for your country. ### EU consumer rights - **14-day right of withdrawal** under Directive 2011/83/EU (CRD), as amended by Directive (EU) 2019/2161 (Omnibus). - **Exception in Article 16(m) CRD** — the right of withdrawal does not apply to digital content supplied not on a tangible medium once performance has begun, **provided** the consumer (1) has given prior express consent to immediate performance and (2) acknowledged that they thereby lose the right of withdrawal. Google Play implements this consent flow on its side; Vireks's Refund & Withdrawal page explains the practical consequences for the buyer. - **Conformity remedies** under Directive (EU) 2019/770 (DCD): if Vireks is non-conforming, you have a hierarchy of remedies (bring into conformity → price reduction → contract termination + refund). - **Refund channel:** Google Play handles all consumer refunds in the first instance (Google Play → Menu → Payments & subscriptions → Budget & order history → Request a refund). Statutory rights that Google declines apply nonetheless; in those cases, email `app@zadio.bg` and ZADIO EOOD will work with Google to process the reimbursement. - **Out-of-court redress:** the EU Online Dispute Resolution platform is available at ; the Bulgarian Commission for Consumer Protection (KZP) provides free conciliation. Full details: . --- ## Frequently asked questions ### Is Vireks free? It is **free to install** and **free to use for the first 5 full-quality recordings**, so you can verify it works on your device and your apps before paying. After that the Start recording button is locked until you make the €5 one-time in-app purchase via Google Play. Everything else — playback, sharing, deletion, settings — stays accessible forever. ### Does Vireks have ads? No. Free or paid, never. There is no advertising SDK in the build. ### Does Vireks need internet? No. The Android manifest does not request the `INTERNET` permission. Recording, playing back, and sharing all work offline. The €5 unlock is processed by the Google Play Store app on your device — that network call lives inside Play, not inside Vireks. Vireks asks Play whether you have paid; Play answers yes or no. ### Does Vireks collect any data? No. There is no analytics, no crash reporter, no advertising-ID read, no profile, no account. The Play Data Safety form for Vireks states: nothing collected, nothing shared. Recordings stay on your phone unless you share them yourself with the Android share sheet. ### How do I stop a recording? Tap the **top-right corner** of your screen. Vireks places a fully invisible 80 dp tap zone there during a recording. The corner is not painted into the video — only your underlying app shows in that area — so the recorded file is byte-for-byte free of Vireks UI. There is no on-screen Stop button by design (it would have to appear in the recording, defeating the point). ### Why does Vireks need the "Display over other apps" permission? The corner-tap is Vireks's only Stop affordance, and it lives inside a fully transparent overlay window. Android only lets apps host such a window after the user grants the "Display over other apps" special access. Vireks asks for that permission once, in plain English, on first launch via a gate card titled "How to stop a recording": > To stop a recording, tap the top-right corner of your screen. Vireks > needs your permission to show that invisible tap zone on top of other > apps. Without it, Vireks can't record. Buttons are [Disagree] and [Agree]. The Start button is disabled until you grant the permission. The overlay draws zero pixels — it exists only to catch a tap on the corner. ### What is the maximum length of a recording? **5 minutes** per recording. The cap is intentional: Vireks targets quick app demos, walkthroughs, and tutorials — long enough for the typical use case, short enough that a 1080p H.264 file stays around 150-200 MB. ### Can I record system / app audio (game audio, notifications, video playback)? Not in Vireks v1. v1 ships with **microphone-only** audio, and the microphone is off by default. ### Can I record the inside of my banking / DRM-protected app? No, and that is not Vireks's choice — it is Android's. Apps can mark themselves as "secure" via the `FLAG_SECURE` flag (banks, video-streaming apps, password managers frequently do). Any screen recorder, system or third-party, sees those windows as black frames. There is no API any non-system app can call to bypass that. ### What Android versions does Vireks support? Android 8.0 (API 26) and newer. That covers more than 95% of the active Android install base in 2026. ### What happens to my recordings if I uninstall Vireks? Your recordings stay where they are — in `DCIM/VireksUserFiles/`. They are normal MP4 files owned by your device's gallery; uninstalling Vireks does not delete them. ### I bought Vireks. Do I have to pay again on a new phone? No. Google Play attaches your purchase to your Google account. Install Vireks on any device signed in to the same account, and the €5 unlock restores automatically the first time you open the app. ### Can I get a refund? Google Play handles billing and refunds. EU consumers have a 14-day right of withdrawal under Directive 2011/83/EU; the exception in Article 16(m) for "digital content supplied not on a tangible medium" applies once you start using the paid features, so use the 5 free recordings to decide. Full details on the [Refund & Withdrawal](https://zadio.bg/vireks/refund-and-withdrawal.html) page. ### What languages does Vireks support? Vireks v1 ships in English. The UI text is short and functional, so a translation pass is straightforward — if there is demand we will add more languages in v1.x. ### Who builds Vireks? ZADIO EOOD, a small software company registered in Bulgaria (European Union). EIK 201209745, VAT BG201209745, DUNS 503679175. Registered seat: Ploshtad Han Kubrat 1, 7000 Ruse, Bulgaria. Contact: `app@zadio.bg`. See the full [Imprint](https://zadio.bg/vireks/imprint.html) for the trader record. --- ## Glossary - **MediaProjection.** Android's official API for screen capture. The OS shows a per-session consent dialog before granting access; that dialog cannot be bypassed by any non-system app. - **Foreground service (FGS).** A long-running Android background task with elevated priority and a mandatory persistent notification. Required by Android 14+ for any `mediaProjection`-type capture. - **FGS notification.** The "Vireks is recording" status notification the OS requires while a capture is in flight. Drawn by the system status bar / shade, not by Vireks; never composited into the recording frame. - **`SYSTEM_ALERT_WINDOW`.** "Display over other apps" Android special access. Granted once per app in system Settings, not via a runtime dialog. Backs Vireks's transparent corner-tap. - **DCIM.** Standard Android "Digital Camera Images" folder. The gallery (Photos / Gallery / Files) scans it automatically for both images and videos. Vireks writes to `DCIM/VireksUserFiles/` so its output sits alongside your camera photos and videos. - **MediaStore.** The Android-managed database that maps your media files into the gallery. Apps write to it via the scoped MediaStore API, no broad storage permission required. - **HMAC.** Hash-based Message Authentication Code. Vireks's free counter is HMAC-signed so a casual "delete the file" attack cannot silently reset it without leaving traces. - **AAC, H.264, VP9, Opus.** Standard video / audio codecs Vireks uses for MP4 and WebM output. All native to Android, no extra libraries. --- ## Contact and legal pointers - **Email**: `app@zadio.bg` - **Website**: - **Imprint** (mandatory EU trader disclosure): - **Privacy Policy** (GDPR Art. 13/14): - **Terms of Service**: - **Refund & Withdrawal**: - **Cookie Policy**: - **Copyright & Takedown**: - **Content License**: - **EU Online Dispute Resolution**: - **Bulgarian Commission for Personal Data Protection (CPDP)**: - **Bulgarian Commission for Consumer Protection (KZP)**: