Legal
Cookie Policy
Last updated: 2026-06-17. Questions: hello@docsiv.com. These documents are provided as drafts for integration; have qualified counsel review before reliance.
What this policy covers
This Cookie Policy explains how Docsiv (“we,” “us,” or “our”) uses cookies and similar technologies on Docsiv websites and the Service.
For how we process personal data more broadly, see our Privacy Policy. For Sign-in and subscription terms, see our Terms of Service.
What cookies and similar technologies are
Cookies are small text files stored on your device. Similar technologies include local storage, session storage, pixels, and software development kits. Together we refer to them as “cookies” unless we specify otherwise.
First-party cookies are set by Docsiv. Third-party cookies are set by partners we use (for example analytics providers).
How you can control cookies
- Use our cookie preferences control to accept or decline non-essential analytics cookies. We show a consent prompt where required, and you can change your choice at any time from the cookie settings link in our site footer. Analytics only load after you accept.
- Use your browser settings to block or delete cookies. Note that strictly necessary cookies are often required for sign-in and security; blocking them may break parts of the Service.
- Some browsers offer “Do Not Track” signals; there is no consistent industry standard, so we treat DNT as one factor among others where applicable.
For more on rights related to personal data, see our Privacy Policy.
Cookies and storage we use
The exact names and lifetimes can vary by release; categories below describe typical behavior on docsiv.com and related app domains.
Strictly necessary
These are required for core operation, security, and session management.
| Category | Purpose | Typical examples |
|---|---|---|
| Authentication and session | Keep you signed in; protect accounts; prevent fraud. | Session tokens or refresh tokens stored in cookies or local storage by our authentication provider (Supabase). |
| Load balancing and security | Route traffic; mitigate abuse. | Short-lived cookies or headers set by our hosting provider (Vercel). |
| Preferences | Remember essential UI choices tied to your session. | Minimal session or local storage keys required for the app to function. |
Functional
Used to remember non-essential choices (for example, theme or locale) and, in client portals and comments, a local identity so guests don’t have to re-enter their details. We store these in cookies or your browser’s local storage. If you disable them, some convenience features may not persist.
Analytics and product measurement
We use PostHog for product analytics (such as feature usage and events) to understand how the Service is used and improve it; PostHog events are proxied through our own domain and load only after you accept analytics cookies. We also use Vercel Analytics for aggregated usage (for example page views) and Vercel Speed Insights for Core Web Vitals and speed metrics. You can decline analytics through our cookie preferences. Depending on configuration and jurisdiction, some regulators treat analytics as requiring consent; consult counsel for your regions of operation.
Collaboration and rich features
Where you use real-time collaboration, components may use WebSockets or similar channels; sessions may be tied to accounts managed through our providers (Liveblocks).
Third-party sign-in
If you use Google or other OAuth providers, those providers may set their own cookies when their sign-in page loads. Their use is governed by their cookie policies.
Payment pages
When you complete billing flows, our payment provider (Dodo Payments) may set cookies or use similar technologies on payment pages subject to their policies.
Changes
We may update this Cookie Policy when our practices or vendors change. We will revise the “Last updated” date on our legal pages.
Contact
Questions: hello@docsiv.com