Privacy Policy

Effective date: November 11, 2026.

Introduction

NOTELORIA values clear explanations of what happens to your information. This policy covers the invitation and message generators, browser storage, file features and email contact. Local processing, local storage and transmission to a service are different activities and are explained separately below.

The current website has no account system or server-side invitation library. Its writing and naming rules run in your browser. Requests needed to load website files still occur, so local generation does not mean visiting a website creates no network traffic.

Information We Process

Inputs and generated text

You may enter event arrangements, host or guest roles, character names, source-work titles, costume instructions, reply deadlines and other notes. JavaScript reads these values to construct names and messages on your device. Generated results can contain your details. The generator does not automatically upload inputs or results to NOTELORIA, an AI provider or another content-processing service.

Favorites, drafts and history

Generating automatically saves the first message version as history. Save Favorite and Save Draft save selected text; name candidates can also be saved as favorites. Records contain an identifier, tool identifier, text, kind and date. These are browser-local records, not server-collected invitations. Saving a draft does not preserve every input field for later restoration.

Technical information and server requests

Your browser requests HTML, CSS, JavaScript and images from the host. Delivery involves network information such as an IP address and requested URL; request headers can include browser information and a referrer subject to browser policy. The generator does not construct a separate device profile or transmit form contents through these requests. Hosting infrastructure can keep access or error logs separately from the local library.

Browser Storage and IndexedDB

Preferred storage is IndexedDB, using the database noteloria. Its records store holds saved messages and names; metadata records schema and migration information. Version 2 preserves earlier records. The All tools library view can show earlier tool records alongside current ones.

If IndexedDB is unavailable, the application tests localStorage and uses the noteloria-records key as a persistent fallback when possible. If neither is available, temporary in-page memory is used. The status area shows the storage mode. Memory-only records may disappear on reload or closing the page. Persistent browser storage can also be removed by private browsing, storage management or browser settings.

An earlier localStorage library may be migrated into IndexedDB. The original localStorage copy is deliberately retained. Storage belongs to the browser profile and site origin; a different browser, device or origin does not automatically share it. There is no account-based synchronization.

User-Generated Content

Character names, work titles, event details and private wording are treated as plain text for local generation and editing. The current application has no form upload, remote generation API or automatic publication mechanism. Importing reads a selected file in the browser rather than uploading it.

You control later sharing. Copy transfers a result to your device clipboard through the browser clipboard facility; your device or clipboard software may have separate synchronization settings. Sending copied text through email, messaging software or another website is a separate action governed by that service’s practices. Avoid unnecessary personal details, especially on shared computers.

TXT and JSON Files

Download TXT creates a file from the selected result using a browser Blob and temporary download URL. Export JSON creates a version 2 backup of all library records, including earlier tools, rather than only the visible tool. Neither download creates a server backup.

Import JSON supports versions 1 and 2, with a maximum size of 2 MB and up to 1,000 submitted records. The application validates record structure and plain-text values. Imports merge by identifier; matching identifiers trigger a replacement confirmation. Review it carefully because replacement can overwrite saved text.

Protect exported files yourself. They may contain private event details and remain in downloads, device backups or locations you copy them to after deleting website storage. Deleting website records does not delete downloaded files or messages already shared elsewhere.

Cookies and Similar Technologies

The current application does not set cookies or use sessionStorage. IndexedDB and localStorage support the library and migration described above, rather than advertising identifiers. Temporary page memory holds form values, generated versions and directory search state while a page is open.

Extensions, your device and infrastructure outside the supplied application can behave independently. Their behavior is not a generator feature. Introducing new tracking or storage requires reassessing the policy and any applicable user controls.

Third-Party Services

Current pages serve scripts, illustrations and other images from their own site paths. They use system and locally available fallback fonts, without Google Fonts requests. They do not load an external script CDN, analytics tag, advertising script or third-party character-image library. Advertising and analytics are disabled; AdSense is not integrated.

Hosting processes requests to deliver website files. The supplied Nginx example does not establish a provider-specific log retention period. Browser-local invitation records are separate from server logs and are not sent as log entries by the generator. New hosting integrations, advertising or analytics must be reviewed and the policy updated before use.

Email to gdhogdjd@gmail.com passes through your email provider and the recipient’s Gmail service, including your address, message and attachments. A mailto link opens an email application; it does not submit generator fields. Include only what is needed to explain a request.

Data Retention and Deletion

There is no application expiry timer for persistent library records. They remain until deleted or removed by browser or device behavior. Delete removes an individual record. Clear History removes history across tools while retaining drafts and favorites. Delete All Local Data clears the active records store after confirmation; it does not remove IndexedDB migration metadata or a retained legacy localStorage copy.

For complete browser-side removal, use browser site-data controls to clear storage for the NOTELORIA origin, including IndexedDB and localStorage. Export a private backup first if needed. Clearing data can remove earlier-version records too. Delete downloaded files and copies shared elsewhere separately.

Hosting-log retention depends on hosting configuration and is separate from browser controls. Contact us about server-side information or email correspondence; clearing the library removes neither. This policy does not promise a fixed log or mailbox retention period. We cannot remotely recover or erase data held only in your browser.

Rights to request access, correction or deletion, or to raise a complaint with an appropriate authority, depend on applicable law. Email us to explain a request without attaching your private library. We may need relevant context to identify information involved; do not send identity documents unless a specific, justified need has been established.

Security

The application validates plain-text inputs and backup structure and inserts library text as text content rather than executable HTML. These measures address specific risks and do not guarantee safety. Local records and downloaded files are not encrypted by the application. There is no end-to-end encrypted storage feature.

Protect your device and browser profile and keep needed backups. Device compromise, extensions, accidental sharing and storage failure can expose or lose text. No storage or communication can be promised risk-free. Actual hosting transport protections depend on deployment; local processing alone does not establish them.

Children’s Privacy

The tools concern event writing and fantasy themes. They do not request dates of birth or provide age verification, child accounts or a parental consent system. Children should involve a parent or guardian before sharing personal information or contacting us. Use fictional examples instead of children’s identifying details when reporting a problem. A parent or guardian can email a concern. No children’s privacy certification is claimed.

International Users

NOTELORIA provides English-language tools for users in different countries. Browser-local records remain under browser storage controls; website requests and email may be handled by infrastructure in other countries. Applicable rights can vary. This policy does not claim certification or legal approval in every jurisdiction.

Policy Updates

Revisions will appear at this URL with an updated effective date. Review the policy when returning to storage or sharing features, particularly if new services are introduced. The current version describes the features and integrations stated above.

Contact

For privacy questions or requests, email gdhogdjd@gmail.com. Contact Us explains how to provide helpful context without unnecessary private information. The Terms of Service explain responsibilities for using results.