This Cookie Policy explains how Hirencer, operated by QuinPin LLP, uses cookies, local storage, pixels, tags, server logs and similar technologies, what information they collect, who receives it and how you can control it, wherever in the world you are.
1. What these technologies are
- Cookies are small text files stored on your browser or device. First-party cookies are set by Hirencer; third-party cookies are set by other companies whose services run on our pages.
- Local storage / session storage keep small pieces of data in your browser, for example your cookie choice or a chosen filter.
- Pixels, tags and SDKs are small pieces of code or images that report that a page was viewed or an action happened. Tag managers (such as Google Tag Manager) load other tags.
- Server and network logs are records our servers and security providers keep of each request, even without cookies.
2. Information we and our providers collect through them
Depending on the category and your choices, these technologies can collect or infer:
- Network and location data: your IP address and the approximate location (country, region or city) derived from it. We do not collect your precise GPS location through cookies.
- Device and browser data: device type, operating system, browser and version, screen size, language, and similar settings.
- Visit and page data: pages and listings you view, the page that referred you, search terms you use on Hirencer, links and buttons you click, scroll depth, time on page, and the date and time of each visit, including your first and last visit.
- Activity data: actions such as signing up, logging in, posting or applying to a job or project, sending a proposal or message, starting or paying for a collaboration, and errors you hit. For signed-in users we also record the last time you were active on your account.
- Identifiers: random IDs stored in cookies or generated by the provider so that repeat visits can be recognised.
- Security signals: failed logins, unusual request patterns, bot or attack indicators, and whether a visitor passed a security challenge.
We use this to keep the Platform secure and working, to understand and improve it, to prevent fraud and abuse, and, only with your consent where required, to measure and (if we ever run them) advertise our own services. We do not sell personal data.
3. Categories we use
| Category | Purpose | Providers and examples | Consent |
|---|---|---|---|
| Strictly necessary | Log you in and keep you logged in; keep a shopping basket and checkout working; protect forms from forgery; remember your cookie choice. The Platform cannot work without them. | WordPress login and session cookies (wordpress_logged_in_*, wordpress_sec_*, wp-settings-*), WooCommerce (woocommerce_cart_hash, woocommerce_items_in_cart, wp_woocommerce_session_*), our consent record (hc_cookie_consent) |
Not required; always on |
| Security and performance | Detect and block bots, attacks, brute-force logins and abuse; deliver pages quickly and reliably through a content delivery network; log security events. | Cloudflare (for example __cf_bm, cf_clearance, challenge cookies), Wordfence or similar security plugins (for example wfwaf-authcookie-*, wordfence_verifiedHuman), the hosting provider’s firewall and caching |
Not required; always on, because they are needed to keep the Platform and your account safe |
| Payments and fraud prevention | Run payment checkout and detect fraudulent payments. These cookies are set only when you open a payment page. | Stripe (__stripe_mid, __stripe_sid), Razorpay (checkout device and session identifiers), and other payment gateways we may add |
Not required when you choose to pay; set by the provider under its own policy |
| Functional and preferences | Remember choices such as your selected profile, tab or filter; show embedded content; and support spam protection and sign-in. | Local storage on your device; Google Fonts; Google Sign-In; Google reCAPTCHA or Cloudflare Turnstile where used; embedded video such as YouTube | Required where the law requires; you can refuse |
| Analytics and statistics | Count visits, learn which pages, features and sources work, find errors and slow pages, and understand how people move through the Platform (including location by region, device type and page flow). | Google Analytics 4 (_ga, _ga_*, and legacy _gid), Google Tag Manager, and similar tools we may add, such as heatmap or session-insight tools (for example Microsoft Clarity or Hotjar) and server-side analytics |
Only after you accept (opt-in) |
| Marketing and advertising | Measure our own campaigns and show relevant promotions of Hirencer on other sites. Not used today unless you see it listed in the cookie settings. | Google Ads and Google Tag (_gcl_au, IDE), Meta Pixel (_fbp), LinkedIn Insight Tag and similar |
Only after you accept (opt-in) |
Names and lifetimes of third-party cookies are set by those providers and can change. Typical lifetimes: Cloudflare __cf_bm about 30 minutes; Stripe __stripe_sid about 30 minutes and __stripe_mid about 1 year; Google Analytics _ga and _ga_* up to 2 years and _gid 24 hours; _gcl_au and _fbp about 90 days; Wordfence wordfence_verifiedHuman about 24 hours; login cookies, up to 14 days if you tick “remember me” and otherwise the session. Google Analytics event data is kept for the period set in our account (normally 14 months or less).
4. Who receives the data
- Google (Google Analytics, Google Tag Manager, Google Ads, Google Fonts, Google Sign-In, reCAPTCHA), acting as our service provider for analytics and, for some features, as an independent controller under its own policy. We configure Google Analytics to anonymise IP addresses where available.
- Cloudflare, Inc., which sits between visitors and our servers to filter traffic, block attacks and speed up delivery, and therefore sees the IP address, requested URL, browser and device details and security signals of every request.
- Security plugin and firewall providers (for example Wordfence by Defiant), which log login attempts and blocked requests, including IP address, time, the request and the user name tried.
- Hosting provider (Hostinger), which keeps standard server access and error logs.
- Payment providers (Stripe, Razorpay and others) for payment pages.
- Any other analytics or advertising provider we add, which we will name here and in the cookie settings first.
5. International transfers
Google, Cloudflare and others process data in India, the United States, the European Union and other countries. Where required, transfers rely on the providers’ contractual safeguards, such as standard contractual clauses and their data-processing terms.
6. Your choices and consent
- Cookie banner. On your first visit you can choose Accept all, Reject non-essential or Customise. Analytics and marketing technologies are switched off until you opt in. Strictly necessary and security cookies are always active because they cannot be switched off without breaking login, checkout or security.
- Change your mind any time with “Cookie settings” in the footer or the button at the end of this page. Withdrawing consent does not affect processing done before you withdrew.
- Browser controls. Most browsers let you block or delete cookies. If you block essential or security cookies, you may be unable to log in, pay or use forms.
- Opt-out tools. Google Analytics opt-out add-on (tools.google.com/dlpage/gaoptout), Google Ads settings (adssettings.google.com), and industry tools such as youronlinechoices.eu and optout.aboutads.info.
- Global Privacy Control / Do Not Track. We treat a Global Privacy Control signal as a request to keep non-essential cookies off where the law requires. We cannot respond to the older “Do Not Track” setting because there is no common standard.
- Regional rules. If you are in the EU, UK, Switzerland, EEA or another region that requires opt-in consent, we ask before using non-essential technologies. Elsewhere, including India under the Digital Personal Data Protection Act, 2023, we ask for consent where the law requires it and always give you the choice.
7. How long data is kept
Cookie lifetimes are shown above. Analytics data is kept for up to 14 months and then deleted or anonymised. Security and server logs are generally kept for up to 12 months, or longer where needed to investigate an incident or as the law requires. Account activity records (such as “last active”) are kept while your account exists.
8. Signed-in activity records
If you have an account, we also keep first-party records that are part of providing the service and keeping it secure, such as when you registered, when you last logged in or were last active, sign-in and security events, and key actions (listings, proposals, messages, collaborations and payments). These are covered in our Privacy Policy and do not depend on cookies.
9. Changes
We update this Policy when we add or remove tools. The date at the top shows the latest version. If we add a new analytics or advertising provider, we will update this page and ask for your consent again where required.
10. Questions
For questions or to exercise your rights see our Privacy Policy or contact us below.
Contact us
QuinPin LLP, 303, Pati Gali, Bara Bazar, Bareilly, Uttar Pradesh, 243001, India
Email: support@hirencer.com · Or use the contact form.