Privacy policy
This page says what leaves your device when you use the Sverk browser for Windows, Android and iPhone and the sverk.ai website, who receives it and what happens to it next. We describe what the browser actually does, from its code and network logs, not from a template.
In short
- Sverk asks for no sign-up and creates no accounts.
- History, bookmarks, passwords, tabs and settings stay on your device, and we never see this data. You can send an open page to another device of yours: it goes through our server encrypted, and only the receiving device can read it.
- Sverk collects no usage statistics and no data for advertising. We do not sell data or pass it on for advertising.
- Sverk checks dangerous sites against lists kept on your device: the addresses you open go nowhere.
- The Sverk server does not record IP addresses or the addresses of requests.
- What does leave your device is listed under “What leaves your device”: requests to the sites and services you use, update checks, blocking list downloads and crash reports unless you turn them off.
Who is responsible
The Sverk browser and the sverk.ai website are made by Destruction LLC. This policy covers Sverk for Windows, Android and iPhone and the sverk.ai website. You can reach us at support@sverk.ai.
What stays on your device
Your device keeps your history, bookmarks, open tabs, downloads, cookies and site data, form data, blocking settings and the list of sites where blocking is off, news feed settings, your list of AI chats and the last conversation for the widget.
On a computer and on Android, Sverk stores passwords itself, encrypted. On Android the encryption key sits in the system’s protected storage, and passwords are left out of cloud backups. On iPhone, Sverk stores no passwords: the system keeps and fills them, in the Passwords app.
Incognito tabs leave no history, cookies or form data once closed. Sites and your internet provider still see you as usual.
On iPhone, Sverk’s data is included in the device backup if you have backups turned on.
You can delete this data in Sverk’s settings, or by removing the app.
What leaves your device
Below is everything Sverk sends by itself or when you do something. “Our server” means the Sverk servers: update.sverk.ai, crash.sverk.ai, news.sverk.ai, components.sverk.ai and sync.sverk.ai.
| What is sent | To whom | When | How to turn it off |
|---|---|---|---|
| The page address, your IP address and whatever the site asks the browser for | The site you opened and the services it brings in | When you open a site | The blocker cuts out ads and trackers, not the site itself |
| What you type in the address bar | The search engine: Yandex by default in Russia and Belarus, Google elsewhere | While you type (suggestions) and when you search | Choose another search engine. On a computer and on Android, suggestions can be turned off in settings |
| Your questions and the conversation with AI | Google: the AI chat is Google’s AI Mode. If you signed in to a Google account in Sverk, Google sees that too | When you write in the AI chat — from the AI button, the new tab or a widget | Do not use the chat. The AI button can be turned off in settings |
| Page text in parts and the target language; on a computer and on Android, also the site address without the path | Yandex (Yandex Translate) or Google (Google Translate): on Android and on a computer, Yandex comes first for translations into Russian and Google first for any other language; if one does not answer, the text goes to the other. On iPhone, and in Sverk for computers before 155.0.8059.118, Yandex only | Only when you ask to translate a page or have turned on “always translate” for a language | Do not translate |
| Requests for translation keys — no page addresses, no page content. Yandex and Google see the IP address and the time | Yandex; on Android, and on a computer from 155.0.8059.118, also Google | Yandex: at most once every 20 minutes while you open pages, and again a minute later if neither translator answered. Google: at first launch, then once a day and after a failed translation | — |
| A page you sent to another device of yours: its address and title, encrypted on your device with the receiving device’s key. For linking devices: their numbers, public keys and platforms (Windows, Android, iPhone), and their names, encrypted with a key your devices share | Our server (sync.sverk.ai). It cannot read the pages or the device names: it sees which device writes to which, when, and how large the message is | When you link a device and when you send a page. While Sverk is open, a linked device waits at the server for new pages | Do not link devices. Disconnect a device or delete the link with all its data on the “Devices” page |
| Confirming a device linked through TG AI | Telegram or TG AI, and our bot @sverk_ai_bot: Telegram tells the bot which account pressed “Confirm”. Our server keeps not the account number but its hash with a secret key. All devices linked through one account form one link | Only when you link a device through TG AI | Link devices with a code or a QR code: then no Telegram account is involved |
| A signal that a page is waiting — no address, title or sender; on iPhone, with the fixed text “A page was sent to you” | The phone’s notification service: Google (FCM) or RuStore on Android, Apple (APNs) on iPhone. It sees the phone’s notification address and the time | When a linked phone has a page waiting and Sverk on it is closed or in the background — at most once every 10 seconds | Disconnect the phone from the link, or turn off Sverk’s notifications on the phone: the pages then arrive when you open Sverk |
| Sverk version and build, channel, system and its architecture, language, the days of the previous check and of the previous use — no install identifier | Our server | Update checks: about every five hours on a computer, on the browser’s own schedule on Android | Cannot be turned off. On iPhone there are no such checks: the App Store installs updates |
| Your IP address and the name of the file being downloaded | Content delivery networks: VK Cloud in Russia, Gcore elsewhere. Our server picks the network by your IP address and does not record it | When you download the APK from sverk.ai or an update of the site version of Sverk for Android, and when it downloads an interface language | Cannot be turned off. Versions from app stores download from the store |
| Blocker version, system and language — no page addresses | Our server | Blocking and dangerous-site list downloads: at launch, then from hourly to every five hours | Cannot be turned off: without fresh lists, blocking and warnings go stale |
| The list of the browser’s security components and their versions — for example, certificate revocation lists | Our server passes this request on to Google without your IP address, cookies or browser string. The component files themselves come from Google’s servers, and Google sees your IP address | Computer and Android: about a minute after launch, then every five hours | Cannot be turned off: without these components the browser would not learn of revoked certificates |
| The ids and versions of the extensions installed from the Chrome Web Store — no page addresses | Our server passes this request on to Google without your IP address, cookies or browser string. Extension updates download from Google’s servers, and Google sees your IP address | Computer, if you have extensions from the store: at launch, then every five hours | Cannot be turned off while extensions from the store are installed: without updates they would keep their vulnerabilities |
| The first 5 characters of the password’s SHA-1 hash. The password, login and site address are not sent | Our server. It checks the hash against the Have I Been Pwned breach database in its own name: the database sees our server, not you | Computer and Android: when you sign in to a site with a password and when you press “Check passwords”. Computer: also when you change a saved password, and on its own about every 10 days, for all saved passwords | In security settings: “Warn you if a password was compromised in a data breach”. “Check passwords” checks only when you press it |
| A request for the news feed for your region and language — no cookies, nothing about you | Our server | While the feed is open on the new tab, at most once every five minutes | Turn the feed off in settings. A feed that is off makes no requests at all |
| Requests for news pictures, small availability checks of sources, RSS of YouTube channels and of your own sources, videos in cards | Publishers’ sites, youtube.com and video services — directly, and they see your IP address | While the feed is on; videos when you press “▶” | Turn off the feed or its videos, remove the source |
| A crash report: Sverk, system and device versions, where in the code the error happened. On a computer and on Android, also a memory snapshot of the crashed process; on Android, the last lines of the app’s log. File paths and page addresses are removed from the report’s fields before sending | Our server | After a crash, at the next launch. On Android, only over Wi-Fi or an unmetered network | On by default. Turned off in settings: on a computer, on the “Browser services” page (profile menu → “Service settings”); on Android, “Crash reports” |
| Sverk and system versions; on Android, also the phone model. On iPhone these details are not sent | Telegram or TG AI, and our support bot @sverk_supportbot | When you press “Contact support” | Do not press it: you can find the bot yourself, and then no device details are sent |
| A voice recording | The speech recognition app on your phone and its developer — for example, Google | Android: only when you tap the microphone. Sverk warns you about this the first time | Do not use voice search |
| Form data on sites | The autofill service you chose on your phone: Google, Yandex or another | Android: only if you turned on “Passwords from this phone” | Turn autofill off |
| A request for the exact time | Google (clients2.google.com) | Computer and Android: only on a certificate error that may mean a wrong clock | — |
| A check whether a Wi-Fi network wants you to sign in | Google (connectivitycheck.gstatic.com) | Computer: only on a secure connection error | — |
| Requests a feature cannot work without | Google: the Chrome extension store, postal address formats, signing in with a passkey from a phone, the Live Caption model | Computer: only when you install an extension, edit an address in autofill, sign in with a passkey from a phone or turn on captions | Do not use that feature |
Sites, search engines, Google, Yandex, VK Cloud, Gcore, Telegram and TG AI handle what they receive under their own rules: Google’s privacy policy, Yandex’s privacy policy, VK Cloud’s privacy policy (in Russian), Gcore’s privacy policy, Telegram’s privacy policy, TG AI’s privacy policy.
What we keep on our servers
| What | How long |
|---|---|
| Records of update checks: time, version, channel, system, architecture, the version offered, the days of the previous check and of the previous use | Indefinitely: they show how many installs run which version and how many of them are in use |
| Memory snapshots from crash reports | 90 days |
| Crash report summaries: version, system, type and place of the error, report fields | Indefinitely: they show whether an error has been fixed |
| Breach database answers for the first 5 characters of a hash | 7 days |
| The server’s own log: errors and events | Until the server is next updated |
| The connection error log | Up to four days |
| Support requests: your Telegram identifier, first name, last name and username, the conversation, links to the files you send, their names and details about them (type, size, duration; the files themselves stay in Telegram), and the Sverk version and device details from the link. If you started the bot from Sverk’s link but wrote nothing, we keep only your identifier and the device details | While the request is open and for 12 months after it is closed or, if you only started the bot, for 12 months after you started it; sooner if you ask |
| The link of your devices: the link’s and the devices’ numbers, their public keys and platforms, the membership log, encrypted names and the hour of last contact; for devices linked through TG AI, a hash of the Telegram account number with a secret key | While the link exists. “Delete the link and all my data” on the “Devices” page erases it |
| Sent pages not yet delivered to the receiving device, encrypted | Until delivered, and no longer than 10 days |
| Phones’ notification addresses (FCM, RuStore, APNs) | While the phone is in the link and Sverk’s notifications on it are on |
Besides our servers, part of a request is copied into the Telegram of our support staff: the bot sends them notifications about new requests and messages (your name, @username, device details and the start of the message), and a staff member may forward a file you sent to their own Telegram. These copies are not deleted automatically: if you ask, we delete them by hand together with the request.
We have no user accounts, cookies or user profiles. Only support requests are tied to a person, through the person’s Telegram account, and so is a link of devices made through TG AI, through a hash of the person’s Telegram account number; no other record on our servers is tied to a particular person.
The sverk.ai website
The site sets no cookies, loads nothing from third-party servers and uses no analytics or counters. Its pages come from the same Sverk server, which does not record your IP address.
If you write to us at support@sverk.ai, we see your e-mail address and your message and use them only to reply.
What Sverk does not do
- it creates no accounts and does not keep your history, bookmarks or passwords; pages between your devices travel only encrypted;
- it sends no usage statistics: on a computer and on Android, the statistics collection built into Chromium sends them nowhere, and Sverk for iPhone does not have it;
- it does not use Google Safe Browsing: dangerous sites are checked on the device;
- it includes no advertising or analytics libraries;
- it does not sell data or pass it on for advertising.
App stores
If you install Sverk from RuStore, Google Play or the App Store, the store collects its own data — for example, about installs and purchases — under its own rules. From the stores we get only aggregate statistics, nothing about particular people.
Children
Sverk is not designed specifically for children. We create no accounts and ask nothing about age or identity.
Your rights
You can ask what data of yours we have and ask us to correct or delete it. Write to support@sverk.ai and we will reply within a month. We will find your support requests by your Telegram account and delete them if you ask, together with the notifications and forwarded files in the Telegram of our support staff — write to the support bot or to support@sverk.ai. The other records on our servers are not tied to a person, so most of the time there is no way to find “yours” among them. If you think we hold your data, write to us and we will look into it.
You can turn crash reports off at any time, and delete the data on your device in Sverk’s settings. “Delete the link and all my data” on the “Devices” page removes your link of devices and everything the server keeps about it.
Changes to this policy
If Sverk starts sending something new, we update this policy no later than the release that does it. A new version appears on this page with the date it takes effect.