- Product: InProQu
- Effective date: 15 October 2026
- Operator: InProQu · Contact: [email protected]
This Policy explains how InProQu uses cookies and similar technologies on:
- the application at
app.inproqu.com, and - our public marketing website at
inproqu.com(andwww.inproqu.comwhen used)
It complements our Privacy Policy. You can link this page from the marketing site so you do not need a separate cookie policy there.
1. What we use
1.1 Strictly necessary (required for the Service — app.inproqu.com)
| Name / pattern | Purpose | Typical duration |
|---|---|---|
Auth.js session cookie (__Secure-authjs.session-token or authjs.session-token) |
Keep you signed in | Session absolute max ~7 days, or up to ~30 days if you choose “Remember this device”; idle timeout may end sooner |
pb_workspace |
Remember which workspace you last used (membership is always re-checked server-side) | Up to ~1 year |
pb_mfa_enroll |
Temporary MFA enrollment state | Short-lived |
pb_mfa_backup_reveal |
One-time MFA backup codes after enroll (so they survive a page refresh) | Short-lived (~15 min) |
| CSRF / callback cookies set by Auth.js | Secure sign-in flows | Short-lived |
share_unlock_* |
Remember unlock of a password-protected shared document | Up to 7 days |
share_rcpt_* |
Remember a verified recipient email for accept/sign flows on a shared document | Short-lived (recipient trust) |
These are necessary to provide a secure, authenticated Service. Disabling them will break login or share unlock.
1.2 Functional / security (platform — app.inproqu.com)
| Technology | Purpose |
|---|---|
| Cloudflare (when CDN / DNS / WAF is enabled) | CDN, DDoS, bot protection; may set security cookies |
| Cloudflare Web Analytics / Insights (if enabled) | Privacy-oriented performance analytics per Cloudflare’s practices |
Cloudflare Turnstile is not used on the application (app.inproqu.com).
1.3 Marketing website (inproqu.com) — security / bot protection
| Technology | Purpose | Domain |
|---|---|---|
| Cloudflare Turnstile | Challenge / verify that form submissions (e.g. contact or lead forms) are from humans, reducing spam and bots | inproqu.com (marketing site only) |
| Cloudflare (CDN / DNS / WAF, when enabled on the marketing site) | Delivery and edge security; may set security cookies | inproqu.com |
Turnstile is operated by Cloudflare, Inc. It may process technical data such as IP address, browser/device characteristics, and interaction data needed to score or complete the challenge, according to Cloudflare’s privacy documentation. We use it as a security / anti-abuse measure on marketing forms, not for advertising.
1.4 Tracking you configure (customer responsibility)
| Technology | When |
|---|---|
Email open pixel (/t/o/...) |
When you send tracked emails from the product |
Email click redirects (/t/c/...) |
When recipients click tracked links |
| Google Analytics 4 / Meta Pixel | Only if you attach them to public proposal pages |
If you enable third-party tags on share pages, you must provide any required notices/consent to viewers under laws that apply to you.
1.5 What we do not currently operate as first-party advertising cookies
Neither the application nor the marketing site currently uses advertising cookies for third-party ad networks (for example Meta Pixel or Google Ads) as first-party InProQu tooling. If we add analytics or advertising tags later, we will update this Policy.
2. Legal bases
- Necessary cookies (app): contract / legitimate interests in securing and providing the Service.
- Turnstile / edge security (marketing site): legitimate interests in preventing spam, abuse, and automated form submissions (and/or consent where a local law requires it for that technology).
- Non-essential cookies (if added later): consent where required (e.g. ePrivacy / PECR / similar).
3. Managing cookies
Browsers allow you to block or delete cookies. Blocking necessary cookies will prevent sign-in. Use in-app logout to clear session cookies where possible.
“Remember this device” extends session lifetime on that browser; do not use it on shared computers.
4. Updates
We may update this Policy when cookie use changes. Check the effective date.