Trust & Safety

Who runs ZabiTech Community?

ZabiTech Community is an independent educational project maintained by its founder. It publishes learning resources about programming, web development, Python, JavaScript, cybersecurity, AI, and related technology topics. The community is intended to make useful learning material accessible to beginners and students.

For questions about the project, its policies, or a concern about something published on the site, use our Contact page or email zabitechcommunity@gmail.com.

What information may be processed?

The public tutorials can generally be read without submitting an account profile. If you use account or community features, the information processed may include the categories below. The details depend on the feature you use and the configuration actually deployed.

Hosting or security providers may also process technical request data, such as requested pages, browser information, timestamps, IP-related network information, or service errors. Optional usage analytics may process additional page-view or performance information if those tools are enabled. We do not sell personal information or intentionally use it to build cross-site advertising profiles.

Read the Privacy Policy for fuller information about data use, service providers, retention, and privacy requests.

Accounts and authentication

Where account features use Firebase Authentication, that service manages the authentication flow and credentials. We do not intend to store readable passwords in ordinary community posts or user-profile documents. Never send your password or sign-in verification code to us by email or in a public post.

You should use a strong, unique password and keep access to your email account secure. If you suspect someone else has accessed your account, contact us and follow the available recovery steps for the authentication method you use.

Database rules and technical security

Account and community data may be stored in Cloud Firestore. Access to that data depends on the application code and the Firebase Security Rules deployed to the project. The rules should restrict reads and writes according to the user's identity, role, and the purpose of each collection. Public pages and policy statements alone cannot prove those rules are correct; they must be reviewed and tested in Firebase.

• HTTPS: pages should be served securely over HTTPS.
• Authentication: Firebase Authentication may handle sign-in for supported account features.
• Authorization: Firestore Security Rules must enforce which records each user can read or change.
• Least privilege: administrative access and service credentials should be limited to those who need them.
• Updates: application dependencies and deployment configuration should be reviewed and maintained.

Firebase web API keys are generally project identifiers, not secret passwords. Google explains that access to Firestore data is governed by Security Rules and related security controls, not by hiding the client API key. Keys for other services, service-account credentials, private keys, and tokens must be handled according to their security requirements. See the official Firebase API key guidance.

These are the security principles we aim to follow, not a claim that an independent security audit has certified the live system. No website can guarantee perfect security.

Community content and moderation

Information you submit as an article or community post may be reviewed before publication and may become visible to other visitors if approved and published. Do not include private personal details, passwords, secret keys, copyrighted material you do not have permission to share, or instructions intended to harm other people or systems.

We may review, restrict, edit for moderation, or remove submissions that violate the website's rules, pose a security or privacy risk, or are otherwise unsuitable for the learning community. If you believe published content exposes private information or creates a safety issue, report it using the Contact page.

ZaBiFetch and software download safety

ZaBiFetch is a separate Windows desktop project associated with the founder. The official project repository is github.com/Zabi178/ZaBiFetch. Use the repository's official Releases section when obtaining a release, and read the release notes before running downloaded software.

An open-source repository allows code to be inspected, but that alone does not prove that every downloadable binary is harmless or built from the exact source code shown. Before running an executable, check its origin, scan it with a reputable security tool, review any operating-system warning, and only proceed when you trust the source. Do not download copies from unknown mirrors or file-sharing sites.

Software behavior can change between versions. For precise claims about network access, telemetry, bundled components, supported sites, or other application behavior, consult the source code and documentation for the specific release you are using. ZabiTech Community does not represent a download as risk-free merely because it is hosted on GitHub.

Advertising and sponsorship

At the time of this policy update, ZabiTech Community does not intentionally serve third-party advertisements on its learning pages. We do not sell personal information to advertisers. If this changes, we will update this page to identify the relevant advertising or sponsorship arrangement and explain any related data practices.

Be cautious if you see a suspicious pop-up, fake download button, or unexpected redirect. It could be caused by a browser extension, another program on your device, or a third-party site. Do not enter credentials or install software from an unfamiliar prompt. If the behavior appears to originate from our website, report the page and steps to reproduce it.

Account deletion and data requests

You may contact us to request access to, correction of, or deletion of personal information associated with your account or submissions. Email zabitechcommunity@gmail.com with the subject Privacy Request. We may need to verify that the request relates to you. We will review the request and take reasonable steps for information under our control, subject to applicable law, technical limits, and legitimate security or recordkeeping needs.

Deletion from the live application does not necessarily erase every copy in backups, security logs, or provider-managed systems immediately. For more detail, see the Privacy Policy.

How to protect yourself

• Use a unique password and never share one-time sign-in codes.
• Download applications only from their official repository or verified release page.
• Do not run unknown scripts or installers with administrator privileges.
• Keep your browser, operating system, and applications updated.
• Do not post private information, access tokens, API secrets, or other people's personal data.
• Check links and domain names carefully before signing in or downloading a file.
• Report suspected account compromise, exposed private data, or a suspicious website behavior.

Report a security or privacy concern

If you discover a suspected vulnerability, exposed information, or a problem with a published page, contact zabitechcommunity@gmail.com or use our Contact page. Include the affected URL, a short description, and safe steps to reproduce the issue if possible.

Please do not access other users' data, disrupt the service, or publish sensitive details while reporting a problem. We will review the report and respond when we can. We do not promise a fixed response or resolution time for every report.

Contact and related policies

For privacy questions, read our Privacy Policy. For site terms, read our Terms. For direct assistance, email zabitechcommunity@gmail.com or visit the Contact page.

Trust depends on accurate information and working technical controls. This page describes the principles and intended practices of ZabiTech Community; statements about implementation should be kept aligned with the live website, Firebase rules, enabled integrations, and the specific software releases offered to visitors.