AUTO HOSTING

AUTO HOSTING · AUTOWEB

Privacy Policy

How the owner's website-management data is handled.

Effective date: September 20, 2026. Operator: Codergy. This policy applies to the Auto Hosting personal automation tool, its autoweb Google OAuth application, and this information website.

Information accessed and purpose

With the owner's authorization, the tool accesses Google Analytics account, property and web-stream configuration; site ownership and verification records; and Google Search Console site and sitemap information. It uses this information to configure analytics, verify the owner's websites, submit sitemaps and check submission status. It also receives OAuth access and refresh tokens needed to make these authorized API calls.

Storage and protection

OAuth client credentials and tokens are stored encrypted in the owner's server-side credentials database. Encryption key material is kept separately from the synchronized workflow files. Website configuration and task receipts are stored on that server. Tokens are not included in public pages or source repositories. Account access is limited to the owner and authorized administration of this personal tool.

Sharing and service providers

Google data is used for the website-management functions described above and is sent to Google APIs as needed. It is not sold, used for advertising, or sent to content-generation models for training or article creation. Cloudflare hosts this information site and may process technical request information, such as IP addresses, for delivery and security. This site provides no public login or credential-upload form and sets no application advertising cookies.

Google API Limited Use

Auto Hosting's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not used to develop, improve or train generalized AI or machine-learning models.

Retention, revocation and deletion

Authorization tokens and configuration are retained while the owner uses the tool. Operational receipts are kept for troubleshooting and preventing repeated actions. The owner can stop the tool and revoke its access at Google Account connections. Revoking access stops future authorized calls; deletion of stored tokens, configuration, receipts and any retained credential backups is a separate server-administration step. Contact the operator to request that deletion.

Contact and changes

For privacy questions or deletion requests, contact 969994617@qq.com. Changes to these practices will be reflected here with an updated effective date.