SupportSupport for document issues, output problems, technical bugs, privacy matters, and business requests.

Contact

Support for document issues, output problems, technical bugs, privacy matters, and business requests.

Contact Jurfi and Sergei Solod about document issues, generated-output problems, content corrections, technical bugs, privacy requests, licensing, or partnership questions.

Direct support

Write directly about Jurfi

Use the form for product questions, content corrections, export problems, privacy concerns, licensing conversations, or serious drafting feedback.

SupportPrivacy questionBusiness inquiry

The most useful notes mention the page, the document type or workflow, and the exact issue you want reviewed.

Please avoid passwords, unpublished legal terms, personal records, private client data, or other sensitive information.

Email

sergeissolod@gmail.com

Use this address for support, document issues, output problems, content corrections, privacy requests, licensing questions, partnerships, and business communication.

Website

https://jurfi.com

Jurfi is published at https://jurfi.com. To learn more about the developer behind the project, visit jsvar.com.

What belongs in a support request

Write when a document looks wrong, a section is confusing, the output does not match the inputs, a page contains an error, export is broken, or a workflow feels incomplete or misleading.

It is also useful to write about market-specific issues, bilingual copy corrections, privacy questions, licensing, partnerships, or serious product feedback from real use.

What helps resolve an issue quickly

Include the locale, page path, document type, and what you expected to happen.

If relevant, include the key inputs, the output you received, short reproduction steps, and whether the problem is repeatable.

If the issue is in the generated draft

Mention which document you generated, which section looks wrong, and whether the issue is about wording, structure, missing logic, market fit, or a factual mismatch.

If the problem depends on country, business model, product type, or a personal-use scenario, include that context so the draft can be checked more accurately.

If the issue is technical or export-related

If the problem concerns export, browser behavior, local draft storage, preview rendering, or another technical step, mention the device, browser, and where the issue appeared.

That makes it easier to separate UI issues from template logic, content problems, and environment-specific bugs.

Privacy, licensing, and business requests

If your message is about privacy, licensing, commercial use, attribution, copyright, trademarks, or partnership, say that clearly in the subject line.

That makes the request easier to route and review in the right context.

Developer

Jurfi was created by Sergei Solod, an independent developer who likes building practical browser-first products.

You can write directly to sergeissolod@gmail.com, and you can learn more about his professional background at jsvar.com.

Related pages

Popular use cases