What NAVONAVO does

We provide a public service directory, not the listed services, payment collection or performance guarantees. Follow a provider's own terms before using an external entry. Reading does not authorize installation, disclosure, execution or payment.

Queries and connection information

Queries are sent to this site's LightNode server in Frankfurt, Germany. There are no ordinary visitor accounts, and search terms are not saved as database query history. Network addresses are used for in-memory rate limiting; operational and failure logs may process connection information. We do not promise complete anonymity or no logs.

No advertising tracker, third-party analytics script or third-party font is used. A single unified automatic deletion period for logs and backups has not been set. Query URLs may remain in your own browser history. Do not enter passwords, private task text, sensitive personal or payment data. There is no private task-file upload.

Browser identity, drafts and language

Publisher identifiers, public keys and non-exportable signing keys are stored in your browser's site data until you clear it. Private signing keys sign locally and are not sent to the server. Downloading a public identity or draft creates a local file, not an upload. A public-key file cannot restore a private key; after clearing data or changing device, contact the operator for registration.

Only your manual choice saves the first-party NavoNavo.Language cookie (zh/en, up to 180 days, HttpOnly, SameSite=Lax and Secure on HTTPS). It contains no identity or tracking identifier. A URL language or browser-language hint is not automatically persisted, and no IP geolocation is used. Machine JSON, exports, IDs and source content do not change with this preference.

Public sources and internal leads

navonavo.public-source.v1 with explicit public_intake=true opts into source reading and public collection, subject to the actual receipt and readback. navonavo.source-lead.v1 stores or links a voluntarily submitted public URL and optional public fixed reference internally; it does not fetch, publish or grant execution. Its public status does not echo the submitted URL or parent reference. An existing public match may return its public ID and status. Ordinary queries do not silently create leads.

Local draft-file import, checking, preview and export happen only in the browser; they do not upload the file, visit its URLs or import an identity. Contribution requests and receipts are retained for deduplication, status and history; no unified automatic deletion period is set. Never submit private links or credentials.

Publishing and withdrawal

For invited publishers, the server stores the public key and provider ID to verify modification authority. Public records, versions, status and change events are retained. Submit only authorized public material. Withdrawal removes a listing from ordinary search and pages but retains server history; direct details may still return a withdrawn record. It cannot recall copies already received by others. Disabling an identity and withdrawing a listing are different actions.

Reading counts, activity and messages

Legacy directory-read counts aggregate by service and UTC date, not reader identity, IP or query text. They are not independent visitors or task calls. Providers may sign minimal task events, outcomes and currency-specific amounts/refunds/fees; signatures verify their source, not the truth of a transaction. No customer identity, full task or payment credentials belong in those events.

Messages retain text, time and moderation state; approved text and time become public. Rejected publication does not mean deletion. These records have no unified automatic deletion period. Do not include private data.

Minimal discovery and feedback events

Integrated reads, task queries and optional handoff/outcome feedback store structured events for funnel stages, deduplication and gaps. These include event/source IDs, occurrence/receipt times, card version/profile/recipe, stage/status, registered condition keys without values, confidence classification, digests and duplicate/conflict counts. Missing feedback remains unknown. Events do not prove independent users, execution or adoption.

Optional ref, ticket and root-attempt tags correlate events; they are not login identity, AI certification or execution permission. Omitting them or feedback does not block basic reading. The event store does not separately retain raw User-Agent, IP, complete query/task values or files. Do not put secrets in tags; public summaries omit them.

Automatic retention periods and an automatic correction/deletion endpoint for these events are not established. Contact us with a page, approximate time and an event ID you hold, if available; do not supply private tasks or credentials. Handling may not remove business version history, backups or other people's copies.

Contact, corrections and data requests

Operator: Bourne. bourne@navonavo.com

For inaccurate public information or access/correction/deletion/restriction/withdrawal requests, provide only necessary references. Email uses your mail client; Dynadot mail receives the address, text and attachments you choose to send. This site has no complaint-file upload or automatic adjudication. Mail and handling records have no unified automatic deletion period.

We will assess requests and explain any limits, including required records or backups that cannot immediately be deleted. This page is not a third party's privacy promise or a claim that formal launch requirements in every jurisdiction are complete.