Last updated: 14 May 2026

Privacy Policy for iNmap.info

English Master Version
Effective date: 14.05.2026
Controller / Operator: VisionEdge s.r.o.

1. Introduction

1.1. This Privacy Policy explains how VisionEdge s.r.o. collects, uses, discloses, stores and protects personal data in connection with the digital platform iNmap.info.

1.2. This Privacy Policy is designed to work together with the Terms of Service for iNmap.info – English Master Version v1.0 and should be read together with those Terms.

1.3. The Platform may provide digital mapping, real estate project presentation, project data management, analytics, lead generation, marketplace-support features, communication tools, AI-assisted analysis, dashboards, APIs and related services.

1.4. Because iNmap.info may be used internationally, this Privacy Policy is drafted to support compliance with multiple privacy frameworks, including where applicable:

1.5. Not every provision will apply to every User. Some rights and obligations depend on the User’s location, the User’s role, the type of data, the purpose of processing, the applicable law, the commercial model and whether legal thresholds are met.

2. Controller Identification

2.1. The controller and operator of the Platform is:

VisionEdge s.r.o.
Company ID / IČO: 51962161
Tax ID / DIČ: 2120848521
Registered office: 29. augusta 1503/1A, 958 01 Partizánske, Slovak Republic, European Union
Website: https://inmap.info

2.2. In this Privacy Policy, VisionEdge s.r.o. is referred to as “VisionEdge”, “iNmap.info”, “Operator”, “Controller”, “we”, “us” or “our”.

2.3. Contact addresses:

2.4. Unless and until a formal Data Protection Officer is appointed, privacy-related communication should be sent to legal@inmap.info.

2.5. If we appoint a Data Protection Officer, EU representative, Thai local coordinator, California privacy contact or other statutory contact in the future, we will update this Privacy Policy or provide a separate notice.

3. English Master Version

3.1. This Privacy Policy is prepared in English as the master version.

3.2. Any Slovak, Thai or other language version is provided for convenience, localisation or user understanding only.

3.3. In case of discrepancy between the English version and a translated version, the English version prevails, unless mandatory local law requires otherwise.

4. Definitions

4.1. “Personal Data” means any information relating to an identified or identifiable natural person.

4.2. “User” means any person who accesses, browses, registers for, uses or interacts with the Platform.

4.3. “Business User” means a User acting in the course of business, professional, commercial, real estate, development, investment, advisory, agency or corporate activity.

4.4. “Consumer” means a natural person acting outside their trade, business, employment or profession.

4.5. “Project Owner” means a User who uploads, manages, publishes or distributes information about a real estate project, development project, property, unit, listing, location, document or related commercial opportunity.

4.6. “Project Data” means data relating to real estate projects, properties, development projects, units, prices, availability, documentation, location, amenities, plans, images, commercial terms or related information.

4.7. “User Content” means content, information, files, data, images, documents, comments, messages, project records, map points, metadata or other materials provided by a User.

4.8. “Processing” means any operation performed on Personal Data, such as collection, recording, storage, use, disclosure, analysis, deletion or transfer.

4.9. “Processor” means a service provider or vendor that processes Personal Data on behalf of the Controller.

4.10. “Third-Party Services” means external tools, providers, platforms, APIs, processors or services integrated into or used by the Platform, including hosting, maps, analytics, payments, email, AI, security, CRM and communication services.

5. Roles: Controller and Processor

5.1. For most Platform operations, VisionEdge acts as the controller of Personal Data. This includes account management, billing, support, security, Platform analytics, legal compliance and user communications.

5.2. In some cases, a Business User may be the controller of Personal Data that it uploads to the Platform, and VisionEdge may act as a processor. This may occur where a Business User uploads customer, lead, investor, employee, contractor, agent or project-contact data for its own purposes.

5.3. Where VisionEdge acts as a processor, the relevant Business User is responsible for:

5.4. If a Data Processing Agreement applies, it prevails over this Privacy Policy for processor-specific obligations.

6. Personal Data We May Collect

6.1. We may collect the following categories of Personal Data, depending on how the User uses the Platform.

6.1.1. Account and identity data

This may include name, surname, username, account ID, company name, job title, role, business address, country, language preference, login credentials, authentication data and account settings.

6.1.2. Contact data

This may include email address, phone number, postal address, company contact details, communication preferences and support contact information.

6.1.3. Business and company data

This may include company identification number, tax identification number, VAT number, registered office, billing details, authorised representatives, corporate documents, business role, project affiliation and verification information.

6.1.4. Billing and transaction data

This may include subscription plan, order details, invoices, billing history, payment status, payment references, tax information, refund records, success-fee information, lead-fee information and transaction-related metadata. Payment card or bank details may be processed by third-party payment providers and may not be stored directly by us.

6.1.5. Project and real estate data

This may include project names, property locations, unit details, prices, availability, floor plans, images, documents, developer contact persons, agent contacts, project descriptions, commercial terms, construction status, legal notices, due diligence documents, listing data and related metadata.

6.1.6. Communications data

This may include emails, support tickets, contact forms, chat messages, meeting notes, complaints, content reports, appeals, feedback, call notes and communication history.

6.1.7. Lead and marketplace interaction data

This may include enquiries, lead submissions, project interest, contact requests, investor-developer communications, saved projects, comparison activity, viewed listings, shared documents, conversion records and business relationship metadata.

6.1.8. Technical, device and usage data

This may include IP address, browser type, device type, operating system, device identifiers, session data, log files, access times, pages viewed, feature usage, clicks, errors, crash logs, API usage, referrer URLs and security logs.

6.1.9. Location and map-related data

This may include approximate location derived from IP address, search locations, map coordinates, project map points, geocoding queries, address searches, distance calculations, travel-time requests, routing metadata and map interaction data.

6.1.10. Cookie and analytics data

This may include cookie identifiers, consent preferences, analytics events, session identifiers, marketing identifiers and similar technologies as described in the Cookie Policy.

6.1.11. AI and analytics data

This may include prompts, instructions, uploaded documents, extracted text, metadata, model outputs, classification results, scores, recommendations, summaries, translation outputs, data-quality labels and analytics results generated through AI-assisted or automated tools.

6.1.12. Compliance and security data

This may include verification records, fraud signals, sanctions screening results, AML/KYC-related metadata where applicable, audit logs, access logs, incident reports, abuse reports, enforcement records and legal correspondence.

6.1.13. Marketing data

This may include newsletter preferences, marketing consent, campaign engagement, event participation, source of registration, content preferences and opt-out records.

6.1.14. Sensitive or special-category data

We do not intentionally request sensitive or special-category Personal Data unless legally necessary or expressly required for a specific feature, agreement or compliance purpose. Users must not upload passports, national ID documents, health data, biometric data, criminal records, political opinions, religious beliefs or other sensitive data unless expressly requested by us and legally justified.

7. Sources of Personal Data

7.1. We may collect Personal Data from:

7.2. If a User provides Personal Data about another person, the User must ensure that the User is legally permitted to do so and that the person has received any required privacy notice.

8. Purposes and Legal Bases for Processing

8.1. We process Personal Data only where we have a lawful basis or other legally recognised ground.

8.2. The following table explains the main purposes and legal bases under GDPR-style regimes. Equivalent or similar legal grounds may apply under other laws.

8.3. Where we rely on legitimate interests, we balance our interests against the rights and freedoms of affected individuals.

8.4. Where we rely on consent, the User may withdraw consent at any time. Withdrawal does not affect the lawfulness of processing before withdrawal.

8.5. Where processing is necessary for a contract, failure to provide required data may prevent us from creating an account, providing services, processing payments or responding to requests.

8.6. Where processing is required by law, failure to provide required data may prevent us from complying with tax, accounting, sanctions, consumer, regulatory or other legal obligations.

9. Platform Accounts and Authentication

9.1. We process account and authentication data to create accounts, manage access, prevent unauthorised use, enforce usage limits, maintain account history and secure the Platform.

9.2. Users are responsible for keeping login credentials secure.

9.3. We may record login attempts, device data, session data and access logs to protect the Platform and Users.

9.4. If single sign-on or third-party authentication is used, the relevant provider may process Personal Data according to its own terms and privacy policy.

10. Project Data, User Content and Visibility

10.1. The Platform may allow Project Owners and Developers to upload and publish Project Data, including data that may identify natural persons, such as contact persons, representatives, agents, photographers, architects, consultants, buyers, investors or other stakeholders.

10.2. Depending on Platform settings and User permissions, Project Data and User Content may be:

10.3. Users must not upload Personal Data into public or semi-public project fields unless they are legally authorised to do so.

10.4. Users must not upload documents containing unnecessary Personal Data, identity documents, bank account details, signatures, personal addresses or sensitive data unless required for a specific lawful purpose and protected by appropriate permissions.

10.5. The Operator may remove or restrict Personal Data contained in User Content if it is unnecessary, unlawful, excessive, inaccurate, reported by a data subject or inconsistent with this Privacy Policy or the Terms of Service.

11. Lead Generation and Business Communications

11.1. The Platform may allow Users to request information, contact Project Owners, submit enquiries, save projects, compare projects, request documents or otherwise express interest in a project.

11.2. When a User submits a lead or enquiry, relevant Personal Data may be shared with the Project Owner, Developer, agent, partner or other recipient selected or reasonably expected by the User.

11.3. Such data may include name, contact details, company, role, country, project of interest, message content, enquiry history and related metadata.

11.4. Recipients of leads must use the data only for lawful business communication, project-related follow-up, customer relationship management or other purposes disclosed to the User.

11.5. Recipients must not use lead data for unlawful marketing, spam, resale, unauthorised profiling, discriminatory practices or unrelated purposes.

12. Maps, Geolocation and Location-Based Processing

12.1. The Platform may use maps, geolocation features, address search, geocoding, routing, distance calculations, travel-time estimates, points of interest, administrative boundaries, satellite imagery and other location-based features.

12.2. Location-related Personal Data may include IP-based approximate location, search queries, map interactions, project locations, saved locations, coordinates, routing requests and metadata.

12.3. The Platform may use multiple map and geolocation providers, including without limitation OpenStreetMap, Google Maps Platform, Mapbox, MapTiler, HERE, TomTom, Esri/ArcGIS, public registers, governmental datasets, commercial datasets, User-submitted data and proprietary datasets.

12.4. Map providers may receive certain technical or location-related data necessary to provide map functionality, such as IP address, map tiles requested, search queries, coordinates, browser data or device identifiers.

12.5. Users should review applicable third-party map provider terms and privacy notices where those services are integrated or linked.

12.6. We do not use precise live location tracking unless a specific feature clearly requires it and the User has granted the required permission.

12.7. The Platform’s map and location features are for informational and analytical purposes only and must not be used as the sole source for legal boundaries, cadastral verification, safety-critical navigation, emergency response, land surveying, engineering or other legally determinative purposes.

13. AI, Automated Analysis and Profiling

13.1. The Platform may use AI-assisted or automated tools to analyse Project Data, classify content, extract information, summarise documents, translate text, detect duplicates, identify inconsistencies, generate recommendations, score data quality, support search, improve user experience and enhance security.

13.2. AI-assisted outputs may be generated from User Content, Project Data, metadata, usage data and third-party data sources.

13.3. We do not intend to use AI outputs as the sole basis for decisions that produce legal or similarly significant effects on Users, unless a specific feature is clearly introduced with appropriate safeguards, notices and legal basis.

13.4. AI outputs may be inaccurate, incomplete, outdated or biased. Users must independently verify AI-assisted outputs before relying on them.

13.5. Where AI providers or large language model services are used as processors or sub-processors, we will seek to apply appropriate contractual, security and confidentiality safeguards.

13.6. Users must not submit sensitive Personal Data, trade secrets, confidential third-party data or regulated information into AI-enabled fields unless they are authorised to do so and the feature is intended for such use.

13.7. Where applicable law grants rights relating to automated decision-making, profiling, access, explanation, opt-out or human review, we will provide those rights as required.

14. Cookies, Analytics and Similar Technologies

14.1. We may use cookies, local storage, pixels, SDKs, tags, analytics identifiers and similar technologies.

14.2. These technologies may be used for:

14.3. Necessary cookies may be used without consent where legally permitted because they are required for Platform functionality or security.

14.4. Analytics or marketing cookies will be used according to applicable law and consent preferences where required.

14.5. Users may manage cookie preferences through the Platform’s cookie settings, browser settings or other available consent tools.

14.6. Additional details will be provided in the Cookie Policy.

15. Marketing Communications

15.1. We may send service-related messages, account notices, billing notices, security alerts and operational communications without marketing consent where necessary to provide the Platform or comply with legal obligations.

15.2. We may send newsletters, product updates, event invitations, offers or marketing communications where we have consent or another lawful basis.

15.3. Users may opt out of marketing communications at any time by using the unsubscribe link or contacting us at hello@inmap.info.

15.4. Opting out of marketing does not stop service, legal, billing or security communications.

16. Disclosure of Personal Data

16.1. We may disclose Personal Data to the following categories of recipients where necessary and lawful.

16.1.1. Other Users

Personal Data may be shared with other Users where the Platform functionality requires it, such as project publication, lead submission, communication between Investors and Developers, team collaboration or document sharing.

16.1.2. Service providers and processors

We may share Personal Data with providers of hosting, cloud infrastructure, databases, analytics, email, customer support, payments, maps, geocoding, AI, security, monitoring, CRM, accounting, legal and business tools.

16.1.3. Payment processors

Payment information may be processed by payment processors or financial institutions. These providers may act as independent controllers or processors depending on the circumstances.

16.1.4. Map and geolocation providers

Map providers may receive technical, device, map-interaction, search, coordinate or geolocation-related data necessary to provide map features.

16.1.5. AI and analytics providers

AI or analytics providers may process data needed to provide AI-assisted or analytical functions, subject to applicable contractual and security safeguards.

16.1.6. Professional advisers

We may share data with lawyers, auditors, accountants, tax advisers, consultants, insurers and other professional advisers.

16.1.7. Authorities and legal recipients

We may disclose data to courts, regulators, tax authorities, law enforcement, supervisory authorities, public bodies or other recipients where required by law, legal process, regulatory request or protection of rights.

16.1.8. Corporate transactions

If we are involved in a merger, acquisition, financing, restructuring, sale of assets, transfer of business or similar transaction, Personal Data may be disclosed to relevant parties subject to appropriate safeguards.

16.2. We do not disclose more Personal Data than reasonably necessary for the relevant purpose.

17. International Transfers

17.1. The Platform may operate globally and may involve cross-border transfers of Personal Data.

17.2. Personal Data may be processed in the European Union, the European Economic Area, the United States, Thailand or other countries where we, our service providers, partners or Users operate.

17.3. Where GDPR applies and Personal Data is transferred outside the EEA to a country not recognised as providing an adequate level of protection, we will use appropriate safeguards such as Standard Contractual Clauses, supplementary measures or other lawful transfer mechanisms.

17.4. Where Thai PDPA applies and Personal Data is transferred outside Thailand, we will assess applicable transfer requirements and may use appropriate safeguards such as contractual clauses, recognised transfer mechanisms, binding corporate rules or other lawful methods.

17.5. Where CCPA/CPRA or other US privacy laws apply, we will implement required contractual restrictions with service providers, contractors or third parties as applicable.

18. Data Retention

18.1. We retain Personal Data only for as long as reasonably necessary for the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by law.

18.2. Retention periods may depend on the type of data, account status, legal obligations, tax rules, accounting rules, limitation periods, dispute risk, security needs, backup cycles and contractual obligations.

18.3. Indicative retention periods include:

18.4. We may anonymise or aggregate data so that it no longer identifies an individual. Such anonymised or aggregated data may be used for analytics, reporting, research, product improvement and business purposes.

18.5. Deletion requests may be limited where retention is required for legal compliance, tax, accounting, security, fraud prevention, dispute resolution, enforcement of rights or other lawful reasons.

19. Security Measures

19.1. We use reasonable technical and organisational measures designed to protect Personal Data against unauthorised access, loss, misuse, alteration, destruction or disclosure.

19.2. Measures may include access controls, authentication, encryption in transit, logging, backups, monitoring, provider due diligence, role-based permissions, internal policies, incident response procedures and security reviews.

19.3. No digital service can guarantee absolute security. Users are responsible for using strong passwords, protecting credentials, managing team access and promptly reporting suspected compromise.

19.4. Security incidents should be reported to hello@inmap.info. Privacy-related incidents or legal notices may also be sent to legal@inmap.info.

20. Personal Data Breaches

20.1. If we become aware of a personal data breach, we will assess the risk and take appropriate measures to investigate, contain, mitigate and remediate the incident.

20.2. Where required by applicable law, we will notify the competent supervisory authority, affected individuals, Business Users or other relevant parties.

20.3. Under GDPR-style regimes, notification to the supervisory authority may be required without undue delay and, where feasible, within 72 hours after becoming aware of a breach that meets the legal threshold.

20.4. Under Thai PDPA, where applicable, notification to the competent authority may also be required without undue delay and, where feasible, within 72 hours, depending on risk.

20.5. If a Business User acts as controller and we act as processor, we will notify the Business User in accordance with the applicable Data Processing Agreement and legal requirements.

21. Children and Minors

21.1. The Platform is not intended for children.

21.2. Users must be at least 18 years old or have the legal capacity required to use the Platform and enter into binding agreements under applicable law.

21.3. We do not knowingly collect Personal Data from children under 16. If we learn that we have collected such data without proper legal basis or required consent, we will delete or restrict it.

22. User Rights Under GDPR / EEA Law

22.1. If GDPR or similar EEA law applies, the User may have the following rights:

22.2. Requests may be sent to legal@inmap.info.

22.3. We may need to verify the identity of the requesting person before responding.

22.4. If the User is located in Slovakia or the processing is under Slovak supervisory jurisdiction, the competent supervisory authority may be the Office for Personal Data Protection of the Slovak Republic.

22.5. The User may also contact the supervisory authority in the EU Member State of the User’s habitual residence, place of work or place of alleged infringement.

23. Thailand PDPA Rights

23.1. If the Thai Personal Data Protection Act applies, data subjects may have rights under Thai law, including where applicable:

23.2. Requests may be sent to legal@inmap.info.

23.3. If we appoint a Thailand local coordinator or representative in the future, we will provide relevant contact details.

23.4. Some Thai PDPA rights may be subject to limitations, exceptions, identity verification and legal conditions.

24. California Privacy Notice

24.1. This section applies only to California residents where the CCPA/CPRA applies to us.

24.2. Depending on the User’s interaction with the Platform, we may collect the following categories of personal information under California law:

24.3. We may use these categories for the purposes described in this Privacy Policy, including providing the Platform, account management, project publication, lead generation, analytics, security, billing, legal compliance, customer support and marketing where permitted.

24.4. We may disclose these categories to service providers, contractors, other Users as part of Platform functionality, map providers, payment providers, AI providers, professional advisers, authorities and transaction counterparties as described in this Privacy Policy.

24.5. We do not intend to sell Personal Data in the ordinary meaning of selling data for money.

24.6. Some disclosures, cookies, analytics or advertising activities may be considered “sharing” or “sale” under California law depending on implementation. If such activities occur and CCPA/CPRA applies, we will provide the required notice and opt-out mechanism, such as “Your Privacy Choices” or “Do Not Sell or Share My Personal Information.”

24.7. California residents may have the right to:

24.8. Requests may be sent to legal@inmap.info.

24.9. We may need to verify the request and may ask for information reasonably necessary to confirm identity or authority.

24.10. Authorised agents may submit requests where permitted by law, subject to verification and proof of authorisation.

24.11. We will not discriminate against a User for exercising CCPA/CPRA rights.

25. Automated Decision-Making and California ADMT

25.1. The Platform may use automated tools for analytics, ranking, recommendations, data-quality scoring, fraud prevention, content classification, security, project matching and operational optimisation.

25.2. We do not intend to use automated decision-making technology to make decisions that produce legal or similarly significant effects on California consumers unless we provide additional notices, access rights, opt-out rights or other safeguards where required.

25.3. If California ADMT rules apply to a specific feature, we will update this Privacy Policy or provide a specific notice explaining the relevant rights and choices.

26. Global Privacy Control and Preference Signals

26.1. Where required by applicable law, we will recognise valid browser-based opt-out preference signals, such as Global Privacy Control, for applicable sale or sharing opt-out rights.

26.2. Recognition of such signals may depend on technical feasibility, jurisdiction, User status and whether the Platform engages in activities covered by the relevant law.

27. Data Subject Requests

27.1. Privacy requests may be submitted to legal@inmap.info.

27.2. The request should include:

27.3. We will respond within the timeframe required by applicable law.

27.4. We may refuse or limit requests where permitted by law, including where the request is manifestly unfounded, excessive, impossible to verify, conflicts with legal obligations, affects rights of others, concerns trade secrets or must be retained for legal claims, security, tax, accounting or compliance purposes.

27.5. If Personal Data is controlled by a Business User and we act only as processor, we may refer the request to the relevant Business User.

28. Processor and Sub-Processor Management

28.1. We may use processors and sub-processors to provide the Platform.

28.2. We will seek to use processors that provide appropriate contractual, technical and organisational safeguards.

28.3. Processor categories may include:

28.4. Where required by a Data Processing Agreement, we may maintain or provide a list of sub-processors and notify relevant Business Users of material changes.

29. Business User Responsibilities

29.1. Business Users are responsible for Personal Data they upload, import, disclose or otherwise process through the Platform for their own purposes.

29.2. Business Users must:

29.3. Business Users must not use lead data, Investor data, contact data or Platform interaction data for unlawful spam, unauthorised resale, unrelated marketing, discriminatory practices or purposes inconsistent with this Privacy Policy and the Terms of Service.

30. Publicly Available and Third-Party Data

30.1. The Platform may use publicly available business, project, property, company, geographic or market data.

30.2. Public availability of data does not automatically mean that data may be used for every purpose. We will assess applicable legal bases and restrictions where relevant.

30.3. If a person believes that publicly displayed data on the Platform is inaccurate, outdated or unlawfully displayed, the person may contact hello@inmap.info or legal@inmap.info.

31. Do Not Track

31.1. Some browsers provide “Do Not Track” signals. Because there is no uniform global standard for such signals, the Platform may not respond to all Do Not Track signals.

31.2. Where legally required, we will recognise legally binding opt-out preference signals, such as Global Privacy Control, as described in this Privacy Policy.

32. Third-Party Links and External Websites

32.1. The Platform may contain links to third-party websites, project websites, map providers, payment providers, developer websites, partner websites or external resources.

32.2. We are not responsible for the privacy practices, content, security or policies of third-party websites or services that we do not control.

32.3. Users should review the privacy policies of third-party services before providing Personal Data to them.

33. Changes to This Privacy Policy

33.1. We may update this Privacy Policy from time to time.

33.2. Material changes may be communicated by email, Platform notice or publication of a new version on the Platform.

33.3. The updated Privacy Policy becomes effective on the effective date stated in the updated version.

33.4. Continued use of the Platform after the effective date means that the User has been informed of the updated Privacy Policy, subject to any consent requirements under applicable law.

34. Contact

34.1. For privacy requests and legal data protection matters, contact:

legal@inmap.info

34.2. For general support, technical matters, billing, complaints and operational questions, contact:

hello@inmap.info

34.3. Postal correspondence may be sent to:

VisionEdge s.r.o.
29. augusta 1503/1A
958 01 Partizánske
Slovak Republic, European Union

End of Privacy Policy