Last updated: 14 May 2026

Cookie Policy for iNmap.info

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

1. Introduction

1.1. This Cookie Policy explains how VisionEdge s.r.o. uses cookies and similar technologies in connection with the digital platform iNmap.info.

1.2. This Cookie Policy should be read together with:

1.3. The Platform may provide digital mapping, project presentation, real estate project analytics, dashboards, lead generation, marketplace-support features, user accounts, AI-assisted analysis, API features and related services.

1.4. Cookies and similar technologies may be used to make the Platform work, keep it secure, remember preferences, analyse usage, improve functionality, enable map and third-party integrations, support marketing where permitted and comply with legal obligations.

1.5. This Cookie Policy is drafted to support compliance with applicable cookie, privacy and electronic communications laws, including where applicable EU / EEA cookie rules, GDPR, Slovak law, Thailand PDPA, California privacy requirements and other relevant legal frameworks.

2. Operator Identification

2.1. The 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. Contact addresses:

3. English Master Version

3.1. This Cookie 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 any discrepancy between the English version and a translated version, the English version prevails, unless mandatory local law requires otherwise.

4. What Are Cookies?

4.1. Cookies are small text files stored on a user’s device when the user visits a website or uses an online service.

4.2. Cookies may allow the website or service to recognise the user’s browser, remember preferences, maintain sessions, improve security, measure usage or provide personalised functionality.

4.3. Cookies may be set directly by the Platform or by third parties integrated into the Platform.

4.4. Similar technologies may include local storage, session storage, pixels, tags, SDKs, tracking scripts, device identifiers, log files and other technologies that store or access information on the user’s device or browser.

4.5. In this Cookie Policy, the term “cookies” includes cookies and similar technologies unless stated otherwise.

5. Types of Cookies by Duration

5.1. Session cookies are temporary cookies that are deleted when the browser is closed or the session ends. They may be used for login sessions, navigation, security or temporary preferences.

5.2. Persistent cookies remain on the user’s device for a defined period or until deleted by the user. They may be used to remember preferences, consent choices, analytics identifiers, security signals or other recurring functions.

5.3. The retention period of each cookie depends on its purpose, provider and configuration.

6. Types of Cookies by Provider

6.1. First-party cookies are set by iNmap.info or by infrastructure directly controlled by the Operator.

6.2. Third-party cookies are set by external providers whose services are integrated into the Platform, such as analytics providers, map providers, payment providers, advertising providers, security tools or embedded content providers.

6.3. Third-party cookies may be subject to the privacy policies, cookie policies and terms of the relevant third-party providers.

7. Cookie Categories Used by the Platform

7.1. The Platform may use the following categories of cookies.

8. Strictly Necessary Cookies

8.1. Strictly necessary cookies are required for the Platform to function properly and securely.

8.2. These cookies may be used for:

8.3. Strictly necessary cookies do not require consent where they are technically necessary to provide the service requested by the user or to operate the Platform securely, but they are still described in this Cookie Policy for transparency.

8.4. If strictly necessary cookies are disabled through browser settings, the Platform may not work correctly or may not be accessible.

9. Functional Cookies

9.1. Functional cookies help the Platform remember user preferences and provide enhanced features.

9.2. These cookies may be used for:

9.3. Functional cookies may be optional depending on implementation. Where legally required, they will be used only with consent.

10. Analytics and Performance Cookies

10.1. Analytics and performance cookies help us understand how Users interact with the Platform.

10.2. These cookies may be used to collect information such as:

10.3. We may use analytics to improve usability, detect bugs, optimise performance, improve product features, measure adoption and support business decisions.

10.4. Analytics cookies will be used only according to applicable law and, where required, only after the User has given consent.

10.5. If analytics are configured to be strictly privacy-preserving and legally exempt from consent in a particular jurisdiction, we may treat them according to applicable local rules. Otherwise, analytics cookies should be treated as optional.

11. Marketing and Advertising Cookies

11.1. Marketing and advertising cookies may be used to measure campaigns, personalise marketing, manage advertising, limit ad frequency, understand conversion events or support remarketing.

11.2. These cookies may be set by us or by advertising and marketing providers.

11.3. Marketing cookies may involve tracking across websites or services and may be subject to stricter consent and opt-out requirements.

11.4. Marketing and advertising cookies will not be placed unless legally permitted and, where required, the User has given consent.

11.5. If the Platform targets California residents and uses technologies that constitute “sale” or “sharing” of personal information under California law, we will provide an appropriate opt-out mechanism such as “Your Privacy Choices” or “Do Not Sell or Share My Personal Information”, where legally required.

12. Map and Geolocation Cookies

12.1. The Platform may use map and geolocation services to display project locations, interactive maps, address search, geocoding, routing, nearby points of interest, distance calculations and location-based analytics.

12.2. Map and geolocation providers may set cookies or similar technologies to provide their services, maintain security, prevent abuse, measure usage, remember map settings, provide tiles, deliver geocoding results or support embedded map functionality.

12.3. The Platform may use map providers including without limitation:

12.4. Depending on the provider and configuration, map services may receive information such as IP address, browser data, device data, map tile requests, coordinates, address searches, points of interest queries or map interaction data.

12.5. Where legally required, optional third-party map cookies or embedded map features will be activated only after consent.

12.6. Some map functionality may not work fully if map-related cookies or third-party integrations are rejected.

13. AI, Product Analytics and Experimentation Technologies

13.1. The Platform may use cookies or similar technologies to support AI-assisted features, product analytics, feature testing, A/B testing, error monitoring, usage analysis and product optimisation.

13.2. These technologies may help us understand how Users use AI-assisted tools, dashboards, map layers, project profiles, lead features and analytics outputs.

13.3. AI or experimentation technologies may process usage metadata, feature events, prompts, output metadata or performance information, subject to the Privacy Policy and applicable law.

13.4. Where such technologies are not strictly necessary, they will be used only according to applicable consent requirements.

14. Security, Fraud Prevention and Abuse Detection Technologies

14.1. The Platform may use cookies and similar technologies for security, fraud prevention, abuse detection, rate limiting, bot detection, protection against scraping, session integrity, API protection and account protection.

14.2. These technologies may process IP address, device data, session identifiers, behaviour signals, login attempts, request metadata and security logs.

14.3. Security cookies and similar technologies may be considered strictly necessary where they are required to protect the Platform, Users and accounts.

15. Cookie Consent

15.1. Where required by law, optional cookies will be used only after the User has given valid consent.

15.2. Consent should be freely given, specific, informed and unambiguous.

15.3. The Platform should not use pre-ticked boxes for optional cookies.

15.4. The User should be able to accept, reject or manage optional cookie categories in a clear and accessible manner.

15.5. Rejecting optional cookies must not prevent access to core Platform functionality, unless a specific optional feature technically depends on those cookies.

15.6. The User may withdraw or change consent at any time through cookie settings where available.

15.7. Withdrawal of consent does not affect the lawfulness of processing based on consent before withdrawal.

16. Cookie Banner and Preference Centre

16.1. The Platform may display a cookie banner or consent management interface when the User first visits the Platform or when required by law.

16.2. The cookie banner should provide clear options, such as:

16.3. The preference centre should allow Users to review and change cookie settings by category.

16.4. Cookie categories should be explained in clear language.

16.5. Consent choices should be stored so the User is not repeatedly asked unless required, preferences expire, cookies are cleared, settings change or consent renewal is necessary.

17. Suggested Cookie Categories for the Platform Interface

17.1. For implementation, the Platform should use the following user-facing categories:

17.1.1. Necessary cookies

Required for login, security, account access, session management, cookie preference storage and core Platform operation. These cannot be disabled through the Platform’s cookie panel.

17.1.2. Functional cookies

Used to remember language, region, map preferences, dashboard settings and other interface preferences.

17.1.3. Analytics cookies

Used to understand how the Platform is used, measure performance, identify errors and improve features.

17.1.4. Map and geolocation cookies

Used by map providers and geolocation services to display maps, project locations, map tiles, address search, geocoding, routes, nearby amenities and location-based features.

17.1.5. Marketing cookies

Used to measure campaigns, personalise marketing, support remarketing or measure conversions, where enabled.

17.2. If the Platform does not use a specific category, that category should not be enabled in the cookie banner.

17.3. If the Platform later adds new providers or purposes, the cookie banner and this Cookie Policy should be updated.

18. Example Cookie Table

18.1. The following table should be completed after a technical cookie scan of the live Platform.

18.2. The final published version should include the actual cookies, providers, purposes and retention periods used by the Platform.

18.3. If the Platform uses a consent management platform, the cookie table may be dynamically generated through the consent tool, provided that Users can access clear and complete information.

19. Third-Party Providers

19.1. The Platform may integrate third-party providers that use cookies or similar technologies.

19.2. Such providers may include, depending on implementation:

19.3. Third-party providers may process data according to their own terms and privacy policies where they act as independent controllers.

19.4. We are not responsible for third-party cookies set by websites or services that are not controlled by us.

20. Google Services

20.1. The Platform may use Google services, such as Google Analytics, Google Tag Manager, Google Maps Platform, Google reCAPTCHA, Google Ads or other Google services, if enabled.

20.2. Depending on the service, Google may receive information such as IP address, device data, browser data, cookie identifiers, usage events, map queries, coordinates, geocoding requests or advertising identifiers.

20.3. Google services may involve international data transfers and independent processing by Google depending on the configuration and service terms.

20.4. Google Analytics or Google Ads cookies should be used only with consent where legally required.

20.5. Google Maps functionality may require certain technical requests to Google. If optional Google Maps integrations involve cookies or tracking beyond what is strictly necessary, consent may be required before activation.

20.6. If Google services are used, the Platform should configure them in a privacy-protective manner, including appropriate consent mode, IP handling, tag controls, retention settings and data-sharing settings where available.

21. OpenStreetMap, Mapbox, MapTiler, HERE, TomTom and Esri / ArcGIS

21.1. The Platform may use map services based on or related to OpenStreetMap, Mapbox, MapTiler, HERE, TomTom, Esri / ArcGIS or other mapping providers.

21.2. Such services may use cookies, local storage or similar technologies to provide maps, load map tiles, process geocoding requests, prevent abuse, measure service usage, provide routing or display location-based features.

21.3. Users should note that map interactions may involve technical communication with the relevant provider.

21.4. Provider-specific attribution, terms, privacy notices and cookie rules may apply.

21.5. The Platform should not remove, hide or modify map provider attribution or legal notices.

22. Legal Bases for Cookie-Related Processing

22.1. Where GDPR-style laws apply, cookie-related Personal Data may be processed on the following legal bases:

22.2. For EU / EEA and Slovak users, storing information on or accessing information from a user’s device generally requires consent unless the technology is strictly necessary to provide a service requested by the user or to transmit communication.

22.3. For California users, certain cookie or tracking technologies may trigger notice, opt-out or preference-signal obligations if they involve sale, sharing, cross-context behavioural advertising or targeted advertising under applicable law.

22.4. For Thailand users, cookies and similar technologies may involve Personal Data under the Thai PDPA where they identify or can identify a natural person. Where required, we will rely on an appropriate legal basis and provide relevant notices.

23. Managing Cookies Through the Platform

23.1. Users may manage optional cookie preferences through the Platform’s cookie settings or preference centre, where available.

23.2. Users may change preferences at any time by selecting Cookie Settings, Privacy Settings or a similar link in the Platform footer or account settings.

23.3. The Platform should record cookie consent choices in a technically secure and auditable way.

23.4. If the User clears browser cookies, uses a different browser or device, or blocks cookies, the Platform may not recognise previous preferences and may ask the User to set preferences again.

24. Managing Cookies Through Browser Settings

24.1. Users can usually manage cookies through browser settings.

24.2. Browser settings may allow Users to:

24.3. Blocking all cookies may affect Platform functionality, login, security, preferences, map display or other features.

24.4. Browser-based controls may not remove server-side records that were lawfully created before cookies were deleted.

25. Global Privacy Control and Opt-Out Preference Signals

25.1. Where required by applicable law, the Platform will recognise valid browser-based opt-out preference signals, such as Global Privacy Control, for applicable sale, sharing or targeted advertising opt-out rights.

25.2. Recognition of preference signals may depend on technical feasibility, jurisdiction, User status, Platform configuration and whether the relevant legal threshold applies.

25.3. If a Global Privacy Control signal conflicts with cookie settings chosen manually by the User, the Platform should apply the more privacy-protective setting where legally required.

26. Do Not Track

26.1. Some browsers provide “Do Not Track” signals.

26.2. Because there is no uniform global standard for Do Not Track signals, the Platform may not respond to all such signals.

26.3. This does not affect legally required opt-out preference signals such as Global Privacy Control where applicable.

27. International Data Transfers

27.1. Cookies and similar technologies may involve data transfers to countries outside the User’s country of residence.

27.2. Third-party providers may process data in the European Union, the European Economic Area, the United States, Thailand or other jurisdictions.

27.3. Where required, international transfers will be supported by appropriate safeguards, such as adequacy decisions, standard contractual clauses, contractual restrictions, supplementary measures or other lawful mechanisms.

27.4. More information is provided in the Privacy Policy.

28. Retention of Cookie Data

28.1. Cookies remain on the User’s device only for their configured duration unless deleted earlier by the User or browser.

28.2. Server-side data associated with cookies, such as consent records, analytics events, security logs or session records, may be retained according to the Privacy Policy and applicable retention rules.

28.3. Cookie duration should be proportionate to the purpose of the cookie.

28.4. Consent records may be retained for as long as reasonably necessary to demonstrate compliance.

29. Changes to This Cookie Policy

29.1. We may update this Cookie Policy from time to time.

29.2. Updates may be required if we add or remove cookies, change providers, introduce new features, update legal requirements, change the Platform architecture or modify consent settings.

29.3. Material changes may be communicated by Platform notice, cookie banner, email or publication of a new version.

29.4. The updated Cookie Policy becomes effective on the effective date stated in the updated version.

30. Contact

30.1. For cookie-related privacy requests, contact:

legal@inmap.info

30.2. For general cookie settings, technical support or operational questions, contact:

hello@inmap.info

30.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 Cookie Policy