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.
If you request beta access, Wepy also collects your name, work email, business details, selected channels and plan, intended use, and setup help preferences. We keep email verification, request decisions and onboarding progress so we can review your request and help you get started. Do not include passwords, API keys or customer contact lists in the request form.
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.
When an owner authorizes future billing, Wepy keeps the agreed plan, prices, tax, terms version, authorization time, payment-provider references and status, billing-notice records and cancellation history. Secure payment details are entered with the payment provider; Wepy does not collect or store full card numbers or card security codes.
Why the data is used
- Review access requests and arrange the setup help you requested.
- 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.
- Record owner authorization, manage subscriptions and cancellation, send transactional billing notices, reconcile payments and meet billing-record obligations. Billing notices do not subscribe you to marketing or authorize campaign sending.
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.
The configured payment provider receives the billing identity and payment instructions required to manage your authorized payment method and subscription. Our transactional email provider processes billing notices and delivery-status events. A provider accepting an email is not proof that it was delivered.
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.
Access-request details are used for application review, related service emails and assisted onboarding. Submitting a request does not subscribe you to marketing emails. You can contact Wepy Support to correct or remove your request, including before you have an account.
Workspace owners can update operational data in the product and may request access, correction, export, or deletion through Wepy Support.
Canceling future billing does not automatically erase authorization, payment, notice or cancellation records. These may be retained as required for accounting, legal obligations, dispute handling and prevention of duplicate charges. Contact Wepy Support for access, correction or deletion requests; payment-provider records are also subject to that provider's policy.
Privacy contact
Privacy requests can be sent to privacy@wepy.ai. Identity or workspace ownership may be verified before a request is completed.