Skip to content
ZabiTechCommunity
Home Community Dashboard Contact Us Login Signup

Privacy Policy

This page explains what information may be processed when you use ZabiTech Community, including its programming tutorials, account features, and community submissions.

Last updated: October 20, 2026

On this page

  1. 1. Who We Are and Scope
  2. 2. Information You Provide
  3. 3. Technical Information and Analytics
  4. 4. How We Use Information
  5. 5. Sharing and Service Providers
  6. 6. Cookies and Browser Storage
  7. 7. Security
  8. 8. Retention and Deletion
  9. 9. Your Choices and Privacy Requests
  10. 10. Children's and Young Users' Privacy
  11. 11. External Links
  12. 12. International Processing
  13. 13. Changes to This Policy
  14. 14. Contact Us

1. Who We Are and Scope

ZabiTech Community is an independent educational website that publishes learning resources about programming, web development, Python, JavaScript, cybersecurity, and related technology topics. This policy applies to the public website and to account or community features provided through the site.

The site is maintained by its founder and is intended to make technology education accessible. Some pages can be read without an account. If you use an account, contact us, or submit community content, additional information described below may be processed.

This policy describes our intended data-handling practices in plain language. The exact information processed can depend on which features are enabled, how you use the site, and the settings of the hosting or service providers involved. Please do not submit passwords, government identity numbers, payment details, or other sensitive information through an article submission or ordinary contact message.

2. Information You Provide

Depending on the feature you use, information you provide may include:

  • Account information: an email address and display name when you create or use an account.
  • Community submissions: article titles, categories, text, code examples, and other content you choose to submit.
  • Support messages: the email address and message content you send when contacting us.
  • Messages or feedback: information you voluntarily include when reporting a bug, requesting help, or suggesting an improvement.

Do not include credentials, private keys, authentication codes, or confidential information in public posts or support messages. If a community feature allows content to be published, information in that content may be visible to other visitors after publication.

If Firebase Authentication is used for your account, authentication credentials are handled through that service. We do not intend to store readable passwords in community article documents or ordinary user-profile fields.

3. Technical Information and Analytics

When you visit a website, the hosting, delivery, and security services involved may process technical request information needed to deliver pages, prevent abuse, diagnose faults, or maintain service reliability. Depending on the service and configuration, this may include the requested URL, time of request, browser or device information, referring page, network information such as an IP address, and error or security events.

The website is hosted using Cloudflare Pages. Account and community features may use Firebase Authentication and Cloud Firestore. These providers may process technical or service data as part of delivering their services; their own privacy documentation explains their practices in more detail.

Site usage or performance measurements may also be processed if analytics or diagnostics features are enabled in the deployed website or hosting configuration. The specific data collected depends on the tool actually enabled. We do not intentionally use analytics to sell personal information or build cross-site advertising profiles. We do not claim that Google Analytics or Firebase Analytics is active unless the corresponding integration is actually enabled in the live site.

We use technical information, where available, to keep the site working, understand errors, protect the service, and assess whether pages load properly. We do not ask visitors to provide an exact home address, telephone number, or government identity number to read public tutorials.

4. How We Use Information

Information may be used for the following purposes:

  • Provide account access and operate community features.
  • Display, review, moderate, and manage submitted articles or other community content.
  • Respond to questions, support requests, and reports.
  • Maintain site availability, troubleshoot technical problems, and help prevent spam or abuse.
  • Understand broad site performance or content usage where relevant tools are enabled.
  • Communicate important service, safety, or policy changes when reasonably necessary.
  • Meet applicable legal obligations and protect the rights, security, and integrity of the service.

We do not sell personal information. We do not intend to use account email addresses for unsolicited marketing. If we introduce an optional newsletter or similar communication, we will explain how to subscribe and how to stop receiving it.

5. Sharing and Service Providers

We do not sell, rent, or trade personal information to data brokers or advertisers. We may share or allow processing of information by service providers where needed to operate the site, such as:

  • Cloudflare Pages: website hosting, delivery, and related operational or security functions.
  • Firebase Authentication: account authentication, if enabled for the feature you use.
  • Cloud Firestore: account-profile and community data, where used by the application.
  • Email provider: handling messages sent to our published support email address.
  • Analytics or diagnostic providers: only if such tools are actually enabled in the deployed service.

Providers process information under their own service terms, privacy documentation, and applicable arrangements. We do not make a blanket claim that every provider or every configuration automatically satisfies every privacy law. We aim to use services appropriate to the information and functions involved.

Information may also be disclosed where we reasonably believe disclosure is required by law, necessary to respond to a valid legal request, or needed to protect users, the public, or the security of the site.

6. Cookies and Browser Storage

The website or its integrated services may use browser storage technologies, including cookies or local storage, to support functions such as authentication persistence, security, interface preferences, or other features you choose to use. The specific technologies depend on the code and service configuration active on the page.

We do not intend to use advertising cookies to follow you across unrelated websites. Browser settings can usually be used to block or clear cookies and site storage, but doing so may sign you out, reset preferences, or prevent some account features from working. Clearing browser storage does not necessarily delete information already held by a service provider or in a community database.

Browser privacy signals such as “Do Not Track” are not interpreted consistently by all services. Do not assume that enabling such a signal disables all hosting logs or every optional analytics feature.

7. Security

We use third-party infrastructure and application controls intended to protect the service. HTTPS helps protect information while it travels between your browser and the website. Firebase states that supported Firebase services encrypt data in transit and that several services, including Cloud Firestore and Firebase Authentication, also encrypt data at rest. The protections available to a particular record depend on the service and configuration.

Where Firebase Authentication is used, Firebase manages the authentication credentials. Access to Firestore data depends on the deployed Firebase Security Rules and application design. Those rules must be configured and tested correctly; a statement on this page does not by itself prove that every database rule is secure.

We take reasonable steps to avoid unnecessary collection and to limit access to data used for operating the site. However, no website, application, network, or storage system can be guaranteed completely secure. Use a unique password, keep your own devices updated, and never share sign-in codes or credentials.

8. Retention and Deletion

We keep information for as long as it is reasonably needed for the purpose for which it was collected, such as maintaining an active account, displaying a published community article, responding to a support request, addressing abuse, or meeting applicable obligations. Retention periods can differ by type of information and by the provider that processes it.

If you request account deletion, we will review the request and take reasonable steps to delete or de-identify personal information under our control where appropriate and technically feasible. Some public submissions may need separate handling so that the request is clear about whether the content should also be removed. Copies in backups, security records, or provider-managed systems may persist for a limited period under their applicable retention processes.

Support correspondence may be retained while needed to resolve the issue and maintain appropriate records. Analytics or operational data, if present, may be retained according to the settings and retention practices of the service that collected it. We do not promise an exact deletion period for every system or backup unless that period is specifically confirmed for the relevant system.

9. Your Choices and Privacy Requests

Subject to applicable law and the design of the feature, you may ask us to:

  • Explain what account or community information we hold about you.
  • Correct inaccurate account information, such as a display name.
  • Delete or de-identify account information or submitted content under our control.
  • Provide a copy of certain information you have submitted, where feasible.
  • Consider an objection or restriction request where an applicable privacy law provides that right.

Email zabitechcommunity@gmail.com with the subject Privacy Request. Tell us which account or content the request concerns, but do not send your password or authentication codes. We may ask for reasonable information to verify that the request relates to you before making changes. We aim to respond promptly; the response time may depend on the nature and scope of the request and the rules that apply.

The rights available to you can depend on your location and the applicable law. This policy is not a claim that every privacy statute applies to every visitor or that a particular legal status has been certified.

10. Children's and Young Users' Privacy

ZabiTech Community publishes educational material for students and other learners. Account and community features are not intended for children under 13 to use independently. We do not knowingly seek personal information from children under 13 through account features. If you are under 13, do not create an account or submit personal information without a parent or guardian's involvement and any permission required by applicable law.

If you believe a child has submitted personal information inappropriately, contact us at zabitechcommunity@gmail.com. We will review the report and take appropriate steps where we can verify the information and have a basis to act.

11. External Links

Tutorials may link to external websites, documentation, repositories, or tools such as MDN Web Docs, Python.org, GitHub, and other learning resources. Those websites operate under their own policies and practices. Once you leave ZabiTech Community, review the privacy and security information of the destination before submitting information or downloading files.

A link to an external service is provided for convenience or educational context and is not a guarantee that every page, download, or third-party service is safe or suitable for every use.

12. International Processing

Cloudflare, Google, and other service providers may process technical or account-related information in countries other than the country where you live. The locations and safeguards involved depend on the services used, their configuration, and their applicable terms. We do not promise that every item of information is stored in Pakistan or that all providers use the same transfer mechanism.

Provider-specific information is available in the providers' own privacy and security documentation. Avoid submitting highly sensitive information through ordinary site forms or public community posts.

13. Changes to This Policy

We may update this policy when the website, its features, or its data practices change. The “Last updated” date at the top will be revised when the policy changes. For material changes, we will consider an appropriate notice through the website or another available communication channel.

Please review this page occasionally. If a new feature introduces a materially different type of collection or a new analytics or advertising provider, this policy should be updated to explain that change.

14. Contact Us

For questions about privacy, account data, a deletion request, or a concern about this policy, email zabitechcommunity@gmail.com with the subject Privacy Request, or use our Contact page.

Please include enough information for us to understand the request, but do not include passwords, authentication codes, private keys, or unnecessary sensitive personal information.

ZabiTech Community aims to handle information thoughtfully, collect only what is needed for the features in use, explain the role of service providers, and respond to reasonable privacy questions. If our implementation changes, this policy must be kept aligned with the actual website and its integrations.

© 2026 ZabiTech Community — Free Coding Education in Programming, Web Development, AI & Cybersecurity

About Trust & Safety Privacy Policy Contact Terms