152-FZ and hosting: where to store the data

If a website or service collects personal data of Russian citizens, that data must be recorded and stored in databases located in Russia: this is Part 5 of Article 18 of Federal Law No. 152-FZ. For choosing a VPS, this means the data centre's country matters, not the host's, and copies abroad fall under separate rules. Here is what the law requires, what duties fall on the server owner, how it applies to companies outside Russia and which setups are used in practice.

Updated 06.11.2026 · Find a VPS for your needs →

Federal Law No. 152-FZ "On Personal Data" is Russia's general data protection law. It concerns almost any project with an order form, sign-up, CRM or mailing list whose users include Russian citizens, and it is not limited to Russian companies. Under Article 3 of the law, personal data is any information relating to an identified or identifiable person: a name and phone number, an email address, a delivery address, an order history. Whoever decides why and how it is processed is the operator, the Russian counterpart of a controller. For a company's website that is the company itself, not the host or the developer. Below is what the law requires of where data is hosted. This is an overview of the rules, not legal advice: check your specific processing with a lawyer.

What Part 5 of Article 18 requires

Since 1 July 2025, Part 5 of Article 18 is worded as a direct prohibition: when personal data is collected, including over the internet, recording, systematisation, accumulation, storage, updating and retrieval of data of Russian citizens using databases located outside Russia are not allowed. The exceptions are narrow and listed in Article 6: processing for the purposes of an international treaty or a law, for the administration of justice, for the exercise of powers of state bodies and for the professional activity of journalists and the media. User consent is not on this list, so a "I agree to my data being stored abroad" checkbox does not lift the requirement.

In practice the law is read like this: the first record of a Russian citizen's data must go into a database physically located in Russia, and that database remains the primary one. If the data is later copied abroad, that is a cross-border transfer with its own rules, covered below.

What this means for choosing a VPS

What matters is the country of the data centre where the server with the database stands. The country where the host is registered is irrelevant for this requirement: a British company with a data centre in Moscow is fine, a Russian company with a server in the Netherlands is not. How else the company's country differs from the server's country is covered in the article Hosting provider jurisdiction.

According to the accsly.io catalog as of November 2026, 218 of the 1,934 VPS hosts with a known location, or 11%, have servers in Russia. 78 of them operate only in Russia, while the other 140 also offer locations abroad. So at one host a Moscow plan and a Frankfurt plan can sit side by side: check the country of the specific plan, not the brand. Russian servers are most often in Moscow (149 hosts), followed by Saint Petersburg (33), Novosibirsk (23) and Kazan (11). Plans are collected in the selections VPS in Russia and VPS for 152-FZ.

Besides the main server, check everything else where data is also written:

  • the host's backups: in which data centre and country they are kept;
  • managed databases and storage: their location may differ from the VPS location;
  • external services: CRM, mailing services, forms, support chats and analytics systems that store visitor data themselves;
  • logs: if a proxy abroad sits in front of the site and logs request bodies with form contents, the data ends up there too.

The operator's duties

A server in Russia is only one requirement among several. The operator must also:

  • Notify Roskomnadzor, the Russian data protection authority, before processing begins, under Article 22. There are few exceptions to this duty. Among other things, the notification states where the database with data of Russian citizens is located, so find out the data centre's address from the host in advance. The notification is filed through the Roskomnadzor personal data portal.
  • Take security measures under Article 18.1 and Article 19: a processing policy, a responsible person, an assessment of threats and of the required protection level, access control, an inventory of media, backups. On an ordinary unmanaged VPS, almost all of this is done by the customer, not the host: updates, a firewall, keys instead of passwords, login logs. Where to start is described in the article First 10 steps after buying a VPS: security.
  • Put a processing instruction in place if another party carries out the processing. Under Part 3 of Article 6, it lists the operations on the data, the purposes and the security requirements, much like a data processing agreement. The law does not say directly whether a host that only rents out a server and has no access to its contents processes the data. With managed services, such as administration, databases or backups with access to files, an instruction is definitely needed. Many Russian hosts sign one on request.

Cross-border transfer

Transferring data abroad is allowed, but under the rules of Article 12. Before the transfer begins, the operator sends Roskomnadzor a separate notification, having first obtained from the foreign recipient information on its security measures, the conditions for ending the processing and its contact details. Roskomnadzor reviews the notification within ten working days. Data may be transferred to countries on the list of those providing adequate protection immediately after the notification; to other countries only once this period has passed, if the transfer has not been prohibited or restricted.

A cross-border transfer is not only moving the database. A backup copy on a foreign server, exporting orders to a foreign CRM, sending mailings through a foreign service: all of these are transfers of data abroad. Each such chain must be stated in the notification.

If your company is outside Russia

The localisation requirement follows the data of Russian citizens, not the operator's country, so it can also concern a company in the EU, the UK or elsewhere that collects such data from Russian users. Your own law applies on top of it. In the EU this is the GDPR, and in the UK the UK GDPR: neither requires the server to be in a particular country, but both require a data processing agreement with the host and a lawful basis for transfers outside their territory. How these rules apply to renting a server is covered in the article GDPR and choosing a host.

Typical setups

  • Everything in Russia. The site, database, backups and mail run on servers in Russian data centres. The simplest setup with the least paperwork. For copies, take a second server from another Russian host, so that one incident does not destroy both the data and the copy; more in the article VPS backups.
  • Database in Russia, front end abroad. Static pages and images are served from a foreign server or a content delivery network closer to the audience, while forms, the shopping cart and the account area send data directly to the server in Russia. The setup works but needs discipline: no form may store or log data on the foreign part.
  • Primary database in Russia, replica abroad. Suitable for projects with an audience in several countries. The primary record goes to Russia and a replica goes abroad after the cross-border transfer notification.
  • A foreign project with Russian users. If the service collects data of Russian citizens, the localisation requirement applies to it as well; one option is a separate server in Russia for those users. For data of EU residents, the European rules are added on top.

Employees' data in accounting and HR systems is personal data too. If a Russian company pays for the server, the documents it receives when paying by invoice are covered on the page VPS paid by invoice.

What to ask the host

  • the data centre address for the chosen plan, which is needed for the Roskomnadzor notification;
  • where the host keeps its own backups and whether you can choose their location;
  • whether the host signs a processing instruction or a confidentiality agreement;
  • whether the host holds FSTEC licences (issued by Russia's technical security regulator) and offers a certified secure segment, if your protection level requires certified tools;
  • which closing documents it issues to companies.

FAQ

Do personal data of Russian citizens have to be stored on a server in Russia?

Yes, if you collect them: under Part 5 of Article 18 of Federal Law No. 152-FZ, recording, storing and retrieving data of Russian citizens in databases outside Russia during collection is not allowed. The exceptions are narrow, and user consent is not one of them.

Does 152-FZ apply to a company outside Russia?

The localisation requirement is tied to the data of Russian citizens, not to the company's country, so a foreign service that collects such data falls under it too. Its own law, such as the GDPR or UK GDPR, applies in addition.

Is a foreign host with a data centre in Russia suitable?

For the localisation requirement, what matters is the country where the database is, not the company's country. A server in a Russian data centre run by a foreign host meets the requirement, but check where its backups are kept.

Can backups be stored abroad?

Yes, if the primary database is in Russia, but a copy abroad is a cross-border transfer. Before it starts, Roskomnadzor must be notified separately under Article 12 of the law. Keeping copies on a second server in Russia is simpler.

Does the Roskomnadzor notification have to include the data centre address?

Yes, the processing notification states where the database with data of Russian citizens is located. Get the address from the host before filing the notification.

Can the site be abroad and the database in Russia?

This setup is possible if forms send data straight to the Russian server and the foreign part neither stores it nor writes it to logs. If the data stays on the foreign server, that is already recording into a database outside Russia.

Plans on this topic

VPS/VDS in MoscowVPS/VDS in Saint PetersburgBest VPS hosting in Russia 2026

More in the guide

  • CDN: when a website needs oneA CDN stores copies of a site's files on servers around the world and delivers them to each visitor from the nearest one. This speeds up loading of images, scripts and video and takes load off your server, but it does not make a slow CMS faster and does not replace choosing the right country for your server. Here is when a CDN is really needed and when a single VPS in the right place is enough.
  • Domains and DNS for a server ownerYou can switch servers in an evening, but a domain stays with a project for years. Through DNS, the domain points to your server, your mail and third-party services, and a single wrong record can take the site offline or send your emails to spam. Here are the records a VPS owner will need, how caching works, where to keep the zone and how to move to a new server without visitors noticing.
  • SSL certificates: free and paidA free certificate encrypts the connection just as reliably as a paid one: browsers make no distinction between them in terms of security. The difference lies in what the certificate authority checks, how long the certificate lasts and who is responsible for renewing it. According to the accsly.io catalog as of November 2026, free SSL is explicitly listed in 1,449 shared hosting plans from 178 hosts. Here is when that is enough and when a certificate is worth paying for.
  • GDPR and choosing a hostThe EU General Data Protection Regulation (GDPR) does not require data to be kept in the EU, but it does require a data processing agreement with the host and a lawful mechanism for any transfer of data out of the EU. According to the accsly.io catalog as of November 2026, 61% of VPS hosts have servers in the EU, but almost half of them are registered outside the European Economic Area. Here is why that matters and what to check in the terms.
  • Hosting provider jurisdiction: what it affectsEvery server has two countries: the one where the data centre stands and the one where the company renting it out is registered. According to the accsly.io catalog as of November 2026, these are different countries for 15% of VPS hosts. The first determines latency and the rules on where data is stored; the second determines the law of the contract, the court for disputes, the documents your accountant receives and whose authorities can request your data. Here is what each of them changes.
  • How to compare VPS prices: the price of a resource unitA plan's price tells you how much you will pay, but not how much you get for that money. According to the accsly.io catalog as of November 2026, a gigabyte of memory on a 1 GB plan costs a median $8.00 a month, while on a 4 GB plan it costs $5.00. Here is how to work out the price per vCPU, per gigabyte of memory and of disk, and what to bring to a common basis before you compare two offers.
  • SLA and uptime: what hosts promiseAn SLA of 99.9% allows a host 43 minutes of downtime a month, 99.99% about four. But a percentage in an advert is not yet a commitment: the commitment is the document that says what counts as downtime, what is excluded and how much you get back. Most often that is a discount on the next invoice, not money. Here is how to read such documents and how to check availability yourself.
  • Free trials and money-back guaranteesThere are two ways to test a server before paying for a month or a year: a free trial or a money-back guarantee. According to the accsly.io catalog as of November 2026, 11% of VPS hosts offer a trial and 36% a money-back guarantee. But at many of them the terms apply only to shared hosting, only to the first order or only to card payments. Here is what to check so that the guarantee actually works.
  • Cloud server or VPSA cloud server and a VPS are usually the same KVM virtual machine. The difference lies in what surrounds it: a cloud sells resources by the hour through an API and offers network disks, snapshots and ready-made services, while a classic VPS is a fixed monthly plan with a local disk and a traffic allowance. Here is which of this you actually need and what it costs.
  • Dedicated server or VPSA VPS is a slice of a physical server, a dedicated server is the whole machine. With 4 cores and 8–16 GB of memory a VPS costs almost half as much, with 4 cores and 32 GB the prices are equal, and with 64 GB on 8 cores or 128 GB on 16 cores a dedicated server in the catalog is a third cheaper than a virtual one. Here is what else changes besides the price: neighbours, guarantees, delivery time, hardware failures and remote management.
  • Shared hosting or VPS for a websiteShared hosting is a ready place for a site where the host looks after the server. A VPS is your own server where you set everything up. For a landing page or an ordinary WordPress site, hosting is enough and costs several times less. You need a VPS when the account limits are too tight for the site or when it needs software that hosting does not allow. Below is what each option includes, what it costs and a table to help you choose.
  • DDoS protection: what hosting providers actually give youEvery second host now lists "DDoS protection" in its plans. Behind that line there may be multi-terabit filtering, or only the right to take your address offline when an attack bothers the neighbours. Here is what protection is made of, how L3/L4 differs from L7, and how to tell from the contract what you are buying.
  • Mail server on a VPS: SPF, DKIM, DMARCInstalling Postfix or a ready-made bundle like Mailcow on a VPS takes an hour. Getting your mail into the inbox rather than spam is harder: mailbox providers look at the port, the server's address, its reputation and three DNS records. Here is what to check with the host before buying and how to set up SPF, DKIM and DMARC.
  • Server monitoring: uptime, load, alertsWithout monitoring you learn that the server is down from your visitors, and that the disk is running out when the database stops writing. A few checks from outside and a dozen metrics from inside are enough to see a problem before users do. Here is what to measure, where to run checks and how to do it for free.
  • How to read hosting plans: the hidden limitsA plan card shows cores, memory, disk and a monthly price. Yet two plans with identical numbers can cost different amounts a year later and behave differently under load. The difference lies in terms printed in small type, in the acceptable use policy, or only in the contract. Below are eight places worth checking before you pay.
  • IPv4 and IPv6 on a serverA typical VPS has one public IPv4 address and, if the host supports it, an IPv6 subnet. An extra IPv4 address almost always costs money, and the cheapest plans sometimes come without their own IPv4 at all. Here is where the shortage comes from, what you can do with IPv6 alone and which address settings a mail server needs.
  • Bandwidth and traffic: what 1 Gbps and unlimited really meanA server plan usually has two network lines: port speed and traffic volume. The first says how fast the server can send data, the second how much it can send in a month. They are linked by simple arithmetic, and once you know it, it is easy to see what "1 Gbps unlimited" actually offers and whether "5 TB" will be enough for you.
  • Docker on a VPS: getting startedDocker lets you run a bot, a website, a database and monitoring on one server without them getting in each other's way, and moving to another VPS comes down to copying a couple of files and the data. Installation takes five minutes; the real trouble starts later: database ports exposed to the internet, logs growing to tens of gigabytes and data that vanished along with a container. Here is how to avoid all of that from the start.
  • How to move a website from shared hosting to a VPSThe move itself takes a couple of hours; the mistakes usually happen around it: a forgotten cron job, .htaccess rules that nginx does not read, an AAAA record with the old address, or mail that disappeared along with the IP change. Below is the order of steps with commands and checks for a PHP and MySQL site.
  • Server control panels: ISPmanager, FASTPANEL, aaPanelA panel turns a VPS into the kind of dashboard you know from shared hosting: sites, databases, mail and certificates are set up with a few clicks instead of editing config files. The three panels most often installed on Russian and budget international servers are ISPmanager, FASTPANEL and aaPanel. They differ in price, memory requirements and how much of the server they take over.
  • Windows VPS for 1CA rented server for 1C saves you from the office PC under a desk that nobody updates or backs up. But 1C on a VPS has its own quirks: the software licence is tied to the parameters of the virtual machine, users need both 1C and Windows licences, and core speed matters more than core count. Here is how to put together a 1C server for a small company.
  • Windows VPS: licensing, RDP and secure sign-inA Windows server costs more than Linux not only because of memory: the price includes a licence, and how it is arranged decides whether you are compliant and how many people can connect. An exposed RDP port is also the most common way such servers get hacked. Here are both topics.
  • When to move from shared hosting to a VPSA VPS does not make a site faster by itself: it gives you resources and freedom, and with them the job of running a server. Here is how to tell that hosting has become too small, when the problem can be solved without moving, and how to migrate a site so visitors notice nothing.
  • VPS backups: strategies and toolsOn a VPS, backups are your job, even if the plan says "backups included". We go through what exactly to back up, why a host snapshot is not enough, how to set up restic or BorgBackup in half an hour, and how to make sure you can actually restore from a backup.
  • First 10 steps after buying a VPS: securityBots start guessing passwords on a new server within minutes of it getting a public IP. Below are ten steps that close the most common holes in about an hour: commands for Ubuntu and Debian, the differences for AlmaLinux and Rocky Linux, and the checks that keep you from locking yourself out of your own server.
  • How to choose a country for your serverPut the server where your visitors are. For an audience across Europe, Germany, the Netherlands and Finland are convenient; for North America, the US East Coast. If you serve EU users, keeping the data in the EU makes GDPR simpler. Price hardly decides it: at the same host a server in Frankfurt, Amsterdam or New York usually costs the same, and only Asia and Australia are noticeably more expensive.
  • Hourly billing: when it pays offHourly billing pays off if you need the server for less than three weeks a month: for a test, a build, a one-off heavy job. At most hosts an hour costs exactly the monthly price divided by 730 hours, so over a full month you hardly overpay. The overpayment hides elsewhere: hourly plans are dearer on average, and for a server that runs all year, monthly billing or a year paid in advance usually comes out cheaper.
  • How much RAM and how many cores a website needsMost websites are fine with 2 GB of memory and one or two cores; a shop with thousands of products needs 4 GB and two cores. Memory matters more than cores: when it runs out, the site slows down or crashes, while an extra core without memory adds almost nothing. Below I show how to work out the memory for your site and how to see what it actually uses.
  • KVM or OpenVZ: which to chooseIn 2026 KVM is almost always the right pick: it costs a dollar or two more per month than OpenVZ, but everything runs on it, from Docker to Windows. OpenVZ makes sense in one narrow case, explained below, and at the end you will find the commands to check your own server in a minute.
  • NVMe or SSD: does it matter for a websiteFor a small site the difference between NVMe and SSD is barely noticeable, because pages are served from memory rather than from disk. It shows up in shops and sites with a large database. At the same host NVMe costs only about $0.50–1 a month more, and sometimes less, so what usually decides it is not the disk type but its size and how the host has limited it.
  • What is a VPS, in plain EnglishA VPS is a slice of a powerful physical server that you rent and that behaves like a separate computer, with its own operating system, its own IP address and full control. Below is how it differs from shared hosting, who needs one, what it costs and what to check right after you buy it.
  • VPS for a Telegram bot: what the bot needs and how to pick a planA bot with a menu and a few commands runs fine on the cheapest server, while a bot with broadcasts, files and a database hits completely different limits. Here is what a bot really consumes, which Telegram limits shape the choice of server and how to avoid overpaying.
  • How to test VPS ping and speed before you payThe numbers in a plan do not tell you the latency to your users or how fast the disk really is. Most of this can be measured before you pay, the rest in the first hour after launch. Here are the tools and how to read the results.
  • Corporate network on a VPS: remote access to the officeA rented server can become the hub of a company's private network: remote employees and branch offices connect through it to the ERP, file server, CRM and Git. Here are the common layouts, protocols, server requirements and security basics.
  • How to choose a VPS: the 7 specs that matterTwo plans with the same "2 cores, 4 GB, 50 GB" can differ several times in speed and twice in price a year later. Here is what stands behind each line of a VPS plan and what to check before you pay.
  • VPS vs VDS: is there a difference and what actually mattersIn most markets VPS and VDS mean the same thing: a virtual server. The difference that really affects your work is hidden not in the name but in the virtualization type and whether resources are guaranteed.