Terms of use

1. Service relationship

Telematric is provided by Sakura Inc. These terms describe the conditions for using our website, APIs and services. Your accepted order and any separately agreed service or data-processing terms define the purchased scope and take precedence over a conflicting general description. An updated webpage does not silently replace an existing negotiated agreement, change a saved subscription price or authorize a new processing purpose.

Use an account you are authorized to operate. If acting for an organization, you must have authority to configure its workspace and authorize the relevant processing and purchases. Telematric is intended for authorized business and technical users, not direct use by children.

2. What the service provides

Depending on enabled capabilities and the documented contract, Telematric provides device provisioning, telemetry/history, alerts, signed webhooks, compatible commands and firmware updates, software connections, energy planning, water calculations and supported AI services. Customers can use their own application and dashboard.

Supported operations, profiles, permissions and limits are described in the API documentation, current service offers and your order. Availability in a directory is not a promise of a functioning adapter, certification, partnership, complete vendor API coverage or compatibility with every installation. Pilots and synthetic sandboxes need separate real-installation acceptance before operational reliance.

Your application retains its own end-user accounts, branding, business database and business workflows. Customer/site/device references in Telematric organize operational records; they do not automatically create application accounts or replace an ERP, LIMS, payment gateway or complete GIS system.

3. Customer data, ownership and permitted processing

You retain your rights in information you provide or are authorized to connect. Third parties retain their rights in their systems and licensed content. Using Telematric does not transfer ownership of customer operational data to us. Personal information also remains subject to individuals’ legal rights.

You authorize us to receive, validate, transform, store, retrieve, transmit and derive results from the information needed to perform the operations you request, secure and support the service, and meet applicable legal duties. This includes selected snapshots, operational logs, histories, backups and authorized model operations as described in the Privacy policy. We do not sell customer operational data or use it to train another customer’s model without separate authorization.

You are responsible for having the necessary source-system permissions, notices and lawful basis for the data and instructions you provide, including your users’ information. Use pseudonymous operational identifiers where practical and provide only the data needed. Contact us before supplying data that requires special processing arrangements; account creation alone does not establish those arrangements.

Telematric retains rights in its platform, SDKs, reusable connectors, schemas, algorithms and training software. Customer-specific model access, artifact delivery and any additional intellectual-property rights should be defined in the applicable service agreement; source-data rights do not automatically establish an exclusive right to the underlying algorithm. No universal model-export format or compatibility with another runtime is promised.

4. Connections, source authority and storage

You select the provider, credentials, allowed scope, mappings and destinations. Source systems remain authoritative for their own equipment, network, laboratory, financial and other records. Telematric retains local mappings, operational evidence and selected snapshots needed by enabled features.

SAP/Maximo and lims.science supported browsing currently reads records on demand. Selected Giswater records and mapped SENAITE results may be stored as versioned snapshots. Telemetry, supported water records and authorized training samples are hosted operational data. A live read still processes data through our infrastructure; it is not a promise of zero data handling.

Confirm source identities and mappings before relying on them. A configuration check does not prove every operation, complete inventory or ongoing source availability. Historical snapshots and cached results must be evaluated with their timestamps, publication state and freshness. You remain responsible for third-party subscriptions, licenses, API permissions, network access and attribution requirements.

Some supported connectors perform explicitly requested writes, such as an existing CRM handoff or merchant checkout. Read-only connectors do not gain write authority through a general account or subscription. Any additional write operation requires its own documented capability and appropriate authorization.

5. Devices, firmware and physical operation

You are responsible for compatible hardware, sensing/actuation logic, calibration, installation, connectivity, power, local controls and safe operation. A command acknowledgement or firmware download is not independent proof of a physical outcome. Use supported firmware, device identities, model/board profiles and local interlocks.

The supported ESP32 setup and OTA path has specific firmware, partition and boot-health requirements. STM32 currently provides a source SDK with board-specific integration requirements; STM32 OTA and browser flashing are not established capabilities. Do not use another board’s image or assume support from a catalog logo.

Telemetry and forecasts do not replace an equipment safety system, engineering assessment or laboratory testing. Customers must implement appropriate human review and local safeguards for their application.

6. AI training, predictions and calculations

Supported training needs separate workspace-owner/administrator authorization, appropriate data and the enabled service. A subscription or use of a forecast is not consent to train on all workspace information. Current customer-specific training and model selection are separated by workspace, supported service and policy revision.

Outputs may be measurements reported by equipment, rules, physical simulations, scenarios or trained predictions. Read the applicable method, units, horizon, assumptions and provenance. We do not guarantee model accuracy, energy or water savings, exact grid-restoration times, battery lifespan, leak location, regulatory compliance or water safety from those outputs.

We may retain a fallback or reject a trained candidate that does not meet the service’s evaluation gate. A percentage or score must not be treated as demonstrated accuracy or calibrated uncertainty unless expressly documented as such. Customers decide how outputs are presented and used in their applications.

Forecast consumption and spending scenarios are distinct from approved consumption and reviewed charges. The utility-calculation service does not itself issue legal/tax invoices, collect utility payments or establish a paid balance. Laboratory staff and the LIMS retain scientific review/publication responsibility. Suggestions do not authorize physical commands or source-system writes.

7. Prices, subscriptions and usage

The selected checkout or accepted order identifies the price, currency, billing interval, recurring authorization and purchased capability. New purchases require the displayed confirmation. Sandbox payments and data are for testing and do not represent live payment receipts. Eligible sandbox access may enable development devices while the platform is in test mode, as documented.

Service access is workspace-specific and separate from API-key scopes, source permissions and model-training authorization. Required services must also be active in that workspace. Under the current separate-subscription model, each required service has its own subscription; disabling, expiring or cancelling one does not automatically cancel the others. Review all renewals in Billing and contact support about a blocked dependent service.

Stopping renewal preserves access through the verified paid period, subject to applicable security/suspension and dependency rules. Disabling new checkout does not cancel existing provider renewals. Refunds, disputed charges and financial corrections are handled through support and the original payment provider, consistently with your agreement and applicable law; nothing here removes mandatory refund or consumer rights.

Usage is subject to the current documented limits. Proposed platform plans, capacity packs, retention windows and automatic trial allowances are not active merely because they appear in a roadmap or discussion. We do not silently convert those proposals into charges or reprice an existing saved subscription.

8. Credentials and acceptable use

Protect account credentials, device keys and provider secrets. Keep business keys on your backend, give integrations only necessary scopes, and notify support@telematric.com if access is compromised. Workspace managers are responsible for authorized membership and source/destination configuration.

Do not access another workspace, bypass permissions or limits, submit malicious content or firmware, misuse a provider’s credentials, or use the service for unlawful processing. Access may be restricted to address security, abuse, nonpayment, unavailable dependencies or legal requirements. Where appropriate we will explain the restriction and recovery options. Restricting access is distinct from cancellation or deletion.

9. Cancellation, disconnection and data requests

Use Billing to stop supported renewals and contact us if provider reconciliation is needed. Retained records are not automatically erased by cancellation, device disablement, site archival or source disconnection. You may also need to revoke credentials at the source and update your own application.

Use documented APIs to retrieve supported data. For a broader export, account closure, correction or erasure request, contact hello@telematric.com. We verify authority and confirm scope, available formats and timing, including source-owned records, backup copies and records requiring separate retention. These requests are currently support-assisted.

There is no universal self-service full-workspace export/deletion guarantee or automatic post-cancellation window under these general terms. Specific retention, exit, recovery or residency commitments must be expressly agreed and supported by the applicable service. We remain responsible for responding to applicable data-protection rights and processing instructions; this section does not waive them.

10. Service changes and operating limits

We maintain supported contracts and document material changes or deprecations. New provider profiles or operations may require a shared adapter update. Roadmap items and demonstrations are not delivery commitments or a production SLA. Any availability, support, recovery or dedicated-hosting commitment must be stated in an applicable agreement.

Customers should maintain appropriate source records, exports and operational recovery procedures. We investigate service failures and support issues under the applicable service arrangement. These terms do not exclude liability or remedies that applicable law does not allow to be excluded.

11. Questions and updates

Contact Telematric at hello@telematric.com for agreements, data handling and commercial questions, or support@telematric.com for technical issues. See the Privacy policy for information rights and processing details.

We date revisions and communicate material changes through appropriate service channels. Existing accepted orders and negotiated commitments remain applicable unless changed under their agreed process. Separate authorization remains necessary where a change requires it.