Privacy Policy
This policy explains what we (Angelica Castro Tiburcio, who operates Dispatch) collect when you use Dispatch, why, and who we share it with. We collect only what Dispatch needs to work, and we do not sell your personal information.
1. What we collect
| Data | Examples | Where it comes from |
|---|---|---|
| Figma identity | Your Figma user ID | Figma, when you open the plugin |
| Device tokens | A hashed token for each plugin install (we never store the raw token) | Generated by Dispatch |
| Klaviyo connection | OAuth access and refresh tokens, Klaviyo account ID | Klaviyo, when you connect |
| Klaviyo account details | Organization name, default sender name and email, industry | Klaviyo |
| Email settings | Footer HTML, background color, email width | You |
| Design content | Image slices of your designs, including those sent for alt text | You, from your Figma file |
| Email records | For each campaign, template or flow email you send: its name, subject line, preview text, the links and alt text of each slice, the Klaviyo IDs it went to, the Figma file and layer IDs it came from, fingerprints of the design (to tell what changed later), and a log of each send, sync or update | Generated by Dispatch when you send |
| Previous flow email content | When you first link a flow email that already had content, a copy of that content, so it can be restored | Klaviyo |
| Organization and plan | Organization name, its members and owner, its plan and billing period, our payment provider's customer and subscription IDs | You and our payment provider |
| Team keys | Key and seat for each team member | Our payment provider, when you activate a key |
| Usage | Emails counted each billing period, last active date, error logs | Generated by Dispatch |
We do not collect your Figma or Klaviyo password, your payment card details, or the subscriber lists and profiles stored in your Klaviyo account. Dispatch can read list and segment names so you can target campaigns, but we do not copy subscriber data to our servers.
2. How we use it
- To run Dispatch: sign you in, connect to Klaviyo, and create the images, templates and campaigns you ask for, link and sync flow emails, and update or unschedule campaigns you scheduled with Dispatch.
- To show what changed in your design since you last sent it.
- To generate alt text when you request it.
- To manage your plan: count the emails your organization sends each billing period, enforce its limits, and report usage to our payment provider so it can bill for it.
- To keep Dispatch secure, fix bugs and prevent abuse.
- To contact you about your account, security or material changes to these policies.
We do not use your content to train AI models, and we do not use it for advertising. We only use AI providers whose API terms bar them from training their models on the content we send.
3. Legal bases (GDPR)
Where the EU or UK GDPR applies, we rely on these legal bases:
| Purpose | Legal basis |
|---|---|
| Running Dispatch: sign-in, Klaviyo connection, sending, syncing and updating emails, alt text | Performance of a contract, Art. 6(1)(b) |
| Plans, usage counting and billing | Performance of a contract, Art. 6(1)(b); legal obligations such as tax records, Art. 6(1)(c) |
| Security, abuse prevention, bug fixing | Our legitimate interest in keeping Dispatch safe and working, Art. 6(1)(f) |
| Account and policy notices | Performance of a contract and legitimate interests, Art. 6(1)(b) and (f) |
Where we rely on legitimate interests, you may object as described in Section 7.
4. Who we share it with
We share data only with service providers who help us run Dispatch, under contracts or terms that limit their use of it:
| Provider | Purpose | Data involved |
|---|---|---|
| Klaviyo | Destination for your images, templates, campaigns and flow emails; hosts your image slices | Content you send, OAuth tokens |
| Figma | Platform the plugin runs in | Figma user ID |
| Hosting and database provider | Runs our API and stores account data | All stored account data |
| AI provider | Generates alt text | Image slices you submit for alt text |
| Payment provider | Sells plans and team seats, issues team keys, bills for emails used beyond a plan's included emails; acts as merchant of record | Your organization's ID, the details you enter at checkout, team keys, and one usage event per email counted (with an internal email reference, not its content) |
The specific providers we use may change over time. Any replacement will fill the same role and receive only the data listed for it. Contact us for the current list.
Image slices are uploaded to your Klaviyo image library and served from public URLs so email clients can load them. Anyone with a link, including every recipient of your emails, can view them. Do not put confidential information in exported designs.
We may also disclose data if the law requires it, to protect our rights or users' safety, or as part of a merger, acquisition or sale of assets.
5. Security
We use encrypted connections (HTTPS), store device tokens only as SHA-256 hashes, use OAuth so we never see your Klaviyo password, and limit Klaviyo access to the scopes Dispatch needs. No system is perfectly secure, and we cannot guarantee the security of your data. If a breach affects your personal information, we will notify you as the law requires.
Reporting a vulnerability. If you find a security issue in Dispatch, email support@trydispatch.biz with the details. We'll reply within 3 business days and fix confirmed issues as a priority. Please don't disclose it publicly until it's fixed.
6. How long we keep data
| Data | Kept until |
|---|---|
| Your user record and devices | You delete your account, or 180 days with no activity. |
| Klaviyo connections, email settings and email records | They belong to your organization. We delete them when the Klaviyo account is disconnected, or when the organization is deleted: a personal organization when its only member is deleted, a team organization 30 days after its last member leaves. We revoke Dispatch's Klaviyo access first. |
| Emails counted for your plan | Kept with your organization for billing, even if the Klaviyo account is disconnected. |
| Image slices | Stored in your Klaviyo image library, not on our servers. They stay there until you delete them in Klaviyo. |
| Content sent for alt text | Not stored by us after the response. Our AI provider processes it under its own terms. |
| Logs | Up to 90 days |
We may keep limited records longer where the law requires, for example billing records held by our payment provider.
7. Your rights
Depending on where you live, including Mexico, the EU and the UK, you may have the right to access, correct, delete or export your personal information, and to object to or restrict certain processing. To make a request, email support@trydispatch.biz. We will verify your identity and respond within 30 days, or sooner if the law requires. We will not discriminate against you for exercising these rights. You may also complain to your local data protection authority.
8. Your subscribers' data
For subscriber data in your Klaviyo account, you are the data controller and are responsible for having a lawful basis and giving notices to your recipients. To the extent Dispatch processes that data, we do so only on your instructions, as your processor. Contact us if you need a data processing agreement.
9. International transfers
We are based in Mexico, and our service providers operate mainly in the United States. By using Dispatch you understand your data will be processed in both countries. Where required, we rely on appropriate safeguards such as Standard Contractual Clauses.
10. What the Figma plugin accesses
- It reads the frame you select, to preview it, and the text in a subject line and preview text table placed just above it. It sends the frame to Dispatch only when you save, schedule, link, sync or update.
- It doesn't change your designs. It saves a few hidden notes in the file, readable only by Dispatch: an ID for the file, and on each frame you send, which campaign or flow email it's linked to and what was last sent. It does not open other files or projects.
- It selects and zooms to layers only when you ask it to, for example with Select layer.
- From your Figma profile, it reads only your user ID, to link the plugin to your Dispatch account.
- It keeps its sign-in token, and which tips you've seen, in Figma's client storage on your device, which other plugins cannot access.
- It communicates only with the Dispatch backend. Links to Klaviyo, checkout or these pages open in your browser.
11. Children
Dispatch is not for anyone under 18, and we do not knowingly collect data from children.
12. Changes and contact
We will post changes here with a new effective date and give notice of material changes. Questions or requests: Angelica Castro Tiburcio, support@trydispatch.biz.
Dispatch