SupportLocal-first drafting, clear limits on what the product needs to store, and transparent expectations around exports and support.

Privacy Policy

Local-first drafting, clear limits on what the product needs to store, and transparent expectations around exports and support.

How Jurfi handles browser-side draft data, local storage, exports, optional analytics integrations, support requests, and privacy-related contact paths.

1. Scope

This Privacy Policy applies to visitors and users of Jurfi and to the pages, generator flows, and support channels connected to the product.

For privacy-related requests or questions about this policy, contact sergeissolod@gmail.com.

2. How Jurfi works

Jurfi uses local templates and conditional rules in the browser to assemble document drafts. The core output is not generated by a remote AI model or external text-generation API.

That local-first architecture reduces the amount of draft data the product needs to send anywhere just to prepare the initial document text.

3. Draft inputs and local storage

Generator answers may be stored in local browser storage on your device so you can revisit a draft by locale and document type.

If you clear browser storage, switch devices, or use restrictive browsing modes, those locally stored drafts may disappear.

4. Exports, copies, and publication

When you copy or export document text, you intentionally move that content outside the browser workspace. From that point forward, the privacy and security of the exported text depends on where you store it, who receives it, and which systems handle it next.

You should avoid exporting or sharing sensitive production details unless the receiving workflow is appropriate for that information.

5. Accounts and mandatory submissions

Jurfi does not require user accounts for the core drafting flow shown on the public site.

The product also does not need you to submit a completed questionnaire to a remote text engine in order to generate the base legal document draft.

6. Analytics, hosting, and technical data

Like most web products, Jurfi may rely on hosting, CDN, log processing, and similar infrastructure that can receive technical request data such as IP address, user agent, requested path, and basic performance information.

A deployment may also enable analytics or event tracking for page views and generator interactions. If such tooling is active, related providers may process technical and usage data under their own terms and controls.

7. Cookies and browser-side identifiers

Jurfi may use browser storage or similar client-side mechanisms to preserve local drafts, preferences, or limited product state.

If analytics or consent tooling is added to a deployment, cookies or comparable identifiers may also be used for those features.

8. Support requests and communications

If you email us, we may process the information you choose to include in order to respond, investigate an issue, or improve the product.

Please avoid sending confidential data that is unnecessary for support unless the situation clearly requires it.

9. Your rights and choices

Depending on the law that applies to you, you may have rights to request access, correction, deletion, restriction, or additional information about personal data that we control.

Because locally stored drafts may never leave your browser, we may not be able to retrieve that local content for you if it was never transmitted to us.

10. Changes to this policy

We may update this policy from time to time as the product, infrastructure, or legal requirements change. Last updated: 2026-04-03.

The version published on this page is the current reference version for the site.

Related pages

Popular use cases