Third-party integrations

Overview

MapToPlay includes optional technical connections to services operated by third parties. These integrations make it possible to send requests to, receive data from, or display content supplied by those services from within a MapToPlay workflow. They do not make the third-party service part of MapToPlay.

MapToPlay is not affiliated with, sponsored by, endorsed by, an agent of, or in a partnership or joint venture with MapTiler or Meshy. All product names, trademarks, services, accounts, and content remain the property and responsibility of their respective owners.

MapTiler Satellite Imagery Preview

Project wizards can optionally use MapTiler to display satellite imagery as a map preview. To enable this preview, the end-user must select a MapTiler API key saved for their team and must be authorized to use the associated MapTiler account. MapToPlay does not supply a shared, bundled, fallback, or platform-owned MapTiler key, account, subscription, or map license.

When satellite preview is enabled, the selected key is validated and made available to the project wizard for that purpose. The end-user’s browser then requests map tiles directly from MapTiler. MapTiler may receive the API key, IP address, requested tile or location information, and other technical request data needed to provide its service. MapTiler controls how it processes those requests.

MapTiler usage is governed by the end-user’s agreement with MapTiler, including the MapTiler Cloud Terms, MapTiler Privacy Policy, and MapTiler map data license and attribution information. The end-user is solely responsible for choosing a suitable plan, securing and restricting the key, monitoring usage, paying fees, staying within request limits, displaying required attribution, and using imagery only as permitted by MapTiler and its data licensors.

Meshy AI Model Generation

The Assets page and the Editor can optionally use Meshy to generate 3D model assets from prompts and supported reference images. The end-user must select a Meshy API key saved for their team and must be authorized to use the associated Meshy account. MapToPlay does not supply a shared, bundled, fallback, or platform-owned Meshy key, account, subscription, or generation credits.

MapToPlay sends the generation request to Meshy on the end-user’s behalf, checks task status, downloads the result made available by Meshy, and imports that result into the end-user’s MapToPlay assets. Depending on the chosen workflow, information sent to Meshy may include prompts, reference images, generation settings, and the technical request data needed to process the job. The Meshy key is resolved and used on the server and is not delivered to the browser as part of the generation flow.

Meshy usage is governed by the end-user’s agreement with Meshy, including the Meshy Terms of Service, Meshy Privacy Policy, and Meshy Acceptable Use Policy. The end-user is solely responsible for provider credits and charges, permitted use, rights to all prompts and reference material, review of generated results, applicable licenses and attribution, and determining whether an output may be used, modified, published, or sold for the intended purpose.

Your Provider Account and Credentials

An integration does not create a provider account or contractual relationship for the end-user. The end-user must obtain and maintain their own provider account and submit only credentials they own or are expressly authorized to use. MapToPlay does not grant access to another user’s provider account and does not sell, sublicense, pool, or redistribute access to either provider.

Saved provider credentials are stored as encrypted team credentials and are used only for the integration selected by an authorized team member. Because team access can change, the credential owner is responsible for deciding which team may use a credential, removing it when access is no longer appropriate, applying provider-side restrictions where available, monitoring activity, and rotating or revoking a key if compromise or unauthorized use is suspected.

Third-Party Terms, Data, and Costs

The end-user’s use of a provider is a separate relationship between the end-user and that provider. Provider terms, privacy practices, acceptable-use rules, account eligibility, plan limits, licenses, retention periods, and pricing may change at any time. The end-user must review the current provider rules before enabling an integration and while continuing to use it.

Any provider fees, subscription charges, usage charges, credits, taxes, overages, suspensions, or account consequences are the end-user’s responsibility. MapToPlay does not determine whether a provider plan is suitable, does not promise that a request will fit within an allowance, and does not reimburse provider charges or credits consumed by successful, failed, repeated, interrupted, or unsatisfactory requests.

No Warranty for Integrations or Results

Third-party integrations and all data, imagery, models, files, responses, and other results obtained through them are provided “as is” and “as available.” To the maximum extent permitted by applicable law, MapToPlay makes no representation or warranty regarding availability, continuity, security, latency, compatibility, accuracy, completeness, uniqueness, legality, quality, licensing status, non-infringement, or fitness for any particular purpose.

AI generation is probabilistic and may fail or produce incomplete, inaccurate, unexpected, non-unique, unsuitable, or unusable results. Satellite imagery and map data may be unavailable, outdated, incomplete, misaligned, obscured, or unsuitable for the end-user’s project. The end-user must inspect and validate every result before relying on, publishing, or distributing it.

Availability and Support

MapToPlay may add, change, suspend, restrict, or remove an integration at any time, including when a provider changes its API, terms, pricing, technical requirements, or availability. MapToPlay does not control provider outages, rate limits, account decisions, moderation, support, or the continued availability of provider content.

Questions about a MapToPlay integration interface may be sent to MapToPlay. Questions about a provider account, invoice, charge, key, license, content, output, suspension, or service operation must be directed to the relevant provider.

Limitation of Liability

To the maximum extent permitted by applicable law, MapToPlay shall not be liable for losses or damages arising from a third-party service, provider account, compromised or misused credential, provider charge, unavailable integration, transmitted input, provider processing, or the use of or reliance on any third-party result. Nothing in this notice excludes liability that cannot lawfully be excluded.

Contact

Questions about how these integrations connect to MapToPlay can be sent to contact@maptoplay.com.