How can we help?

Outlook on Windows uses Microsoft Word as its rendering engine and supports a narrower subset of HTML / CSS than other clients. eSigKit uses tables + inline CSS specifically to render correctly in Outlook 2016+. If a particular template is breaking, try the Preview pane in the dashboard's template editor — it shows a Word-engine approximation. If the issue persists, email support and include a screenshot.

Gmail caches the existing signature on each device for up to 24 hours. The new signature applies to all newly composed emails immediately, but draft messages already open continue to use the old one until refreshed. If after 24 hours the new signature still isn't appearing, check that the user is in the org's Gmail Workspace and that the Workspace OAuth integration has not been revoked.

Open the dashboard, go to Settings → Billing, and click Manage subscription. That opens the Stripe Customer Portal where you can change plan tier, update your payment method, view past invoices, or cancel.

Open the dashboard, go to Settings → Organization. Use Export data to download a full JSON archive of your org, brand, users, and templates. Use Delete organization to soft-delete the org — you have a 30-day grace window to restore before the data is permanently purged. Both actions are admin-only.

Yes — every signature is built from inline-CSS HTML tables, with image URLs hosted on our CDN. We test the rendering against Gmail (web + iOS + Android), Outlook 2016+ on Windows, Outlook Mac, Outlook 365 web, Apple Mail, and Yahoo Mail. We hold ourselves to a 30 KB render budget for Outlook safety.

Please email security@esigkit.com — do not file a public GitHub issue. We follow RFC 9116 for coordinated disclosure and offer a safe-harbor commitment for good-faith research. See the security policy for full scope and timelines.