Privacy at a glance
The detail below separates ordinary delivery of a web page from optional work you choose to save, copy, export, or send.
| Activity | Information involved | Where it is handled | Your control |
|---|---|---|---|
| Read a page | Requested address, IP address and ordinary connection headers | The browser and the selected web host; host-specific logging remains to be documented | Choose whether to visit; contact the operator about host-held information |
| Generate or compare names | Chosen tool, naming settings, motif, seed and exclusion terms | JavaScript in the browser; no live AI request | Change or reset fields; close the page to end the current session |
| Save a draft | Name, creative notes and saved generation settings | Optional localStorage in this browser under pineapple-delivery.notebook.v1 | Remove individual entries, clear the notebook, or clear browser site data |
| Copy or export | The name or report that you choose to copy or download | Your clipboard or a local text file | Review recipients; manage clipboard history and downloaded copies separately |
| Send a question or report | Your sender address, message and any attachments you choose | Your email application and the operator’s Gmail mailbox after you send | Review the draft first; request access, correction or deletion of relevant correspondence |
| Advertising or analytics | No active advertising or analytics collection in this version | No advertising tags, analytics scripts or third-party tracking pixels are supplied | No advertising acceptance is required to use the current naming tools |
1. Scope and responsible contact
This policy describes the Pineapple Delivery website at pineappledelivery.me and the features supplied in this version. Drafitlem operates the website and is the contact for privacy matters at hopkinsuxgqoe@gmail.com. Postal contact address: No. 16 Wenchang West Road, Hanjiang District, Yangzhou, Jiangsu, China. External sites and your email provider have their own policies. This notice describes the implementation; it does not claim that a particular privacy law applies to every visitor or that all legal requirements have been independently audited.
2. A normal page visit
Your browser sends the technical information needed to request a page and its local assets, which can include an IP address, requested URL, request time, browser information, and request headers such as a referring page. A hosting or delivery provider may process those requests for delivery, security, and operation. The public hosting provider, server region, access-log settings, retention period, and any international-transfer arrangements have not yet been selected or verified for this local release. Those deployment-specific details must be added before public operation. We do not invent a hosting contract or a fixed log-retention period.
3. Generator inputs and outputs
Tool selection, tone, name format, seed, and optional motif are processed by JavaScript on your device. The site does not send these fields to an AI service, maintain a server-side generation history, or use them to train a model. These statements describe the supplied code; browser extensions, your operating system, or third-party tools you choose to use may have separate behavior. Avoid entering confidential or identifying information into a creative naming field.
4. The optional local notebook
Pressing “Save name” stores the selected name, its tool label, its creative note, and the information needed to identify the entry in localStorage under the key pineapple-delivery.notebook.v1. Storage occurs when you choose to save, not just by opening a page. Entries remain until you remove them, clear the notebook, clear site data, or your browser removes the data. They are specific to that browser and origin and are not synced by this website. On a shared device, another person using the same browser profile may be able to read them.
5. Deleting and exporting saved names
Use the Notebook page to remove one entry or clear all entries. The clear action asks for confirmation because it removes your locally saved list. You can also delete the site’s data through browser settings. An export creates a text file on your device and is not uploaded. Anyone who receives that file can read it; keep or share it according to the sensitivity of your project. Clearing the notebook does not delete an exported file. If storage is unavailable, the interface reports that saving is unavailable rather than pretending a name was saved.
6. Cookies and other tracking
This version sets no site cookies and contains no analytics scripts, advertising tags, tracking pixels, remote fonts, embedded video players, or social tracking widgets. Optional notebook localStorage is described above. There is no advertising-consent record because no advertising service is active. A decorative “accept all” banner would not accurately describe these features. If a future integration requires cookies, other storage, or personal-data processing, the notice and any required choice controls must be implemented for that actual integration before it runs.
7. Email and contact information
When you send an email, we receive your email address, the message contents, and any information or attachments you choose to include. Correspondence is handled using the contact Gmail mailbox and its associated service infrastructure. The contact helper opens your own email software using a mailto link; nothing is submitted by the page. Email services may process messages and technical metadata under their own terms. Read Google’s Privacy Policy for information about Google services. Please send only information needed to resolve your request.
8. Purposes and applicable legal bases
The practical purposes are to deliver the website, provide local naming and saving features you request, reply to correspondence, investigate errors or abuse, and respond to legitimate rights or legal matters. Where a legal framework requires a specific basis, the relevant basis may include providing a requested service, consent where required, a proportionate legitimate interest in operation or security, or a legal obligation. Which basis applies depends on the actual processing and jurisdiction. This wording does not authorize unrelated new uses or optional tracking without required consent.
9. Sharing and service providers
The website has no public user profiles and does not sell or rent personal information. We do not use personal information for cross-context behavioral advertising in this version. Technical hosting providers and email providers may handle data necessary for their services. We may disclose information when reasonably necessary to comply with an applicable legal requirement, address a substantiated rights or security issue, or protect legal interests. A specific public hosting provider and associated processing locations must be disclosed when selected. No visitor data is intentionally sent to a live AI model by this site.
10. Retention
Local notebook retention is controlled by your browser and your deletion choices. We keep correspondence only as long as reasonably needed for the request, related follow-up, a legitimate dispute, or an applicable obligation; no fixed universal period has been established for every message. Hosting log retention depends on the deployed provider and configuration and remains to be documented before public launch. You can ask about or request deletion of correspondence; certain records may need to be retained where an obligation or legitimate unresolved matter requires it.
11. Your choices and requests
Depending on your location and the applicable law, you may have rights to access, correct, delete, receive a portable copy of, restrict, or object to processing, withdraw consent where processing is based on it, or complain to a competent regulator. Send a focused request to hopkinsuxgqoe@gmail.com. We will consider it under applicable requirements and may ask for proportionate verification before disclosing personal information. The site does not create new legal rights or waive existing ones. Local notebook data can be managed directly without emailing us.
12. Children and sensitive information
This is a general creative resource and is not designed to collect information from children under 13. It has no accounts or public submission feature. We do not knowingly seek children’s personal information or sensitive categories of information. If you believe a child has sent personal information through correspondence, contact us so that we can evaluate and address the concern. Parents and guardians should guide the use of email and external links.
13. Security and external links
The supplied site limits third-party resources and provides security-header templates. Actual transport security and hosting access controls depend on deployment. No website or email system can guarantee complete security. External links take you to independently operated services; their requests, cookies, and policies apply when you visit them. Links are provided for context and are not a claim of endorsement or a transfer of responsibility.
14. Future advertising and policy changes
Advertising is not enabled. If Google AdSense or another provider is added, this policy must identify the actual providers, purposes, cookie or storage use, data disclosures, and applicable user choices. Necessary consent management must be deployed before relevant ad requests. The Advertising & transparency page explains these publication requirements. Material changes will be reflected here with an updated date and additional notice where required; a general update clause is not consent to a new processing purpose.
15. The operator’s address and the scope of this notice
The responsible publishing and privacy contact is Drafitlem, operating the Pineapple Delivery website. Postal contact address: No. 16 Wenchang West Road, Hanjiang District, Yangzhou, Jiangsu, China. Email: hopkinsuxgqoe@gmail.com. This address was supplied for contact purposes. It is not a claim that a separately registered company, a staffed support center, or an independently appointed data-protection officer exists. Use email for an initial request where practical, because a page link and a description can help identify the matter without sending unnecessary documents. This policy covers the website supplied at pineappledelivery.me. It does not govern a separate project in which you later use a name, the privacy choices of people who receive an exported file, or independent websites linked from an article. A browser extension, work-device administrator, operating-system service, or email application may process information under a separate relationship. We do not describe those independent services as though they were controlled by this website.
16. A closer inventory of information
There are several separate information paths, and they should not be treated as one visitor profile. A technical page request may disclose connection information to the host. A naming session contains the fields you choose in the interface. A locally saved draft contains the name and its supporting notes. A message contains only what you choose to send through email, together with ordinary email metadata. The site does not ask for your legal name, date of birth, government identification, payment card, account password, telephone number, or precise location to generate names. No purchase or account registration is offered. Do not use a motif, seed, exclusion list, or report field to store a real person’s confidential information. A neutral phrase such as “orchard-project” is usually enough to identify a creative experiment. A generated fictional character name may happen to resemble a real name; that resemblance does not mean the site has identified, investigated, or created a dossier about the real person.
17. What the browser does during a naming session
The generator reads predefined word banks and applies the choices selected in the form. Depending on the tool, those choices can include tone, genre, sound preference, name format, background, a subject-specific focus, and practical length or exclusion constraints. The calculation does not require these choices to be posted to a server. A result’s phonetic or readability notes describe a naming draft and simple visible properties; they are not a behavioral score about you. Comparing drafts within a page is part of the current working session rather than a public review system. Closing or reloading a page can discard unsaved work. Ordinary browser features, such as restoring a tab or remembering a form value, are outside the website’s notebook and may behave differently between browsers. This website does not silently submit the form to collect creative ideas, run a remote inference request, or claim that the contents have been read by a person. If you deliberately place information in an email or share an exported report, that later action is a separate information flow.
18. Exactly what an optional saved draft can contain
The notebook may retain the generated name, the tool label and route identifier, a local entry identifier, the seed, selected naming settings, the optional motif, and the creative explanation shown with the draft. Expanded tools can also save supporting scene notes, a short display form, a formal form, mechanical checks, and the generator version needed to explain the result. These are saved together so that a draft remains understandable when you return to the notebook. A local identifier distinguishes entries; it is not a visitor advertising identifier sent to a network. The website does not create an account ID or look up a saved draft by your email address. The current notebook is limited to 500 entries to keep browser storage manageable. You should not treat the notebook as a confidential vault, an encrypted document system, or a substitute for your project’s own backup. Other people with access to the same browser profile, device administration tools, or a compromised device could potentially see stored information.
19. Storage controls, private browsing, and migration
You can remove one notebook entry without clearing the rest, or choose Clear notebook and confirm the action. A browser’s site-data settings provide another route to remove localStorage for the website. Private or restricted browsing modes may reject storage, keep it only temporarily, or remove it when the private session closes. Storage limits and browser cleanup can also affect availability. If saving fails, the interface reports that outcome; it should not be interpreted as a hidden cloud save. Local storage is associated with an origin, so a local preview, the public HTTPS domain, and another browser can have separate notebooks. An address change or a move between HTTP and HTTPS does not itself transfer your drafts. Export material you wish to keep before changing devices, clearing data, or moving between environments. No automatic import, cross-device merge, background cloud synchronization, or identity-based recovery service is promised. Updating the website’s code does not give the operator remote access to a previously local notebook.
20. Clipboard, downloads, and shared files
Copy is an explicit action that asks the browser to place a selected name or report on the device clipboard. The clipboard is separate from the notebook. Your operating system, clipboard manager, remote desktop environment, or device-sync settings may retain or synchronize copied text under their own rules. Export creates a readable text file containing the drafts and associated notes that you choose to export. The website does not upload that file as part of downloading it. Deleting a saved name does not remove the corresponding clipboard entry, downloaded report, email attachment, or copy sent to someone else. Before sharing a report, review motifs, seeds, exclusion terms, and any project-specific notes it contains. A reproducibility seed is not a password, an encryption key, or proof of exclusive ownership. A person with the same data version and settings may reproduce the same names. Store downloaded reports in a location appropriate for the sensitivity of your project, and use your own device’s tools to remove copies you no longer need.
21. Contact forms, correction links, and email providers
The contact helper and any “Report this draft” control prepare a message using a mailto link. A draft may include the selected tool, seed, settings, a name, and a short explanation so that you can report a reproducible issue. You should review all of those details before sending. Merely preparing the draft is not a confirmed delivery to the operator. Your configured email software may open a local or web-based compose window, and its provider can handle the draft according to its own arrangements. Once you send, the operator receives the sender address, message, and any attachments you elected to add. Email headers can contain technical delivery information, and replies may include earlier quoted messages. The contact mailbox uses Gmail; Google’s Privacy Policy describes its own services. We do not claim that the mailbox has a specific enterprise contract, country-only storage setting, or custom retention arrangement that has not been verified. We do not add correspondents to a newsletter or a marketing list simply because they asked a question.
22. Technical hosting information that still needs confirmation
The source code can establish that naming inputs are processed locally, but source code alone cannot establish the configuration of an eventual hosting provider. A CDN, reverse proxy, firewall, web server, or hosting dashboard may record requests independently of the page’s JavaScript. Relevant details can include the provider’s identity, countries in which it processes requests, categories of access and security logs, who can access those logs, routine deletion settings, backup practices, and arrangements for incident investigation. Those facts remain to be selected and documented for the public deployment. This notice does not convert an unknown provider into a named processor or promise that it keeps no logs. A local development preview also relies on the local machine and its operating system; it is not evidence about a future public host. Before public operation, the operator must replace deployment-specific uncertainty with the actual information. If you need a specific answer about hosting or log retention, email the operator rather than assuming a standard period from a different website applies here.
23. Information we do not use for profiling
The supplied website has no advertising audience segments, purchase history, account profile, location-based recommendation service, social login, cross-site identifier, fingerprinting script, or analytics dashboard. It does not ask the browser for camera, microphone, contact-list, or precise-location access. The supplied permissions policy disables camera, microphone, and geolocation access for the site. A naming preference such as “mysterious” changes a creative word pool; it is not used to infer your beliefs, health, identity, eligibility, or personality. The rule-based ranking of name candidates is not an automated decision about employment, credit, education, insurance, housing, or another significant matter concerning a person. No personal information is intentionally sent to a live AI model by these tools. The fact that AI assistance was used to develop articles or code does not mean that a visitor’s future session is routed through that development process. If a new feature would materially change these practices, it requires a corresponding implementation and disclosure before use.
24. Retention decisions by information category
There is no single retention period that accurately describes every path. Unsaved form inputs and comparisons belong to the active page session, subject to ordinary browser restoration behavior. Saved drafts remain in localStorage until you or your browser remove them. Downloaded files and clipboard histories follow the settings and deletion choices of your device and any independent service you use. Email correspondence is retained according to the unresolved request, the need for relevant follow-up, a documented rights or legal matter, and applicable obligations; a fixed duration has not been adopted for every message. Hosting and security log retention must be confirmed with the actual deployment provider. A request to delete correspondence is considered in that context and may require retaining a limited record where necessary to address an unresolved obligation or dispute. We do not intentionally retain an entire creative project merely to remember that a bug was reported. We also do not promise that one deletion action instantly removes copies held independently by an email recipient, a legally required record keeper, or a provider’s separate backup system.
25. Access, correction, deletion, and other requests
Send a request to hopkinsuxgqoe@gmail.com, identify the website, and explain the information or earlier correspondence involved. Useful details include the approximate date of a message, the email address used, and the right you wish to exercise. You do not need to send an identity document with an initial request. If verification is necessary before disclosing information, we will seek a proportionate method suited to the request; material about other people should not be disclosed solely because someone knows an email address. Where applicable law grants access, correction, deletion, restriction, portability, objection, withdrawal of consent, an appeal, or a regulatory complaint, requests will be considered under that law and its required procedures. This site does not substitute a general support estimate for a statutory response deadline. We will explain an applicable refusal or limitation where required. There may be no centrally held notebook to provide, because the saved list is on your device. You can use the notebook’s own export and deletion controls without making an identity request.
26. Regional rights and privacy signals
The availability and scope of statutory rights depend on factors such as your location, the operator’s activities, and whether a law applies to the relevant processing. This policy does not declare automatic coverage under every privacy framework. For example, California’s official privacy resources describe rights for consumers dealing with covered businesses, including rights relating to access, correction, deletion, and certain sales or sharing. The supplied website does not sell personal information or share it for cross-context behavioral advertising, so there is no active sale or advertising-sharing feature to opt out of in this version. Browser signals such as Global Privacy Control or Do Not Track do not authorize new collection; they also do not automatically clear a local notebook or erase a previously sent email. If a future integration creates an activity subject to an opt-out signal or consent requirement, the operator must implement the applicable behavior rather than claiming the present lack of trackers satisfies that future requirement. See the California Attorney General’s CCPA information for its own explanation, and contact us about the processing at issue.
27. International access, providers, and disclosure requests
The supplied postal contact address is in China, and visitors or independent service providers may be located elsewhere. An address alone does not establish every processing location, the applicable legal basis for a transfer, or the contents of a service-provider agreement. Website delivery and email may involve cross-border infrastructure depending on the services selected. We have not verified a country-by-country hosting arrangement or announced a particular transfer safeguard for an unselected provider. Where a relevant legal framework requires a transfer mechanism, assessment, contract, or additional notice, the actual operation must be evaluated and the appropriate arrangements made. A legal or official request for information will be considered against the applicable requirements and the information actually held. We do not maintain a hidden central generation history to disclose. Where lawfully appropriate, a disclosure should be limited to relevant information rather than an entire unrelated correspondence archive. This section is an explanation of issues that depend on real operation, not a claim that a particular government request, international contract, or transfer assessment has occurred.
28. Children, parental concerns, and information sent by mistake
The resource is intended for a general creative audience rather than a child account service. It does not operate a children’s registration flow, public profile, chat room, or user-upload gallery. A statement that the site does not seek children’s information is not a substitute for duties that may arise if the operator actually learns that personal information from a child under 13 has been collected. If you are a parent or guardian with a concern, identify the relevant correspondence and describe the issue without sending additional unnecessary information about the child. The operator can assess whether information should be removed, whether further contact should stop, and whether another step is required under applicable law. The FTC’s COPPA information describes its framework. Adults should also avoid sending another person’s sensitive information as part of an ordinary correction. If you send a document to the wrong address or include confidential material by mistake, contact the operator promptly; do not assume a browser-only generator can retrieve or delete a message already handled by an independent email service.
29. Security issues, misuse, and incident communication
The site’s supplied resource policy restricts scripts, styles, images, and connections to local resources, and its templates avoid automatically running third-party embeds. Those measures reduce some unnecessary exposure but do not establish that every host, mailbox, browser, or device is secure. HTTPS, provider access controls, account security, backups, and operational monitoring must be configured for the actual deployment. Do not send passwords, authentication codes, complete browser logs, or secret client data to demonstrate a minor naming issue. For a security report, provide the affected page, a concise description, and a way to contact you; use a minimal example that avoids other visitors’ information. Acknowledging a report is not proof that a vulnerability has been verified. If a personal-data incident occurs, the operator must assess the facts and any applicable notification duties. This notice does not claim an incident has occurred, promise a nonexistent incident-response team, or replace a required notification with a general update to this page.
30. Advertising, future changes, and notice history
There are no active Google AdSense tags, advertising cookies, analytics events, remarketing audiences, affiliate identifiers, or ad-personalization controls in this release. A future advertising notice must explain the providers actually used and the real purposes, identifiers, storage technologies, recipients, and choices before applicable advertising requests occur. Google’s privacy-disclosure requirements address disclosures associated with its products, including relevant cookie and identifier use. Its consent management requirements must be reviewed for the planned integration and traffic. This policy does not say that advertising is already active or imply that a general acceptance of site terms supplies advertising consent. The current update date appears at the top of the page; material operational changes should also be recorded in the update notes. A purely editorial clarification does not silently authorize a new data use, and a future optional feature should not require you to agree to unrelated processing to keep using the current tools.