Scope
The ISMS covers:- The wede API platform.
- The wede dashboard.
- The wede SDKs (JavaScript and TypeScript, React Native, Python, Swift, Android).
- The databases that hold platform and tenant data.
- wede’s source code repositories.
- All customer (tenant) data processed by the platform.
Security controls
Access control
- Role-based access control, checked on every API route. See Security.
- User sessions expire after 8 hours and can be revoked at once through token versioning.
- Passwords stored as bcrypt hashes. API keys stored as SHA-256 hashes and shown only once.
- Accounts lock for 15 minutes after 5 consecutive failed sign-ins.
- Strict tenant isolation, and no access for wede staff to event content, audit entry content or parser schemas.
Cryptography
- HTTPS for all API traffic.
- SHA-256 integrity checksums on offline events, verified on every sync.
- HMAC-SHA256 signatures on every webhook delivery, with webhook secrets encrypted at rest (AES-256-GCM).
- Secrets kept in a managed secrets service, never in source code.
Audit and logging
- Immutable audit log: database triggers reject any update or delete of an entry, whatever the role or application behind the request.
- Each entry records the tenant, the user, the action, the resource, the timestamp, the IP address and the user agent.
- Integrity incidents are recorded immutably; resolving one adds a separate resolution entry.
- Available through the API (
GET /v1/audit) and summarised daily in the compliance report.
Data protection
- Payload minimisation: once delivery is confirmed (or, for event types that send a team, once the event is closed), the stored event payload is cleared and only identifiers, type, channel and lifecycle remain.
- Event destinations (phone, email, device) are used for the delivery only; over the fallback channels they are kept encrypted with the organisation’s key while the delivery runs and removed when it ends.
- Retention per vertical and country: operational data with personal content is removed at the end of the operational period, and evidence records are anonymised at the end of the evidence period. See Privacy Policy.
- Each organisation’s sensitive data is encrypted with its own key, protected by a master key held in a hardware security module.
- Sandbox data is kept apart from production and never reaches a real provider.
Monitoring and incident handling
- Every integrity mismatch on synced data opens an integrity incident and alerts the tenant administrators by email.
- Connectivity changes per zone trigger
connectivity.degradedandconnectivity.restoredwebhooks. - Failed sign-ins and rejected parser changes are recorded and reported daily.
Change management
- Database changes are applied as numbered, sequential migrations.
- Every change to dispatch settings, users, parsers, teams and webhooks is recorded in the audit log.
Business continuity
- Offline-first capture: operations continue without internet and sync when connectivity returns.
- Automatic channel cascade across REST, SMS, voice, satellite, LoRa and edge, or store-and-forward, per tenant.
Hosting
wede is hosted in the European Union by default. Where local regulation requires in-country data residency, a dedicated regional instance is available by agreement.Compliance framework
See Security for how each control maps to these frameworks.
Sub-processors
wede relies on a small number of sub-processors for hosting, transactional email, payments and the communication channels it delivers through (SMS, voice, satellite and LoRa). The current list is in the privacy policy.Personal data incidents
wede notifies the affected organisation of a personal data breach without undue delay, as a processor under Article 33(2) GDPR, and keeps it informed until the incident is closed.Contact
- Security, responsible disclosure and audit documentation: security@wede.pt
- Privacy: privacy@wede.pt
- General: geral@wede.pt