Support email
Email [email protected] for support. We aim to reply within 2 business days for normal product questions and sooner for breakage that affects core document workflows.
Support is best-effort. There is no enterprise SLA at this stage, but actionable bug reports are reviewed and prioritized during active product development.
Best categories to contact us about
Contact is most useful when the message fits a clear category. That helps us route the issue and decide whether the next action is a bug fix, content update, or product clarification.
- Bug reports: broken export, invalid output, crash, or console/runtime failure
- Feature requests: missing workflow, quality improvement, batch action, or UI improvement
- Privacy questions: analytics, cookies, storage, local processing, or offline behavior
- Business and partnerships: licensing, integrations, acquisition, or collaboration inquiries
How to report a bug well
A useful bug report includes the exact page URL, browser name and version, device type, whether the issue happened online or offline, the file type involved, and the final error message if one was shown. If the file is private, describe the pattern rather than sending the original document.
Strong examples: “Compress PDF increases file size on scanned 40-page invoices in Safari 17 on iPhone 15” or “PDF to DOCX drops table borders on a two-column invoice PDF created from Excel.” Weak examples: “tool not working.”
Privacy and data requests
Privacy questions are handled through the same support inbox. If your question is about local processing, optional analytics, consent behavior, or how cached assets work for the offline app, say that directly in the subject line so the request can be handled appropriately.