Answers about how Jurfi works, what stays local in the browser, how document text is assembled, and where legal review is still required.
SupportPractical answers about local drafting, exports, static deployment, and review expectations.
FAQ
Practical answers about local drafting, exports, static deployment, and review expectations.
Context
What this page covers
This FAQ focuses on the real operating model of Jurfi: local browser drafts, typed templates, static content pages, and export workflows designed for review rather than instant publication.
It is here to reduce ambiguity before you rely on the generator for a launch, a compliance sprint, or a content handoff to legal counsel.
Context
Who should read it
This page is useful for SaaS teams, app publishers, store operators, creators, agencies, and site owners who want to understand what the product automates well and what still needs judgment.
It is especially relevant if you plan to deploy Jurfi on static hosting, work in English, Russian, German, Spanish, Portuguese, or French, or use the exported text as the first step in a legal review pipeline.
Guidance
Frequently asked questions
Does Jurfi use AI or an external API to generate document text?
No. The primary generation flow is deterministic and template-based. Jurfi assembles document sections from local definitions, conditions, and the answers entered in the form.
Are my drafts stored on Jurfi servers?
Not by default. The generator stores drafts in local browser storage on your device, separated by locale and document type. You control when text is copied or exported.
Can Jurfi be deployed on static hosting?
Yes. The site is structured for static export, with pre-rendered content pages and a browser-side drafting experience layered on top.
Does Jurfi replace a lawyer?
No. Jurfi is a serious drafting tool, not a substitute for legal advice. Final sufficiency still depends on your market, business model, and counsel review.
Which export formats are available?
Jurfi supports HTML, Markdown, and plain-text exports so teams can move the draft into review, publishing, or internal documentation workflows.
Can I work in English, Russian, German, Spanish, Portuguese, and French?
Yes. Jurfi ships with localized content and pages in English, Russian, German, Spanish, Portuguese, and French.
What should I verify before publishing a generated document?
Confirm the actual business facts, tools, jurisdictions, payment flows, data practices, and operational edge cases that apply to the product. The generator gives structure, but publication still requires review.
Can I share the generated text with a legal or compliance team?
Yes. That is one of the main workflows the product is designed for. Export the draft, annotate business specifics where needed, and route it through review before publishing.
Network
Related pages
Popular use cases
Document catalog
Browse practical legal templates by collection, category, and use case, then open the right generator with the right context already in place.
Document packs
Start from curated packs that group the most useful neighboring documents for launches, client work, money matters, rental scenarios, and other repeatable workflows.
Collection
Web, app, and digital policies
Privacy policies, terms, offers, cookie notices, disclaimers, and other public-facing legal documents for websites, apps, SaaS, and online stores.
Collection
Commercial and business agreements
Supply, sales, agency, licensing, assignment, partnership, and other business agreements built around commercial transactions and operating relationships.
Collection
Services, freelance, and work
Client services, consulting, freelance work, subcontracting, statements of work, hiring documents, and other practical work arrangements.
Collection
Letters, notices, and requests
Formal letters, complaints, demands, requests, authorizations, notices, and other short documents used to communicate or document a position clearly.