VritraSec logo

VritraSec

vritra security organization

Privacy Policy

How VritraSec Protects Your Data and Privacy

Privacy Statement

At Vritra Security Organization ("VritraSec"), your privacy is our top priority. This Privacy Policy explains how we collect, use, and protect your information when you use our tools, services, and software. We are committed to maintaining transparency and ensuring your data remains secure.

1. Mini Tools Input and Output Privacy Policy

1.1 Client-Side Processing Architecture

All mini tools provided by VritraSec - including QR Code Generator, Password Generator, UUID Generator, Base64 Encoder/Decoder, Hash Converter, JSON/CSV Converter, IP Lookup, EXIF Data Viewer, and others - are developed using pure JavaScript intended for client-side execution. These tools function entirely within the user's browser without relying on any server-side backend for input processing, computation, or result generation. This architecture ensures that the user's data never leaves their local environment during tool usage.

1.2 No Transmission of Input to VritraSec Servers

Any data entered by the user (text, numbers, images, code snippets, IPs, etc.) is processed in real-time inside the browser and is not transmitted, logged, or mirrored to VritraSec servers. We do not utilize any background network requests, AJAX calls, WebSockets, or hidden APIs that could transfer user input or result data to any part of our infrastructure. The data resides strictly in volatile browser memory and is discarded automatically when the session ends or the page is refreshed.

1.3 Output Generation and Temporary Data Scope

Tool outputs - such as hashed values, random passwords, encoded strings, UUIDs, or base64 strings - are generated in-browser and presented as direct output without persistence. When users choose to download data (like QR codes or converted files), they are created locally using Blob/File APIs and streamed directly to the user's device without being uploaded anywhere. All outputs remain temporary, session-bound, and private unless the user explicitly saves or shares them.

1.4 No Tracking, No Cookies, No Session Logs

We do not include any tracking frameworks, fingerprinting scripts, analytics beacons, or telemetry systems within our mini tool pages. VritraSec does not use Google Analytics, Facebook Pixel, Hotjar, or any similar services in any mini tool. No cookies, localStorage, or sessionStorage elements are deployed to track user interactions, revisit behavior, or device/browser identity.

1.5 Input Privacy in File-Based Tools (EXIF/QR Tools)

For tools like EXIF Metadata Viewer or QR Code Decoder which accept user-uploaded images or files, all processing occurs locally in the browser via FileReader and Canvas APIs. Images or files uploaded into these tools are never sent to VritraSec servers. No backup, log, or history of such uploads is maintained. Users are encouraged to avoid sensitive files when using such tools in shared or public devices.

1.6 Isolation and Execution Security

Each tool is loaded in a sandboxed browser environment that enforces origin policy and DOM isolation. No tool has access to other browser tabs, external sessions, or hardware-level APIs like clipboard, microphone, camera, or geolocation. This ensures every interaction remains secure and confined to a single isolated execution context.

1.7 User Responsibility for Output Handling

Users are solely responsible for saving, copying, storing, or using the generated output. VritraSec holds no liability for any data loss, leakage, or misuse resulting from user-side activity such as copy-paste errors, screenshot sharing, shared system access, or output reuse. It is strongly advised that users do not use these tools on public devices if the data is sensitive.

1.8 Error Events and Logging Transparency

Any tool malfunction, client-side crash, or browser-specific compatibility issue is handled entirely within the user's browser. We do not capture crash reports, stack traces, input content, or error logs automatically. If a user voluntarily submits a bug report, they may include screenshots or logs at their own discretion. We do not solicit such data automatically and do not connect these reports to any session identity.

1.9 No Identity Association or License Linking

Mini tool usage is 100% anonymous and is not tied to any license key, purchase record, Telegram ID, IP address, or browser identity. We do not link these tools to user sessions, accounts, or cookies. Tool usage has no authentication mechanism and does not require login or token validation of any kind.

1.10 Future Commitment to Client-Side Integrity

VritraSec commits to maintaining all current mini tools as client-side-only and non-tracking. In the event that future tools require server communication (e.g., for AI-based processing or third-party API use), users will be clearly informed, and the tool will include a disclosure prompt. No hidden server transition will occur without prior notice.

2. Third-Party API Disclosure

2.1 Use of Public APIs in Select Tools

While the majority of mini tools on the VritraSec platform operate entirely within the user's browser, certain tools may rely on third-party public APIs to fulfill their intended functionality. These APIs are used solely to provide accurate and real-time processing for specific input types that require external validation, conversion, or data lookup.

Tools that currently utilize external APIs include IP-related utilities and similar modules where local processing is not feasible.

2.2 Scope of Data Shared

Only tool-specific and functional data is shared with these APIs. For example:

  • An IP address entered by the user may be sent to an API to retrieve geolocation or ASN data.

No personally identifiable information (PII), license keys, device identifiers, or session tokens are ever transmitted to third-party APIs.

2.3 Transparency of API Use

We strive to clearly disclose all tools that make use of third-party APIs. Where applicable, the name or link of the API provider is either:

  • Displayed on the tool interface,
  • Mentioned in documentation,
  • Or outlined in this Privacy Policy.

Users are encouraged to review the privacy policies of these providers independently. VritraSec is not responsible for how third-party services handle the data they receive through such queries.

2.4 Nature of APIs Used

All APIs integrated into our tools are:

  • Publicly accessible and do not require API keys, user authentication, or session tracking
  • Stateless and do not store any identifiable information
  • Used solely for single-use, real-time data processing

We explicitly avoid APIs that:

  • Require user accounts, tokens, or cookies
  • Track users across sessions or sites
  • Build behavioral profiles or analytics from queries

2.5 Consent Through Use

By voluntarily submitting data in tools that use external APIs, the user consents to sharing that specific input with the respective API provider solely for output generation. If you do not wish to share input with any third-party service, please refrain from using such tools, which will always be labeled accordingly.

2.6 No Caching, Retention, or Linking

API responses are processed live and are not cached, stored, or linked to any user information such as IP address, device ID, or browser session. All results are transient and vanish upon page refresh or close. VritraSec does not log or retain any request/response data from such interactions.

2.7 Future API Integration Policy

Any future tools that rely on third-party APIs will include:

  • A clear label or warning near the relevant input field,
  • An update to this Privacy Policy,
  • And, where feasible, an option to choose a local (offline) processing method.

VritraSec remains committed to full user transparency and will never silently share any input with external APIs without explicit notice.

3. No PII or Behavioral Tracking in Tools

3.1 No Personally Identifiable Information (PII) Collection

VritraSec's publicly available tools do not collect, require, or request any form of personally identifiable information (PII) from users. At no point during the use of our mini tools are users asked to provide their:

  • Full name
  • Email address
  • Phone number
  • Physical address
  • Government-issued identification
  • Cryptocurrency wallet keys or credentials

All tools are designed to function without any need for user authentication, registration, or profile creation. We do not offer or enforce any form of user login, and no user accounts exist in our infrastructure.

3.2 No Behavioral Tracking Mechanisms

Our tools and static web pages do not utilize behavioral analytics, visitor profiling systems, or interaction-based trackers. Specifically:

  • We do not track mouse movement, scroll depth, or page navigation behavior.
  • We do not log or analyze tool usage frequency, button clicks, typing speed, or error frequency.
  • There is no heatmapping, session replay, or behavior re-targeting logic present in any part of our website or embedded tool interfaces.

Tools operate in a stateless and anonymous environment by design. Every user interaction is independent and unlinked to any previously collected data, IP address, or session identifier.

3.3 Limited Use of Analytics Frameworks

VritraSec uses Google Analytics 4 (GA4) on select informational pages only to measure general website performance and improve user experience. Analytics is not embedded within mini tools, software dashboards, or API-based utilities.

We intentionally avoid behavioral analytics services such as:

  • Facebook Pixel
  • Hotjar
  • Mixpanel
  • Yandex Metrica
  • Cloudflare Analytics (for behavioral data)

No browser fingerprinting or deep behavioral profiling is used. See Section 3A for complete Google Analytics disclosure.

3.4 Zero Use of Tracking Cookies or Persistent Identifiers

Our site does not store or access any cookies, localStorage, sessionStorage, or indexedDB entries related to tool usage or identity. We do not generate or assign user IDs, UUIDs, or tokens to associate activity over time. Every visit is considered a new anonymous session.

3.5 No Cross-Site or Cross-Session Linking

User interactions are not linked across sessions, devices, or tools. If a user uses multiple tools in succession, we do not log the sequence, IP, or context of that usage. There is no tracking of navigation patterns or behavioral profiling across tools or pages.

3.6 Focus on Stateless Utility

Every mini tool provided by VritraSec is built on a stateless architecture. Each page load or refresh resets the tool environment completely. No hidden data remnants or usage trails are preserved beyond the immediate client-side memory scope.

3.7 Assurance of Privacy by Design

The principle of "Privacy by Design" is applied across our tool development process. At no stage is data collection, behavioral logging, or identifier tracking baked into the functionality or interface logic of our utilities. The entire framework is intentionally built to provide output without requiring or storing any personal data or behavioral insights.

3A. Google Analytics & Aggregate Data Policy

3A.1 Purpose of Analytics

To improve user experience and understand general website performance, VritraSec uses Google Analytics 4 (GA4) on select informational pages only. This helps us measure page traffic, performance trends, and system health โ€” without identifying individual users.

3A.2 Data Collected (Anonymous)

GA4 collects basic, non-personal metrics such as:

  • Page views and navigation paths
  • Device type (mobile/desktop)
  • Country (approximate region only)
  • Referring sources (e.g., search engines)

All IP addresses are anonymized before processing, and no personally identifiable information (PII) or tool-generated data is transmitted.

3A.3 No Cross-Linking with Tools or Licenses

Analytics data is entirely separate from software license logs, Telegram interactions, or any tool usage. GA4 tracking is not embedded within mini tools, software dashboards, or API-based utilities.

3A.4 Opt-Out & Control

Users can opt out of analytics collection by:

  • Using browser add-ons such as Google Analytics Opt-out Add-on ,
  • Blocking analytics scripts through browser privacy settings or extensions (e.g., uBlock, NoScript),
  • Or disabling cookies entirely โ€” tool functionality remains unaffected.

3A.5 Data Retention

Analytics data is aggregated and retained by Google for statistical analysis only. We do not export, resell, or combine it with any form of identifiable data.

For more details on how Google handles analytics data, visit Google Privacy Policy .

4. Form-Free Interaction Confirmation

4.1 No Forms or User Registration Mechanisms

All tools and utilities hosted under the VritraSec platform operate without requiring users to fill out forms of any kind. This includes but is not limited to:

  • No user sign-up or account creation process
  • No login screens or credential input fields
  • No subscription prompts or email capture boxes
  • No embedded forms for feedback, queries, or support

Users are never asked to disclose any personal information such as names, email addresses, mobile numbers, or any other identifiers as part of tool usage.

4.2 Voluntary Contact Exception

The only scenario in which VritraSec may receive user-identifiable data is if a user voluntarily reaches out through one of our public communication channels, such as:

  • Direct email contact
  • Telegram bot or channel message
  • Feedback request via linked support platform

In such cases, the data is treated strictly for the purpose it was submitted (e.g., support, inquiry, or clarification) and is never linked with any tool usage, retained beyond the resolution, or sold/shared with third parties.

4.3 No Automatic Data Capture via UI

Since there are no interactive forms embedded in the tool interfaces:

  • There is no browser autofill trigger or data collection
  • There are no hidden form inputs capturing device or user information
  • There is no JavaScript-based form logging or field interaction tracking

User engagement is entirely form-free and anonymous by default, ensuring that no personal data can be harvested even passively.

4.4 Purpose-Bound Communication Only

All communication initiated by users is treated under the principle of purpose-limited handling. For example:

  • If a user emails regarding license validation, the email will be used solely for resolving that specific issue.
  • If a Telegram contact is made for technical help, the chat data is reviewed only for technical context and not stored beyond resolution.
  • We do not use voluntary contact to trigger promotional emails, remarketing, or behavioral tracking of any kind.

VritraSec maintains a strict no-marketing, no-retargeting policy when it comes to user-submitted data - including data received voluntarily.

6. Telegram Bot Message Logging

6.1 Temporary Message Logging for Support and Validation

To ensure seamless support, license verification, and abuse prevention, our Telegram bots may temporarily log the following non-sensitive metadata when a user interacts with the bot:

  • Telegram User ID (numerical only)
  • Username (if public)
  • Messages/queries submitted to the bot
  • License key (if provided for activation or verification)

These logs are used solely for internal diagnostics and resolving user-specific issues, such as:

  • Verifying a user's license validity
  • Resolving complaints or issues raised during chat
  • Handling duplicate activation or misuse reports

No sensitive personal data (like name, phone number, or location) is extracted unless explicitly shared by the user during a support request.

6.2 Retention and Auto-Deletion Policy

All Telegram bot logs are handled with strict retention boundaries:

  • Maximum storage duration: 60 days from message timestamp
  • Auto-deletion triggers:
    • Upon issue resolution (support ticket closed)
    • Or when 60 days have passed - whichever comes first

These records are automatically purged using a scheduled cleanup system, ensuring no historical trail of past interactions is retained beyond necessity.

6.3 No Third-Party Access or Analytics Integration

We do not share bot chat logs with any external platform or analytics service. Logs remain stored in a secure private environment with limited access, strictly for operational and support usage.

There is no integration with Telegram Ads, third-party CRM tools, or behavioral analytics trackers.

6.4 Full Compliance with Telegram Bot API Guidelines

Our logging system fully adheres to Telegram Bot API Terms of Service and complies with:

  • User privacy expectations as per Telegram's privacy model
  • Data minimization principles, logging only what's essential
  • No persistent surveillance or profile building

By design, all messages are handled in a stateless, session-isolated manner, ensuring user privacy is prioritized at every step.

7. Software License Log Policy

7.1 Data Captured During Activation

When a user activates any of our licensed software products (including but not limited to CryptoHunterX, CrackBTC, or CryptoCraX), the system automatically logs a minimal set of non-PII technical data for license verification and fraud prevention purposes. This includes:

  • License Key entered by the user
  • Device Fingerprint (a hashed unique identifier generated using hardware + OS attributes)
  • IP Address used during activation
  • Timestamp of activation
  • Software Version being activated

This logging process occurs only once during activation or re-activation events, and is used solely for backend validation, not for marketing, profiling, or analytics.

7.2 Purpose of Logging

This data is collected to:

  • Prevent license key abuse across multiple devices beyond allowed limits
  • Enable deactivation or revocation in case of piracy or EULA violations
  • Provide users with support regarding failed activations or lost keys
  • Maintain transparency in license usage for refund/dispute resolution

It helps us maintain the integrity of our licensing model and ensures fair usage for all genuine users.

7.3 Secure Storage and Access Controls

All license-related logs are stored in secure, encrypted databases and protected using:

  • AES 256-bit encryption at rest
  • Strict access control lists (ACLs) to limit internal access
  • Zero external sharing with third-party services or cloud APIs

We do not store your actual system files, browsing activity, or any unrelated user data. Only the technical metadata mentioned in 7.1 is stored.

7.4 Retention Policy and Expiry

License logs are retained for the entire active lifecycle of the software, and up to 12 months after expiration or deactivation. This retention helps in handling:

  • License recovery requests
  • Upgrade/migration assistance
  • Legal or payment-related disputes

After this period, logs are permanently deleted via automated data purging routines.

7.5 Compliance and User Trust

We ensure that all license logging is done in accordance with:

  • Data minimization best practices
  • Purpose limitation - no use beyond fraud prevention and license tracking
  • User transparency - all license-based interactions are covered under this policy

Activation never results in monitoring of personal files or application usage behavior.

8. Donation Transparency & Anonymity

8.1 No Tracking of Donor Wallets

We maintain a strict zero-tracking policy for all donations made to our public crypto wallet addresses. When a user donates using BTC, ETH, USDT, or any supported coin/token, we do not attempt to trace, cluster, link, or analyze the donor's wallet address or transaction history.

We do not use blockchain analytics, wallet profiling, address tagging, or any third-party service to associate donations with user activity or identity.

8.2 Purely Voluntary and Anonymous

Donations are entirely optional and serve as a gesture of support. Unless a donor explicitly self-identifies (e.g., by emailing us or messaging our Telegram bot with proof of donation), the transaction remains fully anonymous. We do not require any user to link a license key, name, or email to a donation.

If a donor chooses to reveal their identity for support or shoutout purposes, it will be treated confidentially and only used for that context.

8.3 No Behavioral Profiling or Follow-up

We do not:

  • Contact donors after a transaction
  • Assign any account-based benefits or tracking
  • Perform any behavioral profiling or marketing outreach based on donation history

Our tools, websites, and communication channels remain donation-agnostic, ensuring unbiased access and treatment for all users.

8.4 Public Ledger Acknowledgment

As with any cryptocurrency transaction, donations are recorded on a public blockchain ledger. However, we reiterate that we do not correlate those public records with personal user data or sessions on our platform.

Users may freely inspect our donation wallet history through any block explorer, but we take no additional steps to identify or log sender information from our end.

8.5 Donation Usage Statement

Funds received through donations are used for:

  • Covering server costs, API keys, and infrastructure
  • Supporting open-source tool development
  • Future upgrades, security, and free tool enhancements

We do not use donations for advertising, third-party data purchase, or monetization of user data.

This transparency ensures that privacy-respecting users remain untracked, even while supporting our mission.

9. Tool Abuse Detection

9.1 Basic Rate Limiting Measures

To ensure fair usage and maintain performance of publicly accessible tools, we implement basic abuse prevention mechanisms, such as:

  • Request rate limits per IP address
  • Temporary cooldowns on repeated excessive usage
  • Session-based usage caps (when applicable via browser memory)

These measures are applied uniformly and do not involve deep profiling, persistent tracking, or behavioral analysis.

9.2 No Fingerprinting or Tracking

We do not implement device fingerprinting, canvas analysis, hardware detection, WebGL fingerprinting, or other invasive browser-level techniques for identifying users. All abuse detection is purely surface-level and temporary.

We also do not store any long-term behavioral logs, location data, or usage histories linked to individuals.

9.3 Temporary Throttling Only

If a user exceeds safe usage thresholds, they may encounter temporary tool slowdowns or restrictions, but this resets automatically and does not affect other tools or site access.

There are:

  • No permanent bans
  • No cross-tool profiling
  • No license revocations due to tool usage

The goal is strictly to protect uptime, performance, and fairness - without compromising user anonymity.

9.4 No Abuse Logs Stored

Abuse protection measures are handled in-memory or on the server side in ephemeral systems. We do not store abuse-related flags in any persistent user database. Once a temporary limit period expires, all associated data is discarded.

This approach ensures privacy-first usage enforcement, balancing openness with protection.

10. Proof/Media Upload Handling

10.1 Voluntary Submission Only

All customer-provided screenshots, images, or proofs displayed on our website or social platforms are voluntarily submitted by the respective users. We do not force, scrape, or collect media without consent.

Before any image is displayed publicly, the user either:

  • Submits it directly to us via Telegram, email, or chat, and
  • Explicitly or implicitly grants permission to use it as a testimonial or success showcase.

10.2 No Location or Metadata Retention

We respect the privacy of our users beyond just visuals. Any uploaded image is automatically stripped of all embedded metadata, including:

  • EXIF tags
  • GPS coordinates
  • Device information
  • Timestamps

This ensures that no sensitive personal or location-based data is ever exposed via shared media.

10.3 No Automated Extraction or Scanning

We do not auto-process or scan user-submitted media files for content extraction, face detection, OCR, AI clustering, or any other data mining.

  • No AI pipelines run on uploaded images
  • No content indexing, auto-labeling, or re-use without user intent

Each file remains static, untouched, and contextually locked to its testimonial purpose only.

10.4 Removal Request Policy

If at any point a user wishes to withdraw their submitted image or revoke its display, they may request so via our Telegram bot or support channel. Upon verification, the media will be removed within 48 hours without dispute or delay.

This ensures full user autonomy over their content at all times.

11. IP & Geolocation Logs in Tools

11.1 Public Data Processing Only

For tools that perform IP lookups or geolocation queries, we strictly process only publicly accessible IP addresses - either provided by the user manually or auto-detected through standard HTTP headers.

At no point is personally identifiable information (PII) like names, emails, device fingerprints, or behavioral trails associated with IP requests.

11.2 Temporary In-Session Caching

Tool results may be temporarily cached in-session (browser memory) for speed and usability during the same session. However:

  • No logs are stored on our servers
  • No identifiers are attached to the lookup
  • Sessions are not persisted beyond the tab or session scope

This ensures zero user traceability from IP or geolocation data used in tool operations.

11.3 API Discretion

In case a third-party public API is used for data enrichment (e.g., country, ISP, coordinates), only the query-specific IP is sent - never headers, cookies, tokens, or context from the user's browser.

We transparently mention the name of any such service in the tool description when applicable.

12. Tool Output Privacy

12.1 Client-Side Output Generation

All downloadable content generated by our mini tools - including but not limited to QR codes, base64-encoded files, barcodes, hashed strings, UUIDs, and CSVs - are generated entirely on the client-side using JavaScript within your browser.

At no point does this output:

  • Transmit to our servers
  • Get backed up
  • Or get intercepted for analytics or storage purposes

12.2 Zero Storage Policy

We maintain a strict zero-storage policy for all output data generated through tools. This means:

  • Outputs are not cached or retained on the server
  • Files are not auto-sent to any destination unless the user downloads or shares manually
  • Output previews (where shown) are rendered temporarily in-browser

12.3 Full User Control

All generated content remains completely within the user's control unless they choose to download, copy, or share the output themselves.

This ensures complete confidentiality and isolation of tool-generated data.

13. No Login System = No Credential Storage

13.1 Account-Free Architecture

Our platform operates without any user registration, login, or authentication system. As a result:

  • Users are never prompted to create accounts or provide usernames/passwords.
  • No login sessions, access tokens, or credential cookies are created or stored.
  • We do not manage any user credential database, eliminating the risk of password breaches.

13.2 Zero Authentication Dependencies

Because our tools and software delivery system are designed to function without login requirements, we do not rely on:

  • Third-party OAuth providers (like Google, Facebook, etc.)
  • Email/password-based verification flows
  • Captcha or two-factor authentication (2FA)

This simplifies user interaction and reinforces privacy by avoiding any unnecessary data handling.

13.3 No Session or Persistent ID Tracking

In the absence of accounts or logins:

  • No persistent session identifiers (e.g., session tokens, cookies, browser fingerprints) are assigned to users.
  • We do not perform cross-visit or cross-tool identity correlation.
  • Every visit is treated independently, with no historical linkage to prior activity.

This approach ensures maximum anonymity and a frictionless, credential-free experience.

14. Responsibility of Shared Device Use

14.1 User Awareness on Shared Systems

While our tools are designed to prioritize privacy and operate without storing sensitive data, we urge users accessing the platform from shared or public devices (such as cyber cafรฉs, office computers, or school labs) to practice basic digital hygiene.

14.2 Recommended Post-Use Actions

To protect your session inputs and output data, users on shared devices are advised to:

  • Clear browser cache, history, and form data after use.
  • Close all tabs or windows associated with the tool before leaving the device.
  • Avoid downloading sensitive outputs (e.g., QR codes, converted files) unless you can delete them securely after use.

14.3 No Automatic Sanitization Guarantee

While we do not actively store or track session data, your browser or device may temporarily retain elements like:

  • Downloaded files in the "Downloads" folder
  • Auto-filled input entries
  • Recent history or opened tabs

Therefore, the responsibility for post-use cleanup lies solely with the user when operating on non-personal systems.

15. Scripted Automation Disclaimer

15.1 Allowable Use of Automation

Some advanced users may choose to integrate our mini tools or software into automated workflows, such as shell scripts, cron jobs, or API-based systems. While we do not restrict this behavior outright, all forms of scripted access must comply with our fair use and abuse-prevention guidelines.

15.2 Detection of Automated Patterns

To maintain platform integrity and server performance, we reserve the right to monitor request patterns. This includes but is not limited to:

  • Unusually high-frequency calls to tool endpoints
  • Repeated, rapid-fire queries with identical or rotating input values
  • Non-human behavior detection (e.g., headless browsers or script-based requests without delays)

15.3 Flagging and Temporary Rate Limiting

Automated queries may trigger temporary rate limits or flags if the system detects usage patterns resembling bot-driven abuse. If such limits are applied, it does not necessarily imply misuse but may temporarily restrict access for that IP or session to ensure overall system stability.

15.4 No Behavioral Profiling

We do not perform persistent fingerprinting, user profiling, or session history tracking. Only real-time, pattern-based throttling is used to deter abuse.

15.5 Responsible Automation Encouraged

Users are encouraged to:

  • Add randomized delay between automated queries
  • Avoid excessive concurrent threads or brute-force style access
  • Contact support if they require high-volume legitimate use cases

Automation that respects platform resources and privacy boundaries is welcome, but misuse may result in temporary or permanent access blocks.

16. Offline Tool Clarification

16.1 Current Tool Access Mode

As of now, all mini tools provided through our platform are accessible exclusively via an online interface. Users interact with them through a web browser in real-time, and no downloadable or installable versions are distributed by default.

16.2 Future Availability of Offline Tools

In the future, certain tools may be offered as downloadable utilities or browser-installable Progressive Web Apps (PWAs). These versions will allow users to operate tools in a completely offline environment, without requiring an internet connection once downloaded.

16.3 Privacy in Offline Mode

Should any tool be made available in offline mode:

  • No telemetry or usage tracking will be performed.
  • No background connections will be initiated to our servers or third-party APIs.
  • No auto-update or sync behavior will exist unless explicitly enabled by the user.

16.4 User Responsibility

Offline versions may not receive the same real-time improvements, bug fixes, or updated privacy disclosures. Users are encouraged to periodically check the website for the latest versions and changelogs.

16.5 Trust & Transparency

We commit to maintaining the same high level of privacy in both online and offline modes. Any version of our tools that operates locally will adhere to a strict zero-data-backflow policy - meaning that once downloaded, the tool will not transmit any data back to our servers unless the user chooses to manually re-enable cloud features (if any are available in future).

In short: Offline = Private. No data leaves your device.

17. Third-Party CDN or Asset Disclosure

17.1 Use of External Assets

This website uses certain frontend assets served via trusted third-party CDNs (Content Delivery Networks) to improve page load speed, design consistency, and developer efficiency. These assets may include fonts, JavaScript libraries, and icon packs.

17.2 Specific Integrations in Use

  • Google Fonts CDN
    We load the "Outfit" font family via the https://fonts.googleapis.com CDN to ensure uniform typography across devices.
    โžค This request may expose your IP address to Google servers.
    โžค Google may apply its own cookie or tracking policies.
    โžค Google Fonts Privacy Policy
  • Font Awesome (via jsDelivr or kit.fontawesome.com)
    The site uses icons delivered from Font Awesome's CDN to avoid bundling large icon files locally.
    โžค Assets are fetched from https://kit.fontawesome.com.
    โžค The CDN provider may log generic metadata such as IP address or device type.
  • Optional: Other Libraries
    If we use other assets (e.g., jQuery, Chart.js, Lucide Icons, etc.), they may also be delivered via popular CDNs like cdnjs, jsDelivr, or unpkg. All of these are selected from reputable providers with known security practices.

17.3 Why Use CDNs?

We use CDNs for the following reasons:

  • Faster global asset delivery.
  • Lower server bandwidth consumption.
  • Improved site stability and caching.

17.4 What Is NOT Sent

Importantly, when your browser fetches assets via these CDNs:

  • No form data, PII, license key, session info, or tool input is sent to third parties.
  • Only the HTTP request for that asset (e.g., font or JS file) is logged by the CDN.

17.5 Your Rights

If you're concerned about external CDN calls:

  • You can use browser extensions (e.g., uMatrix or NoScript) to block third-party scripts and fonts.
  • For strict privacy, use a browser with hardened privacy settings (e.g., Brave, Firefox with Enhanced Tracking Protection).

17.6 Cookie Usage by CDNs

Our own site does not use cookies for tracking. However, external services (like Google Fonts) may apply their own cookies under their respective policies.
We do not control these cookies and do not use or access their data.

17.7 Future Local Hosting Plan

We are exploring moving all critical frontend assets to self-hosted versions to reduce dependency on external CDNs in future.

In summary:
Some fonts and icons are loaded from trusted CDNs for speed, but we never share user inputs or track you via them.

18. Security Incident Logging

18.1 Purpose of Logging

To maintain platform integrity and defend against potential abuse or exploitation, we implement anonymous security incident logging on our infrastructure.

18.2 What Gets Logged

In case of abnormal or suspicious behavior, the following data points may be temporarily logged:

  • Failed activation/license attempts.
  • Malformed API or tool requests (e.g., invalid parameters, tampered payloads).
  • Excessively high-frequency requests that indicate brute-force attempts or scraping.
  • Requests flagged by rate-limiting systems or Web Application Firewall (WAF).

18.3 Data Collected (Minimal & Anonymous)

The logs may include:

  • IP address (or its hashed representation).
  • Timestamp of the request.
  • HTTP method, endpoint, and status code.
  • Error/debug messages generated during failed interaction.

No personal data, form entries, or tool input values are stored in these logs.

18.4 Retention & Deletion

These logs are:

  • Used strictly for monitoring and preventing attacks.
  • Retained only for up to 30 days unless part of a deeper incident investigation.
  • Automatically purged via scheduled routines after expiry.

18.5 Internal Use Only

Only the infrastructure security team has access to these logs. They are not sold, shared, or linked to any individual user activity.

18.6 Transparency Note

These logs help us detect:

  • Repeated abuse attempts from the same IP.
  • Scripted attacks or enumeration probes.
  • System-level vulnerabilities being targeted.

We do not log regular tool usage or valid input data - only behavior that appears malicious or abnormal is ever flagged for review.

19. Business Transfer / Ownership Clause

19.1 Ownership Continuity

In the event that Vritra Security Organization (VritraSec) is ever involved in a merger, acquisition, sale of assets, or transition of control, we reserve the right to transfer user-related data as part of the transaction.

19.2 Data Types Potentially Transferred

Only the minimal data we collect, as already outlined in this Privacy Policy, may be included in such a transfer. This may include:

  • Activation logs tied to software licenses.
  • Telegram support logs (user ID + query history).
  • Basic infrastructure abuse prevention logs.

We do not collect PII (personally identifiable information) such as names, emails, phone numbers, or passwords - so no such data exists to be transferred.

19.3 Legal & Ethical Boundaries

Any successor entity or new owner will be:

  • Legally bound by this same Privacy Policy until an updated policy is published.
  • Expected to notify users in advance of any significant changes to the data handling approach.

19.4 User Rights

If such a business change occurs, users may:

  • Choose to stop using our tools and services.
  • Request deletion of any identifiable logs (e.g., Telegram history) if applicable.

Quote Summary:
"If VritraSec is ever acquired or merged, collected data may be part of the transferred business assets. However, our commitment to user privacy and minimal data collection remains unchanged."

20. Country-Wise Privacy Rights Summary

20.1 Global Privacy Rights

We respect user privacy across regions and strive to comply with global privacy laws. Below is a summary of key data rights based on major jurisdictions:

๐Ÿ‡ช๐Ÿ‡บ European Union

GDPR (General Data Protection Regulation)

  • Right to access, rectify, or erase your data
  • Right to restrict or object to processing
  • Right to data portability
  • Right to file complaint with local DPA

๐Ÿ‡บ๐Ÿ‡ธ California, USA

CCPA/CPRA (California Consumer Privacy Act / Rights Act)

  • Right to know what data is collected
  • Right to request deletion
  • Right to opt-out of sale/sharing
  • No discrimination for privacy choices

๐Ÿ‡ฎ๐Ÿ‡ณ India

IT Act 2000 + PDPB 2023 (Proposed Digital Personal Data Bill)

  • Right to know what personal data is processed
  • Right to correction & erasure
  • Right to nominate consent manager
  • Right to grievance redressal

๐Ÿ‡จ๐Ÿ‡ฆ Canada

PIPEDA (Personal Information Protection and Electronic Documents Act)

  • Right to access personal information
  • Right to know how it's used and shared
  • Right to request corrections

๐Ÿ‡ฆ๐Ÿ‡บ Australia

Privacy Act 1988

  • Right to access and correct personal information
  • Right to lodge complaint with OAIC

๐ŸŒŽ Global

Universal Data Ethics

  • No behavioral profiling
  • No hidden data sharing
  • Transparent collection and retention policies

Note: VritraSec does not store personally identifiable data like names, emails, phone numbers, or login credentials. Most tools function without account creation, tracking cookies, or external analytics.

20.2 How to Exercise These Rights

You may contact us anytime at contact@vritrasec.com or via our @ethicxbot to:

  • Request deletion of Telegram message logs (if any).
  • Inquire about stored activation logs (software-specific).
  • Raise privacy-related grievances.

We respond to such requests within 7 working days, in line with applicable regulations.

21. Data Request & Erasure Rights

21.1 Request Data Access

At VritraSec, we respect your right to control your data. Even though we do not collect sensitive personal information or force account creation, users still have the option to:

You may contact us via:

  • ๐Ÿ“ฉ Email: contact@vritrasec.com
  • ๐Ÿค– Telegram Bot: @ethicxbot

To request:

  • A summary of any stored data (such as license activation records, tool usage metadata, or Telegram message logs associated with your user ID).
  • Details of past donations (only if voluntarily disclosed by you).

21.2 Request Data Deletion

You may also request permanent deletion of:

  • ๐Ÿ“Ž Uploaded proof/media voluntarily shared for testimonials or support.
  • ๐Ÿ’ฌ Telegram chat logs stored for support/ticket resolution.
  • ๐Ÿงพ Device/license activation records (note: this may deactivate license).

21.3 Identity Check

To prevent unauthorized requests:

  • We may ask you to verify basic details (e.g., Telegram user ID or software license key) before processing deletion or access requests.

We usually respond within 7 business days and ensure complete transparency and cooperation with all reasonable privacy-related requests.

22. Data Retention Matrix

22.1 Retention Overview

To maintain transparency, here's a clear overview of how long we retain various types of data across our platform, tools, and services:

๐Ÿ”‘ License Logs

Retention: Until license expiry + 90 days

Used for fraud prevention, audit trail, and reactivation cases.

๐Ÿ’ฌ Telegram Chat Logs

Retention: 60 days post-resolution

Automatically purged after support case is closed or inactive.

๐Ÿ–ผ๏ธ Proof Images

Retention: Until manually deleted by admin

Shared voluntarily with permission; no EXIF or metadata retained.

๐Ÿ“ก API Responses

Retention: Not stored

Live responses only; never cached server-side or saved to disk.

๐Ÿ’ฅ Crash Logs

Retention: 12 months

Used for debugging and error diagnosis; anonymized and encrypted.

๐Ÿ’ธ Donation Records

Retention: Not linked to identity

No address clustering; donations stay anonymous unless self-disclosed.

All retention timelines are strictly enforced to balance user privacy, operational needs, and security.

23. Responsible Disclosure Policy

23.1 Security Research Welcome

We welcome ethical security researchers and white-hat hackers to report vulnerabilities responsibly. If you discover any bugs, exploits, or security loopholes in our tools, website, or infrastructure, please contact us directly at:

  • ๐Ÿ“ง Email: contact@vritrasec.com
  • ๐Ÿค– Telegram Bot: @ethicxbot

We appreciate responsible disclosure and will review all valid reports promptly. Unauthorized testing, DDoS attempts, or exploitation for malicious gain is strictly prohibited.

๐Ÿšซ 24. Public Tool Limitations Disclaimer

Some of our public tools - such as the IP Lookup tool and others that rely on third-party APIs or external data sources - may return results based on external providers. As such:

  • Tool outputs may occasionally be incomplete, delayed, or inaccurate, depending on the third-party source.
  • We do not control, modify, or guarantee the correctness or availability of externally fetched data.
  • Users are encouraged to cross-verify any critical information using multiple trusted sources before relying on the results.

These tools are offered strictly "as-is" for educational, research, or convenience purposes - and are not intended for medical, legal, financial, or mission-critical decision-making.

25. Final Statement

Contact Information

Privacy Concerns or Questions

  • You may report privacy concerns or ask questions directly to the support bot
  • Provide details about your concern and we will address it promptly
Need Help?
AI Security Assistant