Security

1. Security approach

EleWave helps teams assign scheduled activities, capture completion evidence, and preserve operational history. We treat security as part of that workflow, not as a separate afterthought.

Our security program focuses on access control, workspace separation, infrastructure reliability, data protection, monitoring, and responsible handling of third-party integrations.

2. Workspace access

Workspaces are designed around explicit membership and role-based access. Customers are responsible for inviting the right people, removing access when it is no longer needed, and configuring integrations for their own workspace.

EleWave limits access to production systems and customer data to authorized personnel who need it for support, security, operations, or product delivery.

3. Data protection

We use technical and organizational measures designed to protect customer data against unauthorized access, loss, alteration, and misuse. These measures may include access controls, secure infrastructure practices, logging, monitoring, encryption in transit, and controlled operational procedures.

Customers are responsible for the content they put into EleWave, including activity instructions, files, proof submissions, messages, and participant data.

4. Infrastructure and monitoring

EleWave is operated on managed infrastructure and service providers selected for reliability and security. We monitor systems for operational issues, service abuse, and security-relevant events.

No internet-facing service can be guaranteed perfectly secure or always available. We continuously improve controls as the product, customer needs, and threat landscape evolve.

5. Integrations

EleWave may connect to third-party channels and tools such as Slack, Microsoft Teams, WhatsApp, email, authentication providers, billing providers, and hosting infrastructure.

Customers should review connected services, manage permissions carefully, and avoid sending sensitive data through channels that are not appropriate for that data.

6. Responsible disclosure

If you believe you have found a security issue, contact hello@elewave.work. Include enough detail for us to reproduce and understand the issue.

Please do not access, modify, delete, or disclose data that does not belong to you. We ask researchers to avoid service disruption, social engineering, spam, and automated high-volume testing.

7. Security questions

For security questionnaires, vendor reviews, or DPA/security documentation requests, contact hello@elewave.work.