Privacy policy

1. Scope and responsible operator

This policy covers the Namewoven pages and tools. The responsible operator is Victorica, website namewoven.com, email victoricanave@gmail.com. The operator’s address is listed below and on the Contact page.

The present website has no account system, paid plan, advertising network, audience analytics, newsletter, remote manuscript storage or third-party AI inference service. Those services are not silently included in this policy. A future version that adds one must describe its actual processing, recipients and controls before the changed processing begins.

Developing the website with AI assistance is different from sending tool inputs to an AI model. The browser tools use explicit local rules; entering a name or excerpt does not invoke an AI API. Material you separately put into a chat, browser extension or other service is governed by that service and your own choices.

2. Information you choose to enter

Depending on the task, inputs can include names and readings, character IDs, family relationships, observer knowledge, unrevealed identities, story dates, manuscript excerpts, contributor credits, source notes, session tokens and responses. A fictional project can still contain personal information if it identifies real people, contributors or recorded participants. A field called character does not make its contents anonymous.

Calculations use these values in browser memory to generate candidates, validate constraints, compare records and explain results. Displayed text can remain in a tab until you change it or close it. The application does not intentionally submit the full worksheet to a remote processing endpoint. Use fictional identifiers where a real person’s identity is unnecessary.

Do not enter passwords, identity documents, private contact details, medical information or recordings you are not entitled to use. Ordinary creative naming does not require them. You can read guides and static examples without entering project information.

3. Favorites and saved projects

Favorites use this origin’s localStorage under namewoven.favorites.v1. A saved record can contain more than its name, including explanations, tool identity and task-specific context. Saving an item creates a local copy of creative material, not an anonymous popularity vote.

Choosing Save on device stores the current tool’s project under a key beginning namewoven.project. A project may include all worksheet parameters, hidden identities, source versions and a favorite-comparison snapshot. Saving is explicit. There is no cloud synchronization or recoverable server-side account copy.

This edition applies no automatic expiry to localStorage. Data normally remains until you remove an item, replace a saved project, clear the origin’s site data, or the browser removes it. Private browsing and storage limits can make storage temporary or unavailable. Different browser profiles, origins and ports can have separate stores; clearing one may not clear the others.

4. Source searches and network requests

Libraries load versioned dictionary or statistical files from the same origin as the website. A source-backed operation may request a manifest, shard or annual-data file. These are network requests, even though filtering and generation happen in the browser. A requested path can reveal which source or partition was needed.

Library tools do not send your search term or worksheet to SSA, the U.S. Census Bureau, EDRDG or another original data publisher. Publishers are credited for imported material. Following an external source link is a separate action that opens a destination with its own privacy practices.

The local edition serves files on your machine. Its preview server has no persistent application request-log database or input-submission endpoint. Browser software and the operating environment can maintain their own diagnostics, history or network records. A public host would involve network and hosting metadata; its providers, purposes, retention and transfer arrangements must be disclosed rather than copying this local statement unchanged.

5. Imports, audio and participant records

A selected project file is read by the browser, validated against the supported format and used to restore controls. The import control does not upload it. Validation checks structure and supported state; it does not certify the truth, safety or rights status of its contents. Keep backups and inspect files from unfamiliar sources.

Audio features access files you deliberately select for playback, duration inspection or a local listening workflow. The current tools do not upload audio for transcription, voice identification or model training. Browser access does not prevent other software on your device from accessing the original file.

Listening records may contain session tokens, protocol settings, intended and selected identities, playback state and clip metadata or content identifiers. A session token is a workflow label, not proof of anonymity to the person administering the session. Restoring a project does not restore access to an audio file; select it again when required. Exported records do not automatically include audio bytes.

6. Clipboard, downloads and sharing

Copy controls write text to your clipboard. The operating system, clipboard history, device synchronization or another application may retain it. Removing a favorite or closing the page cannot erase those independent copies.

Downloads create files in the location controlled by your browser. Project exports are private working files and may include unrevealed identities, future plot events and notes. Result downloads may include detailed traces, audit records and task-specific handoffs as well as card text. An export button’s label is not a promise of anonymization or spoiler removal.

Inspect the actual file before sending it to collaborators. An explicitly observer-scoped or public-credit output has that particular scope; other files do not automatically inherit it. Downloading is not publication by Namewoven, and the website cannot recall a file after you share it through another service.

7. Retention, correction and deletion

Remove saved favorites from the Saved page. Edit worksheet fields and save a replacement project to update that tool’s saved parameters. To comprehensively remove locally saved project data in this edition, use the browser’s site-data controls for the correct origin. This can also remove favorites; first export anything you intend to retain.

Clearing site data does not delete Downloads, backups, clipboard history, screenshots, browser history or recipients’ copies. Remove those through the relevant device or service. The operator cannot remotely erase your localStorage or retrieve a project never sent to an operator-controlled system.

Closing a page ends its live tool session, but browsers may retain tab-recovery or form state. On a shared device, use browser privacy controls and verify which copies remain. The website does not promise secure erasure or a deletion deadline for storage it does not control.

8. Cookies, analytics and advertising

The application currently sets no advertising, analytics or account cookies and embeds no tracking pixels or third-party media. It does use the explicit localStorage features described above. No advertising cookies does not mean that nothing is stored.

The application implements no sale of inputs, advertising sharing, behavioral profile or cross-site measurement, and no website analytics database from which the operator can produce a personal browsing profile. These statements concern this build, not every browser extension, hosting environment or future version.

If optional measurement or advertising is introduced, its providers, storage, purposes and available choices must be explained before use, with controls appropriate to the applicable audience. A banner alone does not authorize an undeclared tracker. Basic naming results will not depend on clicking an advertisement.

9. Security and shared-device limits

The preview server binds to the loopback address and accepts read-only page/file requests. The build restricts resources to the site origin and avoids interpreting worksheet text as executable HTML. These precautions have limited scope; they are not a security certification or a guarantee against every attack.

Do not expose the preview server publicly as a substitute for a reviewed deployment. A public host needs its own HTTPS, access, logging, update and incident-response arrangements. Keep the browser and operating system current, restrict untrusted extensions and protect confidential project files.

If you suspect exposure, stop sharing affected files and review access through the service where you shared them. When reporting a fault, use the minimum reproducible material. A short fictional fixture is preferable to an entire confidential manuscript or participant file.

10. Privacy questions, rights and children

Applicable rights and duties depend on location and actual processing. For privacy requests and concerns, contact Victorica at victoricanave@gmail.com. This statement does not declare a universal legal basis or a fixed statutory response deadline.

Depending on applicable law and context, requests may concern access, correction, deletion, portability, objection, restriction or withdrawal of a permission. Browser controls address copies stored only on your device. Email requests should identify the affected service and data; the operator cannot retrieve projects stored only in your browser.

This is a creative workbench, not a child-directed social service. The local edition has no age-verification or parental-consent system. Do not use participant sessions to gather children’s personal information without appropriate authority and safeguards. An age description alone does not establish compliance with regional child-privacy rules.

11. Changes and related information

Updated 1 November 2026 to document local storage, source shards, audio sessions and export boundaries. Changes in collection or recipients should be described before new processing starts. A revised date must not conceal a materially different data flow, and continued use will not be called consent where another valid choice is required.

Read About for the editorial model and Terms for output and source-licence limits. The UK Information Commissioner’s Right to be informed guidance is a transparency reference, not a statement that UK law necessarily governs this project or that the regulator has approved it.

12. Following a project through its data lifecycle

Typing a worksheet creates a live working state. Generating results derives another representation of those inputs; it does not automatically save a cloud project. Saving on device, adding a favorite, copying text and downloading a file each create a different copy with a different removal mechanism. Review each of those locations when you finish a confidential project.

Source-library files contain imported reference material rather than a private manuscript. The local preview sends a no-store cache instruction, but that instruction is not a command to erase browser history, tab recovery, operating-system backups or files previously downloaded. The application does not offer a secure-erasure function. A future public deployment must verify its own caching behavior rather than assuming this preview configuration applies.

A storage failure can leave a result visible without a durable saved copy. A failed clipboard operation is not confirmation that text reached your clipboard. Check the displayed outcome and keep an independent export when necessary. Moving from the preview address to a public domain will not automatically transfer local projects: any migration must be an explicit, inspected file transfer, not a promise that the operator can retrieve browser data.

13. Collaborators, indirect identification and support examples

Before a shared writing or listening session, agree which participant records are necessary, who will see them and when your team will delete its copies. Namewoven does not obtain consent on your behalf. A worksheet checkbox, an authored review, an approval ledger or a successful software check records a workflow state; it does not verify someone’s identity, authority or legal agreement.

Replacing a person’s name with a token may still leave them recognizable through a distinctive response, recording, relationship or story context. Removing direct identifiers does not establish that a file is anonymous. Keep any separate token-to-person list outside files intended for wider circulation, and inspect notes, traces and handoff fields as well as the visible result names.

If a working support channel is introduced, send a fictional reproducer wherever possible. An initial correction should not require a full manuscript, an identity document or an entire participant roster. Any later request for additional information must explain why it is needed and how it will be handled. This build has no support upload form or automatic diagnostic-report submission; it cannot truthfully promise a retention period for a future support system.

14. Browser permissions and device features

The current interface does not request your camera, microphone, location, contacts or an entire folder of files. Selecting an audio file is different from authorizing live recording. Selecting a project file gives this page the content of that chosen file; it is not a general scan of your disk. A browser may display its own permission or download prompts.

Clipboard access follows an explicit copy action and browser restrictions. Refusing a permission or file selection can prevent the corresponding action without turning it into a background upload. Review browser permissions for this origin if you want to change a prior choice. Operating-system permissions and browser extensions are managed separately from Namewoven controls.

15. Sensitive context and shared workstations

A project may expose a sensitive connection even when every displayed name is invented: a real collaborator may recognize a family history, an unpublished account or a recording. Minimize that context before entering it. Use a short fictional substitute to investigate a tool defect rather than reproducing the underlying private event.

The application provides no project password, per-person access control or encrypted vault. A person with access to the same unlocked browser profile may be able to view saved projects and favorites. Browser-local processing is not a confidentiality boundary between people sharing that profile. For confidential work, use appropriate device access controls and separately protect exports and backups.

16. Hosting, recipients and international processing

This build has no remote project database, cloud backup or configured AI recipient for worksheet inputs. There is no declared list of hosting subprocessors or overseas storage locations for a public deployment because that deployment has not been selected. We do not describe an unchosen provider as if it already processed your work.

Before public hosting or an external feature is enabled, the actual notice must explain the information sent, the recipients, their role, relevant storage locations, retention and available safeguards. A CDN request and a manuscript sent for inference are different data flows. They need to be assessed separately rather than covered by a general statement that everything stays local.

17. Generated analysis and decisions about people

Name comparisons and scores concern the authored naming task and its stated rules. The application is not designed to decide a real person’s eligibility for employment, credit, education, insurance or public services. A name match, inferred style or source frequency must not be treated as evidence of a real person’s character, ancestry or trustworthiness.

Derived records can still be sensitive. A comparison may reveal intended relationships, an author-only identity or a participant response that was not present in the visible name alone. Inspect the explanation and trace as well as the main result before saving or sharing. Deleting the original input elsewhere does not automatically remove an independently saved derived record.

18. Requests, incidents and limits of assistance

Send privacy requests to Victorica at victoricanave@gmail.com. Identify the affected service and copy without including excessive proof of identity. Responses concern data actually held by the operator; browser-only material cannot be retrieved through an operator search. Reading this notice does not submit a request.

If an export reaches the wrong person, review the recipients and sharing service, revoke access where that service supports it, and replace compromised access details if relevant. Removing a favorite does not recall an attachment. Obligations concerning any future incident must be evaluated against the real facts and applicable requirements; no universal notification deadline or completed incident-response program is claimed here.