Privacy Policy
Last updated: 20 October 2026.
GoLinuxCloud is operated by Deepak Prasad, based in India ("we", "us", or "our"), for readers worldwide. This notice explains how information is processed when you read golinuxcloud.com, use the AI Bot, run code examples, comment, or contact us.
For privacy questions or requests, email admin@golinuxcloud.com. Our Cookie Policy explains browser storage and available controls. This notice describes our practices; it does not itself request or establish your consent.
1. Summary of Key Points
- Reading the site: Cloudflare processes technical requests to deliver and protect the website. Google Analytics 4 measures site usage, and advertising services may process identifiers and browsing information.
- Using the AI Bot: We record submitted questions, answers and operational information, including pseudonymous browser and conversation identifiers. Some generated answers are cached for reuse. A separate conversation copy is saved in your browser.
- Optional submissions: Comments are public through GitHub Discussions. Emails contain the information you choose to send. Clicking Run sends the displayed code to an external execution service through our API.
- Sensitive information: We do not ask for passwords, private keys, health information, government identifiers, or other sensitive information. If you include these in a question, code sample, comment or email, they can nevertheless be processed and stored. Please remove them before submitting.
- Advertising preferences: AdPushup supplies its own advertising consent interface where its service presents one. This is separate from our independently loaded GA4 analytics and AI Bot.
2. Information collected through this website
2.1 Personal information you disclose to us
- Email and corrections: Your email address, any name you supply, message contents, attachments and correspondence metadata are processed by our email service and by us to respond, investigate reported problems and maintain correspondence. The current Contact Us page directs you to email or article comments; it does not contain a separate contact submission form.
- Comments: Article comments use Giscus and GitHub Discussions. Signing in and posting may associate your comment, GitHub username, avatar, reactions and timestamps with a public discussion. GitHub stores this information; we can read and moderate discussions. Loading the comment component also makes requests to its providers even if you do not post. See the GitHub Privacy Statement.
- AI questions and ratings: Section 2.3 describes what we record when you submit a question or rate a conversation.
- Code execution: Section 2.4 describes what is sent when you use Run.
You do not need a GoLinuxCloud account to read articles or use the AI Bot.
2.2 Automatic collection of information
When you visit the website, our hosting and security provider Cloudflare processes information such as IP address, requested URL, request time, browser headers and security signals. Request URLs can contain query parameters. Infrastructure logs and security records are separate from our chatbot database.
Google Analytics 4 processes usage information such as page locations and titles, referrals, timestamps, browser/device information, approximate geography and browser identifiers. Advertising services may process IP addresses, identifiers, page context, device information and ad interactions. These services load separately from the AI Bot; see Sections 3 and 5.
2.3 GoLinuxCloud AI Bot (optional)
The AI Bot searches a published article index in your browser. When you submit a question, our API can generate an answer using Cloudflare Workers AI, return a previously cached answer, or receive a report of an answer assembled in your browser. Browser-composed answers and conversational replies can therefore also be recorded on our servers.
| Information | Purpose and storage |
|---|---|
| Submitted question and answer text | Recorded in Cloudflare D1 (chat_history) to investigate problems and improve the bot and tutorials. Questions may be spelling-corrected or expanded with the previous topic before transmission; stored wording is not always identical to what you typed. |
| Normalized question, inferred topic and intent, content-gap labels and failure scores | Rule-based classifications in D1 for quality analysis and identifying tutorials to improve. |
| Request and conversation IDs, turn number and parent-request reference | Link requests and related turns in D1. |
| Pseudonymous visitor hash | Derived from the signed browser cookie to group turns in D1. It is not your name or email, but can link activity from the same browser. |
| Current page path and query parameters; retrieved guide URLs and relevance scores (up to eight) | Stored in D1 to understand context and which guides were selected. URL parameters can contain information supplied in a link. |
| Timestamps, answer type, model/build identifiers, response time, cache status, validation/error status and estimated AI usage | Operational monitoring in D1. Rejected output or a refusal reason can be recorded even when it was not shown as an answer. |
| Session start/end activity, turn counts, initial page, topic, ratings and quality scores | Conversation summaries in D1 (chat_sessions). |
| Thumbs up/down, conversation ID, feedback time and whether feedback came from the panel or closing flow | Ratings are attached to existing history/session records. The rating request does not upload a separate transcript snapshot. |
Signed random browser ID (glc_ai) |
Stored in an HttpOnly cookie for limits and session association. The raw ID is used in the Cloudflare Durable Object budget counter; a derived hash is used in D1. |
| IP-derived label and hourly request count | The API uses the connecting IP to create a keyed label for rate/budget limits. Raw IP addresses are not written as a dedicated field in the chatbot history or budget tables, but may be processed by infrastructure services or appear in text you submit. |
| Generated answer, citations, passage IDs, model/build versions and creation time | Some responses are stored in private Cloudflare R2 for reuse for matching questions. The cache key is derived from the question and source/version information. Cached answers may be served to other readers; do not include private details in questions. |
| Model request and response information | Generated answers are processed by Workers AI. When AI Gateway logging is enabled, prompts, responses and usage metadata may also be retained in Gateway logs, separately from D1 and R2. |
| Conversation copy and interface preferences | Stored in your browser, as described in Section 6 and the Cookie Policy. Other scripts running on the same website origin can technically access localStorage; it is not encrypted private storage. |
The chatbot integration does not send question text, answers, ratings or chatbot-specific events to GA4. GA4 can still measure the page on which the bot appears. We do not sell AI Bot chat records or use them for cross-context behavioral advertising. Operator history is not offered as a public transcript service; answer-cache reuse is described above.
Clearing the conversation with the broom removes the browser copy. It does not delete server records or provider logs. For a request concerning those records, see Section 17.
2.4 Running code examples
When you click Run on a supported code block, the code and language are sent through our Cloudflare API. Go code is forwarded to the Go Playground (go.dev); Python, JavaScript and Java code is forwarded to the public Judge0 CE service (ce.judge0.com). The service returns execution output or errors for display in your browser.
Our code-runner endpoint does not write a separate submission-history database. The execution providers may process or retain submitted code, results and technical logs under their own practices; the chatbot retention periods do not apply to them. Do not run code containing credentials or confidential information. See Google's Privacy Policy and Judge0.
3. Traffic measurement and advertising
3.1 Google Search Console
We use Search Console reports about search queries, impressions and clicks to understand how people find our articles in Google Search. Search Console does not add an analytics script to your page.
3.2 Google Analytics 4 (GA4)
We use GA4 (measurement ID G-ENK40BBCT8) to understand visits, referrals and article usage. The website loads its GA4 tag automatically after page load; it does not currently provide a separate first-party analytics consent selector. AdPushup's advertising interface should not be assumed to control this tag.
GA4 commonly uses cookies to distinguish browsers and sessions. Google states that GA4 does not log or store individual IP addresses, although addresses are processed during collection, including to derive approximate location. This does not make all analytics data anonymous. See Google's data safeguards and Privacy Policy.
You can use Google's Analytics opt-out browser add-on in supported browsers or browser/content-blocking controls. Deleting cookies alone does not disable future analytics requests. We do not intentionally send names, email addresses, passwords or chatbot text to GA4; page URLs can still include query parameters.
3.3 Advertising
Our pages load advertising scripts from AdPushup and AdRecover (AdPushup's ad-block recovery service), alongside the advertising partners those services use. They may process identifiers, browser/device information, page context and advertising interactions for delivery, measurement, fraud prevention and personalization.
AdPushup manages its advertising consent interface. Whether a message appears and the choices it offers depend on its configuration and service behavior. We do not provide a separate site-wide popup covering GA4, the AI Bot or all embedded content. Advertising choices do not automatically change the independent processing described elsewhere in this notice. Available provider and browser controls are listed in our Cookie Policy.
4. Why we use information
We use information to deliver and secure the website; answer submitted questions; enforce fair usage limits; respond to correspondence; investigate errors; evaluate bot quality; identify content gaps; improve tutorials; enable public comments and code execution; measure readership; and support advertising.
Bot quality labels are used to review content and service performance, not to decide eligibility for employment, credit or similar services. Privacy rights and the legal requirements for each purpose depend on the applicable law. Describing a purpose here does not mean that optional tracking is necessary to provide an article or an answer, or that reading this notice constitutes consent.
5. Who receives information
| Recipient | Processing described in this notice |
|---|---|
| Cloudflare | Website hosting and security, API execution, D1 chat records, R2 answer cache, Durable Object limits, Workers AI and optional AI Gateway logs. See Cloudflare's Privacy Policy. |
| GA4 analytics, Google advertising where used by our advertising partners, and Google-hosted content/services when loaded. | |
| AdPushup and AdRecover | Advertising delivery and related processing. See AdPushup's Privacy Policy and AdRecover's Privacy Policy. |
| GitHub and Giscus | Comment component requests, authentication through GitHub and public discussions. |
| Go Playground and Judge0 CE | Code submitted using Run and execution results. |
| Email service providers and GoLinuxCloud operators | Correspondence, attachments, delivery and support. |
| Embedded-content providers | Requests for content such as videos or externally hosted code, where present on an article. |
Public comments can be read by other people. A shared AI cache can return a generated answer to another reader. We may also disclose information when legally required, to address abuse or legal claims, or as part of a business transfer subject to applicable safeguards.
6. How long information is kept
Different stores use different cleanup mechanisms:
| Information | Retention behavior |
|---|---|
| D1 chat history and attached ratings | Configured for cleanup of rows older than 90 days by a separate daily scheduled worker. Actual deletion occurs when cleanup successfully runs, rather than exactly at the 90-day boundary. |
| D1 conversation summaries | Configured for deletion after 90 days since last recorded session activity, at the next successful scheduled cleanup. |
| R2 generated answers | Answers older than 30 days are not reused. Objects older than 30 days are selected for deletion by the daily cleanup worker. |
| Budget browser IDs | Grouped in UTC daily records. Older daily records are pruned after a successful generation reservation, keeping the current day and previous two UTC dates. They can remain longer when there is no successful reservation to trigger cleanup. |
| IP-derived budget labels | Previous UTC hourly records are pruned after a successful generation reservation; idle records can remain longer. |
| In-flight budget reservations | Records older than 120 seconds are settled and removed when the budget is next checked through reservation or status operations; this is not a timed deletion while idle. |
glc_ai cookie |
30 days from issue, unless removed sooner by you or the browser. |
| Browser conversation | The latest 14 messages, normally seven question/answer exchanges, subject to a size limit. The saved conversation is discarded when next read after 12 hours since its last save. Further activity refreshes this time; the browser does not automatically delete localStorage while you are away. |
| Browser preferences | See the Cookie Policy. These localStorage entries can remain until cleared. |
| AI Gateway, infrastructure and provider logs | Separate from D1/R2 cleanup. Retention depends on the relevant service/account settings and deletion operations; the chatbot's 90-day and 30-day cleanup does not remove these logs. |
| Emails and public comments | Correspondence is retained as needed to respond, investigate and maintain a record of the matter. Public comments remain on GitHub until removed through its tools or moderation. There is no chatbot-style automatic retention period for these records. |
Copies in backups or recovery systems may remain subject to their own retention and access restrictions. Clearing browser storage does not erase data already received by us or a provider. Contact us for a request about retained personal information.
7. Security
We use HTTPS, provider access controls and measures such as signed HttpOnly chatbot cookies. Chat database access and the answer-cache bucket are intended for service/operator use, not public browsing. Pseudonymous IDs still link activity and should not be treated as anonymous data.
No service or browser storage is guaranteed to be secure. Do not submit secrets or information you are not authorized to share.
8. Children
The site is a general technical publication, not a service directed at children. We do not request a date of birth and do not operate an age-verification or verified parental-consent system. Young readers should use the site with a parent or guardian and avoid submitting personal information. If you believe a child's personal information has been submitted, email us so we can investigate and address the records under applicable law. No GoLinuxCloud account needs to be closed to make that request.
9. Browser privacy signals
The website's own scripts do not currently implement a general response to Do Not Track (DNT) or Global Privacy Control (GPC). Advertising providers may separately process privacy signals through their own systems. We do not claim that such signals disable GA4 or chatbot logging. This describes current behavior and does not limit any rights you have under applicable law.
10. Cookies and similar technologies
We use cookies, localStorage and sessionStorage for the functions described in the Cookie Policy. The policy lists the actual first-party storage keys, common GA4 cookies, provider-managed storage and browser controls. We do not currently offer a site-wide category selector or set a first-party cookie_consent preference cookie.
11. Embedded third-party content
Some pages contain externally hosted videos, code or other content. Loading an embed can send your IP address, browser headers and request information to that provider before you interact with it. An embed may use cookies or similar storage. The particular provider depends on the article; its terms apply alongside our explanation of why it is included.
12. International processing
GoLinuxCloud is operated from India. Our infrastructure, analytics, advertising, email, comment and execution providers may process information outside your country, including in the United States and other locations. Provider policies linked in this notice describe their processing and relevant safeguards. Contact us for information about arrangements relevant to your request; we do not promise that all website or chatbot data stays in India.
13. US State Privacy Rights
Depending on the applicable state law and whether its coverage requirements are met, you may have rights to access, correct or delete personal information, obtain a copy, and opt out of sale, sharing or certain targeted advertising. You may also have appeal and non-discrimination rights.
We do not sell AI Bot chat records or use them for cross-context behavioral advertising. This statement is specific to chatbot data; advertising providers' processing is described separately. Send requests to admin@golinuxcloud.com.
14. EEA and UK privacy rights
Where applicable, your rights may include access, rectification, erasure, restriction, objection, portability and withdrawal of consent for processing based on consent. You may complain to your relevant data-protection supervisory authority.
Requests are generally handled free of charge. Charges or refusals are limited to circumstances permitted by law, such as manifestly unfounded or excessive requests. The usual GDPR response period is one month, with permitted extensions explained when applicable.
15. India and other jurisdictions
As an India-based operator, we handle requests under applicable Indian law and other laws that apply to our processing. India's Digital Personal Data Protection framework has phased commencement dates; the rights and obligations applicable to a request depend on the provisions in force at that time. Readers elsewhere may have additional rights under local law.
For privacy concerns or grievances, contact Deepak Prasad at admin@golinuxcloud.com.
16. Objection and withdrawal
You can contact us to object to processing where applicable, or withdraw consent where processing relies on it. Withdrawal does not change the lawfulness of earlier processing. Browser controls can limit future requests or storage, and provider controls may apply to advertising, Google Analytics or GitHub. These controls do not themselves remove existing server records.
17. How to exercise your rights
Email admin@golinuxcloud.com, preferably with the subject Privacy request, and explain the information or activity concerned. For AI Bot records, an approximate date/time, article URL and a short non-sensitive description can help us locate the relevant activity. We may need proportionate additional information to verify the request; pseudonymous records cannot always be linked to an email address.
Do not email your signed browser cookie, passwords, access tokens or other credentials. The chatbot has no public server-history export or deletion button. We will explain what can be located, what action applies, and any lawful limitations. Removing a local conversation or cookie does not submit a server deletion request.
18. Following site updates
You can follow our public feeds or linked social accounts. The current site does not provide an email newsletter sign-up form. Following or contacting us through another platform is also subject to that platform's privacy practices.
19. Changes to this notice
We will update the date on this page when these practices or descriptions change. Where applicable law requires additional notice or consent for a change, publishing a revised policy alone does not replace that requirement.
20. Your choices
You can read articles without submitting a question, rating, comment or code-execution request. Automatic infrastructure, analytics and advertising processing is described above. This policy is an explanation of that processing, not a blanket consent agreement or a waiver of your rights.
21. Contacting us
GoLinuxCloud — Deepak Prasad, India
Email: admin@golinuxcloud.com
Contact information: Contact Us