Privacy policy
Know where your creative work goes, what stays in this browser, and what must be configured before public launch.
Prelaunch draft · Updated November 2, 2026. Production services and legal review are pending. This is not yet a finalized legal notice.
1. Scope and current release
This policy describes the local development edition of Midsummer Fruit, intended for midsummerfruit.com. It covers naming tools, editorial stories, browser-local projects, favorites, history and character scenes. It does not describe third-party sites reached through links. Updated November 2, 2026.
Midsummer Fruit is operated by Jousten, based in China. Contact email: livesjon01@gmail.com. Postal address: Room 2705, Building A, Shidai Building, Louxing District, Loudi, Hunan, China.
The intended age audience remains to be confirmed. This policy must be reviewed against the actual production setup before public launch; provider, retention and applicable rights details remain pending.
2. Information stored in your browser
When you generate names, the application can keep up to 300 history entries. Favorites are limited to 500, saved character cards to 300, and projects to 30, with up to 12 roster members per project. Projects may contain the title, genre, world notes, era, cultural setting, style, roles, family groups, organizations, chosen names and lock states. Saved scenes include perspective, relationship choice, character desire, events and addresses.
This information is stored under the localStorage key midsummer-fruit:v1 in the browser you use. It is not uploaded by the current rule-based tools. It is not shared between devices, browser profiles or different website origins. Other people who can use your browser profile may be able to read it. Private browsing, storage limits, browser resets and clearing site data can remove it.
3. Why the local data is used
Local data supports the features you choose: remembering a shortlist, reopening a character scene, keeping a cast consistent and exporting your work. A generated history entry is saved automatically after generation; a favorite or character card requires your action. Unselected private scenes are held in the current page state and disappear when that state is discarded.
We do not use character notes, unpublished story text or private names for an advertising profile, public page, analytics event or model training pipeline in this edition. The application does not send localStorage contents to its server. This statement covers application behavior; it is not a claim that a future hosting provider never processes technical connection data.
4. Requests, technical data and logs
Opening a page sends a normal request to the server providing it. A production host may receive an IP address, browser headers, request path, time and technical error information. Production hosting, access-log retention, processor identities and transfer locations are not yet selected and must be documented before launch.
The application has no analytics SDK, session recording, tracking pixel or marketing event pipeline. Private project text is not placed in query strings, canonical URLs, structured data or public page content. This static edition has no AI endpoint or application-server rate-limit counters. Operators must not add private content to hosting logs or error reporting.
5. Optional AI processing
The current user interface uses local rules and does not call an AI service. This static edition does not provide an AI endpoint and cannot enable one through a hosting environment variable. Any future AI feature would require a separate backend and a reviewed user opt-in flow. No API key is delivered to the browser.
If AI is enabled in a future public release, the interface must identify the provider and what is sent before a user opts in. Relevant provider terms, retention, training practices, locations, processing roles and deletion routes must be reviewed and recorded first. Sending unpublished material to that future service would be a separate choice; it is not implied by using a local generator.
7. Advertising and future monetization
No AdSense publisher ID, ad unit, Google ad script or advertising measurement service is installed in this edition. No claim is made that Google has approved the site. Editorial stories, tool buttons and future ad placements must remain distinguishable.
If advertising is introduced, this policy must identify the providers, cookies or identifiers, purposes, sharing and applicable choices. The operator must implement Google’s then-current consent requirements, including an appropriately certified CMP where required, before sending relevant ad requests. Consent withdrawal and applicable opt-out controls must work. Non-personalized advertising must not be described as necessarily free of all storage or disclosure obligations.
9. Retention, export and deletion
Local records remain until you remove them, overwrite them through a backup import, reach a bounded history limit, or your browser removes them. The application does not set a timed expiration for favorites, cards or projects. A new history entry can displace an older one when the limit is reached.
My library provides a full JSON backup, CSV or text exports and a confirmed Clear all local data action. Clearing removes this application’s storage key, including projects, favorites, history and cards. It does not delete files you downloaded, text you copied, records held by an external service you independently used, or infrastructure logs. A removed local record cannot be restored without your backup.
10. Imported backups and security
Import accepts a versioned JSON backup up to 2 MB, validates bounded field types and record counts, and asks before replacing existing local data. Imported strings are rendered as text rather than HTML. CSV export protects leading spreadsheet-formula characters, but you should still handle unknown files carefully.
Do not store passwords, payment data, identity documents or highly sensitive personal information in story notes. Local storage is not a secure vault and is not encrypted by this app. No system can promise perfect security; the operator must configure HTTPS, appropriate response headers, dependency maintenance and incident procedures for production.
11. Privacy choices and requests
You can use the local tools without an account, decline to save cards, remove favorites, export data or clear all local data. The operator cannot retrieve local-only projects from the server or delete a file already on your device. Browser controls can block or clear site storage, which may prevent persistence.
Privacy rights and the applicable lawful bases, notice details and complaint routes depend on the operator’s jurisdiction, audience and actual processing. Before launch, the policy must describe applicable access, correction, deletion, objection, portability, restriction, consent withdrawal and complaint rights, how to submit a request, and how identity is verified proportionately. This draft does not waive statutory rights or assert that every right applies everywhere.
12. Children and age audience
The intended age audience has not been confirmed. This development edition is not presented as a children’s service and includes no child profiles, age verification or parental-consent workflow. The operator must decide the audience before public release and assess whether child-specific rules and content controls apply.
Do not submit a child’s identifying information in character notes. If the future service learns that it has collected data in a way that requires parental consent or another safeguard, its response must follow the applicable law and the published contact procedure.
13. International processing and legal disclosures
Local-only records remain in the browser unless you export or transmit them yourself. Page delivery from a future host, support correspondence and any optional external processing may involve other countries. No production transfer arrangement or safeguard is claimed before the providers and operator are known.
The production policy must identify applicable international-transfer safeguards, mandatory disclosures and any legal-request procedure consistent with actual practice. Technical logs should be minimized and retained only for documented purposes.
14. Changes and how to contact us
Material feature changes, such as cloud sync, accounts, analytics, advertising or AI, require a fresh data-flow review and an updated notice before activation. The date at the top identifies this draft. Changes requiring consent must not be treated as accepted merely because an old local project still exists.
Privacy requests can be sent to the email listed above or on the Contact page. Public release remains subject to completion of the provider inventory, retention details, audience assessment and applicable rights review.