Skip to content
HOHMANT

About this policy

This policy explains how HOHMANT handles information on hohmant.com and in the HOHMANT cabinet. HOHMANT provides tools for exhibition interactions, contact management, catalogues and optional connected services. For privacy questions, contact the service operator at privacy@hohmant.com.

When a business uses HOHMANT to manage its visitors, contacts or enquiries, that business decides what information it collects and how it uses it. Contact that business about its own collection practices; you can also contact HOHMANT about information held by the service.

Information we handle

  • Account information: email address, profile name, language, time zone and authentication records.
  • Business content: company and team details, contacts, telephone numbers, notes, products, catalogues, materials and enquiries entered by you or submitted by visitors.
  • Interaction records: recorded visits and actions on tracked links, QR routes and published content, timestamps, pseudonymous visitor identifiers and available browser, device and approximate location information.
  • Technical information: IP addresses, request and security records needed to operate the website, limit abuse and diagnose failures.
  • Connected services: account identifiers, authorised configuration and connection credentials for the features you choose to connect.

Not every record identifies a person. Recorded interactions do not by themselves prove a sale, a completed message delivery or the identity of an anonymous visitor.

How information is used

We use information to authenticate accounts, provide the features you request, maintain your business records, display interaction reports, respond to support requests, protect accounts and diagnose problems. Businesses are responsible for having permission to upload personal information and for choosing appropriate uses of contact data.

Optional advertising connections and website advertising measurement are separate from account access. Availability and actions depend on the selected settings, permissions and feature configuration.

Google sign-in and connected Google services

When Google sign-in is available and you choose it, Google supplies an account identifier and basic identity information through its sign-in service. HOHMANT uses the verified Google account identifier to authenticate the HOHMANT profile you explicitly link. Matching email addresses alone do not link two accounts. Email-link sign-in remains an alternative.

Google sign-in does not request access to your Gmail messages, contacts, files or calendar. The Google identity linked to your profile is stored with your HOHMANT account; sign-in tokens are processed to verify the sign-in and are not retained as mailbox credentials. Google sign-in information is not sold or used to create advertising audiences.

A separate Google advertising connection, if you enable one, can access the authorised account and audience configuration needed for its visible features. Connection credentials are stored encrypted. Connecting Google sign-in does not connect an advertising account or authorise advertising actions.

HOHMANT’s use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements where applicable. You can review or revoke authorisations in your Google Account. Revocation does not automatically erase historical HOHMANT records.

Cookies and website analytics

Essential cookies keep you signed in and protect authentication and other requests. The website also uses browser storage to remember your analytics choice. You can clear cookies and browser storage, but doing so may sign you out or remove remembered preferences.

On the public marketing website, the Meta pixel loads only after you allow website analytics. When allowed, it shares website visit and browser information with Meta for advertising measurement. Use “Analytics settings” in the website footer to change your choice. Declining optional analytics does not prevent you from reading the website or using email sign-in. These privacy and terms pages do not load an advertising pixel.

Service providers and disclosure

HOHMANT uses Cloudflare infrastructure to host the service and store its data. Providers that you choose to connect, such as Google, Meta, WhatsApp or Telegram, process information needed for the requested connection or action under their own policies. Opening a prepared WhatsApp link is separate from sending the message.

Business content is available to the account’s authorised users according to their access permissions. Information may also be disclosed when necessary to handle a security incident, comply with a lawful request or protect the service and its users. We do not sell Google sign-in data.

Storage, security and retention

We restrict account access and use protected connections, server-side authentication checks and encrypted storage for integration credentials. No service can promise that every risk will be eliminated.

Information is kept while it is needed to provide the service, maintain requested business history, investigate security issues or meet applicable obligations. Retention depends on the record and the purpose; we do not promise one deletion deadline for every category.

Deleting a profile disables account access and removes its profile name and email from active identity records. Historical exhibition and interaction records can remain, including records used by other authorised accounts. A profile deletion is not a request to erase every business record. Contact us about a specific removal request.

Your choices and requests

You can update available profile settings, manage optional advertising preferences, sign out and use the profile deletion controls when their requirements are met. You can decline website analytics and revoke an external provider’s authorisation.

To request access, correction or deletion of personal information, or to ask about a privacy concern, email privacy@hohmant.com. Describe the account and the information involved without sending passwords or authentication codes. We may need to verify your authority and consider records that must be retained or that belong to another business.

Policy updates

We will update this page when our practices change. The date at the top identifies the current version. If a change requires new permission for an optional connection or data use, that permission must be obtained before the new use.