This is an earlier version of this document, version 2026.11. It applied from 16 November 2026 through 18 November 2026. See the version in force
Privacy Policy
Effective 16 November 2026
Contents
1. Who we are and how to write to us
2. What data we collect and where it comes from
3. Identity check through Evrotrust
4. Payments
5. Technical data
6. Analytics and advertising
7. What others see
8. Why we process data and on what legal basis
9. Who we share data with
10. Transfers outside the EEA
11. How long we keep data
12. Deleting your account and getting a copy of your data
13. Your rights
14. Automated decisions and profiling
15. How we protect data
16. Only for people aged 18 or over
17. Changes to this policy
18. Contact
Here we explain what personal data we process when you use Strehana, why, who sees it, who we share it with, how long we keep it and what rights you have. This policy covers the website strehana.com and the Strehana apps for Android and iOS.
1. Who we are and how to write to us
The controller of your personal data is Vizium EOOD (Визиум ЕООД), the company that runs Strehana. When this policy says "we", it means Vizium EOOD.
- Company number (ЕИК) 208647543
- Registered office and address of management: 1618 Sofia, Vitosha district, 87 Ralevitsa St, entrance A, floor 3, apartment 307, Bulgaria
- Email: legal@strehana.com
- Phone: +359 876 168 215
We have not appointed a data protection officer. For any question about your personal data, write to legal@strehana.com.
2. What data we collect and where it comes from
We collect the data you give us, the data created while you use Strehana, and the data we receive from the partners described here.
An account to sign in with Google, Apple or email
You sign in with Google, with Apple or with a code we email you. We have no passwords.
From Google we receive your Google account id, your email address, your name and your picture. From Apple we receive your Apple id, your email address (or the hidden address Apple creates for you) and, on the first sign-in only, your name.
We keep your email, the ways you sign in (Google, Apple or an email code), your identifier with Google and Apple and when the account was created. If you change your email at Google or Apple, we update it the next time you sign in.
On your first sign-in with Google we copy the picture from your Google account as a photo on your Strehana profile. We do this once per account.
When you sign in with Apple through the app, we keep the token Apple gives us, so that we can end our access at Apple when you delete your account.
We also keep whether the account is suspended or banned, until when and for what reason. If the account is restricted as linked to a banned account (Terms, section 14), we keep when and how it was restricted (automatically or by our team), by which signals and to which banned account it is linked, and when the restriction ended.
When you sign in with an email code, we keep the code hashed and the IP address it was requested from for 24 hours, to limit sign-in attempts.
If an attempt to create an account in the app comes from a banned account's device, we refuse the sign-in. The new account's record stays, marked «blocked device» and linked to the banned account, so that a person on our team can review it.
Profile
The name on your profile is the one Google or Apple gave us, or the one you type in. You can change it. We also keep what you fill in:
- photos
- date of birth and gender, optional (after the identity check they come from your ЕГН, see section 3)
- whether you study, work or both
- languages
- a text about you and about the flatmate you are looking for
- habits: smoking, pets, how social you are, daily routine, working from home and working hours, how often guests come over, whether you are part of a couple
- up to 5 personality traits and up to 3 interest groups
While you use Strehana we create and keep: whether you are online and when you were last active, how quickly you reply to messages (average time and a score), how complete your profile is (a score from 0 to 100), what you are looking for on Strehana, and internal dates for your first steps, for example since when you have been looking for a room.
We keep when you accepted the Terms of Service and this policy, and which version.
Card
Your card says what you are looking for. In it we keep:
- your maximum monthly budget
- your move-in date and for how long you are looking
- your text (up to 500 characters)
- the places you chose: a neighbourhood, a city or a point on the map (for example a place or an address), with a radius
- whether you accept buddy-ups
- whether your photo is shown on the card
- the card's status and dates, and whether it is featured and until when
Alongside the card we also keep how many different signed-in people have seen it, a snapshot of your profile completeness score, a copy of your gender and whether you smoke (for the deck's filters), and the reason if our team restricted it.
The name, age, photo and habits others see on the card are not stored in it. We take them from your profile when the card is shown.
Room listings
When you publish a room, we keep everything in the listing:
- title, description and photos
- the exact location of the home: the point on the map and the address or place name you chose
- the rooms: name, description, size, rent, deposit, available from, bed, photos, for how long they are let
- the home: floor and number of floors, parking, accessibility, bills, rules on smoking and pets
- who lives there: number of people, ages, whether the host lives in the home, type, gender mix and atmosphere of the household, children and how many, pets, languages
- your role: owner, current tenant, subletter or agency, and whether you live in the home
- how viewings work and whether you accept applications only from people with a checked identity
- the listing's status and dates, whether it is featured and until when, and the reason if our team restricted it
The data on who lives in the home is also data about other people. Everyone can see it (see section 7).
We count each listing's views and impressions per day, without keeping in that counter who looked at it.
We also keep your saved rooms and, in the app, your saved searches: a name, the filters (price, place, habits) and whether you want a notification about a new matching listing.
Likes, invites, applications and matches
We keep who likes whom, and when:
- an invite from a host to a card: which room, status, dates and the message, if there is one
- a buddy-up, from a person to a card, with the same data
- an application to a room: who applied, to which listing and which rooms, status and dates. With it we keep a copy of the applicant's habits at the time of applying (smoking, pets, how social, routine, languages). If the application contains a note or details of a group, we keep those too: the number of people and each person's age, gender and occupation.
- a match: when two people like each other, an invite or an application becomes accepted and a conversation opens
For the contact ladder we count how many likes you sent in the last 24 hours. The counter is kept for up to 48 hours.
If you like someone without an account, the likes (up to 3) stay only on your device. We send them when you sign in.
Rooms from agencies
Agencies with a business account publish rooms among the other rooms. When you apply for such a room, the application is accepted at once and a conversation with the agency opens. We keep:
- the application, as for any room (above), and your conversation with the agency
- when you pressed «Обади се» (Call) towards the agency's phone number. The call itself happens outside Strehana and we do not know whether or how long you talked
- what the agency marks about you: new applicant, contacted, viewing, rented this room, rented another of our rooms, did not rent, and when. When the agency takes a room down as let, we also keep who rented it, if a person from Strehana
- your answer to the question «Нанесе ли се?» (Did you move in?), which we ask two weeks after your application: in this room, in another room from the same agency, somewhere else, or still looking
This is how we keep a register of applicants by agency: whom we sent to which agency and what came of it. We settle accounts with agencies by it. The agency sees its own marks and your application, but not your answer to our question.
The question whether you found a flatmate or a room
When you take down a listing or delete your card, we ask whether you found a flatmate or a room. We keep the answer with your profile and count it without data that identifies you.
Agency business accounts
An agency's business account is a company's account, not a person's. For it we keep the agency's name and company number, the office address, the logo, the description, the phone number for applicants, the commission, the sign-in email, the notification emails and the contact person's name. We process the contact persons' data to perform the agreement with the agency and keep it while the agreement is in force.
Agency flats and viewings
In the deck and in the «Квартири» (Flats) tab we show flats of real-estate agencies we work with. When you use them, we keep:
- the flats you like («Харесай», Like), and when
- the card for the flat's likers that we build from your likes: the flats, the highest price per person among them, their quarters, the earliest move-in date, when it expires and whether you hid it
- the flats you skipped, so that we do not show them to you for 14 days
- viewing requests: for which flat, alone or with whom (the person you connected with), which of you said «Искам оглед» (I want a viewing) and when, and the request's status
- when you pressed «Обади се» (Call) towards the agency's phone number, which is shown after the request. The call happens outside Strehana
- what the agency marks about the request: contacted, viewing, rented, did not rent, and when
- your answer to the question «Нанесе ли се?» (Did you move in?) two weeks after the request, and your answers to our questions after a viewing
We do not ask you for a phone number: you call the agency when you decide to. Phone numbers given for viewings before this version have been deleted.
Conversations and messages
We keep your conversations: between which people, about which listing, when they started, whether they are closed and by whom. We keep the text of every message, when it was sent and whether it was read.
When you hide a conversation, it disappears only for you. The messages stay.
Notifications and emails
We keep the notifications we show you in Strehana. Some contain a person's name, a listing title or the first 100 characters of a message.
In the app we keep your phone's notification token so that we can send you notifications. On the website, notifications are shown only in the open browser tab and do not go through any outside service.
We email you about a new application for your room, an accepted application, an invite or buddy-up received or accepted, unread messages, new rooms and people in your areas (a daily digest), a card payment confirmation, and our team's decisions about your content or account and about reports, appeals and notices you sent. We also email you about agency flats and rooms: when the person you connected with asks for a viewing with you, when the request reaches the agency, our questions after the viewing, when the flat or room has been let, and our question «Нанесе ли се?» (Did you move in?) two weeks after an application or request. We also send you flat suggestions: which flats fit you and a person you connected with, and when a person who could rent a flat you like with you likes it too. When you sign in with email, we send you the sign-in code.
The unread-message email names nobody and quotes no messages. You can unsubscribe from it, from the daily summary and from the flat suggestions through the link in the email itself. We keep these settings.
The deck
When you browse the deck while signed in, we record every card we showed you: when, in which position, whether you saw it and for how long, whether you passed or liked it, on the website or in the app, and the reasons for the order.
This is how we avoid showing you the same cards again. Without an account we do not record this on the server. Passed cards are remembered only on your device, for 30 days.
Reports, notices, appeals and decisions
When you report a card, a listing, a message or a person, we keep who reported, what, the reason, your text, the legal provision if you name one, the status and our team's notes. The reported person is not told who reported them. When we decide, we tell you what we decided, in the app and by email, with a way to appeal.
Anyone can send a notice of illegal content, also without an account, from the page strehana.com/en/report. We keep the link to the content, the reason, the provision, the explanation, the name and email if you give them, the decision and our team's notes. We also keep a salted hash of your IP address, to limit notices to 5 per hour from one address.
When you appeal a decision from the page strehana.com/en/appeal, we keep which decision the appeal is about, your text, your account or, if you are not signed in, your email, the outcome of the appeal and our reply.
When we restrict a listing, a card or an account, or remove a text or a photo from a profile, we keep the decision: what we decided, the facts, the ground, the provision, if any, and whether the content was found by the automatic check. We send them to you as a statement of reasons by email and, for listings and cards, also as a notification.
When the automatic check (Terms, section 9) reviews a text or a photo, we keep a record: which content was checked (kind and id) and whose it is, the result (fine or for review), the categories and the confidence, a short explanation for our team, whether the content was held, our team's decision, who made it and when, a fingerprint (hash) of the text, so that we do not check the same thing twice, the address of the photo, the model and the size of the check. For listings, cards and profiles we keep the first 300 characters of the text and, until the check is finished but for no more than 7 days, the whole text too, so that we can repeat the check if the system did not answer. For messages in conversations we keep no text, only the fingerprint.
When the check alerts us about a message, a person on our team can open only that message and the photos in it, without the rest of the conversation. We record who opened it and when.
When we ban an account, we copy into a separate library the text about the person and the text about the flatmate they are looking for from its profile, and the excerpts of its texts flagged by the check, without the name (up to 500 characters each). The automatic check compares new texts with it, to recognise the same person with a new account. So with every check we also send its provider the newest 30 texts from the library, up to 300 characters each (section 9). If the ban is lifted, we delete the texts from the library.
Blocks and feedback
We keep whom you blocked and when.
When you write to us through «Помощ и обратна връзка» (Help and feedback), we keep the category, the subject, the text, the page you wrote from, your browser and the screenshot, if you attach one.
Data other people give about you
Sometimes we receive data about you from other people: a host or an agency describes who lives in the home, an agency marks what came of your application, an applicant describes their group, someone writes to you or reports you or your content.
3. Identity check through Evrotrust
The check is optional. After it, your profile gets the «Потвърден» (Verified) badge.
You enter your ЕГН (Bulgarian personal number). We check that it is valid and work out your date of birth and sex from it. If the ЕГН says you are under 18, we refuse the check without contacting Evrotrust and alert our team with your account id only. A person on the team decides about the account.
Otherwise we send the ЕГН to Evrotrust. Evrotrust checks whether you have a verified account with them and sends a request to the Evrotrust app on your phone. You confirm there. Evrotrust returns only the result to us. We receive no name, photo or data from your document.
We do not keep the ЕГН. We keep:
- a keyed hash (HMAC) of the ЕГН, so that one ЕГН cannot verify two accounts
- the date of birth and sex from the ЕГН
- the Evrotrust transaction number
- when the identity was verified and by which route
While we wait for your confirmation, we hold this data, without the ЕГН, in temporary memory for up to 5 minutes.
After the confirmation we write the date of birth and sex from the ЕГН to your profile. After that they cannot be changed from the profile.
When you delete your account, we delete the check record. We keep separately, with no link to the account, only the hash of the ЕГН and the deletion date, for 12 months. While we keep them, the same ЕГН cannot verify another account. Then we delete them.
If an account with a verified identity is banned, we keep the keyed hash of its ЕГН separately, with no link to the account, for 3 years from the ban, also after the account is deleted, and then we delete it. If the account is suspended, we keep the hash until the suspension ends. While we keep it, the same ЕГН cannot verify another account. If we lift the ban or the suspension, we delete the hash.
If someone tries the identity check with the ЕГН of a banned account, the check does not go through, and our team gets an alert with the id of the account it was tried from.
The old phone check by SMS is no longer offered, and we do not keep the phone numbers from it.
4. Payments
The paid services are a featured listing, a featured card, a boosted application and early access. We do not keep bank card data.
By card on the website (Stripe)
Card payments on the website go through Stripe. You type your card or wallet details (Apple Pay, Google Pay) into a Stripe field. They go straight to Stripe and do not pass through our servers.
We send Stripe the amount, the currency, our payment number, your account id, the type of service and which listing, card or application it is for.
Stripe's code loads only on the payment pages. It collects data about your device and sets cookies to prevent fraud.
After a card payment we email you a confirmation: the service, the amount, when it starts and ends, the payment number and the consent you gave at checkout for the service to start at once and to lose the 14-day right of withdrawal, with the time and the Terms version. Without such consent, the email describes your 14-day right of withdrawal.
In the app (App Store and Google Play)
In the app you pay through Apple's App Store or through Google Play. The payment and its details stay with Apple or Google. They also send you the receipt.
The app sends us the store's receipt. We check it and keep only the transaction number and the product. We do not keep the receipt itself. We check Google Play receipts through Google.
When Apple or Google refund a payment, we learn about it and stop the paid service.
What we keep for each payment
- type, amount, duration, status, dates and which listing, card or application it is for
- the Stripe payment number or the store transaction number
- the consent to start at once, with the time and the Terms version
- the promo code, if you use one, or who on our team gave the service for free and why
- whether the payment came from the website, Android or iOS and whether there was advertising consent
- if there was advertising consent: Meta's identifiers (_fbp, _fbc), the IP address and the browser the payment came from
We also keep until when each paid service runs.
5. Technical data
Record of your cookie and analytics choice
When you answer the cookie banner on the website or the analytics question in the app, we keep your choice (analytics yes or no, advertising yes or no), the policy version and when. With the record we keep a random id from the browser, your account if you are signed in, a salted hash of your IP address and your browser (up to 512 characters).
This lets us show what choice you made and when.
Server logs
Every request to our servers is written to a log: its address and parameters (for example the text of a place search), the IP address, the browser or app, the result and the time.
The logs stay on the servers our services run on. We do not collect them in a separate system.
To limit excessive requests, we hold your IP address or your account id in a counter for up to one minute, and for place searches also until the end of the day (UTC).
Sign-in signals
At every sign-in and every session renewal we record scrambled signals from the sign-in, for every account. The purpose is one: to recognise a banned person who comes back with a new account (Terms, section 14). We record:
- the network address (IP) you sign in from, scrambled with a secret key (HMAC); we do not keep the address itself in this record, and for IPv6 we scramble only the first 64 bits of the address, which point to the network
- in the apps: a device identifier, scrambled the same way; on iPhone this is a random identifier the app creates and keeps in the Keychain, which stays after a reinstall, and on Android the identifier the system gives the app (Android ID); the app sends it only at sign-in and at session renewal
- on the website: a browser signal; the website stores a random identifier in your browser (harbor_client_signal_id, Cookie Policy, section 3) and, at sign-in and at session renewal, sends a one-way hash of it and of a few stable characteristics of the browser (the platform, the language, the number of processor cores, the screen size and colour depth, and the time zone); our server keeps this hash only scrambled with a secret key (HMAC)
- when we first and last saw each signal
We compare the sign-in signals with the signals of banned accounts. When we ban an account, we also check which accounts share a device identifier or a browser signal with it. Our team sees which accounts are linked to a banned account and by which signals. Otherwise the signals are shown to nobody and we use them for nothing else, neither for advertising nor for analytics.
When we ban an account, we copy its scrambled signals into a separate list: the network address for 30 days, the browser signal for 90 days and the device identifier for 12 months from the ban. If the banned account is deleted, the list stays until the end of these periods, but no longer names the account. If the ban is lifted, we delete it.
The device identifier and the browser signal are security measures. We use them only for the purpose above, on the basis of our legitimate interest (section 8), and they do not depend on the cookie banner or on your analytics choice.
Device location
In the Android app, when you tap the location button on the map for a listing's address, your phone asks for permission. We use the location only to move the map. We do not send it to our servers. Google's map sees it to show your dot. As the room's location we store only the point you choose.
The iOS app does not ask for access to your location.
On the website, the location button on the map for a listing's address asks your browser and only moves the Google map. We do not send the location to our servers.
Crash and error reports
The app sends crash and error reports to Sentry and to Google's Firebase Crashlytics. A report contains the error, the steps before it (for example which screens and which addresses of our server were open, with ids removed), the language, the device, the system and the app version. Sentry also receives speed data for some sessions.
The reports are not linked to your account. We do not send your id.
You can stop them at any time: in Settings, section «Поверителност» (Privacy), the «Споделяй диагностика» (Share diagnostics) switch, and without an account from the «Спри отчетите» (Stop the reports) line on the sign-in screen. Stopping applies from then on.
The website sends Sentry reports of errors in the browser: the error message, the page address without sign-in data, the browser and system, and speed data for 10% of page loads. Sentry sees your IP address when it receives the report.
Data on your device
The website keeps some data in your browser, for example your cookie choice, the cards you passed and drafts of a listing or a card. The list is in the «Политика за бисквитки» (Cookie Policy) (strehana.com/en/cookie-policy).
On the sign-in pages and forms, Apple's sign-in library loads. Sign-in with Google opens in a separate Google window only when you press the button.
The app keeps your sign-in data in the phone's protected storage (the Keychain on iOS, encrypted with the Android Keystore on Android). It also keeps a cache of your profile, listings, conversations, notifications and payments, drafts, passed cards and pictures. When you sign out it deletes them, except a few device settings, such as your analytics and diagnostics choices.
On an iPhone, the app's settings and drafts may end up in the phone's backups.
Each time the app starts, Google's Firebase creates an installation id and a notification token. We send the token to our server only while you are signed in, and delete it when you sign out.
Each time it opens, the app asks PostHog whether its version is still supported. The request carries a new random id each time and no data about your account. PostHog sees your device's IP address.
When you download a copy of your data in the app, the file is saved in the phone's temporary folder so that you can share it.
6. Analytics and advertising
Analytics and advertising are optional. On the website you choose in the cookie banner, separately for analytics and for advertising. Both are off by default and none of it runs before you answer. The app has one joint choice for analytics and sharing with Meta. We ask only people with an account. Without an account the app collects no analytics.
With analytics consent
- Google Analytics (website): which pages you open and what you do on them, _ga cookies and, when you are signed in, your account id and three measures of it: how complete it is, whether it is verified and how many days old it is. Google sees your IP address.
- PostHog (website): the same actions and pages, the full page address, the device type, system and language, the source of your first visit and, after sign-in, your account id. PostHog sees your browser's IP address and can derive an approximate location from it.
- PostHog (app): which screens you open and your actions in the deck and elsewhere, the app version, the device type, system, language and your account id. On Android also the install source from Google Play.
- PostHog (from our server): events for your actions, for example a new listing, a like, a message without its text, a payment, with your account id and data such as city, budget, amount, gender, occupation, age group, your email domain (not the address), ids of listings and of the other people in the action, and the listing's location rounded to about 1 km. These events do not carry your IP address.
- Source of the visit to the website: where you came from and the link parameters (utm, gclid, fbclid), in a cookie for 90 days. The channel and campaign are sent to our server with your actions.
When another person has given analytics consent, the events for their actions can contain your account id, for example when they write to you or apply to your room.
With advertising consent
We share key actions with Meta (Facebook, Instagram) and TikTok to measure our advertising:
- Meta Pixel (website): pages opened, listings viewed, searches by city, applications, saved listings, messages, new listings and cards, starting a payment and payments, with amounts and ids of listings and payments. The Pixel sets the _fbp and _fbc cookies and sends your name, gender and account id, hashed.
- From our server (Meta Conversions API), for actions on the website and in the app: registration, application, first message, saved listing, payment, new listing and new card. We send your email, name and account id hashed, on registration and a new listing or card also your gender, and unhashed the IP address, browser, _fbp and _fbc, plus the city, listing type, amount and ids.
- If you give advertising consent within 7 days of registering, we also send Meta the registration event.
- In the Android app: the id of the click on a Meta ad, if the install came from such an ad.
- TikTok Pixel (website only): pages opened, listings viewed, searches by city, applications, saved listings, likes sent, new accounts, new listings and cards, starting a payment and payments, with amounts and ids of listings, cards and payments. The Pixel sets the cookies listed in the Cookie Policy and sends your account id, hashed.
- From our server (TikTok Events API), for actions on the website only: registration, new listing or card, application, saved listing and payment. We send your email and account id hashed, and unhashed the IP address and browser, plus the amount and the ids of listings, cards and payments. We do not send TikTok your name, phone, gender, date of birth or location. If you give advertising consent within 7 days of registering, we also send TikTok the registration event.
- If you create an account, publish a card or send a like before answering the cookie banner, the page keeps these actions in its memory and sends them to TikTok only if you then allow advertising. If you refuse or leave the page, they are discarded.
- If you also have analytics consent, Google Analytics also receives Google's advertising signals.
We send Meta or TikTok a server event only if consent was given at the moment of the action. We do not send Meta or TikTok a phone number, date of birth or precise location.
Without consent
Even without consent, our server sends PostHog counts of actions, so that we know how much Strehana is used. They all go under one shared id, the same for everyone, without your account id and without your IP address, and with the hour but not the minutes. They carry only general fields, for example the kind of listing, the number of results, the position in the deck and whether a sign-in attempt worked, with Google or with Apple. They carry no city, budget, number of places or payment amount.
In the same way we count the cards shown in the deck to people without an account, answers to the cookie banner and failed sign-in attempts (provider and type of error).
How to change your choice
On the website, the «Настройки за бисквитки» (Cookie settings) link at the bottom of the page opens the banner again. If you are signed in, you can also use Settings, section «Поверителност и данни» (Privacy and data), row «Бисквитки» (Cookies).
In the app: Settings, section «Поверителност» (Privacy), the «Продуктова аналитика» (Product analytics) switch.
When you withdraw consent, we stop collecting and sending this data. Our server picks up the change within 5 minutes. Withdrawing does not affect what was already sent.
When you sign out in the app, analytics is switched off. If you sign in again with the same account, we apply your choice again.
7. What others see
The deck, listings and cards are visible without an account. So part of your data is public.
Everyone, even without an account
- Room listings in full: text, photos, prices, rooms, floor, who lives in the home and its rules.
- The room's location: the listing's page shows only the neighbourhood, the city and the country, and the map outlines only the boundaries of the neighbourhood, with no point and no address. We show the address and the exact location of the room to nobody, not even after a match. For searching by place, for distances and for the points on maps of results we use an approximate point instead of the real location: a point inside the neighbourhood's boundaries or, if we do not find them, the centre of a square of about 1 km that holds the room.
- For the host of every listing: first name, age, gender, the first profile photo, the «Потвърден» (Verified) badge and the host's number of listings. That photo cannot be hidden from the listings. For a room from an agency, the agency's name, logo and description, the «Проверена агенция» (Verified agency) badge and its number of listings stand there instead; the household data comes from the agency.
- The card: first name, age (if there is a date of birth), gender (if given), budget, move-in date, duration, text, the places with their points on the map, languages, the «Потвърден» (Verified) badge, whether you accept buddy-ups, when it was published and whether it is featured. If you choose a point (for example a place or an address), it is shown exactly.
- The first photo from your profile is shown on the card, unless you hide it in the card form.
- Every listing's page contains the host's account id. With it, anyone can open the same person's other active listings and active card.
- The address of every uploaded photo contains the id of the account it was uploaded from.
- The pages of active listings and cards can appear in search engines. The preview when a card is shared contains the first name, the places and the start of the text or the budget, but never your photo. The preview of a listing contains a room photo, the title, the price and the city, with no data about the host.
- For agency flats: how many people liked the flat, and up to three of them with an active public card: the first name, and the photo if their card shows it. Who else liked it is seen only by people with an account who liked it too.
People with an account also see
- the habits on the card: smoking, pets, occupation, daily routine, guests, working from home and whether you are part of a couple
- your profile: the name as entered, all photos, the text about you and about the flatmate you are looking for, your age (not the date of birth), gender, occupation, languages, habits, traits and interests, the badge, the scores for profile completeness and reply speed, whether you are online and when you were last active, and since when you have been on Strehana
- your account id, including on your card and your listings
- which agency flats you like: when you like a flat, the people who also liked it see, in their deck and under the flat, a card with your profile (first name, photo, age, gender, occupation, habits, languages and the text about you) marked «Харесва същата квартира» (Likes the same flat) and can like you back; if someone could rent it with you, they also get a notification and an email with your first name; this card is visible only to the people who liked the same flat, disappears 28 days after your last like and you can hide it at any time from «Моите обяви» (My listings) with «Скрий ме» (Hide me); after a match, the person you connected with sees, in the conversation, in our notifications and in our emails, the flats either of you likes and whether you said «Искам оглед» (I want a viewing)
A person you block does not see your profile, card and listings while they are signed in, and you do not see theirs. Without an account, public content stays visible to everyone.
Other people do not see
- your email
- your date of birth (we show only your age)
- your ЕГН, which we do not keep
- the address and the exact location of your room
- your messages, except the person in the conversation (our team can open a single message that the automatic check has alerted us about, section 2)
- your payment records
- your content held for review, until a person on our team approves it
- your sign-in signals
8. Why we process data and on what legal basis
To provide Strehana to you (contract, Art. 6(1)(b) GDPR)
- the account and sign-in with Google, Apple or an email code
- your card and listings and showing them in the deck
- the deck and its order for people with an account
- likes, invites, buddy-ups, applications, matches and conversations, with the contact ladder
- applications to agencies and viewing requests: we pass them to the agency when you (and, for a viewing together, the person you connected with) ask us to, and show you its phone number
- notifications and emails about things that concern you
- the identity check, when you ask for it
- the paid services
Legitimate interest (Art. 6(1)(f) GDPR)
- security and protection from abuse: server logs, limiting excessive requests, blocks and reports of breaches of the Terms
- the automatic check of the texts and photos in listings, cards and profiles before we show them, and of the messages in conversations, to protect the people on Strehana from scams, sexual exploitation, harassment and illegal content and to enforce the Terms
- the sign-in signals (the scrambled network address, the device identifier in the apps and the browser signal on the website) and their comparison with the signals of banned accounts, the library of texts of banned accounts, the restriction of the accounts linked to them and the refusal of sign-in from a banned account's device, so that a banned person cannot come back with a new account
- Stripe's fraud protection for card payments
- crash and error reports from the website and the app, so that we can fix errors. In the app you can stop them.
- the counts without consent that our server sends PostHog under a shared id, so that we know how much Strehana is used
- showing and ordering the deck for people without an account
- the daily summary, the unread-message emails and the flat suggestions, which you can unsubscribe from
- the register of applicants by agency: whom we sent to which agency, what it marked and what you answered, so that we can settle accounts with agencies and check their marks
- the question whether you found a flatmate or a room, when you take down a listing or delete your card: we keep your answer with your account to know how many people find someone to live with, and count it without data that identifies you
- Google's maps on listing pages and when choosing an address
- checking whether the app version is still supported
- keeping the ЕГН hash for 12 months after an account is deleted, for a banned account for 3 years from the ban, and for a suspended account until the suspension ends, so that nobody can avoid a restriction with a new account
- keeping reports about content and records of listing reviews after the content is deleted
The automatic check, the sign-in signals (including the device identifier and the browser signal) and the restrictions of accounts linked to banned accounts are measures for safety and against scams. Their basis is the legitimate interest, ours and that of the people on Strehana, in being protected from scams, sexual exploitation, harassment and people banned for breaches. We do not ask for consent to them, because this protection has to apply to every account.
You can object to this processing (see section 13).
Consent (Art. 6(1)(a) GDPR)
- analytics: Google Analytics, PostHog and the source of the visit
- sharing with Meta and TikTok and the advertising signals to Google
You can withdraw your consent at any time (see section 6). Withdrawing does not affect processing before it.
Legal obligation (Art. 6(1)(c) GDPR)
- the accounting and tax records of payments
- notices of illegal content, statements of reasons and appeals under the Digital Services Act
- the records with which we prove your consent
- our answers to requests under this policy
9. Who we share data with
We share data only with these recipients and only for what is described:
- Other people on Strehana: they see the data in section 7. The person in a conversation sees the messages, and the host sees the application.
- Real-estate agencies we work with. For a room from an agency, the agency sees your application as any host does: your first name, your card and your profile as people with an account see them (section 7), the message in the application and your conversation. For a flat, when you say «Искам оглед» (I want a viewing) alone or together with the person you connected with, we send the agency, for that flat, your first name and from your card and profile: your occupation, whether you smoke and whether you have pets, your budget and your move-in date. We do not give it your phone number or email; you decide whether to call it. The agency does not see your answer to the question «Нанесе ли се?» (Did you move in?). The agency is an independent controller of the data it receives. Once a week we also send it how many people saw and wanted its flats, without names.
- Hébergement OVH Inc. (Canada): hosting, as a processor. Our servers and databases run in OVH's cloud in Warsaw, Poland, where the photos are kept too.
- Google, as an independent controller: sign-in with Google; maps on listing pages and in the app; place and address search, where our server sends only the text typed or the point on the map, without your IP address; payments and receipt checks in Google Play. Google, as a processor: app notifications through Firebase Cloud Messaging (the token and the notification text, sometimes with a person's name or a listing title, without the text of messages), crash reports through Firebase Crashlytics, and Google Analytics with consent.
- Apple: sign-in with Apple, payments in the App Store and delivery of notifications to iPhones. For App Store purchases the seller is Apple Distribution International Ltd., which processes the purchase data as an independent controller.
- Stripe: card payments on the website (section 4). For the payment itself Stripe is a processor; for its fraud checks and its legal duties it is an independent controller.
- Evrotrust: the identity check. It receives your ЕГН (section 3). Evrotrust is an independent controller and processes the data in the EU.
- Meta: only with advertising consent (section 6). For collecting the data with the pixel and sending it from our server we are joint controllers with Meta Platforms Ireland Ltd.; for what Meta does with it afterwards, Meta is an independent controller. The essence of our arrangement with Meta is in Meta's controller addendum (www.facebook.com/legal/controller_addendum). If advertising consent was ever given, when the account is deleted we also send Meta an erasure signal with a hashed account id.
- TikTok: only with advertising consent (section 6), and only from the website. For collecting the data with the pixel and sending it from our server we are joint controllers with TikTok Technology Limited (Ireland) and TikTok Information Technologies UK Limited (United Kingdom); for what TikTok does with it afterwards, TikTok is an independent controller. The essence of our arrangement is in TikTok's Business Products terms (ads.tiktok.com/i18n/official/policy/business-products-terms). When an account is deleted we stop sending actions; TikTok receives no separate erasure signal.
- PostHog: analytics (section 6) and the app version check, in PostHog's EU cloud (Germany). PostHog is a processor.
- Sentry: error reports from the website and crash reports from the app, in Sentry's EU region (Germany). Sentry is a processor.
- Anthropic Ireland, Limited (Ireland): the automatic content check (Terms, section 9), as a processor under Anthropic's data processing addendum. It receives the texts and photos of room listings with details from the listing such as the city, the rent, the deposit, the bills and who the room is for; from cards, the text, the places, the budget, the move-in date and the length of stay, together with the name, the text about you, the text about the flatmate and the photos from your profile; from profiles, the name, the text about you, the text about the flatmate you are looking for, and the photos; the texts and photos of messages in conversations; the path of each photo in our storage (which holds the id of the account it was uploaded from, section 7); and excerpts of texts of banned accounts it compares with (section 2). It receives photos scaled down, to at most 2000 pixels on the long side and usually 1024. We do not send it your email, phone number, ЕГН or IP address, nor the content of agencies' business accounts. Anthropic's commercial terms do not allow it to train its models on this data. Anthropic deletes it automatically within 30 days of the request. It keeps it longer only if its safety systems flag a request as breaking its usage policy (the request and the answer for up to 2 years, and the scores of those systems for up to 7 years), or if the law requires it.
- Proton AG (Switzerland): sends our emails from no-reply@strehana.com. It receives your address and the email's text. Proton is a processor.
- OpenStreetMap Foundation (United Kingdom), the Nominatim service: for the boundaries of neighbourhoods, our server sends a point on the map (for a room, its location), with no data about you.
We do not sell personal data. We give data to public authorities only when the law requires us to.
10. Transfers outside the EEA
Some recipients are companies outside the European Economic Area (EEA) or belong to groups based outside it. So data may also be processed outside the EEA:
- Google, Meta and Stripe: to the US on the basis of the EU-US Data Privacy Framework (European Commission decision of 10 July 2023) and, where it does not apply, the European Commission's standard contractual clauses.
- Anthropic: the data is stored in the US, and requests may be processed in the US, Europe, Asia and Australia, on the basis of the European Commission's standard contractual clauses (module 2, controller to processor, and module 3, processor to processor), included in Anthropic's data processing addendum.
- TikTok: to the US, Malaysia and Singapore, where TikTok keeps the data, and for limited access by other companies in its group outside the EEA, on the basis of the European Commission's standard contractual clauses.
- PostHog and Sentry: the data is kept in the EU (Germany), but both companies may also process it in the US, on the basis of the EU-US Data Privacy Framework, or otherwise standard contractual clauses.
- Apple: on the basis of the European Commission's standard contractual clauses.
- Proton, in Switzerland: on the basis of the European Commission's decision that Switzerland ensures adequate protection.
- OpenStreetMap Foundation, in the United Kingdom: on the basis of the European Commission's adequacy decision.
- Hébergement OVH Inc., in Canada: the data is kept in Warsaw, Poland; OVH's access from Canada rests on the European Commission's adequacy decision for Canada.
You can ask for a copy of the standard contractual clauses at legal@strehana.com. Whether a company is in the Data Privacy Framework can be checked at www.dataprivacyframework.gov.
11. How long we keep data
When you delete your account, we delete most data at once (section 12). Otherwise the periods are:
- Profile, photos, habits and the records of accepting the Terms and this policy: while the account exists.
- Email sign-in codes (hashed) and the IP address they were requested from: 24 hours.
- Sign-in signals: the scrambled network address for 30 days, and the device identifier and the browser signal for 12 months from the last time we saw them. We keep at most 10 signals of each kind per account. When the account is deleted, we delete them, unless the account is banned (below).
- The scrambled signals of a banned account: the network address for 30 days, the browser signal for 90 days and the device identifier for 12 months from the ban, also after the account is deleted, with no link to it. When the ban is lifted, we delete them.
- The record that the account is restricted as linked to a banned account: for as long as the account exists. The records of which accounts are linked and by which signals: 12 months from the last match.
- An account refused sign-in because of a banned account's device: it stays until a person on our team decides whether to unblock the device or delete the account. You can ask for its deletion at legal@strehana.com.
- The card is active for 30 days and you can renew it. After that it is hidden, and the record stays until the account is deleted. A card you delete is removed completely 30 days later; until then the record stays so that we can look into reports.
- A listing is active for 30 days and you can renew it. An expired listing is archived and deleted 7 days later. A listing you delete is deleted at once. A paused listing, or one our team restricted, does not expire.
- When we delete a listing, we delete the photos in it too. A photo you remove from a listing or profile stays in our storage until you delete your account, and anyone who has its address can open it.
- Likes, invites and buddy-ups: until the sender or the recipient deletes their account. An invite you withdraw before an answer is deleted at once.
- Applications: while the listing exists and while the applicant and the host have accounts. The entry in the register of applicants by agency stays under the rule below.
- The register of applicants by agency (application or request, the «Обади се» (Call) press, the agency's marks and your answer): 24 months after the last action on the entry. When you delete your account the entry loses its link to you: the first name is removed and only a short code remains.
- Your answer to the question whether you found a flatmate or a room: until you delete your account.
- The flats you like: until you remove the like or delete your account. A skipped flat: hidden from you for 14 days; the record is deleted the next time you open the deck after that, at the latest with the account.
- The card for the flat's likers: visible for up to 28 days after your last like of a flat. After that it is hidden, and the record stays until your next like or until the account is deleted.
- Viewing requests: until you or the other person in the request deletes their account; their entry in the register of applicants stays under the rule above. The agency keeps its own copy under its own rules.
- Deck history: 12 months after the last action on the card or listing, or until the account is deleted if that comes first. If you take back a pass, the record for that card is deleted.
- Conversations and messages: until one of the two people in the conversation deletes their account. When a listing is deleted, its conversations are closed but stay.
- Notifications: read ones 90 days, unread ones 180 days.
- Email settings and the records of daily summaries and flat suggestions sent: until the account is deleted. The record of an unread-message email is deleted as soon as the conversation is read.
- Notification token: until you sign out in the app or delete the account.
- Saved rooms and searches: until you remove them or delete the account.
- Blocks: until you unblock or one of the two accounts is deleted.
- Feedback: until the account is deleted.
- Identity check record: until the account is deleted. After that only the ЕГН hash and the deletion date, for 12 months. The ЕГН hash of a banned account: for 3 years from the ban, also after the account is deleted, and of a suspended account, until the suspension ends.
- Payments: when the account is deleted, the records lose the link to your account and the advertising data. We delete them 10 years after the end of the year of payment.
- Reports: those you filed and those against your account are deleted with your account. The rest are deleted 12 months after the decision on them.
- Notices of illegal content: until we decide and 12 months after the decision.
- Appeals: until we decide and 12 months after the decision. An appeal filed from an account is also deleted with the account.
- Records of the cookie and analytics choice: 3 years, as proof of consent; your latest choice is kept while it stands. When an account is deleted, we remove the account, the IP address hash and the browser from them. Records made without an account keep the IP address hash and the browser.
- Records of listing edit reviews (old and new text, photos, whose listing it is), when such review is switched on: 12 months after the review decision, also after the listing is deleted. Reviews not yet decided are kept until the decision.
- The records of the automatic check: 12 months from the check. The whole text stays in the record until the check is finished, but for no more than 7 days; after that, the first 300 characters remain. For messages we keep no text. When an account is deleted, we delete the records about its content. The records of who on our team opened a flagged message and when (without its text) stay in the log of our team's actions, so that every such access can be checked; we do not delete them automatically.
- The library of texts of banned accounts: 12 months from the ban, also after the banned account is deleted, with no link to it. When the ban is lifted, we delete the texts.
- Server logs: until the servers replace them.
- Counters against excessive requests: up to one minute or until the end of the day. Likes counter: up to 48 hours.
- Internal delivery records of events between our services: 7 days after sending. Copies in our event system are kept for 7 or 30 days depending on their type.
- Cache of place searches, not linked to any person: from 1 hour to 30 days.
- Database backups: OVH makes them automatically. Deleted data can remain in them until the backups are replaced.
- How long PostHog, Google Analytics, Meta, TikTok, Sentry and Firebase Crashlytics keep data is set in their settings.
12. Deleting your account and getting a copy of your data
Deleting your account
You delete your account from Settings: on the website in «Опасна зона» (Danger zone), row «Изтрий профила завинаги» (Delete account permanently), and in the app in section «Поверителност» (Privacy), row «Изтриване на акаунт» (Delete account).
Deletion is immediate and final. There is no cooling-off period and it cannot be undone.
Your account disappears at once. Our other services delete their data, usually within seconds. If one fails, we try again automatically over the following hours.
We delete the account, the photos you uploaded, the card, your listings and the applications to them, the likes, invites and buddy-ups sent and received, your applications, the deck history and the records of who saw your card or listings, the conversations, your notifications and other people's notifications that mention you, the reports filed by you and against your account, the blocks, the feedback, the saved rooms and searches, the notification tokens, the email settings, the flats you liked or skipped, the flat-likers card, the viewing requests you are part of, your applications to agencies, your sign-in signals, the records of the automatic check of your content, and the identity check record.
Conversations are deleted in full, also for the other person in them. They also lose their own messages in the conversation. A viewing request is deleted for the other person in it too. The copy the agency has already received stays with the agency. Your entry in the register of applicants by agency stays without a link to you (section 11).
If your account is linked to Apple through the app, we also end our access at Apple.
We send PostHog a request to delete the data about your account and the events linked to it. If advertising consent was ever given, we send Meta an erasure signal with a hashed account id. We send TikTok no such signal; we stop sending it actions.
What remains after deletion
- the payment records, with no link to you, until 10 years after the end of the year of payment; Stripe keeps its own record of the payment with your account id
- the records of the cookie and analytics choice, with no link to the account
- the ЕГН hash and the deletion date, for 12 months, and if the account is banned, the ЕГН hash until 3 years from the ban
- if the account is banned: its scrambled sign-in signals, with no link to the account, until the end of the periods in section 11
- if the account is banned: its texts in the library of texts of banned accounts, with no link to the account, until 12 months from the ban
- reports and notices from other people about a specific listing, card or message, until 12 months after the decision on them
- the entry in the register of applicants by agency, without your first name, for up to 24 months after the last action on it
- records of listing edit reviews
- the id of the deleted account and the date of deletion, for 30 days, so that we can finish the deletion in all our services
- technical records of revoked sessions, for up to about an hour
- data in the backups, until the backups are replaced
- the data Google Analytics, Meta, TikTok and Stripe already received, under their rules, and the counts without an id in PostHog
A copy of your data
From Settings you download one JSON file with your data: on the website in section «Поверителност и данни» (Privacy and data), row «Изтегли данните си» (Download your data), and in the app in section «Поверителност» (Privacy), row «Изтегли моите данни» (Download my data). You need to be signed in.
The file contains:
- the sign-in account: email, provider and when it was created
- the profile and the records of accepting the Terms and this policy
- the records of your cookie choice
- the card
- the invites and buddy-ups received and sent
- your listings
- the applications sent and received
- your applications and requests to agencies with the agency's marks and your answer
- your answers to the question whether you found a flatmate or a room
- the deck history
- the conversations and every message in them
- the notifications
- the email settings
- the saved searches and rooms
- the people you blocked
- the reports you filed and your feedback
- the payments
- the identity check record: whether verified, when, by which route, the date of birth, the sex, the Evrotrust transaction number and whether we keep an ЕГН hash (never the hash itself or the ЕГН)
Photos are in the file as links. For a copy of anything that is not in the file, write to legal@strehana.com.
13. Your rights
Under the General Data Protection Regulation (GDPR) you have the right to:
- Access: to learn what data we process and to get a copy. The quickest way is from Settings (section 12).
- Rectification: you correct most data in your profile, card and listings. If you sign in with Google or Apple, the email comes from there: change it there and we update it at your next sign-in. If you sign in with an email code, write to us. After the identity check, the date of birth and gender come from the ЕГН and cannot be changed from the profile. If they are wrong, write to us.
- Erasure: from Settings (section 12) or by a request to us.
- Restriction: to ask us to stop processing data, for example while we check whether it is accurate or whether your objection is justified.
- Objection: to processing based on legitimate interest. For crash reports in the app, use the «Споделяй диагностика» (Share diagnostics) switch. For everything else, write to us.
- Portability: the copy in Settings is in a machine-readable format (JSON).
- Withdrawing consent: at any time, as described in section 6.
- Complaint: to the Commission for Personal Data Protection, www.cpdp.bg. You can also go to court.
For any request, write to legal@strehana.com. We answer within one month. For complex or numerous requests the period can be extended by two more months, and we will tell you why.
14. Automated decisions and profiling
The deck orders cards automatically. This is profiling: we use data about you to decide what to show you first. The order has no legal effects on you and does not affect you in a similarly significant way.
When you are signed in, the order takes into account who has already liked your card, your filters, the budget and date from your card or the rent and date from your listing, the distance to the place you are looking in, how many people have already seen the card, how complete the person's profile is and how new the card is. A person's age, habits and languages do not affect the order by their values. Only whether they are filled in counts, as part of profile completeness. Gender and smoking come in only as filters. Featured cards take set places in the deck.
A detailed description is on the page «Как подреждаме картите» (How we order the cards) (strehana.com/en/how-ranking-works).
We also work out the contact ladder automatically. How many likes you can send in 24 hours depends on whether you have an account, an active card or listing, how complete your profile is and whether your identity is checked.
We automatically choose whom to notify about a new room or card, based on the places and budget in the cards.
The identity check automatically refuses an ЕГН that says you are under 18. A person decides about the account.
Decisions on reports, notices and appeals, and every decision to restrict content or an account because of a breach, are made by a person on our team.
Applications for agency rooms are accepted automatically so that the conversation opens at once. This decides nothing about you: the agency decides for itself after that.
The automatic check (Terms, section 9) assesses texts and photos with an artificial intelligence model and can hold a listing, a card or a change to a profile until a person on our team has reviewed it. The hold is temporary: whether there is a breach is decided by a person. In conversations the check only alerts our team.
If the sign-in signals of your account match the signals of a banned account, or the texts of a new account closely resemble texts of a banned account, your account can be restricted automatically (Terms, section 14) until you verify your identity. A new account in the app on a banned account's device may not be let in. You can ask for a person on our team to review the restriction or the refusal, express your point of view and contest them by writing to us at legal@strehana.com. An account with a verified identity and an agency's business account are not restricted in this way.
15. How we protect data
- Connections to the website, the app and our servers are encrypted (HTTPS).
- We have no passwords: you sign in with Google, with Apple or with an email code.
- On the website the session is in cookies that JavaScript cannot read. The access token is valid for 15 minutes and the refresh token for 30 days. We keep refresh tokens only as a hash.
- In the app, sign-in data is in the Keychain on iOS or encrypted with the Android Keystore.
- We do not keep the ЕГН, only a keyed hash of it.
- We keep the sign-in signals (the network address, the device identifier and the browser signal) only scrambled with a secret key (HMAC).
- Your bank card details go straight to Stripe.
- We re-process every uploaded photo and remove its hidden data (EXIF), including GPS coordinates.
- Messages are not end-to-end encrypted. We keep them as text in our database.
- Our databases have automatic backups at OVH.
- Only the members of our team who need the data to run Strehana, handle reports and answer requests under this policy can access it.
16. Only for people aged 18 or over
Strehana is only for people aged 18 or over. The sign-in page, the sign-in card in the deck, the sign-in in the listing and card forms and the sign-in in the app say that by signing in you confirm you are 18 or over.
If you enter a date of birth, we check that you are 18 or over.
The identity check refuses an ЕГН that says you are under 18, and alerts our team.
17. Changes to this policy
When we change the policy, we publish the new version at least 15 days before it takes effect. We use a shorter period only for a change that is needed to comply with the law or to protect the people on Strehana from scams and abuse. Until the new version takes effect, a note at the top of this page gives the date and links to it. The page shows the version number and the date from which it applies, and earlier versions are on the «Earlier versions» page.
When the new version takes effect, the website and the app ask everyone who is signed in to accept it before continuing. If you do not accept it, you can sign out.
On the website the cookie banner is shown again when a new version of the policy takes effect.
18. Contact
Write to us at legal@strehana.com or call +359 876 168 215. Our address is 1618 Sofia, Vitosha district, 87 Ralevitsa St, entrance A, floor 3, apartment 307, Bulgaria.
If you think we are infringing your rights, you can complain to the Commission for Personal Data Protection, www.cpdp.bg.