Privacy in Hazain apps for Apple apple-privacy-v1-2026-11-16 Information, purposes, recipients, retention and rights for the iOS, iPadOS and macOS apps and their accounts. 1. Scope, controller and contact The controller is VIGINTI, EIK 207777167, address: Zhk Mladost 2 217, Sofia, Bulgaria. Privacy and rights contact: info@hazain.bg. This common notice covers the Hazain iOS, iPadOS and macOS apps and their tenant/landlord accounts in the current long-term-rental platform. The visitor, tenant and landlord distinctions below identify the processing relevant to you. The Shop offers the application through the profile, a banner and a representative package; other new offers remain Coming soon. Future services are not described as already operating. Reading this notice is not consent to every processing activity. Accepting account terms is a contractual choice; optional features have separate actions/settings. This separately versioned document includes the common account processing from Privacy22 and the Apple app details below. The common website/other-platform notice is https://hazain.bg/legal/privacy. Describing a function does not enable it or grant a device permission. 2. Information and its sources We receive information from you, the other party in an authorised workflow and provider results: name, email, phone, birth date/age, role, photo and preferences; property/offering authority, public photos/plans, price and conditions; searches, applications, viewings, authorised chats, contract versions/signatures, recorded tenancies and reviews. For a chosen full application: supplied employment/income, household, references, necessary attachments and the human review result. Reference contacts may be provided by the applicant; we do not collect an address book. Payment data includes identifiers, amount, currency, status, billing details and refund/dispute information. Full card credentials and banking codes are not stored in the Hazain account. Technical categories are explained separately below. Do not put national identifiers, health information, full card/bank credentials or other people’s sensitive information in free-text fields; use only an expressly identified protected process and the necessary minimum. For a selected guarantor we receive, from the applicant or guarantor, their first and last names, workplace, work document and an employer contact’s name and phone. We do not require a previous-landlord contact or an income amount. If the applicant neither works nor studies and has no guarantor, an employer, contact and work or study document are optional. We record the study answer to determine which selected evidence applies; unselected historical employment details and documents are excluded from a new review or transfer. Your own employer and work or study document are optional when using a guarantor. The guarantor should receive this notice before their details are entered; at first direct communication with them or an employer contact, Hazain provides the relevant information about the source, purpose and rights. GDPR Article 14 deadlines and applicable exceptions remain in force. For online signing we retain the drawn signature as a bounded set of strokes, with the document version and digest, consent, time and authentication evidence. We do not use it for biometric recognition. The signature is visible to the document participants and authorised staff where review is necessary. Arrival and lateness updates are entered by a participant, not automatic location tracking. The landlord’s private notes are not shown to the tenant; report explanations are reviewed by authorised staff. For a private contract we receive full names, date of birth, verified-profile identifier and correspondence address. The address may be supplied in the private profile or for the particular contract, independently of buying an application. For a company we also retain the representative’s capacity and basis of authority. Contract participants see these details in the particular document and necessary linked attachments; authorised staff access requires an applicable purpose. They do not become public-profile information. Signed versions and evidence are not replaced by later profile edits. 3. Purpose, information and legal basis • Public website and security: technical information to deliver pages, diagnose faults and prevent abuse — legitimate interests, GDPR Article 6(1)(f), in an available and secure service. • Account, login and verification: contact, age/adult eligibility, session and verification results — contract/steps requested by you, Article 6(1)(b); separate fraud/abuse protection uses Article 6(1)(f). • Tenant: searching, matching, profile, applications, viewings and communication — the requested service, Article 6(1)(b). Information shown to another party follows visibility choices and the permissions of that workflow. • Landlord: property, listing, photos, conditions and expressly requested external distribution — Article 6(1)(b). Proportionate offering-authority/refund verification and rights protection — Article 6(1)(f). • Paid application review: supplied material and result — Article 6(1)(b); necessary checking of third-party/reference information — Article 6(1)(f), to provide a reliable requested review. Inform references before supplying their contacts. We send no automatic messages to references; if contacting them directly we provide the applicable processing information. • Agreements, recorded tenancies and participant communication — Article 6(1)(b); necessary evidence for a particular legal claim — Article 6(1)(f). • Payments and refunds — Article 6(1)(b); required accounting/tax records and statutory withdrawal handling — legal obligation, Article 6(1)(c); disputes/fraud — Article 6(1)(f). • Support — Article 6(1)(b); reports, protection of people/property, proportionate moderation and legal claims — Article 6(1)(f), with Article 6(1)(c) for a particular legal duty. • Necessary choice, version and access records — Article 6(1)(f) for accountability/security and Article 6(1)(c) where a particular duty requires it. An ‘I have read’ record does not make these purposes consent-based. For legitimate interests we consider necessity, reasonable expectations and effects on you; you may object and request human review. Optional advertising tracking is not a condition of the basic service. • Optional device notifications: account/device push token or browser subscription, selected event and routing/status data — Article 6(1)(b) for requested alerts and Article 6(1)(f) for delivery/security. OS/browser permission can be revoked; marketing has no blanket permission. • In-app audio calls: participant, call/signalling times/status and network/relay connection data — Article 6(1)(b) for a call you make/accept and Article 6(1)(f) for secure routing. Microphone permission is separate; Hazain does not record call audio. • Post-rental reminders and a personal invitation link: signed-rental eligibility, visit/prompt status, link and expressly confirmed inviter association — Article 6(1)(f), to limit repeated prompts and support voluntary recommendations; Article 6(1)(b) for a specifically requested referral/support action. You may dismiss prompts and object. We do not read Facebook likes, an address book or the content/outcome of a Play review. Gifts are not awarded for likes or reviews. • Optional support for the Hazain team: the explicit amount/confirmation and related payment or refund allocation — Article 6(1)(b); accounting obligations — Article 6(1)(c). Declining never reduces refund eligibility. • Guarantor and employer contact: necessary data for the requested check is processed under Article 6(1)(f) for a reliable application and misuse prevention, subject to relevance and the individuals’ rights. Direct steps requested by a guarantor towards a future agreement may rely on Article 6(1)(b). Entering details triggers no automatic call, marketing or legal guarantee. The person may object and request human review. • Limited public-site statistics: server requests are used to estimate visits, page openings and a broad acquisition channel, such as Google, Facebook, another website or direct access. The purpose is to understand which pages and channels help people use the service and to plan improvements; the basis is legitimate interests under GDPR Article 6(1)(f). A daily pseudonymised key groups requests from a similar browser; a gap exceeding 30 minutes starts another estimated visit. The key is not an account identifier and does not link different days. Only a predefined source category is retained, without the full referring address, advertising identifiers or URL parameters. We set no analytics cookie, send none of these data to Google or Meta and build no advertising profile. These estimates do not establish unique people or why someone registered. You may object at info@hazain.bg and request human review. Call history in chat contains participants, time and call outcome, without audio recordings or conversation content. An attempt not accepted by the server for signalling to the other participant, and its failure, are visible only to the caller. After accepted signalling, decline, cancellation before answer and no answer appear as a missed call for both participants. This history follows chat retention and deletion rules; technical signalling is separate and cleared within 24 hours. To complete a request after an interrupted connection, the device may retain minimal identifiers, time and outcome for up to one day: encrypted on Android or in the current browser tab. The local request is removed after confirmed saving, sign-out or account replacement. Authorised photos already loaded in the private website may remain temporarily in the current account’s memory, without persistent browser storage; account replacement and detected access changes clear that cache. 4. Required information and consequences of withholding it Public browsing does not require an account. Connection information needed to deliver a page cannot be avoided while loading it. An account/secure login requires a working email and the necessary verification; a phone/check is required for the identified protected steps/new-device access. Without it those actions remain locked; Support and rights requests remain available. Adult-eligibility information and a name are needed at the relevant registration/contract steps, not for anonymous browsing. Public profile views use age instead of the full birth date. A listing needs offering authority, real characteristics/location and chosen public material; required missing information prevents submission/publication. Exact contractual/payment details are needed for the relevant contract or payment. A chosen full application needs the marked information/references or the process’s permitted answer/alternative evidence; incomplete material cannot be presented as reviewed. Unnecessary data is not required to consider statutory withdrawal or privacy rights. Optional fields, dictation, automatic translation and notifications may remain unused. Without translation you see the original; without push permission you check messages inside Hazain. Withdrawal needs an identifiable contract and an electronic acknowledgement destination, not a reason, account deletion or blanket marketing consent. 5. Visibility and human access The city, neighbourhood and dwelling floor are public listing characteristics. The chosen listing scope and public photos/profile elements are visible publicly. Protected street/number/unit, internal name, private folders and payment/verification information are not part of the default public view. Contract participants receive the necessary information for authorised applications, viewings, chat and the signed document. Paying or saving a draft does not publish a full application or private evidence. Sending for review gives authorised staff access; disclosure to a named landlord follows its separate authorised workflow. Staff have limited roles; sensitive access requires the applicable reason/check and is audited. We do not sell personal information. For an agreement with a guarantor, the invited person receives limited access through their own account with a verified email. Before accepting they see minimal invitation information; after personally accepting and supplying their details they can see the private agreement and the necessary details of all three participants. Their own name, birth date, verified account, correspondence address, consent, review, signature and attendance confirmation bind the exact version. They receive no general access to the application, chats, payments or tenancy management. A paid application is not required solely for this participation. Processing supports the requested preparation and performance of the agreement and necessary protection of participants’ rights, under this policy’s grounds and retention rules for contractual information. In the current service mode, tenants do not need an enrollment deposit or a routine Hazain camera check before applying. After completing your profile, you can submit a request for a listing. A submitted confirmation means Hazain has received it; it does not mean the landlord has received it. Our team reviews the profile, and the request and its notification are withheld from the landlord until approval. We provide instructions if changes are needed. Approval for delivery does not certify identity, ability to pay or acceptance by the landlord. 6. Listing publication outside Hazain Choosing channels and accepting the applicable sharing terms requests a particular service; it is not blanket permission for all processing. For selected alo.bg and OLX publication we prepare title/description, approved public photos, price/currency, city/district, property characteristics/conditions, a publication-reconciliation reference and that publication’s contact details. Automatic preparation uses Hazain’s business contact, not an automatic copy of the private account phone/email. Other details you expressly provide for the public text/contact form part of that chosen distribution. Private applications, references, identity documents, agreements, messages and payment records are not automatically included. Selected Facebook groups and other expressly confirmed manually handled channels are used only within the confirmed scope; Facebook automatic publication is not claimed. External-site recipients and visitors may view, copy or index a public advert under their rules. A request confirmed inside Hazain is not proof the partner has published it. Removal requests are sent to the relevant channel; independent copies/search engines cannot be guaranteed erased by Hazain. Contact info@hazain.bg about particular publication data. 7. Optional Google translation Automatic translation is off until you enable it. The account setting applies to eligible chats and contract text. Once enabled, text can be submitted automatically as supported messages or a canonical contract revision come into view. Each request contains an accessible message or that exact revision, rather than an entire chat attachment. Google Cloud Translation receives the text of the selected accessible message or exact selected contract-text revision. It may contain names, property address, contractual amounts/conditions and other personal information already in that text. We do not automatically attach an entire chat, profile, login codes or a PDF; imported PDFs are excluded from this function. We use the Cloud Translation Advanced EU endpoint with europe-west1. Google describes brief in-memory text processing for translation without using the content to train translation models. Hazain keeps an actor/original-bound result in memory for at most 5 minutes; disabling clears that cache and stops future requests. It does not delete the original message/agreement. The bases are performing the specifically requested function, Article 6(1)(b), and the necessary legitimate interest under Article 6(1)(f) in authorised communication/other participants’ information. Your choice is not consent on behalf of everyone named in the text. You can object or disable the feature. Machine translation may be wrong; the original/accepted version remains authoritative and translation does not sign or amend a contract. 8. Assistant, summarisation and dictation Google Vertex AI/Gemini receives the submitted question, role/general app area, limited recent text and Hazain-curated reference context. Support summarisation uses up to six recent customer questions/messages; it does not automatically submit an entire private rental chat. Detected emails/long numbers are redacted, but we do not claim perfect removal of every name/address you type. A profile, contract, ID copy or payment record is not automatically attached. Supply only necessary information and avoid sensitive data in a general question. This supports requested assistance/communication — Article 6(1)(b) and Article 6(1)(f) legitimate interests in a short, human-checkable summary and limited assistant quality review. AI does not decide refunds, moderation or tenancies. The configured location is EU; international-access rules are below. Google may retain limited security/abuse records for up to 30 days where applicable under Vertex AI terms; an unverified provider zero-retention promise is not made. For voluntary dictation, the chosen device/browser voice service may process audio under its own terms. Hazain receives the text you review and submit, not assistant audio. You may type instead. For an audio call, the microphone feeds an encrypted real-time connection through Hazain’s configured TURN relay, using a short-lived opaque relay credential. Hazain stores signalling/status, not an audio recording. You can decline permission or end a call and continue in text. Google/Firebase push delivery may process an installation token and a minimal event/routing payload. Browser push is used only if enabled and expressly subscribed; disabling optional push does not remove messages inside Hazain. For quality review, the authorised platform owner may inspect the question and actual answer from the last 30 days, with additional staff authentication, a specific purpose and an access audit. Pre-login help uses a separate encrypted record of the explicitly submitted question, answer, general area/language, time and retry identifier; registration-field answers are not attached. After login we use existing private history without a hidden duplicate: deleting a conversation also removes it from this review. Separate pre-login records are cleaned after 30 days. This review is not used to train an external model, advertise or make an automated decision about you. You may object or request erasure at info@hazain.bg; for a pre-login question provide only the necessary text/approximate time to locate it. 9. Current providers and recipients • Google Cloud/Firebase: hosting, storage, identity and selected functions; technical/account information and content necessary for the particular service. Google Workspace/Gmail transports business correspondence, codes and confirmations. • Google Maps receives network/device information and map-display context on map pages. Website maps load on map pages, separately from advertising tracking. reCAPTCHA for protected login/registration actions processes network/device and anti-bot security signals. These Google functions also have https://policies.google.com/privacy and https://policies.google.com/terms. • Google Cloud Translation and Vertex AI: only the text/context described in sections 7–8. • Dexatel OÜ and necessary telephone carriers: number, requested verification reference/status and necessary call/check routing information. The current integration does not use SMS fallback. • Stripe and necessary payment/banking partners: payer/transaction and refund/dispute data. Stripe is a processor for some operations and an independent controller for its own payment, anti-fraud and legal purposes; https://stripe.com/privacy. • Chosen external channels: the public advert and publication contact described in section 6. They apply their own terms to public content. • Authorised participants/staff, advisers and authorities: only what is needed for the authorised workflow or particular legal ground. A private profile is not sent to every listed provider. 10. International processing and safeguards Hazain’s main resources are in Google Cloud europe-west1 (Belgium); translation uses an EU endpoint and AI is configured for an EU location. That does not make every connected service, support access or recipient EEA-only. Google account/Firebase/Workspace, Maps/reCAPTCHA and subprocessors can involve international processing. Stripe expressly describes transfers to Stripe, LLC in the United States and global affiliates/subprocessors. Phone verification can use international carrier infrastructure; an external public advert can be accessed worldwide. Relevant processing/transfer terms apply: Google Cloud Data Processing Addendum, Google Workspace/Firebase terms, Stripe Data Processing Agreement/Data Transfers Addendum and Dexatel’s service DPA. Restricted transfers use an applicable adequacy decision within its actual scope, including EU–US DPF for a covered certified entity/processing, or the applicable European Commission standard contractual clauses with the relevant measures. Hosting region does not replace that analysis, and not every US company is assumed covered by DPF. Request information/a copy of safeguards applicable to your data from info@hazain.bg, with only protected third-party/confidential information redacted. Public references: https://cloud.google.com/terms/data-processing-addendum ; https://stripe.com/legal/dpa ; https://dexatel.com/terms-of-service/ ; https://policies.google.com/privacy/frameworks . 11. Retention periods and criteria • Ordinary technical HTTP logs, minimised request history and customer-activity facts: 30 days. The minimised history contains no copied IP, full browser headers, URL parameters or form text; daily browser groups are not named customer profiles. Non-identifying daily totals without browser references may be retained for service planning. • Separate administrative Cloud audit records: Google’s mandatory `_Required` log is 400 days; this is not a 400-day history of ordinary visits. • Codes/short checks and unfinished login challenges: until their displayed expiry/consumption. Sessions/trusted devices: until recorded expiry/revocation; an expired bearer does not authorise login merely because a limited device-proof record remains valid. Short-window authentication abuse data is pruned on the applicable 24-hour schedule. • Separately, a minimised identifier/evidence for a particular security or promotion-abuse concern may be retained after reasoned review with legal basis/end date, for at most 365 days in that category. This does not justify keeping an entire profile or all logs for a year. • Profiles, drafts and listings: while the requested account/function is active or necessary for its related tenancy. Shared chats, contracts and history also involve the other party’s rights. Assistant history can be deleted through its controls. Closure/deletion initiates the process below, not indefinite retention of the entire dataset. • Application/reference material: for preparation, requested review and maintaining the application/result you have stored; you may request removal of unnecessary material. Specific contractual/dispute evidence is isolated and retained with reason/end date, not by keeping every private document without a limit. • Accounting/tax data: the legal period depends on category; registers, financial statements and tax-control/audit documents have a 10-year period, while other accounting media under the general rule have 3 years, calculated under Article 12 of Bulgaria’s Accountancy Act. A specific longer legal need/pending proceeding is considered separately. All profile information does not thereby become accounting data. • Withdrawal, claim, moderation or protected-access evidence: while the particular process/legal claim and applicable period require it, with limited scope, legal basis and a recorded end date for retention. You may ask for the reason/deadline for your case. • Translation cache: at most 5 minutes in memory, purged on disabling. Provider periods are explained with the relevant function. • Audio call signalling: only for the conversation’s communication/history and security need; active call/signalling records expire within 24 hours and are cleaned by maintenance. No recording is retained. Push tokens/subscriptions last until revocation, invalidation or account erasure; an Android delivery expires after five minutes. • Prompt/session and personal invitation state remains with the active account until removal/erasure; an attributable financial claim, if any, follows its separately documented necessary retention. Ordinary reminders are not an indefinite financial record. • Assistant quality review: access to questions/answers from the last 30 days. Separate encrypted pre-login records expire after 30 days and are cleaned on schedule; private account history follows your deletion controls. Daily protected backups have a locked 14-day minimum and automatic lifecycle; deleted or expired records are not returned to active use on restoration. • After a personal invitation is deleted, a restricted pseudonymised fingerprint of its previously used code may remain while the same invitation address space is maintained. Its sole purpose is to prevent an old public link from being assigned to another person. It is not anonymous information, contains neither the raw code nor name, and is not used for new invitations or advertising tracking. Access is restricted; the record is reviewed and deleted when this need ends. 12. Erasure, backups and restoration Request account/selected-data erasure through Legal and data, https://hazain.bg/delete , https://hazain.bg/delete-data or info@hazain.bg. Ordinary scheduling is 30 days from receipt with cancellation before execution; identity verification does not restart that period. Applicable law/a request for earlier erasure is considered with priority. Merely signing in does not cancel it. Necessary contractual/financial data, another participant’s rights or a particular legal claim may require limited retention. We identify reason, basis, scope and end date; the remainder is erased/anonymised. Erasure does not waive a refund legally due; withdrawing from a contract does not automatically delete personal data. Routine encrypted recovery archives have 14-day protection/rotation. Provider-native automatic backups and separate manual migration/incident restore points have a distinct lifecycle according to recovery/rollback need or a particular legal hold;14 days does not assert that every older manual copy has already expired. Access is restricted, they are not the ordinary active database, and recorded erasures/restrictions are applied before restored data is reused. Ask for the applicable deadline/basis for particular retained information. Financial originals also have a separate encrypted archive protected against alteration or early deletion for the applicable accounting period in section 11. For the ordinary ten-year category, protection expires on 1 January after the ten calendar years following the issue year. This archive contains the document, necessary financial facts, applicable terms and delegation evidence, rather than the whole profile, chats or identity-document copies. It is separate from the 14-day recovery archives; after expiry it is subject to deletion unless a specific applicable legal hold requires further retention. Deletion removes the public personal invitation code, its older aliases and the invitation attribution link. The restricted pseudonymised fingerprint preventing reassignment of an old link is separate from the active profile and retained only for the purpose described in section 11. Necessary financial records retain their own grounds and periods. 13. Rights, response period and complaints Subject to the applicable conditions, request access/copy, rectification, erasure, restriction, portability, objection to legitimate interests/direct marketing and withdrawal of consent actually given. Withdrawal does not affect earlier lawful processing; a separate specific legal ground can still require limited retention. Contact info@hazain.bg. Proportionate identity verification may be needed, not an unnecessary identity-document copy by default. GDPR responses are generally due within one month of receipt; where a necessary lawful extension of up to two further months applies, we notify you within the first month with reasons. This rights-response period differs from consumer 14-day withdrawal and the deletion-cancellation window above. A refusal explains its grounds and complaint routes. The Bulgarian supervisory authority is the Commission for Personal Data Protection: https://cpdp.bg . You may also approach the applicable supervisory authority or court. 14. Scores, safety and changes Profile/listing readiness, matching and technical checks support Hazain’s workflows. An incomplete profile/unverified contact may automatically limit the relevant function; this does not automatically conclude a tenancy or promise application approval. The landlord/tenant and authorised human team make the relevant decisions. Request an explanation, correction and human review of a restriction/disputed assessment. Do not collect protected/sensitive ranking traits in general fields. The service is for adults. We use role limits, encrypted transport/protected storage and access accountability; do not ask for/send passwords or banking codes in chat. External websites you choose to open have their own terms. Material changes get a new published version and updated notice; new consent is sought only for purposes that actually require it. An older identifier/date without a retained text hash is not presented as proof that new text was read. 15. Companies, billing and electronic documents For a landlord company we collect its legal name, registration number, registered address, declared VAT status/number, representative, document email, selected property/tax treatment and delegation versions/times. A company is separate from the personal login profile. The selected lawful lessor’s details appear in its offer/agreement; your other companies and private document email are not published. Personal invoices use a name, billing address and the necessary Bulgarian EGN/LNCh or foreign billing identifier through a separate protected form. Billing does not require an identity-card copy. The identifier is excluded from the public profile and masked in checkout previews; the official invoice includes necessary details and is accessible to its lawful issuer and recipient. VIGINTI is controller for its own supplies, invoices, payment confirmations and legally necessary accounting/claim evidence: GDPR Article 6(1)(c) for mandatory documentation and Article 6(1)(b) for the requested service. For company rent invoices the company is supplier/controller and Hazain follows documented instructions under the separate company-invoicing conditions. Hazain retains its own responsibilities for platform security/data. Necessary billing details are required before an invoiceable purchase or signing an enabled company letting. Without them that operation cannot continue; browsing public offers does not require a national identifier. Company/payment details are used in an expressly requested Stripe setup; bank/KYC details are supplied to Stripe in its own process. Google Cloud stores protected records; Google Workspace/Gmail delivers the PDF and applicable terms. The international safeguards above apply. Each issued invoice/credit note retains the original parties, number, date, price/tax, PDF and reference to the exact applicable terms. Profile edits do not rewrite documents. Invoices, corrections and delegation evidence follow the necessary accounting/tax periods in section 11 with restricted access; unrelated profile data is considered separately for erasure. A sent status means mail-provider acceptance, not proof that the recipient read it. Issued documents are also in Settings → Receipts and invoices. Corrections, copies or questions: info@hazain.bg. 16. Camera presence video check Following a specific flag, suspected misuse or an individual assessment by our team, we may request Hazain’s own camera check. This is separate from Stripe Identity. The affected request remains held until the requested check and human approval are complete. Before capture, we provide separate information and ask for the applicable confirmation; these terms alone do not authorize camera access. If you decline or encounter a technical problem, you may ask for human assistance and an applicable alternative review, without an automatic penalty. Each step makes a short continuous silent video before, during and after the screen lights up. Hazain checks for a human face, the requested position and the change in face illumination. This is our own automatic presence check, not government identity-document verification or certified deepfake protection. It does not create a face-recognition library. Failed steps can be repeated; a failed recording does not grant verification. Successfully accepted videos are encrypted and retained for 30 days in the separate restricted Google Cloud evidence store in europe-west1, outside the public profile and ordinary backups. Other customers and the landlord do not receive the recordings. An authorized staff read requires additional authentication, permission, a reason and an assigned case where required by the role; access is audited and a protected-access notification is sent. Withdrawal, a new check or changed personal details ends access and triggers earlier deletion. After expiry, the check result and necessary limited verification records remain, not the video. The data is used for the security and authenticity of the requested connection under GDPR Article 6(1)(f). The separate camera-start choice is not blanket consent to other processing. You can withdraw the check in your profile and request human assistance, contest a result or exercise your rights through info@hazain.bg. The isolated test camera has its own explicit notice and does not define production retention. 17. Stripe Identity — document and selfie To help prevent impersonation during a full application or a justified additional check, Stripe receives your identity document and selfie directly through its hosted page. Hazain does not download those images and does not retain your document number. Additional document fields, if returned by the provider, are discarded without storage. Limited verified names and date of birth are compared with your profile; we then retain the result, its binding to the current profile, the check identifier, timestamps and notice version. We do not send Stripe results or documents to landlords or use them as a credit assessment or government-registry search. Hazain and Stripe have independent controller responsibilities for their respective purposes. Hazain uses the limited data for security and fraud prevention under GDPR Article 6(1)(f). Biometric processing for identification requires separate explicit consent under Article 9(2)(a), where this is the applicable basis; general terms do not replace it. You may withdraw consent and request an alternative human review through Support without automatic loss of a deposit. We request redaction/deletion after a final result or cancellation; unfinished checks are cancelled after approximately 47 hours. Temporary provider failures are retried through system maintenance. Hazain’s minimal record remains only while needed for the active account, accountability or a specific lawful dispute and is covered by the erasure process. Stripe may retain data for its own lawful purposes under its policy; our request does not promise deletion of all its independent records. Processing may involve international transfers, including to the US. See https://stripe.com/privacy and https://stripe.com/privacy-center/legal. Hazain’s own camera check is separate and described in section 16. When there is a guarantor, their Stripe check is separate from the applicant’s. They personally open the check, receive the information and give their own explicit consent to Stripe where required. Hazain matches their first and last names to the saved guarantor details and retains a separate limited result and binding; the applicant’s result cannot verify a guarantor. We do not ask the guarantor to enter a date of birth separately. The same access limits, absence of Hazain ID copies, Stripe deletion requests, international-processing safeguards and rights apply. Work or study documents remain private evidence for authorised human review, not public profile attachments. 18. Onsite services and credits For an ordered service we process contact details, exact address, requested and confirmed dates, visit completion and internal factual reports: GDPR Article6(1)(b) for the customer and Article6(1)(f) for necessary rights protection and counterparty data. Access is restricted to staff fulfilling and supervising the service; reports are not public or automatically sent to another party. They are kept for the active service; later retention for a specific claim requires a reasoned basis and expiry. A report does not automatically become an accounting record. Erasure requests are reviewed separately from the minimal record of paid and used visits. For referrals and credits we record the selected inviter, qualifying confirmed payment, amount, rationale and balance movements: Article6(1)(b) for the requested programme and service, Article6(1)(f) to prevent duplicate awards or abuse and Article6(1)(c) for applicable accounting obligations. Compensation retains the authorised staff decision and reference to the reviewed case and counterparty account closure. Customer history does not disclose other accounts' identities or internal reports. Financial retention in section11 applies only to necessary financial records. A personal invitation link may contain a transliterated first name and digits, for example /r/George559. This is a public identifier, not a password or sign-in credential; do not share it if you do not want the recipient to see that name. Older codes may continue to lead to the same invitation. You confirm the inviter for your own account or decline; the answer is recorded so the question is not repeated. After you explicitly choose an invitation, the site may retain its protected cookie for up to 7 days under the Cookies Policy. A manually entered link is checked as a code; we do not open an external address to validate it. 19. Contract annexes, guarantors and a new-home gift For a new guarantor without an account, we privately process full legal name, birth date, correspondence address, email, phone and the last four ID characters. This form does not request the full ID number or an ID copy. Participants check the original in person; signed contract pages may contain additional information. Data and evidence are available only to the relevant contract parties and expressly authorised staff for fulfilment, safety and legal claims, not as a public profile. The basis is performance of the agreed participation, recording and protection of rights; necessary retention follows the general contract periods described above. Inform the person before entering their details. Annexes, direct-payment declarations and bank notices retain their exact version, signatures and history. They are not public bank details, and a transfer declaration is not independent bank confirmation. An external signed original is an optional private upload to evidence the tenancy. After confirmed move-in we may offer a free gift, without a review, advertising or marketing-consent condition. Only if you request it do you provide a name, delivery address, town/village, postcode and phone. Your express consent covers delivery through the postal or courier operator identified at dispatch and an email shipping notice. Details are not shared with the landlord and do not change your profile or contract address. Staff see only what preparation and actual dispatch require. You can decline before dispatch; after preparation begins we first check whether the parcel has already been handed over. Confirmed cancellation or decline removes the address and phone from the parcel record. After dispatch they and the tracking reference are removed within 90 days. A minimal staff record and basis remain for accountability and rights under the general retention periods. Test parcels are clearly labelled and not actually shipped. 20. Optional advertising measurement with Meta Pixel Only after explicit permission through Allow all or the Meta checkbox in cookie settings do we load Meta Pixel (1113055794700967) on the main landing, tenant/landlord landings and public rental topic pages. The basis is consent under GDPR Article 6(1)(a). Refusal does not restrict the service or affect invitations or gifts. Dismissing the previous information notice was not consent. Meta receives a PageView event, the visited public URL and referring URL, IP address, browser/device information and its identifiers for ad measurement, audiences and relevant ads. We disable automatic matching and automatic events, and send no session recordings, form fields, contacts or Hazain account identifiers. We send no events from registration, login, profiles, agreements, payments, messages or other private pages. Meta Platforms Ireland Limited is a recipient; responsibilities for collection and transmission through Business Tools are described in https://www.facebook.com/legal/controller_addendum, with subsequent processing covered by https://www.facebook.com/privacy/policy/ and https://www.facebook.com/legal/technology_terms. International transfers may take place under the safeguards described by Meta. The choice is stored locally for up to 180 days. You can withdraw permission at any time through Manage cookies in the footer: we stop subsequent events and remove Hazain-accessible _fbp/_fbc cookies. Withdrawal does not undo lawful earlier processing or automatically erase data already received by Meta; use Meta’s settings/contact to exercise rights with Meta. You may also contact info@hazain.bg. The limited server statistics in section 3 are separate and do not depend on Meta. 21. Google Analytics and saved cookie choices Google Analytics (G-HMMR875VEH) loads only after separate permission to analyse public visits. The recipient is Google Ireland Limited; data and restrictions are described in the “Google Analytics on this website” supplement. Private account, application, agreement, payment and chat pages are not measured. Google advertising features remain disabled. For signed-in customers, the private account stores the separate Google Analytics and Meta choices, notice version, decision time and record version to restore settings after sign-in without repeating the same question. The record implements and evidences the choice, rather than serving advertising; it is available only to its owner through settings and is included in applicable data-access and erasure procedures. A valid previous choice from this browser can be retained at first sign-in; without a choice, optional purposes are off. After 180 days, permitted measurement stops until a new explicit choice is made. Updating the Terms or Privacy Policy does not enable analytics or marketing and does not override refusal. Accepting updated documents preserves the separate settings. New optional purposes remain off. Change the choice through “Manage cookies”; withdrawal stops future measurement and clears accessible cookies for that service. Core functions and necessary storage remain available. 22. Profile and customer-request review To handle requests and prevent abuse, authorised staff can see the current profile, phone verification and related applications, viewings, reports and requests. Phone verification is the completed-registration milestone; email confirmation alone is not. After registration we retain up to 50 earlier profile versions from the last 30 days, including submitted details and photographs, to compare requested corrections. Staff access is recorded. Erasing the relevant information also erases these versions. This history is not displayed publicly or used for advertising. When you report a conversation participant, authorised staff can review the specified conversation to investigate the report; this does not grant general access to your other conversations. Messages sent by staff to your account include their sending and dismissal times; up to 100 messages are kept for at most 30 days. Registration, first property-contact and Support requests generate minimal internal notices to the Hazain team, and phone verification triggers a welcome email to your verified address. Existing email preferences continue to apply. The purposes are providing and reasonably protecting the requested services, under the same bases and rights described above. 23. Optional messages and unsubscribing With a separate voluntary choice, we use your verified email for Getting started with Hazain reminders, new listings matching your saved search, and email news/offers. Viber offers use the separately selected, verified phone number. The basis for these optional messages is consent under GDPR Article 6(1)(a), not acceptance of the Terms or Privacy Policy. Listings are selected using your current saved-search criteria, not a decision producing legal or similarly significant effects. We store the category, choice, time, notice version, source of change and a protected binding to the address/number. The current choice and a bounded history of up to 40 decisions are retained to administer messages and demonstrate accountability while the account exists; closure follows the deletion rules and specific lawful grounds for limited retention. An old choice is not activated for a new email or phone without the corresponding confirmation. Withdrawal is free, does not disadvantage core service use, and is available in settings or through an email link without signing in. For Viber we also accept a STOP reply, excluding subsequent promotional sends. Unsubscribing suppresses queued unsent messages in that category. A message already handed to its delivery provider cannot be recalled. Sign-in codes, essential security notices and payment documents remain separate. If you choose Viber, recipients include Viber Media S.à r.l. and applicable Rakuten Viber entities/providers, handling the number and content under their own terms and policy: https://www.viber.com/en/terms/viber-privacy-policy/. We do not send identity documents, contracts or sensitive profile data through this channel. The international-processing rules above apply to external providers. Gmail/Google delivers emails under the conditions described in this policy. 24. Photo checks with SynthID To prevent fraud and support accurate profiles and listings, an authorised staff member may check any photo uploaded to a profile or listing through Google SynthID Detector (https://synthid.com). The basis is legitimate interests under GDPR Article 6(1)(f), subject to necessity and proportionality. This excludes identity documents, verification videos and standalone biometric identification. For a check, Google receives the photo and technical data relating to use of the tool. According to the SynthID Detector notice, the original is processed in real time and deleted after the result is returned; an anti-abuse digital signature linked to the checking account is retained for up to 24 hours. https://policies.google.com/terms, https://policies.google.com/privacy and the specific SynthID terms apply. Google is a separate recipient under those conditions; international processing follows the rules above. We use the permitted interface and do not bypass quotas or automation restrictions. Hazain retains the result, time and review decision with relevant moderation history for as long as necessary for content review, an objection or a specific legal claim, subject to the general deletion rules. The tool detects supported watermarks only and can miss AI content. We do not deny access solely through an automated SynthID decision. You may object, request human review or provide an original through Support or info@hazain.bg. 25. Apple maps and building search Apple apps use Apple Maps/MapKit. When you view a map or search for a building, Apple receives the search query, selected coordinates or visible map area and technical information needed for the service, such as the network request, device model, software and language. Hazain uses this to show the requested place or help select a property address. The app does not request the device GPS location for these maps. Separate apartment and floor fields are not sent to the building lookup. Avoid unnecessary personal details in the free-text query. Apple describes its own service at https://www.apple.com/legal/privacy/data/en/apple-maps/ and https://www.apple.com/privacy/. Map information does not make a private address public; the listing and participant permissions described above continue to apply. 26. Enabled Apple notifications When delivery is available and you allow notifications, Hazain associates the installation identifier and APNs token with your account/device to deliver selected notifications. Apple receives the delivery token, app/environment, a generic Hazain alert and technical event/subscription references. The APNs message does not contain private chat text, a document or private property details. Content is fetched from Hazain after authentication and access checks. Necessary delivery serves the requested service; optional message choices remain separate under the rules above. You can control permission in Apple device settings and categories in Hazain. Signing out revokes the binding for that device. The retention, protection, erasure and rights rules in this document apply to these records. Permission alone does not mean an unimplemented or unconfigured delivery service is active. 27. Audio calls, language and device storage Microphone use starts after your action to make an audio call and device permission. Live audio is encrypted with WebRTC to the other participant; a network relay processes the traffic and technical network information when needed. Hazain does not record call audio. Status, time and duration are retained in the authorised conversation context and follow the common information/history rules above. Language suggestions use on-device recognition. Message translation is sent to the Google EU service only after the separate translation choice described in this document. The app sends no events through the website Meta/Google Analytics pixels. Their separate rules above apply when visiting the website. The embedded Stripe payment SDK processes technical device data and interactions with its payment components for functionality, product analytics and fraud prevention; this data may be linked to your identity. Stripe does not use it for advertising tracking. Stripe’s responsibilities, international transfers and your rights are described above and at https://stripe.com/privacy ; technical details: https://support.stripe.com/questions/stripe-mobile-sdk-privacy-details . Necessary protected sessions and bounded local drafts/caches serve the requested function rather than advertising tracking.