Last updated: September 20, 2026 · REKSIDE LLC
Who this policy covers
This policy covers people who visit Wush or use a Wush account. If you receive a campaign sent by a Wush customer, that sender decides why your contact details are used and which messages you receive. Contact the sender about their mailing list, permission to contact you, or removal from their audience.
Information you provide
When you create an account, Wush stores your name, email address, and a password hash. Your workspace can include profile preferences, an optional avatar, imported contacts and their attributes, audiences, campaign instructions, email drafts, and delivery records. When you connect an email server, Wush stores its connection settings and protected credentials so it can send the messages you approve.
How information is used
Wush uses this information to authenticate you, operate your workspace, import and organize contacts, prepare and send campaigns, report delivery results, manage billing, and protect the service against misuse. Operational and security records help diagnose failures, enforce limits, and investigate unauthorized activity.
Connected services and AI
Sending a campaign shares recipient addresses and message content with the SMTP provider you configure. When you request AI-generated drafts, campaign instructions and the contact information included in the generation request are processed by the AI provider configured for the service. Billing features use Stripe when enabled. Hosting and operational providers also process information needed to run Wush. These providers have their own privacy terms; only submit information you are authorized to share.
Cookies, preferences, and profile images
Wush uses authentication and security cookies to maintain sign-in and protect requests. Preferences may be stored in your browser. Blocking required cookies can prevent sign-in. If you choose the Gravatar profile-image option, Wush requests an image using a hash of your email address; choosing initials or uploading an image avoids that Gravatar lookup.
Email-open measurement
Campaign emails include a remote image used to record an approximate open event. Loading the image can associate an open with the campaign email. The tracking endpoint does not set cookies or store the recipient’s IP address or user agent in that event. Email applications may block, proxy, or preload images, so open reports are not proof that a person read a message. Open tracking is currently included in campaign sending without an in-app opt-out setting. Senders are responsible for appropriate notices and any required permissions.
Retention, exports, and deletion
Workspace information remains associated with your account while you use the service. Account settings provide data export and account-deletion controls. Deletion requires verification and may be blocked while billing records must be retained. Legacy provider-backed trial eligibility records may retain pseudonymous hashes and minimal grant dates for up to 24 months after collection, including after account deletion, and are then pruned when no account remains linked. These records do not retain the email address or full card details. Copies held by connected providers, recipients, backups, or operational records may follow separate retention requirements; deleting a Wush account does not recall sent email. This policy does not promise immediate deletion from every system.
Your choices and requests
You can update profile information, manage workspace records, export your account data, and request account deletion through the available account controls. Depending on your location, additional access, correction, deletion, objection, or other privacy rights may apply. Use Wush’s contact page for the available support route. If your question concerns an email campaign you received, contact the sender directly. Providers may process information in other countries; the protections and rights available depend on the applicable arrangements and law.
Security and policy updates
Wush uses account access controls and protections for stored credentials, but no service can guarantee absolute security. Keep your account and SMTP credentials private. This page may be updated as the service or its data practices change; check the date shown here when reviewing the policy.