Privacy Policy

VK Backup · Last updated: 24 July 2026

The short version

VK Backup collects no data at all. There are no servers of ours, no analytics, no ads and no trackers. Everything runs locally in your browser, and your files download from VK’s servers straight to your Downloads folder.

1Who we are

VK Backup ("the extension") is a browser extension for Google Chrome that saves a copy of your own VKontakte content — photos, videos, documents, friends, groups and profile information — to your computer. It works through your own, already signed-in VK session on vk.com / vk.ru and the official api.vk.com interface. This policy explains what information the extension does — and, more importantly, does not — handle.

2What data we collect

None. The extension has no back-end. The developer operates no servers, no analytics, no advertising networks and no trackers of any kind, so there is nowhere for your data to be sent and nothing is ever collected, transmitted, sold or shared. Specifically, we do not collect:

The photos, videos, documents or lists you back up — they travel directly from VK’s own servers to your computer through Chrome’s download manager; the developer never sees them
Your VK account details, credentials, cookies or session — the extension uses the VK session already present in your browser, and nothing about it leaves your browser
Your browsing history or the addresses of pages you visit
Personal details such as your name, email address or identifiers
Usage analytics, telemetry or crash reports

Every step — reading your content through VK’s own interface, organising it and writing the files — happens locally, inside your browser, on your device.

3What is stored on your device

The extension stores only your own settings, a local record of your backups, and short-lived working data:

Your settings — what to include in a backup, file-naming and folder options, and similar preferences. These are kept in Chrome’s extension storage (chrome.storage.sync). If you have Chrome sync enabled, Chrome itself syncs them across your devices as part of your Google profile — the developer never sees them.
Backup history metadata — for each completed run, the date, the type of backup, the number of files, the total size and how long it took. This is kept locally in chrome.storage.local. It is a record of your own activity for your own reference; it contains no copies of your content and is never sent anywhere.
Your VK access token and transient run state — the token taken from your own VK session, plus the progress bookkeeping a running backup needs (what has already been fetched, what is next). These live in chrome.storage.session, which Chrome clears automatically when the browser closes. The token never leaves your browser and is only ever sent to api.vk.com — the official VK interface it belongs to.

Uninstalling the extension removes all of the above from your device. Your downloaded files stay where you saved them.

4Why the extension requests its permissions

Permission	Why it is needed
`storage`	Saves your settings, your local backup history and the short-lived session data described in section 3. Nothing is stored outside your browser.
`downloads`	Writes the backed-up files to your Downloads folder through Chrome’s normal download manager, with sanitized file names.
`notifications`	Shows a Chrome notification when a backup finishes or fails, so you don’t have to watch the progress window.
`alarms`	Keeps a long-running backup alive and lets it resume where it left off if the browser suspends the extension’s background worker.
`offscreen`	Turns the CSV, JSON, TXT and ZIP exports built on your device into files the download manager can save, using a hidden page in your own browser because the background worker cannot create them alone. Nothing is uploaded anywhere.
`Access to VK websites` (host permissions)	Limited to `api.vk.com`, `vk.com`, `.vk.com`, `vk.ru` and `.vk.ru` — needed to read your own content through VK’s interface and to fetch your files from VK. The extension does not request and has no access to any other website.

5Third-party services

VK is the only third party involved, and only because it is the service your content lives on. The extension talks to VK’s own websites and interfaces on your behalf, using your own session; anything VK does with those requests is governed by VK’s own privacy policy and terms, not by this one. There are no other third-party services, analytics providers, advertising networks or remote APIs — all of the extension’s code is bundled inside it and runs on your device.

6What the extension backs up

The extension only backs up your own content that is already visible to you while you are signed in to VK. It does not, and cannot, reach private content belonging to other people, and it does not attempt to circumvent any of VK’s access controls. Please respect VK’s terms of service and the copyright and data-protection law of your jurisdiction when keeping copies of anything that involves other people.

7Your control over your data

Uninstalling the extension clears everything it stored — settings, backup history and session data — from your browser.
Backup history can be cleared at any time from inside the extension, without uninstalling it.
Your downloaded files are entirely yours. They sit in your Downloads folder like any other file, and the extension neither reads them back nor keeps track of them.

8Children’s privacy

Because the extension collects no data from anyone, it collects no data from children. It is not directed at children under 13, and no age-related information is requested or processed.

9Changes to this policy

If a future version of the extension ever changes how data is handled, this policy will be updated and the "Last updated" date above revised before that version is released. Material changes will be noted in the extension’s store listing changelog.

10Contact

Questions about this policy or the extension? Contact the developer through the Chrome Web Store listing's support tab.