Documents
Personal data policy
DraftDraft, not in force. Operator: fill in: operator’s legal entity; a lawyer reviews the text before launch. In the demo the site collects nothing: requests go nowhere and are stored nowhere. This is a translation; the Russian text is the legally binding one.
AbsoHome collects about people only what a listing, a request and a stay cannot work without. The exact address of a home is stored separately and opens only to a guest with a confirmed stay. Data are stored in Russia. This policy sets out what is collected, why, who sees what, where it is stored and for how long.
Contents
1.Operator
- 1.1
The personal data operator is fill in: operator’s full legal name, OGRN (state registration number) fill in: OGRN, INN (taxpayer number) fill in: INN, address: fill in: registered address. Number in the Roskomnadzor (Russian data protection authority) register of operators: fill in: register number. The notification is filed before processing starts (Federal Law 152-FZ on personal data, art. 22 part 1).
- 1.2
Email for personal data requests: fill in: operator’s email.
- 1.3
AbsoHome and Absolute are separate products. Home addresses and stay dates are not passed to Absolute’s database. When Absolute membership is checked, the following is compared: fill in: which data are compared with Absolute and on what basis.
2.Principles
- 2.1
Minimum: only what is needed for a listing, a request, a stay, a review and handling a complaint is collected.
- 2.2
Privacy is held by the database, not by a form. The exact address lies in a separate table that neither visitors nor members can access. Only a database function hands it out, and only to a guest with a confirmed stay.
- 2.3
Everything is stored in Russia: recording, systematising, accumulating and storing data of Russian citizens in databases abroad is not permitted (152-FZ art. 18 part 5).
- 2.4
The site has no foreign analytics and no third-party trackers; fonts are served by the site itself.
- 2.5
Passports, document scans and biometrics are not collected. Biometrics cannot be compulsory (Federal Law 572-FZ on biometric identification, art. 3 parts 11–12), and checks do not need them.
3.Host data
- 3.1
Name, phone number, the “Absolute member” mark.
- 3.2
The exact address and coordinates of the home, entrance, floor, flat number, how to find the door — in a closed table.
- 3.3
The public district: a cell of the H3 hexagonal grid and the name of the district.
- 3.4
Photos and videos of the home — without location metadata (EXIF). Photos that reveal the place (facade, view from the window) open only after confirmation. The video walk-through for verification is deleted after the moderator’s decision.
- 3.5
Description, house rules, form, price and currency, deposit terms, the guest house register number where required.
- 3.6
The occupancy calendar; for house-sitting and exchange, the dates when the home stands empty.
- 3.7
Verification results: method, date, moderator, verified name. The check of the right to let: type of document, date, moderator. No copies of documents are kept.
- 3.8
The address log: to whom and when the address is opened.
- 3.9
Statistics of answers to requests: the share answered and the time to answer.
4.Guest data
- 4.1
Name, phone number, the “Absolute member” mark.
- 4.2
Requests: dates, number of guests — how many adults, children and pets, without names or ages — the request text, arrival time.
- 4.3
History of stays and their statuses, including cancellations and no-shows.
5.Common to host and guest
- 5.1
Reviews and answers to them; private notes to the team about safety.
- 5.2
Complaints and dispute materials: photos, estimates, correspondence — with the parties’ consent to the review.
- 5.3
Accepted versions of documents and consents, with dates.
- 5.4
Pauses, restrictions and the log of the team’s actions.
- 5.5
Technical records: fill in: list of technical cookies and server logs, and how long they are kept.
6.What AbsoHome does not collect
- 6.1
Passports and document scans: the host takes the document for guest registration personally at check-in.
- 6.2
Biometrics.
- 6.3
Key box and lock codes, Wi-Fi and alarm passwords: the host passes them personally on the day of arrival.
- 6.4
Health information. “There are animals” is a property of the home, not a questionnaire for the guest.
- 6.5
Visitors’ geolocation: if it is needed to search for homes nearby, it stays in the browser and is not stored.
7.Why
- 7.1
Sign-in by mobile phone number with a code sent by SMS (149-FZ art. 8 part 10) and the check of Absolute membership.
- 7.2
Publishing a listing and showing it on the map as a district, not a house.
- 7.3
Passing the request to the host, the answer and confirmation; handing the exact address and phone numbers to the parties after confirmation.
- 7.4
Reviews, complaints and disputes, safety of guests and hosts, measures against fraud.
- 7.5
Moderating listings and checking the right to let.
- 7.6
There are no advertising mailings. If they ever appear, only with separate consent.
8.Legal grounds
- 8.1
Consent to personal data processing is a separate document, not part of the rules and not part of this policy (152-FZ art. 9 part 1 as amended by 156-FZ, from 01.09.2025).
- 8.2
Publishing a listing and a review — under a separate consent to dissemination (152-FZ art. 10.1).
- 8.3
Passing the phone number and address to the other party after confirmation — to perform the agreement with the user, that is, the platform rules (152-FZ art. 6 part 1 cl. 5).
9.Who sees what
- 9.1
A paid listing is visible to fill in: all site visitors or only signed-in members — owner’s and lawyer’s decision: the host’s name, district, photos, description, rules, form, price and reviews. Listings without money — only to signed-in members. The host’s surname before confirmation: fill in: shown or not.
- 9.2
Dates when a home stands empty — only to signed-in members and only by month.
- 9.3
Before confirmation the host sees the request: the guest’s name, the “member” mark, dates, number of guests, the message and reviews of the guest. After confirmation, the guest’s phone number.
- 9.4
After confirmation the guest sees the exact address — from confirmation to the day after departure — and the host’s phone number. Every opening of the address is logged; the host can see who opens it and when.
- 9.5
The AbsoHome team — by role: a moderator sees what a check or a complaint needs, and every action is logged.
10.Where and for how long
- 10.1
Data are recorded and stored on a server in Russia: fill in: hosting provider and data centre city.
- 10.2
The exact address is deleted together with the listing. The address log is anonymised after fill in: period — agreed with the lawyer.
- 10.3
An account and its data — while the account is open and fill in: period after it closes. Reviews — fill in: period. Dispute materials — fill in: period.
- 10.4
The video walk-through — until the moderator’s decision, then deleted.
11.Who receives data
- 11.1
The other party to a stay — only after confirmation and only what is listed in “Data passed to host and guest”.
- 11.2
The SMS provider — the phone number for the sign-in code: fill in: SMS provider.
- 11.3
The hosting provider — as the place of storage: fill in: hosting provider.
- 11.4
The map tile server — the browser’s IP address when the map loads: fill in: map tile server for the working version and its country.
- 11.5
The police and other authorities — on request, in cases set by law.
- 11.6
Absopit, insurers and advertising networks — no.
- 11.7
A host outside Russia — on the same terms. A cross-border transfer is a transfer to the territory of a foreign state, to a foreign authority, a foreign individual or a foreign legal entity (152-FZ art. 3 cl. 11), so passing data to a host who is a Russian citizen is probably not cross-border: fill in: classification — lawyer’s answer. Vietnam is on the list of countries with adequate protection of the rights of personal data subjects (Roskomnadzor order No. 128 of 05.08.2022). Until a Vietnamese lawyer answers, hosts on Phu Quoc are Russian citizens only, and the data stay in the database in Russia.
12.Rights
- 12.1
To learn which data are stored and get a copy. To correct inaccurate data. To demand deletion or blocking of what is no longer needed for the purpose. To withdraw consent.
- 12.2
To take down a listing and demand that dissemination stop — at any moment (152-FZ art. 10.1 part 12).
- 12.3
Requests go to fill in: operator’s email. The answer comes within the period set by 152-FZ.
- 12.4
If the answer is not satisfactory, a complaint can be made to Roskomnadzor.
13.Version
- 13.1
Anything new the site collects about people or shows to others appears in this policy first. A new version is published on this page; earlier versions are kept.
- 13.2
Version of fill in: version date.