Telisky MDM Terms of Service (2026-07-17)

Version identifier: mdm-terms-2026-07-17
Effective date: July 17, 2026
Immutable snapshot URL: https://docs.telisky.com/legal/mdm-terms/versions/2026-07-17/

This page is the accepted legal text for version mdm-terms-2026-07-17. It is an immutable public snapshot. Future changes will appear only as new versioned files and URLs. Do not rely on the current-pointer page alone as the accepted text.

1. Parties, scope, and agreement

These Telisky MDM Terms of Service (the MDM Terms) are a contract between Telisky Inc. (Telisky, we, us, or our) and each party that accepts them: the business customer that obtains the Telisky cloud management / mobile device management service for managed routers and related features (the MDM Service), where a Customer is bound under Section 1.1, and each accepting Account User in that person’s individual capacity for their own access and conduct.

In these MDM Terms:

Customer means the organization or other business entity that obtains the MDM Service.
Account User means an individual human who has credentials to use the MDM Service through a Telisky account. That includes people invited for Customer-organization access, platform administration, or installer duties (for example an administrator, operator, viewer, platform administrator, or installer). An Account User may or may not be associated with a Customer organization.
You means, as the context requires, the Customer, an Account User, or both.

By creating an organization through self-service signup (as an authorized actor for the Customer under Section 1.1), accepting an invitation that creates or grants Account User access (including Customer-organization, platform-administration, or installer invitations) where you are presented these MDM Terms in individual Account User capacity, or otherwise expressly accepting these MDM Terms where presented for the applicable capacity, you agree to the version of these MDM Terms identified at acceptance, including the version identifier and the exact immutable URL of this snapshot.

These MDM Terms apply to the MDM Service and related cloud account features. They do not replace a separately signed order, subscription agreement, or data processing agreement (DPA) for the subjects those documents cover.

1.1 Capacity and who is bound

Self-service organization creation. If you create a Customer organization through self-service signup, you represent that you have authority to create that organization and to bind the Customer to these MDM Terms. Your acceptance is treated as the Customer’s acceptance for that organization (organization-subject acceptance by that authorized actor). Self-service organization creation does not, by itself, record a separate individual Account User acceptance for the creator.

Invite acceptance. If you accept an invitation that creates or grants a new Account User identity—whether for Customer-organization access, platform administration, installer duties, or another invite-created account type implemented by the MDM Service—you agree to these MDM Terms as an Account User for your own access and conduct. Invite acceptance is individual Account User assent only. It does not, by itself, bind a Customer or purport to bind a Customer organization. An invitee binds a Customer only if that person separately has authority to bind the Customer and completes an organization-authority acceptance flow that expressly records Customer acceptance (for example self-service organization creation under this Section 1.1). Existing Account Users who later accept an invite to another organization or another account type are not required by these MDM Terms to re-accept solely because they already have an account; acceptance is required when a new identity is created through invite acceptance or when the product flow expressly requires assent for a new account.

No login gate. These MDM Terms describe contract assent collected at the applicable signup or invite-acceptance step. They do not require a separate terms gate on every subsequent login for users who already accepted, and they do not invent acceptance records for users who never went through a new-account assent step.

2. The MDM Service

The MDM Service is a variable business service for managing supported routers and related devices enrolled under a Customer account. Depending on plan, configuration, device capability, network path, and product availability, the MDM Service may include features such as:

organization, user, and role administration;
device inventory, online/offline status, and last-seen information;
configuration profiles, rollouts, jobs, and firmware updates;
monitoring dashboards, reports, audit history, and data export;
optional location and fleet map views where enabled;
optional customer-directed integrations and destinations;
optional automated assistance features, where offered.

Features, data retention windows, export options, and device capabilities vary. Not every organization, plan, device, or account role receives every feature. Telisky may add, change, limit, or discontinue features over time. These MDM Terms do not promise any particular uptime, response time, real-time delivery, geographic coverage, or service level unless a separate written order or support plan expressly states one.

3. Accounts, roles, and security

3.1 Account information

You agree to provide accurate registration and profile information and to keep it reasonably current. You must not share Account User credentials in a way that defeats role separation or auditability.

3.2 Roles and access

For Account Users associated with its Customer organization, Customer controls which such Account Users it invites and which roles or permissions they receive within that organization, and Customer is responsible for promptly revoking that organization-associated access when a person should no longer use it. Telisky controls invitation, access, and revocation for platform administrators and installers who are not associated with a Customer organization.

3.3 Security responsibilities

Customer and Account Users are responsible for:

safeguarding passwords, single sign-on settings, recovery methods, and API tokens;
using appropriate access controls for exported files and screenshots;
promptly notifying Telisky of suspected unauthorized access to the Customer account.

Telisky implements technical and organizational measures appropriate to a cloud business service, but no service is perfectly secure. These MDM Terms do not promise absolute security, invulnerability, or that unauthorized access can never occur.

4. Customer authority over devices and people

4.1 Device and network authority

Customer represents and warrants that it has, and will maintain, all rights, title, licenses, and authority needed to enroll, configure, monitor, locate, command, update, and otherwise manage devices and networks under its account. That includes authority from device owners, site operators, vehicle owners, employers, contractors, and other rights-holders as applicable.

4.2 Notices and authorizations for personnel and users

Customer is solely responsible for providing all notices, obtaining all authorizations or consents, and establishing all lawful bases required under applicable law for:

employees, contractors, drivers, passengers, site visitors, and other individuals who may be affected by managed devices;
location, movement, radio/network, health, configuration, logging, export, and remote-control features Customer enables;
any workplace, vehicle, public-safety, industrial, or other monitoring use.

Account assent is not tracked-person consent. Acceptance of these MDM Terms by an organization creator or Account User is contract assent for the MDM Service. It is not consent by every individual whose location, device, vehicle, or communications may be observed through Customer’s use of the MDM Service. Customer remains responsible for those obligations.

4.3 Prohibited covert, unlawful, or stalking uses

Customer and Account Users must not use the MDM Service to:

track, surveil, or locate individuals without lawful authority and required notices or authorizations;
engage in stalking, harassment, domestic abuse facilitation, or similar unlawful monitoring;
gain unauthorized access to networks, devices, accounts, or data;
conceal monitoring from people who must be informed under applicable law or Customer policy;
violate wiretap, privacy, employment, consumer, export, sanctions, or other applicable laws.

Telisky may suspend or terminate access for suspected prohibited use.

5. Data categories the MDM Service may process

When devices report and when Customer enables relevant features, the MDM Service may process operational and account data in categories such as the following. Exact fields, frequency, and availability depend on device model, firmware, configuration, connectivity, plan, and product version. Not every sample includes every category.

5.1 Account and organization data

Names, email addresses, organization names, roles, invite status, authentication events, preferences, billing contacts, and similar account administration data.

5.2 Location and movement

Geographic coordinates, altitude, speed, heading, fix quality indicators, trails or history used for maps and exports, dwell or stop-related derived views, and related timing. Location features may be delayed, buffered, incomplete, inaccurate, or unavailable when GPS, power, sky view, configuration, or connectivity limit reporting.

5.3 Cellular, radio, and network

Carrier or operator identifiers, radio access technology, band and signal quality metrics, cell or sector identifiers and neighbor summaries, modem or radio health indicators, IP addressing and gateway information for managed links, latency or quality observations, approximate data-usage counters, SIM slot or presence status, and related network path information. Some sensitive identifiers may be limited, redacted, or not stored even when a device observes them.

5.4 Device health and status

Online/offline state, last-seen time, firmware versions, temperatures or resource indicators, WAN or cellular link state, outage or buffered-telemetry flags, alerts, optional diagnostic test results, and similar operational health signals.

5.5 Configuration and control state

Desired and reported configuration, profile assignments, Wi‑Fi / APN / VPN / GPS / management interval settings as configured by Customer, job and command history (such as reboot, configuration apply, firmware update, diagnostics), and related control metadata. Secrets are intended to be protected and are not meant to be exposed in ordinary UI or API responses.

5.6 Logs, events, and audit records

Device-reported events, severity and kind labels, structured event payloads, operator audit history of actions and views in the cloud portal, and support or debug session metadata when privileged support access is used.

5.7 Raw payloads and exports

Devices may send structured heartbeats or snapshots. Customer-authorized exports may include selected fields or broader raw payload content for support, compliance, or offline analysis. Customer is responsible for securing downloaded archives.

5.8 Derived and integration data

Reports, trends, coverage or problem-area rollups, map heat or trail views, geofence or rule evaluations where offered, and data sent to customer-directed destinations or integrations Customer configures (for example operational sharing destinations). Derived views can be incomplete or approximate.

5.9 Accuracy and completeness limits

Telemetry can be delayed, buffered while offline, partial, duplicated, out of order, or inaccurate. The MDM Service is not a guarantee of continuous, real-time, precise, or complete observation of any person, vehicle, or site. Do not treat map positions, signal values, or last-seen times as courtroom-grade or safety-critical truth without independent verification appropriate to your use.

6. How Telisky uses data (service purposes)

Telisky processes Customer Data and related service data to:

provide, maintain, secure, and support the MDM Service;
operate account, billing, and access-control functions;
apply Customer-directed configurations, jobs, rollouts, and integrations;
generate operational views, reports, exports, and audit history for Customer;
diagnose faults, prevent abuse, and improve reliability and quality of the MDM Service;
create aggregated or deidentified statistics, benchmarks, coverage insights, and analytical products as described in Section 8;
comply with law and enforce these MDM Terms.

Telisky does not sell personal information or identifiable Customer Data as a consumer data brokerage product. For the research, benchmarking, network and coverage analysis, product-development, and commercial-analytics purposes described in Section 8, Telisky uses or discloses Customer-derived data only in aggregated or deidentified form. Use of personal information is further described in Telisky’s Privacy Policy, which explains privacy practices and does not convert account assent into consent by tracked individuals.

7. Access by Telisky personnel and service providers

Telisky personnel and subprocessors may access Customer accounts, device metadata, telemetry, logs, and configuration as needed to operate, secure, and support the MDM Service, including troubleshooting, abuse response, platform reliability, and billing operations.

Privileged support access, when used, is intended to be limited in purpose and time and subject to internal controls and logging. These MDM Terms do not promise that every support access will be pre-approved by Customer on a per-session basis, or that support can never view operational data necessary to fix a problem you asked us to fix.

Service providers (for example hosting, email delivery, observability, or payment processors) may process data only to help Telisky deliver the MDM Service, under contractual obligations appropriate to their role. Details of subprocessors may be addressed in a DPA or related documentation when one applies.

7.1 Customer-directed integrations

If Customer enables an integration, export destination, or external publish path, Customer directs Telisky to transmit the configured data to that destination. Telisky is not responsible for the security, retention, or lawful use of data after it leaves the MDM Service under Customer’s direction.

7.2 Optional automated assistance

Where Telisky offers optional automated assistance features, those features may send limited prompt, device, configuration, or diagnostic context to assistance systems in order to generate suggestions. Assistance output can be wrong, incomplete, or unsafe if followed blindly. Customer remains responsible for reviewing suggestions before applying changes to production devices. These MDM Terms do not promise any particular AI provider, model, accuracy level, or continuous availability of assistance features.

8. Customer Data ownership and license

As between the parties, Customer owns Customer Data—meaning content and operational data Customer or its devices submit to the MDM Service under Customer’s account (including device telemetry Customer is authorized to collect, configurations Customer applies, and exports Customer generates), excluding Telisky’s software, documentation, brands, and underlying platform.

Customer grants Telisky a worldwide, non-exclusive license to host, copy, process, transmit, display, and create derivative operational views of Customer Data solely as needed to provide, maintain, secure, support, and improve the MDM Service and to meet legal obligations. This license ends when Telisky no longer needs the data for those purposes, subject to the Privacy Policy, any applicable DPA, applicable law, and documented technical or legal retention requirements. Residual copies may remain in backups, archives, or similar systems for as long as those requirements and technical limits apply; these MDM Terms do not promise that residual copies are deleted or made inaccessible in the ordinary course, consistent with Section 10.

Telisky may create data derived from Customer Data that has been aggregated or deidentified so that it cannot reasonably be linked to Customer, an Account User, a tracked person, or an individual device (Deidentified Data). Telisky may use, disclose, license, and commercialize Deidentified Data for lawful business purposes, including research, benchmarking, network and coverage analysis, product development, and commercial analytics. Telisky will not attempt to reidentify Deidentified Data or authorize a recipient to reidentify it. Identifiable Customer Data remains outside this grant, and Telisky must apply reasonable technical and organizational measures designed to prevent attribution or reidentification before disclosure.

9. Privacy Policy relationship

Use of the MDM Service is also subject to Telisky’s Privacy Policy, as updated from time to time. The Privacy Policy describes privacy practices. These MDM Terms are the commercial terms for the MDM Service. If there is a conflict about commercial terms for the MDM Service, these MDM Terms control over generic website terms. If a signed order or DPA addresses its stated subject (for example fees, subprocessors, or data-processing roles), that document controls for that subject.

Again: organization or Account User assent to these MDM Terms is not consent by tracked persons.

10. Retention, export, and deletion limits

Retention, query windows, archive restore options, and export formats depend on plan, product configuration, and technical limits. Hot queryable history, longer archives, and complete raw exports may differ. These MDM Terms do not promise:

any exact retention period for every data type;
that every historical sample remains exportable forever;
immediate or complete deletion from all backups upon request;
that Customer can always erase data that law, security, billing, or audit obligations require Telisky to keep for a period.

Customer should use product export tools for its own records when it needs offline copies. Upon account termination or data requests, Telisky will handle Customer Data in accordance with the Privacy Policy, any applicable DPA, and legal retention needs.

11. High-impact remote actions

The MDM Service may allow Account Users with sufficient permissions to send high-impact actions to devices, which can include (depending on product capability) reboots, configuration changes, firmware updates, factory resets, diagnostics, messaging or SMS-related device actions, and other remote commands.

Customer is responsible for:

limiting who can run high-impact actions;
verifying the target device and change before confirming;
understanding that a remote action can disconnect a site, clear local configuration, or interrupt service;
maintaining on-site recovery procedures when cloud reachability fails.

Telisky is not responsible for operational loss caused by Customer-authorized commands, mistaken targets, or changes applied without adequate internal controls.

12. Acceptable use

In addition to Section 4.3, Customer and Account Users must not:

probe, scan, or overload the MDM Service except through documented interfaces within fair use;
reverse engineer the MDM Service except to the limited extent applicable law allows and after required notice;
resell, white-label, or provide the MDM Service to third parties as a managed service unless a written Telisky agreement allows it;
upload malware or unlawful content;
bypass technical limits, billing meters, or access controls;
use the MDM Service for any purpose that is illegal in the applicable jurisdiction.

13. Third-party networks, carriers, and dependencies

The MDM Service and managed devices depend on third parties Customer or Telisky does not control, including mobile carriers, private APNs, internet providers, GPS satellite systems, Customer firewalls, Customer identity providers, and external integration endpoints. Outages, policy changes, radio conditions, SIM issues, and third-party API changes can degrade or block service. Telisky is not responsible for those third-party networks or services.

14. No emergency or safety-critical reliance

The MDM Service is not designed or warranted as an emergency-response system, life-safety system, 911/E911 replacement, sole means of dispatch, sole means of theft recovery, or sole control path for hazardous equipment. Do not rely on the MDM Service as the only channel for emergency communications or safety-critical decisions. Maintain independent procedures appropriate to your industry and risk.

15. Fees, orders, and taxes

Fees, taxes, payment timing, suspension remedies for nonpayment, renewal terms, plan packaging, and other commercial billing terms for paid use of the MDM Service are governed by Customer’s applicable signed order, checkout flow, or invoice (or other commercial terms presented at purchase). These MDM Terms do not invent default billing obligations. If an applicable order, checkout, or invoice does not state a particular fee, tax, payment-timing, suspension, renewal, or packaging term, these MDM Terms do not create it.

These MDM Terms do not publish pricing. If there is a conflict between these MDM Terms and a signed order about price, quantity, term, fees, taxes, payment, suspension for nonpayment, or renewal, the order controls for that subject.

16. Intellectual property

Telisky and its licensors own the MDM Service, software, documentation, APIs, brands, and all related intellectual property. Except for the limited right to use the MDM Service under these MDM Terms and Customer’s order, no rights are granted by implication. Customer must not remove proprietary notices or use Telisky marks in a misleading way.

Feedback Customer provides may be used by Telisky without obligation to Customer.

17. Suspension and termination

Customer may stop using the MDM Service and may request account closure through supported channels.

Telisky may suspend or terminate access immediately if:

Customer materially breaches these MDM Terms or an order;
fees are past due and Customer’s applicable signed order, checkout flow, invoice, or other commercial terms presented at purchase expressly authorize suspension for nonpayment;
continued service would create security, legal, or abuse risk;
required by law.

Telisky may also discontinue the MDM Service or a feature with reasonable advance notice when practicable. Upon termination, the right to access the MDM Service ends. Sections that by nature should survive (including ownership, license survivals needed for wind-down, confidentiality-like protections in the Privacy Policy/DPA, warranties disclaimer, liability limits, indemnity, and governing law) survive termination.

18. Warranties and disclaimers

Customer warranties. Customer warrants that it has the authority described in Sections 1 and 4 and that its use of the MDM Service will comply with law.

Service disclaimer. TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE MDM SERVICE IS PROVIDED “AS IS” AND “AS AVAILABLE.” TELISKY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. TELISKY DOES NOT WARRANT THAT THE MDM SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, SECURE, ACCURATE, COMPLETE, OR AVAILABLE AT ANY PARTICULAR TIME, OR THAT LOCATION, RADIO, OR HEALTH DATA WILL BE TIMELY OR PRECISE.

Some jurisdictions do not allow certain disclaimers. In those jurisdictions, disclaimers apply to the fullest extent permitted.

19. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW:

TELISKY WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, LOST REVENUE, LOST DATA, COST OF SUBSTITUTE SERVICES, BUSINESS INTERRUPTION, OR LOSS OF GOODWILL, EVEN IF ADVISED OF THE POSSIBILITY.
TELISKY’S TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THE MDM SERVICE OR THESE MDM TERMS WILL NOT EXCEED THE AMOUNTS PAID BY CUSTOMER TO TELISKY FOR THE MDM SERVICE IN THE TWELVE (12) MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM (OR, IF NO FEES WERE PAID, ONE HUNDRED U.S. DOLLARS).

These limits apply regardless of theory (contract, tort, strict liability, or otherwise) and are an essential basis of the bargain. They do not limit liability that cannot be limited under applicable law (for example certain bodily injury claims where such a limit is unenforceable).

20. Indemnity

Customer will defend, indemnify, and hold harmless Telisky and its officers, directors, employees, and agents from and against claims, damages, losses, liabilities, costs, and expenses (including reasonable attorneys’ fees) arising out of or related to:

Customer’s or its Account Users’ use of the MDM Service;
Customer Data and Customer’s devices, networks, and monitored people or property;
alleged failure to provide required notices or obtain required authorizations or consents;
high-impact commands or configurations Customer initiates;
Customer-directed integrations and destinations;
breach of these MDM Terms or violation of law by Customer or its Account Users.

21. Governing law and venue

These MDM Terms are governed by the laws of the State of Delaware, excluding conflict-of-law rules. The parties consent to exclusive jurisdiction and venue in the state or federal courts located in Delaware for disputes arising out of these MDM Terms or the MDM Service, except that Telisky may seek injunctive relief in any jurisdiction to protect its intellectual property or the security of the service.

22. Changes to these MDM Terms

Telisky may update these MDM Terms by publishing a new immutable version with a new version identifier and URL, and by updating the current-pointer page to identify that version. For material changes that require renewed contract assent under applicable law or Telisky’s product design, Telisky will provide direct notice through reasonable account contact methods (for example email to organization contacts or an in-product acceptance step for new accounts or renewed assent flows).

Past snapshots remain available for audit. Acceptance records should store the version identifier and the exact immutable URL accepted. Mere continued use after a website post, without more, is not the sole mechanism these MDM Terms rely on for new-account assent.

23. Precedence, severability, waiver, assignment, entire agreement

23.1 Precedence

For the MDM Service:

a signed order or DPA controls its stated subject;
these MDM Terms control over generic Telisky website terms of service for the MDM Service;
product documentation describes features but is not a warranty or SLA unless expressly incorporated in an order.

23.2 Severability

If a provision is unenforceable, it will be modified to the minimum extent necessary to be enforceable, and the remaining provisions remain in effect.

23.3 Waiver

Failure to enforce a provision is not a waiver. Waivers must be in writing to be effective.

23.4 Assignment

Customer may not assign these MDM Terms without Telisky’s prior written consent, except to an affiliate or successor in connection with a merger or sale of substantially all assets, provided the assignee is not a competitor and assumes the obligations. Telisky may assign these MDM Terms to an affiliate or in connection with a corporate reorganization or sale of assets. Any other attempted assignment is void.

23.5 Entire agreement

These MDM Terms, together with any applicable order, DPA, and policies they expressly incorporate, are the entire agreement between the parties about the MDM Service and supersede prior or contemporaneous proposals and communications on that subject. Account acceptance flows may create electronic records of assent; those records are intended to satisfy applicable electronic transactions rules.

23.6 Electronic records and signatures

You agree that electronic acceptance (including an unchecked checkbox that you affirmatively select, click-to-accept, or similar recorded assent tied to a version identifier and immutable URL) has the same legal effect as a signed writing to the extent permitted by law.

24. Contact

Questions about these MDM Terms: sales@telisky.com

Telisky Inc.
Delaware, United States

End of immutable snapshot mdm-terms-2026-07-17.