01Who we are and what this covers
Wispmail is run by Swyft Media LLC, a limited liability company registered in Wyoming, USA, under the name Swyftlabs ("we", "us"). This policy covers the Wispmail app at wispmail.swyftlabs.org and the images and links it serves inside the emails our customers send. You can reach us at hello@swyftlabs.org.
There are two groups of people in this policy: customers, who have a Wispmail account, and readers, who receive an email from a customer that contains a Wispmail image or link. Sections 2 and 6 are about customers. Section 3 is about readers. If you visit our website without an account, the usage and cookie parts of sections 2 and 11 apply to you too.
02What we collect from customers
- Account details: your email address, and your name and email address from Google if you sign in with Google.
- Workspace members: the people you add to your workspace and their roles.
- What you create: widgets and their settings, brand settings, testimonials and the images you upload.
- Connection credentials: a Klaviyo private API key, webhook signing secrets and Google refresh tokens, if you set up those connections. They are stored encrypted in Supabase Vault.
- Billing: payments are handled by Polar, which is the merchant of record. We never see your card number. We keep your plan and the customer and subscription references Polar gives us.
- How you use the site and app: the pages you visit, the buttons you click, the widgets you make and publish, errors you run into, and recordings of some sessions so we can see where things get confusing. Recordings hide everything you type into form fields. We use PostHog for this (section 7).
- Basic usage and logs: how many images are drawn each month for your workspace, and technical logs needed to run and secure the service.
03Data about email readers
When an email image loads or a link is tapped, we record that it happened, which widget it belongs to, the time, the approximate country, the kind of email app (Gmail, Apple Mail, Outlook or other, worked out from the request) and a field for marking automated traffic such as link scanners. For add-to-calendar we also record which calendar the reader picked. Requests we recognise as automated, such as crawlers, link scanners and scripts, are marked so they stay out of the customer's stats and render counts. The approximate location (country and time zone) is worked out while the request is handled. The IP address is not stored by us, and neither is the time zone.
For polls and quizzes we store the answer, the time, and an optional comment on polls. We store them against a reader id: the opaque value that the customer's email platform puts in the link (for example a Klaviyo profile id). We do not receive the reader's name or email address from this. For a countdown that starts on first open, we store the subscriber ID your email platform sends and the time that countdown started. We never store an email address for it. Values placed in an image link, such as a first name on a personalized image, are used to draw the image and are not saved in our database.
Our hosting and network providers (section 7) handle IP addresses to deliver requests and may keep them in their own logs under their own policies. A reader's browser may remember the last calendar they chose on a Wispmail calendar page, using local storage on their device.
For this data the customer is the controller and we process it on their behalf. If you are a reader and have a question about your data, contact the brand that emailed you. You can also write to us and we will pass your request on. Customers who need a data processing agreement (DPA) for this data can ask us for ours.
04How we use data
We use data to run the service and draw images, show customers their stats, send answers to the destinations a customer chose, handle billing, keep the service secure, and send service emails such as sign-in links and usage notices. When you create an account you also get product and marketing emails from us about Wispmail. Each one has a link to unsubscribe, and unsubscribing doesn't affect your account or its service emails. We never share, sell or rent your email address, and we do not use personal data for advertising.
We do not sell or rent anyone's personal data. We do not use readers' data to build profiles of them, to train AI models or to make benchmark reports, and we do not combine it with other data sets.
05Legal bases
If you are in the European Economic Area, the UK or Switzerland, these are the legal bases we rely on:
- Contract: to run your account, provide Wispmail, bill you and send service emails.
- Legitimate interests: to keep the service secure and stop abuse, to understand how the site and app are used so we can improve them, and to send customers product and marketing emails, which you can stop at any time.
- Consent: for analytics cookies and session recordings, which you can accept or decline (section 12).
- Legal obligation: to keep records the law requires, such as for tax.
For readers' data, we act on the customer's behalf, and the customer decides the legal basis.
06Google user data
This section describes how Wispmail uses data it receives from Google APIs.
- Sign in with Google: we receive your name, email address and profile picture URL. We use them only to create your account and sign you in.
- Connect Google Sheets: this asks for the drive.file permission. It lets Wispmail create one spreadsheet, called "Wispmail answers", in your Google Drive, and add to it the poll and quiz answers you chose to send there. It gives us no access to any other file in your Drive. The request also asks for your Google account email address, which we keep with the connection so you can see which account is connected.
We store the Google refresh token encrypted and use it only to write those answers to that spreadsheet. We do not use Google user data for advertising. We do not sell it, and we do not transfer it to others except as needed to provide this feature, to comply with the law, or as part of a merger or sale with notice to you. No person reads Google user data unless you give consent, it is needed for security, or the law requires it.
When you remove the connection in Wispmail, we delete the stored token. You can also revoke access at any time at myaccount.google.com/permissions.
Wispmail's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
07Service providers
We use these providers to run Wispmail:
- Vercel: hosts the app.
- Supabase, self-hosted on Oracle Cloud in Dubai, United Arab Emirates: database, sign-in and background functions.
- Deno Deploy: serves the images and links in emails.
- Cloudflare: DNS, network, and Turnstile, which checks that sign-ups and log-ins come from a person.
- Polar: billing and payments, as merchant of record.
- Customer.io: sign-in, account, product and marketing emails.
- PostHog, in the United States: product analytics, error reports and session recordings for this site and the app. It is never used on the pages readers open from an email.
- Google: sign-in and Google Sheets, if you use them.
- Klaviyo and webhook receivers: only when a customer connects them. Answers are then sent to the service the customer chose.
08Where data is stored
We are based in the United States. Our database is in the United Arab Emirates, and our other providers handle data in the United States and in the countries where they run servers. These countries may not have the same data-protection laws as yours. When personal data leaves the European Economic Area, the UK or Switzerland, we rely on the Standard Contractual Clauses or the other safeguards in our providers' data processing terms, and our DPA includes the Standard Contractual Clauses for customers who need them.
09Retention
We keep customer data, and the reader data that belongs to it, while the account is active. Records of answers sent to a connected destination are deleted 30 days after they are created, or 90 days if sending failed. We delete an account and its data on request, within 30 days. Copies in our database backups are kept for up to 30 days and then expire.
10Security
Connection secrets are stored encrypted, access to customer data is limited by workspace, and traffic is sent over HTTPS. No system is perfectly secure, so we cannot promise absolute security. If a breach affects personal data, we will tell the customers affected without undue delay and give them what they need to meet their own duties.
11Your rights
You can ask us to give you access to your data, correct it, delete it or export it. Email hello@swyftlabs.org and we will reply within 30 days. If you are in the European Economic Area, the UK or another place with a data-protection authority, you can also complain to it. You can stop product and marketing emails at any time with the unsubscribe link in any of them. Readers should start with the brand that emailed them (section 3).
12Cookies
Wispmail uses the session cookies needed to keep you signed in, and PostHog's analytics cookie, which tells one visit from the next so we can count visitors and see how the site and app are used. The app also keeps a few settings in your browser's local storage, such as the email platform you picked last. We do not use advertising cookies, and no cookies are set on the pages readers open from an email.
If you are in Europe, including the EU, the UK and Switzerland, we ask first: PostHog's cookie and session recordings only start if you choose Accept. Anyone can change their choice at any time with Cookie settings at the bottom of any page. Your choice is kept in your browser's local storage.
13Children
Wispmail is not for anyone under 16, and we do not knowingly collect data from them.
14Changes
If we change this policy we will post the new version here and update the date at the top. For a significant change we will also tell customers by email.
15Contact
Swyft Media LLC (Swyftlabs), Wyoming, USA, hello@swyftlabs.org.