Privacy policy

Effective date: October 28, 2026. This policy describes the supplied version of Grape trellis. It currently contains no advertising scripts, analytics services, tracking pixels, account registration, or payment processing.

1. Who is responsible for this site

Grape trellis is published by Kaissr at grapetrellis.me. For privacy questions or requests concerning correspondence sent to us, email kaiy00432@gmail.com with “Privacy request” in the subject. Postal address: No. 18 Xiyu Street, Jinyuan District, Wanbailin District, Taiyuan, Shanxi, China. We do not list an invented office or claim a legal establishment in a country that has not been confirmed.

2. Website delivery and technical information

Your browser must request files from the server or content delivery service hosting this site. Those requests necessarily reveal technical information such as an IP address, requested URL, request time, and browser-provided headers to that service. The hosting provider may keep access or security logs according to its configuration and terms. The application itself does not create a visitor analytics database.

A production hosting provider and its logging settings have not been identified in this source edition. We therefore cannot truthfully specify a provider, server country, or fixed log retention period. These details must be confirmed and this section updated when production hosting is selected. For questions about a live deployment, contact the publisher rather than assuming that no infrastructure logs exist.

3. The name generator

Generator controls, word combinations, and seed calculations run in your browser using files delivered with the site. The application does not upload your seed, selected style, generated results, or shortlist to a naming service or AI API. Do not enter private information in a seed; it is a creative reference field and is not a password or secure identifier. A seed can be included in text you choose to share with someone else.

4. Saved names and browser storage

When you explicitly save a name, the site uses your browser’s localStorage under the key grape-trellis-saved-v1. Each entry contains the saved name, associated tool, and creation time. Storage persists in that browser profile until you remove an entry, clear the shortlist, clear site data, or the browser removes it. The site does not synchronize this list across devices or send it to the publisher.

You can remove individual entries or use “Clear saved names” on the saved names page. Clearing site storage through your browser also removes the list. Other people using the same browser profile may be able to see it. Private browsing and storage restrictions may prevent saving. Export a local text copy if you need to retain your work; the site does not provide recovery or cloud backup.

5. Clipboard and downloads

Copy buttons ask your browser to write the selected text to your clipboard after you activate them. The site does not read your clipboard. Export buttons create a plain-text file locally from your saved list. They do not upload that file. Your device and browser control the resulting clipboard and downloaded file.

6. Email correspondence

The contact form prepares a mailto: draft in your own email app. Nothing is sent by the website form itself. If you send the message, we receive the sender address, message text, and any information you choose to include. Email is processed through the providers used by you and by the recipient; the published contact address is a Gmail address. Provider terms and privacy practices apply to their handling of email.

We use correspondence to understand and respond to inquiries, investigate corrections or rights concerns, and maintain necessary records of those exchanges. We have not established a fixed retention schedule in this source edition. Please ask about a specific message if you want information about its handling or deletion. We may need to retain limited correspondence to resolve a dispute or meet an applicable obligation.

7. Cookies, analytics, and third-party resources

This edition does not set application cookies or load analytics, ad tags, third-party fonts, embedded media, social widgets, or external image services. Fonts, scripts, styles, and PNG assets are delivered with the site. Local saved-name storage is described separately above. A hosting provider could introduce delivery or security cookies; its actual production behavior must be checked before making broader claims about a live site.

Ordinary links to other websites do not embed those services here. If you follow a link, the destination receives a request and handles information under its own policy. Review that policy before providing information.

8. Advertising and any future Google AdSense integration

No Google AdSense code is active in this edition, and we do not claim an approved AdSense account. If advertising is introduced, this policy must first be updated to identify the actual providers, information collected, purposes, relevant choices, and any required consent controls. Advertising providers may use cookies, web beacons, IP addresses, or similar technologies to collect information as a result of ad serving. If Google ads are introduced, Google and its partners may use advertising cookies to serve ads based on visits to this or other websites.

Information about Google’s handling of partner-site information is available at Google’s partner-sites privacy information. Google’s personalized advertising choices are available through My Ad Center. These links are information about possible future services; visiting this site currently does not activate Google advertising.

Before serving personalized Google ads in the EEA, the UK, or Switzerland, the publisher must implement a Google-certified consent management platform integrated with the applicable Transparency and Consent Framework, in accordance with Google’s requirements. Any applicable consent, withdrawal, and regional privacy choices must operate before the corresponding processing begins. A decorative cookie banner alone does not implement those requirements.

9. Sharing, sale, and international handling

The site application does not sell saved names or build advertising profiles. We do not provide your local shortlist to data brokers. Website delivery and email handling involve the providers described above, and those providers may process information in countries different from yours. We have not verified a production provider’s locations or contractual safeguards and do not invent them here. Information may also need to be disclosed where an applicable legal requirement requires it or where necessary to handle a substantiated security or rights matter.

10. Your choices and requests

Delete local names directly in your browser or on the saved names page. For email correspondence, contact kaiy00432@gmail.com and identify the messages or request sufficiently for us to locate them. Depending on applicable law and circumstances, you may have rights to access, correct, delete, restrict, object to, or receive certain personal information, withdraw consent where processing relies on it, or complain to an appropriate supervisory authority. We do not promise identical rights in every jurisdiction or ask for identity documents unless a proportionate verification need arises.

This edition does not track users across websites and does not use advertising cookies. Browser signals such as Do Not Track or Global Privacy Control do not change the generator’s local operation. If future processing requires a response to such signals, its implementation and disclosures must be updated before release.

11. Children and sensitive information

This is a general-audience creative writing resource, not a service directed specifically to children under 13. It has no public posting, profiles, or account messaging. Please do not send children’s personal information or sensitive personal information through email. If you believe such information has been sent, contact the publisher so the matter can be reviewed.

12. Security and changes

Local operation reduces the information this application needs to transmit, but no website, browser profile, or email system can promise absolute security. Use a device you trust, avoid private information in generated content, and keep local exports secure. Material changes to this policy will be published here with an updated effective date. Where required, additional notice or consent must be provided before a changed practice begins.

13. A feature-by-feature privacy explanation

Searching and filtering the directory

The search box filters the tool cards already present on the page. It does not submit the query to a search provider or create a search history in an application account. Selecting a category changes which local cards are displayed. Ordinary page requests for a tool or guide still go to the hosting service, so a requested URL can appear in that service’s technical records. A local search term is not appended to the URL by this edition. Do not assume that a hosting provider’s access records contain the content of an interaction that the application never sends.

Advanced naming controls

The generator’s word-bank direction, name structure, sound preference, result count, anchor phrase, anchor position, required initial, maximum character count, exclusion fragments, variety setting, and seed are handled in browser memory. Changing a control does not send it to an outside naming service. An anchor phrase should be a creative word rather than a person’s private information. Exclusion fragments are editing constraints, not a confidential-information protection system. A reproducible seed is convenient for collaboration but is not encrypted, secret, or guaranteed unique.

Comparing a batch

The comparison desk keeps up to three selected names from the current batch in page memory. It displays visible properties such as construction parts, character count, word count, and an example sentence. It does not create an assessment of the visitor, a behavioral profile, or a scientifically validated score. A new generated batch resets that comparison. Leaving or reloading the page may remove the current batch and comparison unless you separately save or export what you need. The publisher has no remote comparison history to retrieve.

Copying or exporting a full brief

A batch export includes the selected tool, generation settings, seed, generated names, construction notes, and example sentences. This is different from the saved-name export, which contains the local shortlist and tool references. Review an exported brief before sharing it, especially if you entered a personal phrase as an anchor or seed. The website creates the file locally, but your operating system, cloud-backed download folder, backup software, or later sharing choices can handle the file elsewhere under their own settings. This policy does not control those separate services.

14. What a privacy request can and cannot locate

If you ask for information about email correspondence, provide the sender address you used, an approximate date, and a subject or short description sufficient to identify the exchange. We may need to clarify an ambiguous request or verify that it concerns your own information. We do not need a complete browser export to locate a message. Please do not send sensitive identification material preemptively. If verification becomes necessary, the request should be proportionate to the information and circumstances.

A request about a local shortlist works differently. The application does not hold a server copy, account identifier, or backup of that list. You can view and remove it in the browser profile where it was saved. If browser data has been cleared, a publisher-side search cannot reconstruct information we never received. If you exported a text file or copied names elsewhere, those copies need to be handled in the place you saved them. Removing a shortlist entry does not delete a downloaded file, an email attachment, or a copy you sent to another person.

For infrastructure records, the answer depends on the actual production provider and its configuration. The supplied source does not establish a universal log-retention rule. Contact the publisher with the relevant date and page if you have a specific concern. We cannot truthfully promise that all provider records can be individually located, amended, or erased on request, nor that no record exists. Applicable obligations and technical circumstances determine what action is available. Confirmed production information should replace the pending hosting disclosure when the service is selected.

15. Shared devices, private sessions, and recovery

Browser storage belongs to a browser profile, not necessarily to one person. A family member, coworker, or other person using the same profile may see saved names. Use a profile and device appropriate to the material you are creating. The site does not add a password lock around localStorage. An exported file may remain in a downloads folder after the browser list is cleared. A clipboard copy may remain available to other applications according to the device’s clipboard settings. These are reasons to avoid using the naming tool as storage for confidential material.

A private browsing session may keep data only temporarily, and storage policies differ between browsers. Disabling storage can prevent saves while leaving generation and article reading available. Storage space can also be exhausted or removed by browser cleanup. The interface reports a save failure when the browser rejects the write; it should not imply that the publisher has created an online copy. If a shortlist matters to an ongoing project, export a copy and store it somewhere you control. We cannot guarantee recovery of local data from a device, a removed profile, or a damaged browser store.

16. Third-party links and optional future features

The site links to official policy information and other ordinary destinations where relevant. Following an external link takes you to a service outside this application. The destination can receive technical request information and may use cookies, accounts, or other features under its own terms. A link to Google’s privacy information does not mean the current page embeds Google advertising. A contact link opens an email draft; it does not make your email provider part of the generator. Evaluate the destination’s actual behavior before providing personal information there.

If an account system, newsletter, public comments, embedded media, analytics, payments, or advertising is added later, that is a change in processing rather than a feature silently covered by every sentence of this policy. The publisher must identify what information is involved, why it is needed, which service providers receive it, how long it is kept where known, and what choices apply. Required notices and consent must be in place before relevant processing begins. The supplied version does not claim to implement those future systems, and a disclosure alone would not configure them.

17. Responsible reporting and further questions

If you find a technical problem that appears to expose information, contact the publisher with a concise description and the affected URL. Do not gather other people’s information or submit sensitive data merely to demonstrate a problem. A report can usually begin with the behavior observed, browser, and approximate time. Avoid publicly posting private correspondence or credentials. We may ask for limited additional detail to reproduce the issue, but we will not need a visitor’s password because this edition has no visitor accounts.

For any uncertainty about these explanations, email kaiy00432@gmail.com and identify the feature or passage involved. We aim to answer within the limits of the actual information held and the resources of an independent site. This policy is intended to describe the current application accurately, including what remains unconfirmed. It should not be read as a guarantee that every browser, email provider, future hosting arrangement, or legal jurisdiction handles information in exactly the same way.