Privacy policy

Who this policy covers

Horton Technologies LLC operates LodgeMind. This policy covers the public website, sales and support communications, and the information we use to provide the hotel operations platform. A hotel's written service or data-processing agreement may add account-specific requirements.

For information a hotel places in its workspace, the hotel determines the business purpose and authorized users. We handle that information to operate and support the service for the hotel. For website inquiries and our own business records, Horton Technologies LLC determines how the information is used.

Information we handle

Contact information: the name, work email, hotel or company, inquiry topic, and message you send. The contact form also records a request reference, time, source page, browser information, and an abuse-prevention request fingerprint.

Account and operational information: authorized staff accounts, property and room references, work orders, room checks, maintenance plans, assets, inventory, vendors, documents, and associated activity that a hotel chooses to put into LodgeMind.

Technical information: request and security logs needed to deliver and protect the service. If you allow optional analytics, we also process page visits, campaign parameters, referral information, session identifiers, and contact-conversion events. Do not send passwords, payment-card details, health records, or unnecessary guest personal information through the website or public demo.

Why we use information

We use information to answer inquiries, prepare quotes, configure accounts, deliver onboarding and support, operate the platform, keep business records, prevent abuse, investigate problems, and meet applicable obligations. Optional website analytics help us understand which pages and campaign links are useful.

Submitting the contact form lets us reply about that request. It is not an automatic subscription to a newsletter or permission to send unrelated marketing. You can ask us to stop nonessential marketing communications without affecting account or support messages.

Cookies and browser storage

The sales site stores your cookie preference in your browser for up to 180 days. Essential functionality and security do not depend on accepting optional analytics.

If you allow analytics, LodgeMind's campaign-attribution storage can remember the first and latest campaign links for up to 90 days, and session storage helps group activity during a browsing session. Google Analytics may also run when configured. Optional analytics are off until you choose to allow them; a recognized Global Privacy Control or Do Not Track preference keeps them off.

Use Cookie preferences in the footer to change your choice. Turning analytics off stops the sales site's optional analytics and clears its accessible attribution and analytics cookies. Browser settings can clear or restrict additional storage. Property workspace sign-in uses separate session mechanisms needed for authenticated access.

Service providers and other disclosures

We use service providers for functions such as hosting, email delivery, analytics, security, and business operations. Information is shared as needed for those functions. We may also disclose information to professional advisers, in a lawful business transfer, to protect rights or safety, or when legally required.

We do not sell website inquiry or hotel workspace information for monetary consideration. We do not offer a public directory of customer workspaces or publish hotel operational records as marketing material. Real customer information will not be used in sales screenshots without appropriate authorization.

Service providers and infrastructure may process information in the United States or other locations used to deliver their services. Specific location or transfer requirements must be discussed and documented before a hotel begins using the service.

Retention and account closure

We keep information for the purpose it serves, including active service, support, security, billing records, and applicable retention obligations. The hotel's written arrangements can specify operational retention and handover requirements. We do not promise an unlimited archive or immediate removal from every backup.

When you request account closure or deletion, we confirm the requesting person's authority, identify any records that must be retained, and explain the account-specific handling. Backup copies and records required for security, disputes, or legal compliance may follow separate retention requirements. Cancellation of renewal does not itself instruct us to delete an active workspace.

Requests and choices

Use the contact form and select Privacy or a data request to ask about access, correction, deletion, marketing preferences, or other applicable privacy rights. Include enough information to identify the account or inquiry, but do not send identity documents or passwords in the initial message.

We may need to verify identity or hotel authority before releasing or changing information. Requests about a hotel's workspace may need to be directed through its authorized administrator. Available rights, exceptions, and response requirements depend on applicable law and the service arrangements.

Security and age suitability

We use access controls and operational safeguards appropriate to the service. No internet service can guarantee absolute security. See the Security page for the boundaries of our public security statements.

LodgeMind is a business service for adult professional use. The public website and demo are not directed to children. Please contact us if you believe a child has supplied information that should be removed.

Changes and contact

We update this page when the described practices materially change. Its updated date identifies the current website policy. Account-specific notices may be sent to the hotel's designated contact.

Contact Horton Technologies LLC through the contact form, or by mail at 1305 Barnard St #726, Savannah, GA 31401, United States. Choose the privacy inquiry topic so the request can be routed correctly.