Miller Ingatlan
Miller Ingatlan

+36 20 932 1077

milleringatlan1@gmail.com

4026 Debrecen, Péterfia utca 4

Browse

  • All Properties
  • Sell
  • About
  • Contact

Legal

  • Privacy Notice
  • Terms and Conditions
  • Cookie Policy
  • Reporting unlawful content
  • Imprint

© 2026 Miller Ingatlan. All rights reserved.

Powered by

Privacy Notice

Revised: 14 October 2026 · Effective from: [EFFECTIVE_DATE]

Introduction

This notice describes what personal data Miller Ingatlan processes on the milleringatlan.hu website and related services, for what purpose and on what legal basis, for how long, to whom it passes the data, and what rights you have. It is based on the EU General Data Protection Regulation (GDPR – (EU) 2016/679), Act CXII of 2011 on informational self-determination and freedom of information (Infotv.), Act C of 2003 on electronic communications (Eht.) and Act CVIII of 2001 on electronic commerce services. This information is not your consent: where consent is needed (analytics) we ask for it separately.

The controller

Controller: [TELJES_JOGI_NÉV]; registered office: [SZÉKHELY]; mailing address: [LEVELEZÉSI_CÍM]; registry and number: [NYILVÁNTARTÓ_SZERV], [NYILVÁNTARTÁSI_SZÁM]; tax number: [ADÓSZÁM]; e-mail: info@homio.hu; telephone: [TELEFONSZÁM]. The brand of the service is Miller Ingatlan.

We currently do not appoint a data protection officer; for privacy matters you can reach us at the contact details above. If circumstances (such as the scale of processing) require it, we will appoint one and publish the contact details here.

If you enquire about a listing or send a message or a viewing request, the advertiser also receives its content. Depending on its type (estate agency, agent or private individual) the advertiser may be an independent controller of the processing of your enquiry for its own purposes; the advertiser determines and is responsible for its own status, and Miller Ingatlan only passes the enquiry on.

Overview of processing

The overview below shows, purpose by purpose, who is affected, what data we process and where it comes from, the legal basis, whether providing the data is required, the recipients, how long we keep the data and whether it is transferred to a third country. The details of retention are in the retention table below.

  • Creating an account, sign-in, security

People affected
Registered users, advertisers, agents and administrators.
Data and its source
Name, e-mail address, password (only as a one-way salted hash), role, language and notification settings, two-factor authentication data; with Google sign-in, the name and e-mail address Google passes on. Source: you, or Google.
Legal basis
Performance of a contract (GDPR Art. 6(1)(b)).
Whether providing the data is required, and the consequence
Needed for the account; without it no account can be created, and browsing is available without one.
Recipients
Hosting and infrastructure providers, e-mail delivery provider; Google (if you choose Google sign-in).
Retention
For as long as the account exists; see the retention table for deletion.
Transfer to third countries
Possible for infrastructure and e-mail providers and for Google.
  • Enquiries, messages, viewing times

    People affected
    People enquiring (with or without an account) and advertisers.
    Data and its source
    Name, e-mail address, telephone number (if given), the content of the message, viewing-request data; the identifier of the listing and the advertiser. Source: you.
    Legal basis
    Performance of a contract or steps at your request (Art. 6(1)(b)); legitimate interest (f) for secure message delivery.
    Whether providing the data is required, and the consequence
    Name, e-mail and message are needed to make contact; without them the enquiry cannot be sent.
    Recipients
    The advertiser (as an independent controller), e-mail delivery provider, hosting provider.
    Retention
    See the “Conversations” and “Enquiries” rows of the retention table.
    Transfer to third countries
    Possible for the e-mail provider.
  • Posting and showing listings

    People affected
    Advertisers, estate agencies and agents; third parties who appear in a listing (owner, people in images).
    Data and its source
    Property data, the advertiser’s and agent’s displayed contact details, photos, floor plans, videos, the address (exact, or approximate if so set), drafts. Source: the advertiser; the advertiser adds data of people in the images.
    Legal basis
    Performance of a contract (Art. 6(1)(b)) with the advertiser; public display of the listing rests on the advertiser’s decision.
    Whether providing the data is required, and the consequence
    The data needed for the listing must be given; without them it cannot be published.
    Recipients
    Anyone, for a public listing; Cloudflare, Inc. (media storage), Geoapify GmbH (to geocode the address).
    Retention
    A published listing: until archived or deleted; see the retention table.
    Transfer to third countries
    Possible for Cloudflare.
  • Favourites, saved searches, alerts, collections, personalisation

    People affected
    Registered users.
    Data and its source
    Favourites, saved searches and alerts, collections, hidden listings, price-drop watches, viewing history. Source: you (your own actions).
    Legal basis
    Performance of a contract (Art. 6(1)(b)): providing the feature requested; we send commercial newsletters only with separate, express consent (a).
    Whether providing the data is required, and the consequence
    Not required; without them these features do not work.
    Recipients
    Hosting and e-mail providers.
    Retention
    For as long as the account exists.
    Transfer to third countries
    Possible for the e-mail provider.
  • Floor-plan designer

    People affected
    Registered users who use the designer.
    Data and its source
    The floor plans you design and their preview images. Source: you.
    Legal basis
    Performance of a contract (Art. 6(1)(b)).
    Whether providing the data is required, and the consequence
    Not required; needed to use the feature.
    Recipients
    Hosting and media storage providers (Cloudflare, Inc.).
    Retention
    For as long as the account exists or until the plan is deleted; when you delete your account we delete the images too.
    Transfer to third countries
    Possible for Cloudflare.
  • Security, abuse prevention, error monitoring

    People affected
    All visitors and users.
    Data and its source
    IP address (also hashed for abuse checks), browser and device type, request times, technical data in error reports, the reCAPTCHA result. Source: your browser.
    Legal basis
    Legitimate interest (Art. 6(1)(f)): running the service securely and reliably, protection against fraud and spam. We give our balancing test on request.
    Whether providing the data is required, and the consequence
    Technically necessary to reach the service; if the reCAPTCHA check fails the form cannot be submitted.
    Recipients
    Functional Software, Inc. (Sentry), Google (reCAPTCHA), hosting providers.
    Retention
    Up to 90 days; see the retention table.
    Transfer to third countries
    Possible for Sentry and Google.
  • Visit and usage analytics

    People affected
    Visitors who accepted analytics.
    Data and its source
    Pseudonymous visitor and session identifier, pages visited, searches and usage events. Source: your browser, only after consent.
    Legal basis
    Consent (Art. 6(1)(a)); can be withdrawn at any time with “Cookie settings”.
    Whether providing the data is required, and the consequence
    Not required; refusing carries no disadvantage.
    Recipients
    No external recipient; stored in our own system with our hosting provider.
    Retention
    Raw events for 90 days, after that only aggregated statistics.
    Transfer to third countries
    No.
  • Address and location search

    People affected
    People using address autocomplete, the map or nearby places.
    Data and its source
    The address fragment typed, the map query. Source: you. Your IP address does not reach Geoapify.
    Legal basis
    Performance of a contract (Art. 6(1)(b)): providing the feature requested.
    Whether providing the data is required, and the consequence
    Not required; without it the feature cannot be used.
    Recipients
    Geoapify GmbH (Germany).
    Retention
    Results are cached without link to a user until they expire, then deleted.
    Transfer to third countries
    No.
  • Content reports, moderation, complaints

    People affected
    Reporters, advertisers whose content is reported, and complainants.
    Data and its source
    The reporter’s name and e-mail address (or account), the reasons, the good-faith statement, a hashed IP address for abuse protection, the decision and its reasons; for a complaint, the complaint and the reply. Source: the reporter, the advertiser, moderation.
    Legal basis
    Legal obligation (Art. 6(1)(c)), or legitimate interest (f): lawful running of the platform.
    Whether providing the data is required, and the consequence
    The reporter’s name and e-mail address – with the statutory exceptions – are needed for a valid report.
    Recipients
    Administrators; the advertiser concerned only gets the decision and its reasons (we do not pass on the reporter’s data).
    Retention
    See the retention table.
    Transfer to third countries
    No.
  • Evidence of contract and consent

    People affected
    Registered users; visitors who made a cookie choice.
    Data and its source
    The accepted document and its version, the time, the source and a hashed IP address; for the cookie choice, the browser’s random identifier, the decision, the version and the time.
    Legal basis
    Legal obligation and legitimate interest (Art. 6(1)(c), (f)): to show when and to what you agreed.
    Whether providing the data is required, and the consequence
    Accepting the Terms is needed to register.
    Recipients
    Hosting provider.
    Retention
    See the retention table.
    Transfer to third countries
    No.
  • Legal claims, official requests, mandatory retention

    People affected
    Anyone whose data is needed for the matter.
    Data and its source
    The data needed for the matter. Source: those involved, authorities.
    Legal basis
    Legal obligation (Art. 6(1)(c)), or legitimate interest (f): bringing, asserting and defending legal claims.
    Whether providing the data is required, and the consequence
    Required where a legal obligation applies.
    Recipients
    Authorities, courts, legal representatives.
    Retention
    Until the matter is closed, or for the statutory retention period.
    Transfer to third countries
    No.
  • Data from other sources

    Some data does not come from you: advertisers may give data of third parties – such as owners, neighbours, agents – in listings (photos, texts, floor plans, contact details); an agency gives the data of agents acting in its name; a person reporting content provides information about the advertiser or content reported; and with Google sign-in Google passes on your name and e-mail address. If you believe your data appears in a listing without authority, tell us by reporting unlawful content or through our privacy contact.

    Recipients and their roles

    We do not sell your personal data. Those who access data fall into three groups with different roles:

    Acting as processors, on our instructions and as far as needed to provide the service: hosting and infrastructure providers (application and database hosting: [TÁRHELYSZOLGÁLTATÓ_NEVE_ÉS_CÍME]); Cloudflare, Inc. (R2 object storage: uploaded images, floor plans, videos); the e-mail delivery provider (forwarding system messages, notifications and enquiries); Geoapify GmbH (Germany; address autocomplete, geocoding, maps, nearby places: the address fragment or map query reaches them, not your IP address); Functional Software, Inc. (Sentry; error monitoring, with technical data in filtered form); Google (reCAPTCHA: according to Google’s published information, a processor for customer data from 2 April 2026).

    Acting as independent controllers: advertisers (estate agencies, agents and – depending on type – private individuals), who handle your enquiry for their own transaction; Google Ireland Limited for Google sign-in in its own account processing.

    Authorities and courts: where a legal obligation or an official request requires, to the extent the law provides.

    Transfers to third countries

    Some of our providers (for example those established in the United States: Cloudflare, Sentry, Google) may also process data outside the European Economic Area. We carry out or use such a transfer only where one of the conditions in Chapter V of the GDPR is met. On request we tell you what solution applies at a given provider.

    Retention periods

    We keep your data only as long as needed for the purpose or as long as a legal obligation lasts. The table below ties retention to Miller Ingatlan’s actual systems and shows when the clock starts.

    • Account data, profile, settings, favourites, saved searches, collections, alerts (primary database)

      Retention period
      For as long as the account exists; deleted at once when the deletion is carried out.
      What starts it
      Deletion of the account (by you or at your request).
    • Conversations, messages, viewing requests

      Retention period
      No separate automatic deletion deadline: a conversation stays until the account of either participant or the listing is deleted.
      What starts it
      Deletion of either participant’s account or of the listing concerned.
    • Enquiries sent through the contact form and about a listing (including without an account)

      Retention period
      No separate automatic deletion deadline; we keep them as long as needed to handle them, and you can ask for deletion.
      What starts it
      Closing the enquiry; a deletion request.
    • Listings, drafts, photos, floor plans, videos

      Retention period
      Published listing: until archived or deleted. Archived listing: not public, kept until the owner or an administrator deletes it. Blank draft: deleted automatically after 24 hours.
      What starts it
      Archiving or deletion; listings must be dealt with before the account is deleted.
    • Content reports and moderation decisions

      Retention period
      Closed cases for 24 months; an open case until it is closed. If the reporter deletes their account, the reports they made are deleted too.
      What starts it
      The date of the decision.
    • Analytics events (with a pseudonymous identifier)

      Retention period
      Raw events for up to 90 days, after that only aggregated statistics that cannot be traced back to a person.
      What starts it
      The event being created.
    • Log of administrators’ actions (including actions on accounts and listings, with the name of the person concerned)

      Retention period
      24 months. The name of a deleted account may remain in the log during that time.
      What starts it
      The log entry being created.
    • Technical and security logs, error reports (Sentry)

      Retention period
      Up to 90 days; for as long as needed if a security incident is being investigated.
      What starts it
      The entry being created.
    • Database backups

      Retention period
      Up to 90 days, then destroyed automatically.
      What starts it
      The backup being made.
    • Media backup (a copy of uploaded images, floor plans and videos in a separate bucket)

      Retention period
      The backup does not remove files deleted from storage, and there is currently no automatic deletion deadline for them: a deleted file can remain in the backup until the backup is cleaned up.
      What starts it
      The file being deleted from the live storage.
    • Record of acceptance of the Terms and the notice; record of cookie consent

      Retention period
      The record of acceptance is deleted with the account. The cookie-consent record is pseudonymised (random browser identifier, hashed IP) and currently has no automatic deletion deadline.
      What starts it
      Deletion of the account; the cookie choice.

    Account deletion, backups and third parties

    If you delete your account (or ask for it to be deleted), we delete the data belonging to it from the primary database at once when the deletion is carried out, and we also remove your profile photo and the images of your saved floor plans from storage. Deletion also ends the conversations connected to your account, so they disappear on the other party’s side too. An account cannot be deleted while listings (drafts included) belong to it: those must first be deleted or handed over. In exceptional cases deletion may be prevented by a statutory retention duty, or by narrowly scoped retention tied to a specific matter that is needed to assert or defend a legal claim; in that case we keep only the data needed for that and tell you.

    Database backups are made and kept for up to 90 days, then destroyed automatically. So deleted data may still be in backups for that long, but we do not use them for anything; if we had to restore from a backup, we would carry out the deletions already made again. We cannot guarantee the deletion of independent copies held by third parties – for example messages already forwarded to advertisers, data handed to authorities, or public listing content already copied by search engines and other users – but on request we tell the recipients concerned where the law requires it. Uploaded images, floor plans and videos are also backed up in a separate bucket; a deleted file does not disappear from there at once (see the retention table).

    We do not treat pseudonymised data (such as the random browser identifier in the consent record) as anonymous while the link between the identifier and the browser exists; we speak of anonymisation only where the possibility of re-identification has actually been excluded.

    Data security

    We apply appropriate technical and organisational measures to protect your data, including:

    • encrypted (HTTPS) data transfer;
    • passwords are never stored in readable form;
    • access tokens travel in HttpOnly, SameSite=Strict cookies, and requests that change data are protected against CSRF;
    • role-based access control and logging in the administration interfaces;
    • scanning of uploaded files for malicious content (where switched on in operation), regular backups, and limiting access to the minimum needed.

    In case of a personal data breach that is likely to result in a risk to people’s rights and freedoms, we notify the supervisory authority without undue delay and, where feasible, no later than 72 hours after becoming aware of it (GDPR Art. 33); if the breach is likely to result in a high risk, we also notify the people affected without undue delay (GDPR Art. 34), subject to the exceptions in that article. The notification goes to the supervisory authority competent for the operator’s actual place of establishment; where it is established in Hungary, that is NAIH.

    Cookies and similar technologies

    Our Cookie Policy gives detailed information on the use of cookies and data stored in the browser, their purpose, expiry and how to set them. The analytics category works only with your express consent, which you can withdraw at any time with the footer link “Cookie settings”. The analytics identifiers are pseudonymised, not anonymous.

    Personalisation, automated decisions and profiling

    The personalised sections on the home page and in listings (such as “recently viewed”, recommendations, alerts) are based on your own earlier actions – views, favourites, saved searches. This may count as simple profiling, but we do not base decisions with legal effect, or that similarly significantly affect you, on it. We do not use recommendations for an advertising profile, and you may object to the handling of your viewing history.

    Some protective measures work automatically: rate limiting, the reCAPTCHA check, the security scan of uploaded files and restriction of failed sign-ins may temporarily stop an action. If you think such a measure affected you wrongly, you can ask for human review at our contact details.

    Children and age

    Our service is not for people under 16 and we do not knowingly collect personal data from them. The age for data processing and the capacity to contract are separate questions: the contractual conditions (for 14 to 18 year olds, with the legal representative’s consent) are in the Terms. If we learn that someone under 16 has given data without parental consent, we delete it without delay.

    Your rights as a data subject

    Under Articles 15–22 of the GDPR you have the following rights:

    • Access: you can ask whether we process your personal data and get a copy of it.
    • Rectification: you can ask us to correct inaccurate or incomplete data.
    • Erasure (“right to be forgotten”): you can ask us to erase your data where one of the conditions in GDPR Art. 17 applies (for example the processing no longer has a legal basis); erasure may be limited where retention is required by law or is needed to assert legal claims. You can also delete your account yourself in the settings.
    • Restriction: you can ask us to restrict processing, for example while you contest the accuracy of the data.
    • Portability: where processing is based on consent or contract and carried out by automated means, you can receive the data you provided in a structured, machine-readable format and transmit it to another controller.
    • Objection: you can object, on grounds relating to your situation, to processing based on legitimate interests; we then stop processing unless there are compelling legitimate grounds that override your interests, or it is needed for legal claims.
    • Withdrawal of consent: you can withdraw consent at any time; this does not affect the lawfulness of processing before withdrawal.
    • Complaint and remedy: see the next section.

    We answer your request without undue delay and at most within one month of receiving it; where needed, given the complexity and number of requests, this period may be extended by two further months, and we tell you of this and the reason within one month. Information and action are free of charge; for a manifestly unfounded or excessive request we may charge a reasonable fee or refuse to act. We may need additional information to confirm your identity.

    Remedies

    If you feel your data is being processed in breach of the law, you can complain to the Hungarian National Authority for Data Protection and Freedom of Information (NAIH): 1055 Budapest, Falk Miksa utca 9–11; postal address: 1363 Budapest, Pf. 9; telephone: +36 1 391 1400; e-mail: ugyfelszolgalat@naih.hu (a procedure cannot be started by plain e-mail); electronic filing: naih.hu/online-ugyinditas or epapir.gov.hu; KR ID: 429616918 (checked on 14 October 2026; current details at naih.hu). You can also turn to the supervisory authority of the EU Member State where you live.

    If your rights are violated you can also go to court (GDPR Art. 79, Infotv. section 22). At your choice the case can be brought before the regional court of your place of residence or stay. Contacting us first is not a condition of going to the authority or to court, but we are glad to settle the matter directly.

    Changes to this notice

    We update this notice when the law or the service changes. We tell you about material changes on the site and, where needed, by e-mail; the version in force is always on this page.

    Contact

    For privacy questions, or to exercise your data-subject rights, please reach us through the our contact page.