> ## Documentation Index > Fetch the complete documentation index at: https://docs.wede.pt/llms.txt > Use this file to discover all available pages before exploring further. # Terms of Service > Conditions of use of the wede platform *Version 2.0, 22 October 2026. Replaces version 1.0 of June 2026.* ## 1. Parties and definitions These Terms govern the use of the wede platform between **WEDELI, LDA** ("wede", "we") and the organisation that subscribes to it ("Customer", "you"). A signed contract or order with wede prevails over these Terms where they differ. | Term | Meaning | | - | - | | **Platform** | The wede API, SDKs, dashboard and related services | | **Tenant** | The Customer's organisation on the Platform | | **User** | A person who uses the dashboard, an application or the API on behalf of the Tenant | | **Device** | Any equipment that sends operations to wede: a phone or tablet with the SDK, or the Customer's own hardware (terminals, ATMs, kiosks, meters and others) | | **Offline queue** | The operations a Device keeps while it has no connection, sent when the connection returns | | **Event** | An operation sent to wede, with the content the Customer chooses | ## 2. The service wede is operational continuity infrastructure. It keeps the Customer's critical operations going when the internet, the cloud or local infrastructure fail: events are captured on the Device even without a connection, delivered through the Customer's channel order (internet, SMS, voice and others the Customer enables), synchronised and reconciled when the connection returns, and recorded with an audit trail. Depending on the plan and configuration, the Platform also ranks and dispatches field teams, manages missions, keeps an operation ledger, reconciles operations against the Customer's own records and produces signed evidence of outages. wede is infrastructure, not an end-user application. Operational decisions and their consequences remain with the Customer. wede does not validate the physical state of the Customer's teams, equipment or resources, and does not replace the Customer's own emergency communications. ## 3. Plans, prices and payment * Plans are annual. Each plan sets what is included (users, devices, zones, events and communications per year) and the availability target. The Customer's own conditions for each plan are shown in Billing in the dashboard. * A plan becomes active once its first payment is received. Invoices are issued by wede and are payable within the term stated on them. * Usage above what the plan includes never stops the service. It is counted and shown in Billing, and charged only as agreed in the contract. * Usage alerts are sent by email when 50, 40, 30, 20, 10 and 0 percent of the yearly allowance remains. ## 4. End of a licence When a licence ends without renewal, a renewal window of 30 days follows. After it, the account is degraded, never switched off: critical and high priority events, synchronisation of offline operations, devices, missions, dispatch and connectivity keep working, and data can still be read; other new events, management, configuration, new integrations and reports stop until the licence is renewed. The privacy settings, to restrict or delete personal data, keep working. Data is kept and removed according to the [Privacy Policy](https://docs.wede.pt/legal/privacy). ## 5. Offline operation * Each Device keeps its offline queue in the storage the Customer's application provides. Every operation carries a sequence number per Device and an integrity checksum. * When the connection returns, the queue is synchronised. Synchronisation is idempotent: an operation already received is never applied twice, and an operation whose content changed after capture is refused and recorded as an integrity incident. * For each Device, the Platform shows what arrived, what is missing and since when. * wede cannot recover operations lost to the failure, loss or reset of a Device, or kept in storage the Customer's application does not preserve. ## 6. Communication channels Fallback channels (SMS, voice, satellite, LoRa and others) work through providers in each country and through the Customer's own providers when connected. wede provides a resilience architecture with per-message observability and fallback between transports; it does not guarantee the delivery of any single message, which depends on networks and providers outside its control. ## 7. Customer responsibilities * The readiness of its teams, equipment and resources, and keeping their status up to date on the Platform. * The configuration of its catalog, parsers, teams, zones, channel order and retention choices. * The security of its API keys, sessions and user accounts. * The content of its events: it must have a lawful basis for any personal data it sends, and must not send data it is not allowed to process. ## 8. Security and data protection wede processes the Customer's personal data as a processor on the Customer's instructions. The [Privacy Policy](https://docs.wede.pt/legal/privacy) describes the data, retention, sub-processors, transfers and incident notification, and the data processing agreement in the contract governs this relationship. Security measures are described in [Security](https://docs.wede.pt/concepts/security.md) and [ISMS](https://docs.wede.pt/compliance/isms.md). ## 9. Availability wede aims at the availability target of the Customer's plan for the production API, as stated in the contract. Interruptions caused by third-party networks and providers, scheduled maintenance announced at least 48 hours in advance, force majeure or the Customer's own actions are excluded. ## 10. Limitation of liability wede is not liable for indirect or consequential damages, for losses caused by the failure of the Customer's Devices or third-party networks, or for operational decisions made by the Customer. wede's total liability to the Customer is limited to the amounts paid by the Customer in the 12 months before the event that caused the damage, except where the law does not allow such a limit. ## 11. Intellectual property The Platform and its technology belong to wede. Parts of that technology are the subject of pending patent applications. The SDKs are licensed to the Customer privately, under the contract and the SDK terms, and may not be redistributed. ## 12. Confidentiality Both parties keep confidential all non-public information shared under the contract, including operational data, technical configurations and commercial terms. ## 13. Changes wede may change these Terms with at least 30 days' notice by email. Continued use after that period means acceptance of the new Terms. ## 14. Law and courts These Terms are governed by Portuguese law. Disputes go to the courts of Lisbon. ## 15. Contact * General: [geral@wede.pt](mailto:geral@wede.pt) * Support: [support@wede.pt](mailto:support@wede.pt) * Security: [security@wede.pt](mailto:security@wede.pt) * Privacy: [privacy@wede.pt](mailto:privacy@wede.pt) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.