Privacy Policy
This policy explains how Runze Fluid handles information collected through the product-selection website, registration, quote workflows, social sign-in, email verification, and contact forms.
Last updated: 2026-08-03
Information We Collect
We collect the information customers provide when they register, request email verification, submit contact forms, build quote requests, save selections, or communicate with sales and support. This may include name, email address, phone number, company, shipping or billing details, product selections, technical requirements, quote notes, and support messages.
How We Use Information
Runze Fluid uses customer information to verify accounts, respond to product and documentation requests, prepare quotations, route distributor or sales inquiries, provide technical support, maintain saved product selections, improve the website, and communicate about related service needs.
Email Verification
New customer registration may use email verification codes. Verification messages are sent only to confirm account ownership and protect the registration flow from automated abuse.
Account Selection Synchronization
When a customer signs in, shopping-cart selections, quote-cart selections, product lists, saved carts, and quote history may be synchronized with the customer's Runze account so they remain available across browsers. Anonymous selections remain in that browser and are merged into the account after sign-in. Signing out removes synchronized account selections from that browser; the account copy is retained according to the retention terms below.
Analytics And Advertising
When measurement IDs are configured, the website may use Google Tag Manager, Google Analytics, Google Ads conversion tracking, Yandex Metrica, or Matomo to measure page views, registrations, quote requests, contact submissions, and advertising performance. Google Consent Mode v2 starts ad storage, ad user data, ad personalization, and analytics storage as denied before any Google tag loads. Until a customer accepts optional measurement, Google tags do not receive permission to use advertising or analytics storage or personalized advertising, while Yandex Metrica and Matomo are not loaded. With denied consent, configured Google tags may send limited cookieless consent and measurement signals. When accepted, Yandex Metrica and Matomo may collect allowlisted public page paths and the completion of allowlisted quote or lead goals. Session Replay, click maps, link tracking, form analysis, title collection, and ecommerce collection are disabled; account, cart, checkout, order, Admin, and API paths are excluded from page-view measurement. Conversion events are restricted to allowlisted operational event names; names, contact details, addresses, URL queries, URL fragments, and free-form inquiry text are not sent to analytics tags. Matomo may receive an opaque first-party attribution identifier and numeric advertising resource identifiers through a configured visit-scoped custom dimension. When a visitor submits an inquiry, allowlisted campaign identifiers may also be attached to the sales request so the business can identify its source.
Cookies
The site uses necessary cookies or similar storage for login status, security, region or language preferences, cart and quote workflows, campaign-source continuity, and fraud prevention. Allowlisted advertising click identifiers and UTM values may be retained for attribution continuity so an inquiry can include its originating campaign; this information is not combined with free-form messages in analytics tags. When optional measurement is configured, the consent control stores the customer's accepted or rejected choice in first-party browser storage and applies it on later page loads. Customers can reopen Cookie settings on any page to change that choice. Rejecting or later withdrawing optional analytics keeps Yandex Metrica and Matomo unloaded and Google storage denied. Browser settings may also allow customers to block or delete stored data, although some account and quote features may not work correctly without necessary storage.
Sharing Information
Customer information may be shared with Runze Fluid sales, support, fulfillment, distributor, or service teams when needed to answer requests or prepare quotations. We do not sell customer contact information as a standalone product.
Retention And Security
We keep customer information for as long as needed to manage accounts, quote history, support requests, legal obligations, and business records. Public forms and account flows should be handled over HTTPS on production.
Customer Choices
Customers may contact Runze Fluid to request correction, deletion, or review of their account and inquiry information, subject to business, legal, and security recordkeeping requirements.
Contact
For privacy questions or account information requests, contact Runze Fluid through the Contact page.
Social Sign-In
Customers may sign in with an enabled Google, YouTube, Apple, LinkedIn, or TikTok account. YouTube sign-in uses the Google authorization service and the same Google account identity; it is a convenient login choice, not a separate identity provider. The provider authenticates the customer on its own authorization page; Runze Fluid does not receive or store the provider password. We use the provider's account identifier and available basic profile details, such as name, verified email address, and profile image, only to create or access the Runze account. Provider access and refresh tokens are not retained after the sign-in exchange. A first social sign-in automatically creates a Runze customer account. When a provider supplies the same verified email address as an existing Runze customer account, the new sign-in method is linked to that account. We do not link accounts using an unverified email address or display name. Some providers, including TikTok, may not supply an email address; in that case the customer may be asked to add a verified contact email separately.