Data Wepy handles
Wepy processes account identity, workspace membership, sender setup, contact and consent records, campaign content, automation configuration, delivery outcomes, and product-security metadata.
Provider credentials are encrypted before storage and are never returned to the browser after setup. Wepy does not place raw credentials, message bodies, recipient data, provider payloads, or access tokens in analytics or operational alerts.
Why the data is used
- Authenticate accounts and enforce workspace membership.
- Prepare, schedule, send, and report on customer campaigns.
- Honor unsubscribe, suppression, and consent decisions.
- Protect the service, diagnose failures, and prevent abuse.
- Improve product workflows using sanitized product events.
Infrastructure and subprocessors
Wepy uses hosted infrastructure for web delivery, application services, authentication, databases, background queues, error monitoring, and product analytics. Customers also connect their own email provider. Each provider receives only the information required for the requested operation under its own agreement with the customer.
Retention and customer control
Workspace data is retained while the workspace is active and as reasonably required for security, legal obligations, and reliable service operation. Suppression and unsubscribe records may be kept to prevent future unwanted sends.
Workspace owners can update operational data in the product and may request access, correction, export, or deletion through Wepy Support.
Privacy contact
Privacy requests can be sent to privacy@wepy.ai. Identity or workspace ownership may be verified before a request is completed.