Mapit GIS Privacy Policy

Scope​

This section covers privacy practices applicable to the Mapit GIS websites.

Websites:

• Mapit GIS
• Mapit Spatial

User Provided Information​

When you write to us through the contact form, including to register your interest in Mapit GIS Cloud, We receive your name, email address and message, and use them only to reply to you. We do not add you to a mailing list.

When you use our apps, you may provide login credentials to access 3rd party services and providers. This information is never relayed back to Us.

Usage Data​

Usage Data is collected automatically when using the Service.

Usage Data may include information such as Your Device's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that You visit, the time and date of Your visit, unique device identifiers and other diagnostic data.

Cookies and browser storage​

The Website does not use advertising or analytics cookies. It keeps small preferences, such as light or dark theme, in your browser's own storage, which never leaves your device. You can clear it from your browser's settings at any time.

Use of Your Personal Data​

The Company may use Personal Data for the following purposes:

• To provide and maintain our Service, including to monitor the usage of our Service.
• To manage Your requests: To attend and manage Your requests to Us.
• To contact You about updates, security notices or the products and services You have purchased or asked about.

Scope​

This section covers privacy practices specific to the Mapit GIS iOS application.

Application:

• Mapit GIS, available on the Apple App Store

Data Collection​

The Mapit GIS iOS application is designed with an offline-first approach. All survey data, geographic features, and attachments are stored locally on your device. The application does not collect analytics, does not serve advertisements, and does not transmit your survey data to any external servers unless you sign in to Mapit GIS Cloud and sync a cloud project.

The application does not require an account. Signing in to Mapit GIS Cloud is optional, and is described in the Mapit GIS Cloud tab.

Purchases​

If you purchase a subscription from the Apple App Store, the transaction is handled entirely by Apple. We have access to subscription status information provided by Apple to verify your entitlements. Please see Apple's Privacy Policy for further details on how Apple handles purchase data.

When you register for Mapit GIS Cloud, the app sends Us the purchase as the App Store signed it, and an App Attest statement that the app is genuine. We check both against certificates Apple publishes, without sending Apple anything about you, and keep the purchase's original transaction identifier.

Sign in with Apple​

If you link your Apple ID to your Mapit GIS Cloud account, We keep the identifier Apple gives us for it, so you can sign in with Apple afterwards. If you chose to hide your email from us, Apple's relay address is what We see.

Third-Party Services​

The iOS application uses the following third-party services:

Mapbox Maps SDK​

The application uses the Mapbox Maps SDK and Mapbox Search SDK to provide map display, geocoding, and place search functionality. When using map and search features, the application communicates with Mapbox servers. Mapbox may collect certain data automatically, including:

• Telemetry data: Anonymised usage data about map interactions to improve Mapbox maps and services.
• Location data: General location information when the map is in use, used to improve map accuracy and services. When using the search feature, your approximate location may be sent to Mapbox to provide location-relevant results.
• Device information: Device model, operating system version, and screen resolution.

For more information, please see the Mapbox Privacy Policy.

NGA GeoPackage Libraries​

The application uses open-source GeoPackage and projection libraries developed by the National Geospatial-Intelligence Agency (NGA). These libraries operate entirely locally on your device and do not transmit any data to external servers.

Permissions​

The iOS application may request the following permissions:

• Location Services - The application's primary purpose is to carry out precise GIS measurements related to location. The application cannot function without this permission. Both precise and approximate location may be used. The application may also use background location to continue tracking your position whilst the app is not in the foreground.
• Camera - Required to carry out certain tasks during surveys, such as recording photographic evidence related to collected features or scanning QR and bar codes within forms.
• Local Network - Required to connect to external GNSS receivers (such as Trimble devices) via TCP/IP for high-accuracy positioning.

Data Stored on Your Device​

The application stores the following data locally on your device:

• GeoPackage databases containing your geographic features, layers, and attributes
• Attachments (photographs, videos, audio) associated with collected features
• Application settings such as your preferred basemap, coordinate format, and units
• A device identifier stored securely in your device's Keychain, which identifies this installation to Mapit GIS Cloud if you sign in

You can access and manage your data files through the iOS Files app. Nothing is uploaded automatically: a project is synced only once you have signed in to Mapit GIS Cloud and the project is a cloud project.

What We Do Not Do​

The Mapit GIS iOS application:

• Does not contain any advertising or ad-tracking SDKs
• Does not collect analytics or usage telemetry (beyond what Mapbox may collect as described above)
• Does not share your personal information with third parties for marketing purposes
• Does not upload your survey data anywhere except to Mapit GIS Cloud, and only for a cloud project you have signed in to
• Does not upload photos or videos, even in a cloud project

Scope​

This section covers privacy practices specific to the Mapit GIS Android applications.

Applications:

• Mapit - GIS Data Collector
• Mapit Spatial - GIS Data Collector
• Mapit GIS, on Google Play and as the Standalone edition supplied directly by Us

Websites:

• Mapit GIS
• Mapit Spatial

User Provided Information​

If you purchase the application add-in or subscription from Google Play Store, we also have access to information about your purchase. This information is stored by Google Play. Please see their privacy policies for further details.

When you register for Mapit GIS Cloud from Mapit GIS, the app asks Google Play Integrity to confirm the app is genuine, and sends Us that verdict with your Google Play purchase. We ask Google Play to confirm the purchase, keep its order identifier and purchase token, and check it again from time to time so that your cloud access follows your licence. The Standalone edition sends instead a licence grant that We signed, which We check without contacting anyone.

When you use the Application, you may also provide login credentials to access 3rd party services and providers (like Google Drive or Dropbox). This information is never relayed back to Us.

Third Party Services and Service Providers​

Mapit GIS applications and websites utilize however some 3rd party services for analytics and statistical purposes like Google Play Developer Console, Firebase Console, Google Analytics as well as utilizing 3rd party SDKs and APIs like Google Maps, Google Drive, Dropbox, Microsoft Bing Maps and to some extent those 3rd party SDKs or APIs might collect certain personally identifiable information and may be a subject to the 3rd party policies and terms of use.

We may employ third-party companies and individuals due to the following reasons:

• To facilitate our Service;
• To provide the Service on our behalf;
• To perform Service-related services; or
• To assist us in analyzing how our Service is used.

We want to inform users of this Service that these third parties have access to your Personal Information. The reason is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the information for any other purpose.

Automatically Collected Information The Applications in scope may also collect certain information automatically, such as: the type of mobile device you use, your mobile devices unique device ID, the IP address of your mobile device, your mobile operating system, the type of mobile Internet browsers you use, and information about the way you use the Application.

If errors occur while using the Application, an error log can be sent back to Us. This error log contains non-personal data, such as device model, operating system version, where in the Application the error happened. This information is intended to assist further improvement of the Application.

Advertising We may use tools or third party analytical software to collect and use certain non-personal data that does not enable us to identify you. The types of non-personal data we may collect and use include, but are not limited to: (i) mobile device type and device properties; (ii) mobile device software platform and firmware; (iii) mobile phone carrier; (iv) geographical data; and (v) other non-personal data as reasonably required by us to enhance our services.

We reserve the right to use and disclose the collected non-personal data in an anonymized and obfuscated way for purposes of advertisement by us or our partners. We do not pass any personally identifiable information to ad networks or advertisers.

We may work with analytics companies to help us understand how the Application is being used, such as the frequency and duration of usage. We also work with advertisers and third party advertising networks that need to know how you interact with advertising provided in the Application. Advertisers and advertising networks use some of the information collected by the Application, including the unique identification ID of your mobile device. To protect the anonymity of this information, we use an encryption technology to help ensure that these third parties can't identify you personally.

None of this applies to data you sync with Mapit GIS Cloud: no project data is ever shared with an advertising or analytics provider.

Links to privacy policy of third party service providers used by the applications:

• Google
• Google Play Services
• Crashlytics
• Firebase
• Google Drive Terms of Service
• Dropbox
• OpenStreetMap

Use of Your Personal Data​

The Company may use Personal Data for the following purposes:

• To provide and maintain our Service, including to monitor the usage of our Service.
• To manage Your Account: to manage Your registration as a user of the Service.
• For the performance of a contract: the development, compliance and undertaking of the purchase contract for the products, items or services You have purchased or of any other contract with Us through the Service.
• To contact You about updates, security notices or the products and services You have purchased.
• To manage Your requests: To attend and manage Your requests to Us.

We may share your personal information in the following situations:

• With Service Providers: to monitor and analyze the use of our Service, to show advertisements in the app, to contact You, or for payment processing.
• For Business transfers: in connection with, or during negotiations of, any merger, sale of Company assets, financing, or acquisition of all or a portion of our business to another company.

Log Data We want to inform you that whenever you use our Service, in a case of an error in the app we collect data and information (through third party products) on your phone called Log Data. This Log Data may include information such as your device Internet Protocol ("IP") address, device name, operating system version, the configuration of the app when utilizing our Service, the time and date of your use of the Service, and other statistics.

Sensitive Permissions​

The applications require acceptance of some sensitive Android permissions for example access to CAMERA permission and this is used only to provide support for a bar code scanner inside the forms and to take pictures related to the collected location features, similarly LOCATION is needed to carry on necessary surveys and measurements.

The full list of Android Permissions used by Mapit apps listed in the scope above are as follow:

• LOCATION - the applications aim is to carry on precise measurements related to the location. The application cannot work without this permission.
• CAMERA - required to carry on certain tasks during the survey, like recording the photographic evidence related to the collected features or scanning the QR or bar codes into the form.
• STORAGE - Vital data used by application is being stored on user internal/external device memory. For the convenience of adding additional resources or quick access e.g. to the collected data access to the storage is necessary.
• INTERNET - the applications can work offline, however most mapping providers require active internet connection to display the map tiles. The Internet connection is also needed to perform other tasks like data export or import to external providers, search for places, or sync with Mapit GIS Cloud.

Google Drive​

Some application functionality includes usage of Google Drive. This functionality is optional and allows users to export or import files from the cloud location.

Before accessing Google Drive Content you will be presented with the Google OAuth Consent screen where you will be asked to provide credentials and allow access to the Google Drive Content. At any point these credentials are not being stored or processed in any way by Us and are used only to facilitate access to your own content.

Drive Scopes: Mapit - GIS Data Collector DRIVE.FILE - View and manage Google Drive files and folders that you have opened or created with this app

Mapit Spatial - GIS Data Collector DRIVE - permits an application to read, modify, or manage the content or metadata of a user's Drive files, without the user individually granting file-by-file access.

The extended DRIVE scope is considered due to the fact that we have been receiving a lots of requests from users asking for possibility to access the files inside the app which were created or shared outside of the application. Mapit Spatial is productivity application that only use Restricted Scope to handle Drive files (or their metadata or permissions) via the application's user interface. The files will be always loaded/sync from/to the same Drive location.

Mapit GIS and Mapit Spatial complies with the limited use principles listed below.

Limited Use: 1. Google Drive data will be used only to provide and improve user-facing features related to Import/Export of the data.

2. The Google Drive Data will never be transferred automatically by the app to any other network or 3rd party location. The data will be always stored locally on user device.

3. We never use or transfer the data for serving ads, including retargeting, personalized, or interest-based advertising.

Scope​

This section covers Mapit GIS Cloud: the portal at cloud.mapitgis.com, the sync service at sync.mapitgis.com, and the parts of the apps that talk to them. Using it is optional.

Our two roles​

• For your account, your licence, billing and the security of the service, We are the controller. This Privacy Policy is Our notice to you about that data.
• For an organisation's project data, the organisation is the controller and We are its processor. We handle it only on the organisation's instructions, under the data processing terms in Schedule 1 of Our Terms of Use. If you collect data as a member of an organisation, the organisation decides what is collected and who sees it; ask its admin about it, and We will help them answer you.

What We collect​

Your account

• Your email address, which is how you sign in: We email a one-time code, and never store a password.
• Your name, if you give one, shown to the people in your organisations.
• If you link Sign in with Apple, Apple's identifier for your Apple ID.

Your licence

• Proof that you hold Mapit GIS Pro or Pro+: the Google Play order identifier and purchase token, the App Store purchase's original transaction identifier, or the Standalone licence identifier.
• The verdict that the app is genuine (Google Play Integrity or Apple App Attest), recorded with how your account was created.

Your devices

• For each app or QGIS installation you sign in from: an installation identifier, the device model, the app's edition and version, the platform, and when it was last seen. Each person may use two app installations and one QGIS installation per organisation, and the admin and managers can see and remove them.

Your organisation

• The organisation's name, its members and their roles, groups and what is shared with them, invitations (with the invited person's email address) and requests to join.
• Billing: the admin's billing name and address, the organisation's VAT number if given, and the payment card, all held by Stripe. We never see the card number.

Projects and content

• Cloud projects: the layers, fields and features the crew collects, including their locations and attribute values, the names of photos and videos (never the files themselves), and the sync history: which person and which device changed what, and when. Conflicting edits are kept as records, so nothing is silently lost.
• Attribute sets, styles, web maps, WFS publications and draft projects that people design on the portal.
• The team activity board: for each person, when they last synced, and how many records and photos they collected each day, per layer. The board's figures contain no locations and no feature contents. The admin and managers of the organisation see it.

The AI project designer

• If you use Design with AI, what you type and the draft's structure (layer and field names, types and pick lists) are sent to the AI model, which runs on Amazon Bedrock in the EU. It never receives anything your crews collect.
• We keep no conversation. It lives only in your browser tab. We record each call's size and cost, against your account and organisation, so that spending can be limited.
• The model provider does not use it to train models.
• Whether an organisation uses the designer is its admin's decision: the admin can turn it off for everybody in the organisation.

Claude and ChatGPT connections

• If your organisation's admin allows it, the admin and managers can connect their own Claude (Anthropic) or ChatGPT (OpenAI) account to Mapit GIS Cloud, to design projects from there.
• A connection reads the structure of the organisation's cloud projects, drafts and attribute sets (layer and field names, types and pick list values) and Mapit's survey templates, and can create draft projects. It never receives anything your crews collect, and it cannot publish.
• What a connection reads goes to Anthropic or OpenAI under your own agreement with them, and their privacy policies apply to it. They are not companies We use: your organisation chooses to send it, by its admin turning connections on and a member connecting. They may process it outside the EU.
• We record each connection you allow (the app's name and when you allowed it), which you can see and end under Connected apps on Your settings; the number of calls each person's connections make, to limit them; and, in Our server logs, which drafts a connection created. We keep no conversation.
• Whether an organisation allows connections is its admin's decision. It is off until the admin turns it on, and off whenever the AI designer is off.

Technical data

• Your IP address and browser details pass through Cloudflare, which protects the service, and appear in Our server logs, kept for security and fault finding.
• The portal uses only necessary cookies: your sign-in session, and which of your organisations you are working in. Your theme choice is kept in your browser's own storage. There are no analytics, advertising or tracking cookies.

Email

• We send sign-in codes, invitations, and notices about your account, your organisation and its subscription. Mapit GIS Cloud sends no marketing email.

Who can see what​

• Inside an organisation, content is private to its author until it is shared with a group or the whole organisation. A viewer sees only what is shared with them; for a cloud project that is its outline (layer names, kinds and counts), never its data.
• Mapit GIS staff do not look at an organisation's data in the course of running the service. When support needs to, the view is read only and is recorded in an audit log.
• Encryption: each organisation's project files are encrypted with a key of its own, which is itself protected by a key held in AWS Key Management Service. This protects against a stolen disk or backup. It does not protect against Us: the service must decrypt the data to sync it, and that is why staff access is logged.

Who handles it for Us​

Supabase, Amazon Web Services, Hetzner, Cloudflare and Mapbox handle data only to provide their part of the service, under a data processing agreement with Us. Stripe and Google also act on their own account: Stripe for fraud prevention and the checks the law requires of a payment provider, and Google for the Google Play purchase and the integrity check, which are its own records under its own privacy policy. We tell organisation admins before adding a company to this list or changing what one does, so they have time to object.

Anthropic and OpenAI are not on this list: when a member connects Claude or ChatGPT, they act under that member's or organisation's own agreement with them, not for Us.