AmeriHost Website Forms Privacy Policy

This document describes the forthcoming AmeriHost Website Forms service and will apply when that service is enabled on a participating website.

This policy covers AmeriHost Website Forms, which will be operated by AmeriHost to process and deliver inquiries from participating websites. It will cover this service rather than all AmeriHost products. The business receiving an inquiry may have its own privacy policy governing its subsequent use of the information.

Information processed

The service will process information entered into a participating form, such as a name, email address, phone number when requested, and message. It will also process the submission time, the originating form or website, and delivery status information needed to route and troubleshoot the inquiry. Please do not submit passwords, payment-card details, or sensitive personal records through these forms.

Google account access

An authorized administrator will grant the service the Gmail permission to send email (gmail.send). The service will use that permission to send form-related messages from the connected account. This permission will not allow the service to read inbox messages or contacts. The service will store authorization tokens so it can send messages without requiring the administrator to sign in for each submission. It will also process the sending address, outgoing message content, recipient addresses, and delivery responses needed for this function.

Purpose and sharing

Information will be used to deliver inquiries, support responses, prevent abuse, maintain submission records, and troubleshoot or retry failed deliveries. Submission and message information will be shared with the designated business recipient and with providers needed to operate the service. The planned infrastructure will use Cloudflare for form processing, abuse protection, and record storage, and Google for email delivery. Recipient email providers will also process delivered messages. Authorized personnel may access records when necessary to handle an inquiry or support the service.

Google user data will be used only to provide and support these messaging functions. It will not be sold, used for advertising, or used to train generalized artificial-intelligence models. Use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Storage and retention

Submission records and delivery records will be stored on the service's server-side infrastructure. Authorization credentials will be kept in server-side secret storage and will not be included in public page code. Records will be retained for handling inquiries, resolving delivery problems, and maintaining business records. There will be no fixed automatic deletion interval stated by this policy. Email copies may also remain in the sending and receiving mailboxes under their respective retention practices.

Access, deletion, and disconnecting Google

Contact [email protected] to request access to, correction of, or deletion of information held by this service after it is enabled. We may ask for information needed to verify the request. Requests concerning a recipient business's own records should also be directed to that business. Removing a service record will not automatically remove email copies held by recipients.

The connected Google account owner will be able to revoke the service's access through their Google Account's third-party connections settings. Revoking access will stop the service from using that authorization for further sending; it will not erase existing submissions or delivered messages. Contact [email protected] to request removal of stored service authorization credentials and related records.

Changes and contact

We will update this page when the service's data practices change. Questions about this policy can be sent to [email protected].