Skip to main content
MTNinfo
Policy

MtnInfo Privacy Policy — Meta Page-Posting App

Effective date: September 3, 2026. This page describes MtnInfo’s current practices for its Meta Page-posting app, MtnInfoAuto. It is factual information, not legal advice.

Operator and scope

This policy is published by MtnInfo and applies to MtnInfoAuto, MtnInfo’s Meta Page-posting app for authorized administrators and system automation to publish and manage content on the MtnInfo Facebook Page.

Meta app setup for MtnInfoAuto is complete. MtnInfo currently has no Facebook posting backend or connector in production use. A small secure connector will be built and connected later.

The public mtninfo.com website does not offer Facebook Login. Visitors are not asked to sign in with Facebook to read guides, maps, or The Liftline Times, and MtnInfo does not collect public user data through Facebook on this site.

Who this app is for

MtnInfoAuto is for authorized MtnInfo administrators and system automation only. The general public does not use this app through mtninfo.com.

What MtnInfo currently collects and stores

Integration credentials. A system-user access token and app secret are stored in secure credential storage for setup and operation of the MtnInfoAuto integration. These credentials are not published on mtninfo.com.

No Meta user data. MtnInfo does not collect or store Meta user profile data through this app.

No publishing operational data yet. No app-generated publishing requests, responses, logs, posts, or post records exist or are persisted. Because no publishing operational data exists, there is currently no operational-data retention practice.

The mtninfo.com site includes static Open Graph meta tags so links can display previews when shared. Those tags do not receive user data from Meta through a login flow.

How stored data is used

Stored integration credentials are used only to set up and operate the MtnInfoAuto integration. When a production connector is enabled, its purpose will be to publish and manage content on the MtnInfo Facebook Page on behalf of authorized MtnInfo administrators and automation.

Storage and retention

Integration credentials are retained securely for setup and operation of the MtnInfoAuto integration. MtnInfo does not publish a fixed retention period for these credentials.

Because no publishing operational data exists yet, there is currently no retention practice for publishing requests, responses, logs, or posts.

This policy will be updated before production connector use if idempotency records, publishing responses, or logs are introduced.

Sale and sharing

No Meta user data or publishing operational data currently exists to sell or share. MtnInfo does not sell integration credentials. The stored credentials are operational secrets kept in secure credential storage and are not published on mtninfo.com.

User data deletion / data deletion instructions

There is currently no Meta user data or publishing operational data to delete.

To request revocation or deletion of stored MtnInfoAuto integration credentials, or for other Meta app data inquiries, email privacy@mtninfo.com with the subject line Meta app data deletion. Include the Facebook Page name and, if applicable, the administrator account that authorized the app.

MtnInfo will process credential revocation or deletion requests and will update this page before production connector use introduces idempotency records, publishing responses, or logs.

Pass Calculator — third-party ZIP lookup

The Pass Calculator on mtninfo.com is a static, client-side page. When you enter a US ZIP code, your browser sends a request directly from your device to https://api.zippopotam.us (Zippopotam.us) to look up that ZIP. MtnInfo does not operate that API and does not receive your ZIP on MtnInfo servers.

The purpose of the lookup is to convert your ZIP into latitude and longitude so the calculator can filter ski resorts by approximate drive distance. MtnInfo has not verified what Zippopotam.us logs, stores, or retains about those requests.

After a successful lookup, the calculator caches ZIP-to-coordinates results in your browser’s sessionStorage under keys prefixed calc-zip-. This data stays on your device for the browser session. MtnInfo servers do not receive these keys.

When you copy a share link, the calculator puts your ZIP code and other inputs in the page URL query string (including a zip= parameter) so the link can be shared. Anyone with the link can see that ZIP and those inputs. MtnInfo static hosting may log request URLs at the CDN/edge like any page view. The calculator does not POST your ZIP to MtnInfo.

Contact

Questions about this policy or MtnInfoAuto: privacy@mtninfo.com

Updates

MtnInfo will update this page before production connector use if idempotency records, publishing responses, or logs are introduced, and whenever integration practices change. The effective date at the top reflects the latest revision.