Privacy
Privacy policy
FieldWeft is a browser-based tool that does not require an account. It does not automatically upload your graphs to a separate application server, and the service operator has no feature for collecting or viewing their contents.
Effective date: August 21, 2026
Stored in your browser
Graphs and pages are stored in IndexedDB, while localStorage keeps lightweight preferences such as language, navigation, and canvas view settings.
Sharing is your choice
A compressed graph structure is added to a URL only when you choose to copy a share link.
1. Information processed by the service
FieldWeft itself does not request or collect registration details, names, email addresses, phone numbers, or payment information. The entities, processes, fields, node relations, field mappings, and boundaries you create remain in the current browser's local storage.
- IndexedDB: page names; entities, processes, and fields in the canonical FieldWeft v1 document; node relations and field mappings; descriptions, tags, and metadata for every target; input variants; collapsed state; and boundary names, colors, kinds, membership, and screen layout
- localStorage: the identifier of the last-opened page, language preference, Korean language-suggestion and beta-notice dismissals, page- and sample-scoped canvas view settings, and your defaults for new pages' view settings
Examples in the sample gallery are read-only documents bundled with the app. Moving nodes or changing display state while exploring a sample does not write to IndexedDB. Each sample's canvas view settings may be written separately to localStorage. Once you select Start with this sample and create an independent copy, the normal local-storage rules apply.
2. Share URLs
When you choose Copy link, the current page's complete graph is compressed into the URL's #g=d1.… fragment. A recipient can restore the entities, processes, node relations, field mappings, descriptions, tags, metadata, stable IDs, exact positions, collapsed state, boundary membership, and sizes. Page names, other pages, viewport state, page-scoped canvas view settings, and temporary selection, filter, or trace state are not included.
Fragments are not sent in web-server requests or typical Referer headers. The complete link can still remain in the browser address bar, history, clipboard, messages, and documents, and anyone who receives it can restore its contents. Do not put passwords, access tokens, real customer information, or other confidential values into a graph or share link, including names, labels, descriptions, tags, and metadata.
3. Backup and report files
An exported backup contains every page and all descriptions, tags, and metadata. Backup files, impact-analysis Markdown reports, and files selected for import are processed on your device. They are not sent to the FieldWeft operator unless you send or upload them yourself.
4. Access logs
The web server or hosting provider may process standard access-log information—such as IP address, browser details, access time, and requested path—for reliable operation and security. The actual deployment's operating policy determines the precise scope and retention period.
5. Cookies and external services
FieldWeft currently sets no first-party cookies and uses no advertising or visitor-analytics service. If a cookie-based external service such as Google AdSense is introduced later, this policy and any required consent flow will be updated before deployment.
6. Deletion and management
You can remove local graphs by deleting pages in the app or clearing this site's stored data in browser settings. The operator cannot access your browser storage to restore or delete it for you. Export important graphs before clearing browser data.
7. Questions and policy changes
For privacy questions, use the contact page. If product features or external services change the information we process, both this page and its effective date will be updated.