Back to RIGMER

RIGMER · YOUR INFORMATION

Privacy policy.

A clear account of what we collect, why we use it, and the choices you have.

Effective 10 October 2026 · Version 1.2

You choose how to connect. Verification is separate from marketing. Optional Google Analytics starts only after you allow it.

Your request stays yours. We use contact and project information to respond, manage your account and support the business you ask us to provide.

01

Who we are and what this covers

RIGMER is operated by RIGMER INC. RIGMER INC. is responsible for the personal information described in this policy when it determines how and why that information is used for RIGMER.

This policy covers rigmer.com, RIGMER account and enquiry interfaces where offered, and our business communications by email and WhatsApp. The public homepage currently offers a launch notification list. Account, equipment enquiry and voice features are described below for the interfaces in which they are available; their inclusion does not mean every feature is live on the public homepage.

Contact our privacy team through privacy@rigmer.com, with “Privacy request” in the subject. You do not need to create an account to contact us.

02

Information we collect

Launch notifications
Your email address, subscription time, country reported by our hosting provider and the page or form used to subscribe.
Accounts and verification
Your name, email, verified phone number, authentication provider identifier, verification outcome and session records. Google sign-in supplies the identity details you authorize. We do not receive your Google password. Website verification codes are stored as protected hashes, rather than readable codes.
Enquiries and business communications
Your contact details, company, equipment selections, quantities, configuration, destination, timing, requirements, submitted reference files, enquiry history and communications with us. Later quotations, orders or service matters include the information needed for that specific request.
Website operation
Network and device information necessary to serve and protect the site, such as IP address, browser information, request time, security events and message delivery status. The subscription rate limiter uses your IP address. Optional analytics can measure page visits and interactions after you allow it.
Voice input, where enabled
Only after you start recording and grant microphone permission, a short audio clip may be sent for transcription. The recording interface identifies availability and the configured service before use. Voice transcription is not currently enabled on the public homepage. Typed search does not require microphone access.

We receive information directly from you, from an identity provider you choose and from the service providers described below. Please avoid including passwords, payment card details, government identity documents or unnecessary sensitive information in enquiry text or reference files.

03

Why we use it

  • To provide the launch notifications you request and send a subscription confirmation.
  • To verify a contact method, protect sign-in, create or maintain your account and link an additional identity only when you request it.
  • To respond to enquiries, prepare quotations and documents, maintain enquiry history and communicate about the equipment or service you ask us to provide.
  • To operate the website, prevent abuse, investigate delivery failures, protect records and comply with applicable legal obligations.
  • To understand website use through optional Google Analytics when you allow it.

Where a law requires a legal basis, we rely on consent for optional analytics and requested marketing notifications; steps you request before a contract or performance of a contract for relevant business services; legitimate interests in secure operations and appropriate business correspondence; and legal obligations where applicable. Legitimate interests do not override rights protected by applicable law.

Authentication, enquiry submission and WhatsApp service updates do not automatically subscribe you to marketing. We do not use this website’s information to make solely automated decisions with legal or similarly significant effects on you. We do not sell personal information or use it for cross-context behavioural advertising.

04

WhatsApp and email, with clear choices

When you request a WhatsApp verification code, your phone number and the code are sent to Meta’s WhatsApp Business Platform for delivery. A verified number may then be used to authenticate your RIGMER account. Requesting a code does not authorize promotional messages.

Our system WhatsApp sender is +1 339 238 8999. The website may also link to a separate customer service number shown in that link. Opening a WhatsApp link moves you to WhatsApp; your message is sent only when you send it there. WhatsApp and Meta also process information under their own policies.

For enquiries, we use your chosen channel for replies and service messages. Additional WhatsApp enquiry updates require the separate choice shown in the enquiry form. You can ask us to stop non-essential updates without deleting your enquiry. Contact us or reply “STOP” in a conversation; we process these requests through our business support workflow.

Email verification and confirmation delivery use Resend when configured. Enquiry emails can include the reference files you submit. Delivery providers process recipients, message content and delivery events to provide those services. A provider accepting a message is not proof that it reached your inbox.

Within RIGMER’s message-status integration, we keep delivery identifiers, recipient, timestamps, status and numeric failure codes. That receiver discards incoming conversation bodies and does not log verification codes. Messages that you deliberately send to our business team may be handled separately as business correspondence.

05

Who receives information

Authorized RIGMER personnel access information needed for their role. We use the following providers for the stated purposes:

  • Cloudflare: website and media hosting, subscription database, network security, rate limiting and cookie-free Web Analytics. A temporary HTTPS callback tunnel may also relay Meta events during integration testing.
  • Meta / WhatsApp: requested verification codes, business messages, approved templates and delivery events.
  • Resend: requested verification emails, subscription confirmations and enquiry communications where enabled.
  • Google: optional Google Analytics and Google sign-in if you choose it. Advertising storage, advertising user data and advertising personalization are disabled in this website’s analytics configuration.

Other quotation, logistics, dealer or service recipients may receive the information needed to fulfil your particular request; we identify relevant recipients in that transaction or service context. We may disclose information when lawfully required, to protect rights and security, or in a business transfer subject to appropriate protections. We do not make contact lists available to unrelated advertisers.

Social links are links rather than embedded social feeds. When you follow them, the destination service handles your visit under its own privacy policy.

06

Cookies, analytics and your browser

Essential session and verification cookies support features you use. Equipment shortlists and comparison selections can be kept in your browser. Enquiry drafts, including contact details you enter, are stored in that tab’s session storage until you clear the draft or the browser ends that session. A draft is not an enquiry submission. Requesting a verification code does transmit the contact details necessary for verification.

The public homepage uses a preference called rigmer-privacy-choice-v1 in local storage to remember your optional analytics choice for up to 180 days. This preference is necessary to honour that choice. If browser storage is unavailable, the choice applies only to the current page session.

Google Analytics is off until you choose “Allow analytics”. You can decline or change your choice through “Manage cookie choices” in this policy. Declining prevents further Google Analytics loading on subsequent page loads and removes readable first-party Google Analytics cookies on this domain. Your browser’s Global Privacy Control signal takes precedence: optional Google Analytics remains off when that signal is enabled.

When allowed, Google Analytics measures visits and limited interactions such as an equipment-independent subscription event or a social-link click. We do not include form email addresses, phone numbers, enquiry text or verification codes in those analytics events. Google Analytics may use its own identifiers and cookies, whose duration is determined by its configuration. Cloudflare Web Analytics is cookie-free and separate from this optional Google Analytics choice; infrastructure and security processing also continue so the website can work.

You can also clear saved site data in your browser. Clearing a device’s saved equipment, drafts or cookies does not delete a server-side account, subscription or submitted enquiry.

07

How long information stays

  • Launch list: retained for the requested launch communication until you withdraw, the list is no longer needed, or a deletion request is processed. This is managed operationally, not through a fixed automatic expiry.
  • Website verification: WhatsApp codes expire after five minutes; email codes after ten minutes. A verification code can be used only once. Expired records and abuse-prevention records are cleaned up when the related service next runs; expiry does not imply immediate physical erasure. WhatsApp rate-limit request records cover up to 24 hours.
  • Account sessions: sign-in sessions expire after seven days unless you sign out earlier. Some verification-session cookies last up to 24 hours.
  • Accounts and enquiries: retained while needed to provide the account, respond to the request, support continuing business, or meet applicable recordkeeping and dispute obligations. These records are not currently subject to a fixed automatic deletion period. Contact us for deletion or for the retention criteria applicable to your record.
  • RIGMER delivery metadata: the message-status integration removes records older than 90 days when processing the next callback.

Service providers may retain their own service, security or legal records under their applicable terms. Where information must be retained after a deletion request for a lawful reason, we explain the reason and restrict its use. Copies in backups may remain until the relevant backup is replaced or expires; they are not used for routine business activity.

08

Your choices and rights

Depending on your location and the applicable law, you may ask to access or obtain a copy of your information, correct it, delete it, restrict certain uses, receive a portable copy, object to processing based on legitimate interests, or withdraw consent. Withdrawal does not change the lawfulness of processing before withdrawal. You may also complain to your local data protection authority.

Send requests to privacy@rigmer.com. Include the email or phone number used with RIGMER and the action you want. We may ask for proportionate verification before sharing or changing records. Do not send a password or verification code. An authorized representative can contact us with appropriate evidence of authorization.

We respond within the period required by applicable law, explain any lawful exception and do not penalize you for exercising applicable rights. To leave the launch list, email the same address with “Unsubscribe”. Signing out ends the current session; deleting an account or enquiry requires a separate request.

If California privacy law applies to your interaction and to us, its applicable access, correction, deletion, portability and non-discrimination protections also apply. We do not sell or share personal information for cross-context behavioural advertising. The website honours Global Privacy Control by disabling optional Google Analytics.

09

International services

RIGMER serves international business enquiries. Our providers and the authorized teams handling your request may process information in the United States or other countries whose privacy laws differ from yours.

Where applicable law requires a transfer safeguard, the service must use an appropriate lawful transfer arrangement before that transfer is enabled. This policy does not claim that a particular certification or contractual mechanism applies to every service. Contact us for the countries, recipients and transfer arrangements relevant to your information.

10

Security and sensitive information

We use controls appropriate to the feature, including restricted staff access, private server credentials, protected verification-code hashes, browser-bound verification, request limits and validation of Meta callback signatures. Public services use HTTPS. No system can guarantee absolute security.

RIGMER never needs your Google password or your one-time login code in a support conversation. Verification is completed in the relevant sign-in interface. We do not collect payment card information through the enquiry form. If a later transaction requires payment, its payment process and privacy information are provided separately.

If voice transcription or an AI service is introduced, the recording or submission interface will explain the provider and relevant processing before use. We will update this policy for material new processing. This policy does not claim that an OpenAI service is currently connected.

11

Business use and children

RIGMER’s equipment and business services are intended for adults acting in a business capacity, not children. We do not knowingly request children’s personal information. If you believe a child has provided information to us, contact us so we can investigate and take appropriate action.

12

Changes and contact

We update this policy when our services or data practices change. The effective date and version appear at the top. When applicable law requires notice or a new choice before a material change, we provide it. An updated policy does not by itself authorize a new use that requires consent.

For privacy requests, complaints or questions: privacy@rigmer.com · RIGMER INC., operator of RIGMER · rigmer.com.