Legal

Privacy Policy

Last updated · September 2, 2026

Privacy is a fundamental right, not a luxury. Pragmys is built on a minimal data footprint — we don't collect, harvest, or sell your personal information. Your code remains yours, and your profile is built entirely on your own terms.

01

Our philosophy

At Pragmys, privacy is a fundamental right, not a luxury. Our platform is built on a minimal data footprint. We do not participate in the data economy — we do not collect, harvest, or sell your personal information. Our systems prove that verified engineering credentials and un-fakeable proof-of-work can be generated without compromising digital anonymity or proprietary source code.

02

Intentional privacy & source code protection

Our platform is privacy-first by design. Pragmys evaluates the actual projects you build to generate an engineering skill graph, but we never store your raw source code.

When we analyze your repositories (whether via local CLI or GitHub integration), the raw source code is discarded immediately as soon as the structural analysis is finished. We only retain the derived insights — such as architectural patterns, your verified skill graph, and telemetry footprints — required to maintain your Pragmys profile. Your private code never sits on our servers.

03

Data collection & usage

To provide the Pragmys experience and maintain your verified profile, we process only the data strictly necessary for functionality:

Secure authentication: We use industry-standard protocols to secure your account, storing only the identifiers necessary to manage your session.
Behavioral & structural insights: To facilitate accurate skill mapping, we process the structural skeleton of your repositories and aggregated telemetry, enabling personalized project recommendations and accurate role-readiness diagnostics.
AI usage & intent telemetry: To calculate your AI orchestration skills and verify authentic code ownership, our local systems evaluate your AI conversations (such as IDE prompts) and localized code snippets. Crucially, all AI conversations and snippets are strictly redacted and PII-scrubbed locally on your machine. Only the sanitized, anonymized telemetry is securely transmitted for analysis.
Zero-PII execution: All code redaction and PII-scrubbing happens safely on your machine before any telemetry reaches our cloud engine.
04

Data sovereignty & visibility control

Your data exists only to serve your growth and career trajectory. We implement robust security layers to ensure your information is protected. Because we avoid storing raw source code, your digital safety is inherent to our minimalist architecture. You maintain full control over who sees your profile:

Public links: Your data is shareable using public portfolio links strictly based on the visibility preferences you set in Pragmys. You choose what to reveal.
Opt-in job matching: To connect your verified profile with active career pipelines, your insights can be shared with hiring companies for job matching — but only with your explicit, proactive consent.
05

Third-party transparency

Pragmys as an organization does not share your performance, insights, or account data with any third party for advertising or marketing purposes. We only interact with external services essential for secure account management, structural AI evaluation, and platform stability.

06

Analytics

We partner with Microsoft Clarity to capture how you use and interact with our website through behavioral metrics, heatmaps, and session replay to improve our products/services. Website usage data is captured using first and third-party cookies and other tracking technologies to determine the popularity of products/services and online activity. Additionally, we use this information for site optimization and fraud/security purposes. For more information about how Microsoft collects and uses your data, visit the Microsoft Privacy Statement.

07

Browser extension & permissions

The Pragmys Job Matcher browser extension has a single purpose: it shows you how well your verified Pragmys skill profile matches a job posting you're viewing, directly on supported job sites (LinkedIn, Naukri, Indeed, Glassdoor, Wellfound, and Unstop).

The extension scores a posting in two tiers, and what leaves your device is different for each:

Instant tier: The moment you extract a job posting, it's scored entirely on your device against a cached copy of the public skills taxonomy and your own cached skill confidences. Nothing about the job posting is sent anywhere for this tier.
Deep analysis tier: Only when you explicitly click for the full breakdown, the job title and description are sent to api.pragmys.com so our LLM can extract the specific skills the posting requires and generate a written match summary.

What we retain from a deep analysis: the derived result — matched, weak, and missing skills, your match score, and the written summary — plus the job title and the domain of the site it came from (e.g. "linkedin.com"), so the analysis appears in your diagnostics history at pragmys.com. We do not retain the full text of the job description or the specific URL of the posting. That content is used only to compute the match for your request and is not written to our database.

It requests the following browser permissions, each used strictly for that purpose:

activeTab: Used when you click the extension icon or the in-page widget to read the currently open job posting's title and description so we can score it against your skills. The extension never reads a tab you haven't actively interacted with.
scripting: Used to inject a content script that extracts job title and description text from the active job-posting tab, and as a fallback extractor on pages where the primary content script hasn't loaded yet.
storage: Used to cache your auth session token, your skill profile, and the public skills taxonomy locally in your browser, so the extension can score jobs instantly without re-fetching data on every page view.
alarms: Used to periodically check for completion of the device-code login flow you initiate from the popup, without keeping the background service worker running continuously.
cookies (optional): Requested only if needed, to check for an existing pragmys.com session cookie so you don't have to log in again inside the extension if you're already signed in on the web.
Host permissions: Access to job-board domains (LinkedIn, Indeed, Glassdoor, Naukri, Wellfound, Unstop) is required to inject the in-page match widget and read job content on those specific sites. Access to api.pragmys.com is required to send the job title and description to our backend for the deep-analysis tier described above.

The extension does not download or execute remote code — all logic ships inside the packaged extension bundle, and its network requests only exchange data (job text in, match result out), never executable code. Consistent with the rest of this policy, the extension does not sell your data or share it with third parties for advertising or marketing.

08

Disclaimer

Pragmys is an independent software development entity and is not associated with, or a subsidiary of, any other corporation.

09

Contact us

We are committed to maintaining these standards. For questions regarding our privacy practices, reach out to us:

Website · pragmys.com
Entity · Pragmys