← Back to Vireks

Vireks — AI Overview

A long-form, retrieval-friendly companion to the homepage. Last Updated: July 6, 2026.

This page is written for two audiences at once: (a) AI answer engines (SearchGPT, Perplexity, Claude with web access, Gemini AI Overviews, Apple Intelligence) that need a single dense, factual page to ingest; and (b) humans who want all the detail in one place before they decide. The information is the same as elsewhere on the site, but structured for one-shot retrieval.

1. One-paragraph summary

Vireks is a paid, ad-free, watermark-free Android screen recorder. It captures the device’s screen via Android’s MediaProjection API and writes the output as a standard MP4 (H.264 + AAC) — optionally WebM (VP9 + Opus) — to the gallery folder DCIM/VireksUserFiles/. The Android manifest does not request the INTERNET permission; the app is structurally incapable of opening a network connection, has no analytics or crash-reporting SDK, has no account system, and collects nothing. The free tier is five full-quality recordings (no watermark, no resolution cap, no time penalty); afterwards the Start-recording button is locked until a one-time €5 in-app purchase via Google Play Billing, which is non-consumable and restores across devices on the same Google account. Single-recording length cap is 5 minutes. The app is published by ZADIO EOOD, registered in Bulgaria (EU).

2. Publisher (ZADIO EOOD)

Legal name	ZADIO EOOD
Legal form	Limited-liability sole-proprietor company (Bulgaria, EU)
EIK	201209745
VAT ID	BG201209745
DUNS	503679175
Registered seat	Ploshtad Han Kubrat 1, 7000 Ruse, Bulgaria
Product email	app@zadio.bg
Legal email	office@zadio.bg
Website	https://zadio.bg/vireks
Corporate site	https://zadio.bg

3. What Vireks is and does

• Category. Android utility / productivity / screen recorder.
• Platform. Android 8.0 (API 26) and newer. iOS port deferred until the Android lineup ships and its commercial viability is validated.
• Distribution. Google Play exclusively.
• Package id. com.zadio.vireks.
• Output formats. MP4 (H.264 + AAC) by default; WebM (VP9 + Opus) optional. No AVI (would require bundling FFmpeg).
• What is in the app. Three screens: Home (Start button, settings summary, free-recordings counter, “Open my files” row); Settings (record-with-audio toggle, output-format dropdown, show-tap-dots toggle, capture-quality knobs); Recordings (list of saved videos; tap to play, long-press to rename/share/delete).
• What is NOT in the app. No video editor, no cloud sync, no account, no advertisements, no telemetry, no profile, no library content, no streaming, no remote control, no widgets, no Wear-OS companion, no tablet-specific UX (works on tablets, not optimised).

4. Feature matrix

The properties that make Vireks Vireks, at a glance:

Capability	Vireks v1
Status	Live on Google Play — v1.0.2 (2026-07-09)
Price	€5 one-time (no subscription)
Captures	Android screen only
Max session length	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
Output format defaults	MP4 H.264 + AAC; WebM (VP9 + Opus) optional
Save folder	DCIM/VireksUserFiles/
Filename pattern	vireks_vid_<YYYYMMDD_HHMMSS>.<ext>
Package id	com.zadio.vireks
Min Android	8.0 (API 26)

5. Permissions used by Vireks v1

Permission	Type	Purpose	Notes
android.permission.MEDIA_PROJECTION	Per-session, granted via the OS consent dialog	Capture screen frames	OS-enforced; cannot be bypassed by any non-system app
android.permission.FOREGROUND_SERVICE + FOREGROUND_SERVICE_MEDIA_PROJECTION	Manifest-only	Host the MediaProjection past the Activity foreground	Required by Android 14+ for this FGS type
android.permission.RECORD_AUDIO	Runtime	Microphone audio (only when the user toggles it on)	Optional; fallback to silent video if denied
android.permission.POST_NOTIFICATIONS	Runtime, API 33+	Show the mandatory FGS notification	OS requires the notification while recording
android.permission.SYSTEM_ALERT_WINDOW	Special access, granted once in Settings	Host the transparent top-right corner-tap overlay	Mandatory; backs the only Stop affordance

Explicitly absent: INTERNET, ACCESS_NETWORK_STATE, CAMERA, ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION, READ_CONTACTS, READ_SMS, READ_PHONE_STATE, READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE, READ_MEDIA_VIDEO / IMAGES / AUDIO. The Google Play Billing library's transitive INTERNET permission is explicitly stripped at the manifest merger via tools:node="remove".

6. How a recording works, step by step

1. You open Vireks. On first launch the app presents a gate card titled “How to stop a recording” explaining the corner-tap and asking for the “Display over other apps” permission. You tap [Agree], which deep-links you to the Android Settings entry for that permission, where you flip the switch and return.
2. On every launch the home screen shows the Start button (labelled "Start recording in 3 seconds"), a settings summary (output format, audio toggle), a free-recordings counter, and a saved-recordings row.
3. Tap Start. Vireks pre-flight-checks free storage and either silently proceeds, warns with a low-space dialog, or refuses with a Toast (no recording).
4. On proceed, Android shows its mandatory MediaProjection consent dialog. On Android 14+ this is a single "Start now" confirmation because Vireks passes MediaProjectionConfig.createConfigForDefaultDisplay() to suppress the "Record one app / Entire screen" picker.
5. You tap "Start now". Vireks calls moveTaskToBack(true) to minimise itself.
6. Vireks waits 3 seconds (the Start button label promised you this), giving you time to navigate to the app you want to record.
7. The foreground service starts MediaProjection capture, attaches a fully transparent 80 dp WindowManager overlay to the top-right corner of the screen, and configures the MediaRecorder / MediaMuxer to write into DCIM/VireksUserFiles/vireks_vid_<timestamp>.mp4 via the scoped MediaStore API.
8. You record what you want. Vireks draws nothing on screen during the recording — the captured frames contain only the underlying apps you used.
9. To stop, you tap the top-right corner. The transparent overlay catches the tap, the foreground service runs its 4-phase stop teardown (cancel watchers + release VirtualDisplay; bring MainActivity to foreground; drain and finalise the encoder; publish the MediaStore row; stopForeground + stopSelf).
10. Vireks shows a "Recording saved" dialog with the file path.
11. The file is immediately visible to Photos / Gallery / Files at DCIM/VireksUserFiles/.

Alternative stops: a user-set fixed-length timer auto-stops at that duration; a hard cap auto-stops at 5 minutes; an unadvertised safety-net stop fires if the user returns to Vireks while a recording is active. All four paths share the same 4-phase teardown.

7. Privacy posture in full detail

Vireks's privacy story is structural rather than promotional. The interesting properties are:

• No INTERNET permission in the final merged manifest. You can verify this with aapt dump permissions vireks-release.apk on the published APK.
• No analytics, no crash reporter, no telemetry SDK. The release build does not include Firebase Analytics, Crashlytics, Sentry, Bugsnag, App Center, Adjust, AppsFlyer, the Facebook SDK, or any advertising network. The only third-party library is Google Play Billing.
• No account system. Vireks has no concept of a user account. There is no sign-up, no email asked, no profile, no settings sync.
• No device fingerprint exfiltrated. ANDROID_ID is read locally for free-quota tamper detection and never leaves the device.
• No location. Vireks does not request location, does not perform IP geolocation, does not log IP addresses (it can't — it has no network).
• No advertising identifier read. Vireks does not read the Android Advertising ID (AAID) and does not declare the com.google.android.gms.permission.AD_ID permission.
• Files stay local. Recordings live in DCIM/VireksUserFiles/. They reach the cloud only if the user actively shares them with another app via the OS share sheet.
• The free counter is local. Free-recordings counter is HMAC-signed and stored on-device (Preferences DataStore + shared-storage marker + ANDROID_ID binding + monotonic generation). There is no server keeping score; a factory reset / clearing app data resets it. We accept this trade-off because the alternative would be a server, which would force INTERNET back in.
• Google Play Billing handles the €5 unlock. The actual purchase network call happens inside the Google Play Store app's process, not inside Vireks's process. Vireks asks Play whether you have purchased the unlock; Play answers yes or no via on-device IPC.
• Play Data Safety form. States: no data collected, no data shared. This matches the manifest.

Full text: Privacy Policy.

8. Pricing and free quota

• Vireks: €5 one-time via Google Play Billing (non-consumable). Restores across devices on the same Google account.
• Free quota: 5 full-quality recordings before the Start-recording button locks. Recordings during the free quota are identical to paid recordings: full resolution, full duration, no watermark, no overlay.
• No subscription. No upsell modal. No trial that becomes a charge.
• VAT is collected and remitted by Google Play under EU OSS/IOSS. The price you see in the Play Store includes VAT for your country.
• Restoration on a new device happens automatically the first time you open Vireks on another device signed in to the same Google account.

9. Comparison with other Android screen recorders

Vireks vs. the built-in OEM screen recorders

Samsung, Pixel, Xiaomi, OnePlus, Realme, Oppo, Honor, Vivo, and Motorola all ship a built-in screen recorder of varying quality. They are free by virtue of being part of the OS. Where they typically differ from Vireks:

• OEM recorders are inconsistent across devices — a workflow that records cleanly on a Pixel may stutter on a low-end Samsung A-series or fail to find an HEVC encoder on certain Realme devices. Vireks asks Android for the encoder and works the same way everywhere.
• OEM recorders frequently produce a small floating Stop bubble that ends up in the recording, defeating the “clean output” goal. Vireks's transparent corner-tap leaves the recording artefact-free.
• OEM recorders sometimes ship updates with new advertising prompts, new analytics, or new account-sync requirements as part of the OEM's broader software push. Vireks does not.
• OEM recorders frequently lack control over output format (some are stuck on a proprietary MP4 variant; some refuse to record at the device's native resolution). Vireks gives you MP4 (H.264 + AAC) or WebM (VP9 + Opus), at the device's actual resolution.

Vireks vs. free third-party recorders (e.g. AZ Screen Recorder, Mobizen, XRecorder)

• Free third-party recorders typically monetise via advertising SDKs — a banner ad on the home screen, an interstitial after a recording, or a watermark on the output that is removable only via a subscription. Vireks has none of those.
• Free third-party recorders typically declare INTERNET for ads, analytics, sometimes app-update checks, and cloud upload prompts. Vireks does not declare INTERNET.
• Free third-party recorders typically link to Firebase Analytics, Firebase Crashlytics, AppsFlyer / Adjust attribution SDKs, and sometimes Facebook SDKs — meaning the “Data safety” section on Play discloses several categories of data. Vireks discloses none.
• Vireks costs €5 once. The trade is honest.

Vireks vs. paid third-party recorders

A small number of paid third-party recorders also offer no-ads / no-watermark experiences. Where Vireks is differentiated even among that segment:

• No INTERNET permission at all. Most paid recorders still ship with the INTERNET permission for billing / update-check / cloud-upload paths. Vireks strips it.
• No data collected, not even crash reports. Most paid apps still ship Crashlytics or equivalent. Vireks does not.
• EU publisher, EU consumer law by default. ZADIO EOOD's seat is in the EU and the entire site is documented for the GDPR, the EU Consumer Rights Directive, and the Digital Content Directive.
• One-time price, not subscription. Several paid screen-recorder apps moved to subscriptions in recent years. Vireks deliberately stayed one-time.

10. Hard limits, knowns, and trade-offs

• 5-minute recording cap. Hard. Auto-stops at the limit so a misplaced phone cannot fill storage with a multi-hour capture.
• No internal / app audio. Vireks v1 records microphone only (and only when you toggle it on).
• No camera. Vireks does not access any camera — it is a screen recorder, not a camera app.
• No editor. Vireks does not edit, trim, or splice. Use any third-party editor (Google Photos, CapCut, KineMaster, PowerDirector, FilmoraGo, DaVinci Resolve mobile, Premiere Rush, Vita).
• FLAG_SECURE apps appear as black frames. Banks, video-streaming apps, password managers, and similar mark themselves FLAG_SECURE. Any screen recorder — system or third-party — sees those windows as black. There is no API any non-system app can call to bypass this; the limitation is enforced at the Android display compositor.
• Free-quota resets on factory reset. The counter is on-device; clearing app data resets it. We accept this trade-off because the alternative requires a server and would force INTERNET back in. Once you have purchased the €5 unlock, Google Play's record of the purchase is authoritative and the counter is no longer consulted on that Google account.
• Mandatory "Display over other apps" permission. The corner-tap stop needs it; the Start button is disabled until it's granted. This is a deliberate trade-off in favour of a recording free of Vireks pixels.
• The 80 dp top-right corner is a tap dead zone during recording. Apps rarely place tap targets there (most place the close button / overflow menu a notch below), so conflicts are rare. v0.2 will add a Settings entry to relocate the zone.

11. Deep FAQ

What does Vireks record?

Only the device's screen frames produced by Android's MediaProjection API, plus (optionally) the microphone audio if you toggled it on. Nothing else.

Does Vireks record system / app audio?

Not in Vireks v1. v1 ships microphone-only, off by default.

What is the recording's resolution / bitrate / frame rate?

Vireks defaults to the device's native screen resolution, the device's natural refresh rate (capped at 30 fps for storage-friendliness), and a quality preset bitrate appropriate to the chosen codec. Resolution, frame rate, and orientation are exposed as Settings knobs with sensible device defaults.

What encoder does Vireks use?

Android's MediaCodec, configured for H.264 (AVC) by default and HEVC if you switch to the HEVC variant in Settings (where the device supports it). Audio is AAC at 128 kbps for MP4 output, Opus for WebM output. The muxer is MediaMuxer for both MP4 and WebM.

Can I record at 60 fps?

The Vireks v1 default is 30 fps. Whether 60 fps is exposed and works depends on your device's encoder capabilities; some mid-range devices reject 1080p60 H.264. v1 exposes the frame-rate knob with sensible defaults; v1.x may add a 60-fps preset where the device reports support.

What size will my recording be?

Roughly 30-40 MB per minute at 1080p H.264; roughly 18-25 MB per minute at 1080p HEVC. A maximum 5-minute Vireks recording therefore lands around 150-200 MB worst case.

Can I edit the recording inside Vireks?

No. Vireks does not include an editor. Use any third-party editor (Google Photos, CapCut, KineMaster, PowerDirector, FilmoraGo, DaVinci Resolve mobile, Premiere Rush, Vita).

Can I trim or rename a recording inside Vireks?

You can rename a saved recording (long-press the entry in the Recordings list). Trimming is not implemented in v1.

How do I share a recording?

Long-press the entry in the Recordings list and tap Share, or use any other Android app that reads from DCIM/VireksUserFiles/. The share goes through the standard Android share sheet — Vireks does not call out to anything by itself.

Does Vireks back up my recordings to the cloud?

No. Vireks has no network access. Your recordings live on your device in DCIM/VireksUserFiles/. If Google Photos is set to auto-backup that folder on your device, that backup is configured in Photos / Backup & sync, on your account — ZADIO EOOD is not involved.

What happens if I uninstall Vireks?

App-private storage is wiped (settings, the free-quota counter, the onboarding flags). Your recordings remain in DCIM/VireksUserFiles/ as normal MP4 files. Reinstalling Vireks on the same Google account restores the €5 unlock from Google Play automatically.

What happens if I clear app data?

Same as uninstalling, plus the free-quota counter resets. If you have already purchased the €5 unlock, the next time you launch Vireks it restores from Google Play and the counter is no longer consulted.

Can I move Vireks to an SD card?

Modern Android (8+) treats SD-card-installed apps as a per-OEM optional feature; if your device exposes it, you can move Vireks the same way you move any other app. The recordings always go to DCIM/VireksUserFiles/ on the storage volume Android picks as the “primary external” (usually the device's internal storage).

Is Vireks open-source?

No. Vireks is proprietary software. ZADIO EOOD reserves all rights. See the Content License.

Will there be an iOS version?

Deferred. iOS ships a built-in screen recorder in Control Center; a third-party paid alternative there competes against a free system feature, which is a different market dynamic. ZADIO EOOD will revisit iOS after Vireks v1 ships on Android and its commercial viability is validated.

Will there be a desktop version?

Not planned. There are excellent screen recorders for Windows, macOS, and Linux (OBS Studio, Camtasia, ShareX, QuickTime). Vireks is a phone-first product.

How can I report a bug?

Email app@zadio.bg with: your device model + Android version (Settings → About phone); the Vireks app version (Settings → About Vireks); a description of what you tried, what happened, and what you expected.

How can I request a feature?

Same email. We will not be able to land every requested feature in Vireks v1 (the product is deliberately minimal) but we read every request; especially noisy requests inform what we land in v1.x.

Does Vireks work with screen mirroring (Chromecast, Miracast, Samsung DeX)?

Yes, in the sense that Vireks captures the same logical display Android composites for you; if your phone is mirroring to another surface, Vireks captures the frames being produced for that display. Behaviour with multi-display setups varies by OEM; if you find a setup that doesn't work, email us.

12. Contact and legal

ZADIO EOOD · EIK 201209745 · VAT BG201209745
Registered seat: Ploshtad Han Kubrat 1, 7000 Ruse, Bulgaria, EU
Product / support: app@zadio.bg
Legal / partnerships: office@zadio.bg
Website: https://zadio.bg/vireks

Terms of Service · Privacy Policy · Refund & Withdrawal · Imprint · Copyright & Takedown · Content License · Cookie Policy