Integration Terms of Use

1. Scope and approval

These Terms of Use apply to the operator portal, sandbox, machine API, webhooks, documentation, and all data made available through Boring Order Tracker (“BOT”). Operators may use the platform only for the purpose reviewed by BOT, the approved scopes, and the resources expressly shared by users.

Registration, sandbox access, or technical availability does not create any entitlement to production access. Every integration and every material change is subject to BOT's manual review and approval.

2. Non-commercial use by default

The standard permission is strictly non-commercial. Any direct or indirect monetisation or commercial use in connection with BOT data is prohibited unless a separate written agreement has been concluded in advance.

Commercial use includes, without limitation, Google Ads, Google AdSense and any other advertising; sponsorships; subscriptions; paywalls; premium or paid features; paid apps or services; affiliate or referral compensation; commissions; lead generation; data sales or licensing; paid analytics or consulting; and donation or crowdfunding models used to finance the operator's offering. An offering without an immediate charge may also be commercial where BOT data creates a business or other economic advantage.

Anyone wishing to use BOT data commercially must contact BOT before that use begins, obtain an individual offer, and receive express written permission. Silence, technical enablement, or general production approval does not replace that agreement.

3. Source attribution and BOT credit

Every page, view, output, and export in which BOT data appears must display the BOT-prescribed credit and a clearly visible link to the BOT app or website in an immediately recognisable manner. Attribution only in a legal notice, footer, or general sources page is insufficient. A footer alone is not enough.

Where BOT data is mixed with data from other sources, every individual BOT-originated or BOT-derived entry, record, table value, map point, chart value, or other result component must be clearly labelled as originating from BOT directly at the point of display. Provenance must be preserved throughout internal processing and must not be obscured through aggregation, renaming, or derivation.

The operator must not claim a partnership, endorsement, certification, or affiliation with BOT or Tesla unless BOT has expressly permitted that claim in writing.

4. Consent, purpose limitation, and data minimisation

Only data authorised by the currently valid grant for the relevant integration, resource, and scope may be processed. Consent for one integration, order, or vehicle must not be transferred to another integration, resource, account, or purpose.

The operator must not guess missing identifiers or sensitive information or infer them from other data. Re-identification, cross-integration correlation, and reconstruction of a VIN, real order number, BOT account, Tesla account, or internal BOT identifier are expressly prohibited.

5. Prohibited uses

Prohibited uses include, without limitation, scraping or circumventing internal BOT interfaces; resale or public raw-data dumps; data-broker or profiling purposes; personalised advertising or tracking based on BOT data; surveillance; discriminatory or unlawful use; and safety-critical or solely automated decisions about individuals.

BOT data must not be used to contact users, enrich third-party profiles, train generally available artificial-intelligence models, or develop a competing dataset unless BOT has expressly approved that use in writing beforehand.

6. No uncontrolled onward sharing

BOT data must not be disclosed or made accessible to third parties. Technically necessary processors may be used only with BOT's prior written consent, under appropriate data-protection and security agreements, and only to the extent required. The operator remains responsible for their actions.

7. Revocation, deletion, and evidence

Revocation terminates access immediately. The operator must delete all individual data and all derived or cached copies from production systems, caches, search indexes, exports, and controllable backups no later than the deadline specified by the API, which is generally seven days, and may acknowledge deletion through the designated endpoint only after deletion is complete.

Deletion obligations continue after suspension or termination. BOT may require reasonable technical or organisational evidence that deletion has been completed.

8. Security and incidents

Private keys, certificates, and credentials must be protected in accordance with the state of the art, granted only the minimum necessary privileges, and never shared between independent integrations. Rate limits, mTLS, signatures, cursors, suspensions, and other safeguards must not be circumvented.

Any actual or suspected security or privacy incident relating to BOT must be reported to BOT without undue delay and no later than 24 hours after discovery. The operator must disable affected credentials, preserve evidence, and reasonably cooperate with investigation, containment, and user notification.

9. Operations and API behaviour

The operator must comply with the current API documentation, quotas, polling recommendations, and idempotency, ETag, cursor, and revocation contracts. The operator must safely handle errors, retries, reordered events, and temporary unavailability and must not evade safeguards by using multiple certificates, IP addresses, or integrations.

10. Data quality, availability, and user transparency

BOT data may be delayed, incomplete, or inaccurate. The operator must communicate this clearly to users, must not derive guaranteed delivery, production, or shipping commitments from the data, and must promptly implement a correction or removal after being notified.

To the extent permitted by law, the platform is provided without any guarantee of particular availability or fitness for a particular purpose. Mandatory statutory rights remain unaffected.

11. Audit, suspension, and termination

BOT may inspect the submitted review URL, public presentation, source attribution, and compliance with these Terms and may request reasonable information or evidence. In the event of a breach, security risk, overdue deletion acknowledgement, or withdrawal of approval, BOT may immediately suspend or revoke scopes, certificates, webhooks, or the entire integration.

After termination, the operator must not retrieve or display new BOT data. Continuing deletion, confidentiality, provenance, and evidence obligations remain in force.

12. Trademarks, content, and public presentation

BOT grants only a revocable right to use its name, prescribed credit, and approved brand elements in the form specified by BOT for source attribution. No other rights in software, documentation, databases, content, or trademarks are transferred. BOT or Tesla trademarks must not be used as the operator's own product name, domain component, or misleading indication of origin.

13. Changes to these Terms

BOT may amend these Terms for the future. Every new material version must be expressly accepted in the portal before new integrations can be created or production access can be activated or reactivated. An amended purpose or scope approval does not automatically expand existing user consent.

14. Governing law and contact

German law applies to the extent permitted by law. Mandatory consumer-protection, data-protection, and conflict-of-laws provisions remain unaffected. If any provision is invalid, the remaining provisions remain unaffected.

Requests for a commercial licence or an individual offer must be sent to info@hosting-fox.de before monetisation begins. Provider information and privacy information are available in BOT's linked legal notice and privacy policy.