Transparency
Service Providers & External Processing
Effective and last updated: 11 July 2026
HireWiz uses external infrastructure and APIs to provide the functions below. Some integrations are configurable and are used only when production credentials are enabled or you initiate that feature. We do not present an inactive payment provider as available. The provider used for a market request is also shown with the result.
Payment card details, CVV, UPI PINs, and bank-login credentials are entered with the checkout processor and are not received or stored by HireWiz.
| Provider / role | When used | Purpose | Data involved | Processing region |
|---|---|---|---|---|
| Vercel | Website hosting | Serve the HireWiz frontend and static assets | Standard web-request, device, network, and security-log data | Vercel edge/cloud infrastructure |
| Google Cloud (Cloud Run, Cloud Tasks, and Cloud Logging) | Backend hosting | Run the HireWiz API, private analysis worker, task dispatch, and operational logs | Application requests and data needed to perform the requested feature | Configured Google Cloud deployment region |
| Production database host configured by HireWiz | Account and application storage | Store account, profile, resume text, match history, entitlement, and transaction records | The account and service data described in the Privacy Policy | Configured production database region |
| Configured AI API provider | When you request an AI-assisted feature | Resume parsing, text comparison, skill extraction, summaries, and suggestions | Relevant resume text, job-description text, prompts, and contextual output needed for the request | Provider infrastructure; may be outside India |
| TheirStack, Adzuna, or Jooble | Only when the corresponding job-data API is configured for a market request | Return a sample of job postings for market skill-demand analysis | Role, location, country, experience, work-mode, recency, and result-count search parameters; resume content is not intended to be sent | Provider infrastructure |
| Only if you choose Google sign-in | Authenticate your Google account and return basic account information | Google account identifier, name, and email made available by the sign-in flow | Google infrastructure | |
| Google Analytics | Only when configured and after you accept analytics | Aggregate website-usage measurement | Page/usage events and browser, device, network, and approximate-location information | Google infrastructure |
| PostHog | Only when configured and after you accept analytics | Product funnels, retention, cohorts, and rollout measurement | Minimized product events, route, device, acquisition, and internal user identifier; no resume or evidence text | Configured PostHog cloud region |
| Sentry | When operational error reporting is configured | Detect frontend, API, and worker errors and release regressions | Minimized error, trace, release, route, and request-correlation metadata with default PII disabled | Configured Sentry project region |
| Resend | Only when lifecycle email delivery is configured | Deliver onboarding, completed-analysis, reminder, and payment-confirmation messages | Email address, message type, and the minimum account or transaction references needed for the message | Resend infrastructure |
| Razorpay | When you start the enabled India checkout | Hosted payment entry, payment confirmation, fraud screening, refunds, and disputes | Customer and transaction data needed for payment; raw payment credentials remain with the processor | Processor and banking/network infrastructure |
This page is updated when the production provider configuration changes. See the Privacy Policy for purposes, retention, choices, and rights. Questions may be sent to work@hirewizhq.com.