Privacy Policy

VOLOGOLO is an independent US power-tool discovery and comparison platform in development. The protected partner DEMO uses server-validated invitation access and fictional products, offers and permanent read-only SAMPLE rankings. It does not accept public Likes or votes. Production/live mode does not publish those fictional records, and no public consumer account service is active.

There is no checkout, newsletter signup or on-site contact submission endpoint. You can voluntarily email contact@vologolo.com. This draft describes implemented behavior, not approved public hosting, operator identity or final legal practices.

If you send an email to contact@vologolo.com, your sender address, message and any attachments you choose to include are processed through Lark Mail, with contact@vologolo.com configured as a shared mailbox for its assigned member. VOLOGOLO uses the information to review and respond to your inquiry, including research corrections, feedback, privacy questions and partnership discussions.

A mailto link opens your email application; it does not automatically send a message or submit a site form. Your email provider and Lark Mail process messages under their own practices. Please send only what is needed for the inquiry, and do not include passwords, payment details or unnecessary sensitive information.

An email retention schedule and formal privacy-request handling process have not been approved for public launch. This draft does not promise a response or deletion deadline. Those practices require owner/legal review alongside the actual email-service configuration.

• Email contact@vologolo.com ↗

Catalog search and filters use GET URLs. Search terms and selections are sent to the site server to render results and may appear in browser history, bookmarks, copied links and technical request logs. Do not enter passwords, contact details or other sensitive information in search.

Serving a page requires technical request processing, including network addressing, requested paths and browser request headers. The application does not implement a persistent search-history database. This does not mean browsers, network services or a future hosting provider keep no logs.

With JavaScript, protected DEMO Saved Tools and Compare selections use browser localStorage. Only allowed product identifiers are stored in these lists, not prices, contact details or an account profile. Clearing one list preserves the other. Browser settings can remove stored data; blocked storage leaves a visible tab-only fallback, and invalid entries are ignored.

My Battery Platform stores the selected platform identifier in localStorage. Setup Builder quick save stores product identifiers and quantities. The named Saved Setups Library stores setup identifiers, user-entered names, item quantities, and created/updated timestamps; setup comparison uses those local selections. These records do not store verified prices or prove compatibility. Avoid personal or sensitive information in setup names.

DEMO and LIVE tools, preferences and setups use separate storage namespaces. The protected product-selection namespace is also separate from the legacy local DEMO selection store. The unpublished verified-product foundation uses localStorage for Saved Tools and sessionStorage for Compare. Browser-local data is not cloud-synced, an account backup or an access credential. Clearing cookies alone does not erase localStorage.

Opening Compare or a Builder prefill can include product identifiers and quantities in a GET URL. After invitation access, supported search, filters, navigation and offer sorting work without JavaScript; browser-local controls require it.

The application contains no analytics tags, advertising pixels or social SDKs. Essential invitation cookies are described below. Hosting logs, analytics or additional providers would need their own review before activation.

An authorized invitation contains a reusable bearer credential, not a verified individual or company identity. Anyone holding a forwarded link may use the grant while it remains active. The invitation opens through /preview-access; JavaScript clears its credential fragment from the address before a same-origin session exchange. Do not forward private access links without authorization.

The server checks the credential against an active grant registry containing credential hashes and any configured expiry. It sets an essential host-only HttpOnly, SameSite=Strict cookie so protected pages and media can validate access. The cookie is Secure on HTTPS; the explicit local HTTP QA mode has a loopback-only exception. Its seven-day browser lifetime is not a universal access duration: configured grant expiry or revocation can end access sooner, and a grant without an expiry remains subject to revocation.

Protected page and media requests recheck the current grant. Removing a cookie does not revoke the grant or erase browser-local planning data; revocation cannot retrieve pages or images already downloaded. This DEMO has no active voting datastore or automated erasure service. Public voting, accounts and any future retention/deletion process require separate review.

Following an external source link sends a request to an independently operated destination. Private demo images are served locally; manufacturer photographs are not hotlinked. Source evidence and media permission are separate.

Product Share copies a clean product link or opens a selected email, text or social application only when you choose it. Opening an intent does not mean a message was sent. No social SDK or share-tracking script is loaded. A localhost link is accessible only on the device running that local preview; shared product links omit credentials, search parameters and invitation/session tokens.

There are no active retailer affiliate redirects, payment processors or public consumer account providers. Demo handoff does not visit a retailer, create an order or record a billable click. Voluntary email uses the Lark Mail service described above; there is no on-site email submission endpoint.

• Manufacturer evidence explained ↗

No production-host logging/retention schedule, processor list or public privacy-request workflow has been approved for launch. We do not promise a specific deletion period, request response time, encryption guarantee or blanket legal compliance in this draft.

Before public launch, the owner must confirm the operator details, actual hosting/logging and email retention, applicable privacy rights and request handling, and any data sharing. Privacy questions can be sent to contact@vologolo.com; a contact address does not by itself establish an approved request-handling policy. Browser-local tools, preferences and setups are implemented as described above; optional accounts, cloud sync and alerts would need separate ownership, security and consent controls and are not implemented today.

• Current contact status ↗
• Browse without an account ↗
• Explore systems ↗