Cookie Policy
ContentsClaims LLC · Last updated October 8, 2026
ContentsClaims LLC, 401 Ryland Street, Ste 200-A, Reno, NV 89502 · privacy@contentsclaims.com
1. What Are Cookies and Similar Technologies?
Cookies are small text files placed on your device by websites you visit. They are widely used to enable website functionality, improve performance, and provide site owners with information about usage. ContentsClaims LLC uses cookies and similar client-side storage technologies (collectively, "cookies") as described in this policy.
Similar Technologies: In addition to cookies, we use browser storage for functional purposes only: localStorage records your choice on our cookie notice and, if you arrived through an invitation link, holds that pending invitation for up to 7 days; sessionStorage holds short-lived functional state, such as sign-in, verification, and password-reset steps, and is cleared when you close the tab. We do not use advertising pixels, and we do not use browser fingerprinting (canvas fingerprinting, WebGL fingerprinting, or font enumeration) for tracking purposes.
Server-Side Tracking: ContentsClaims also collects certain information server-side — including your IP address and approximate geolocation — on each request to our servers, independently of cookies. See our Privacy Policy §1 for details on IP address collection and use.
2. Cookies We Use
| Cookie | Category | Provider | Purpose | Duration | Opt-Out? |
|---|---|---|---|---|---|
| cc_otp_state | Strictly Necessary | ContentsClaims LLC | Holds your pending email-verification step during sign-up, sign-in, or an email-address change. Set as HttpOnly, Secure, SameSite=Lax, scoped to our API path. | 10 minutes | No — Required |
| cc_access | Strictly Necessary | ContentsClaims LLC | Keeps you signed in. Required for the Service to function. Set as HttpOnly, Secure, SameSite=Lax. | 15 minutes | No — Required |
| cc_refresh | Strictly Necessary | ContentsClaims LLC | Renews your sign-in without asking for your password again. Sent only to our API. HttpOnly, Secure, SameSite=Lax. | 7 days | No — Required |
| cc_csrf | Strictly Necessary | ContentsClaims LLC | Security token that protects your account against cross-site request forgery. Secure, SameSite=Lax. | 7 days | No — Required |
| _stripe_* | Strictly Necessary | Stripe, Inc. | Fraud detection and secure payment processing. Required when completing a payment transaction. Governed by Stripe's Privacy Policy (stripe.com/privacy). | Session / 1 year | No — Required |
| Cloudflare security cookies (e.g. __cf_bm) | Strictly Necessary | Cloudflare, Inc. | Set by our network and security provider (including Turnstile bot protection on sign-up) to distinguish people from automated traffic. Governed by Cloudflare's Privacy Policy. | Up to 30 minutes | No — Required |
This table reflects cookies currently in use. Third-party providers may update their cookie names or add cookies in connection with updates to their services. We review and update this table periodically.
3. Cookie Categories — Detailed Description
Strictly Necessary: These cookies are essential for the Service to operate and cannot be disabled. They enable core functionality including secure login session management and protection against cross-site request forgery attacks. Stripe's strictly necessary cookies are required to process payments securely. You cannot opt out of strictly necessary cookies while using the Service; doing so would prevent the Service from functioning.
Analytics and Advertising: ContentsClaims does not currently use third-party analytics cookies (such as Google Analytics) or advertising and marketing cookies (such as Google Ads or social-media pixels). Any usage statistics we keep are derived from our own server logs. If we add analytics or advertising cookies in the future, we will update this policy and provide the required notice and opt-out choices before they are set.
4. Third-Party Cookie Providers
Stripe, Inc.: Stripe sets cookies for fraud detection and secure payment processing. Stripe's cookies are strictly necessary when you complete a payment and cannot be disabled for payment flows. Stripe's data practices are governed by Stripe's Privacy Policy at stripe.com/privacy. ContentsClaims is not responsible for Stripe's cookie practices.
Cloudflare, Inc.: Cloudflare provides our network security and the Turnstile bot check shown on sign-up. It may set short-lived security cookies to distinguish people from automated traffic. Cloudflare's practices are governed by its Privacy Policy at cloudflare.com/privacypolicy.
Microsoft (Outlook Connection): When you connect an Outlook, Hotmail, or Live account, you sign in on Microsoft's own site, and Microsoft may set authentication-related cookies governed by Microsoft's Privacy Statement. ContentsClaims does not control these cookies. Other providers (such as Gmail) connect with an app-specific password and do not involve a provider sign-in page.
5. How to Control and Opt Out of Cookies
Browser Settings: Most browsers allow you to view, block, or delete cookies through their settings. Blocking all cookies will prevent the Service from functioning (strictly necessary cookies are required). Below are instructions for common browsers:
- Chrome: Settings → Privacy and security → Cookies and other site data
- Firefox: Options → Privacy & Security → Cookies and Site Data
- Safari: Preferences → Privacy → Manage Website Data
- Edge: Settings → Privacy, search, and services → Cookies and site permissions
- iOS Safari: Settings → Safari → Privacy & Security
- Android Chrome: Chrome app → Settings → Privacy and security
Do Not Share My Personal Information (California CPRA): Because ContentsClaims does not use advertising cookies, our cookies are not used to share your browsing activity for cross-context behavioral advertising. ContentsClaims does not sell personal information. You may still send a Do Not Sell or Share request to privacy@contentsclaims.com — see our Privacy Policy.
Global Privacy Control (GPC): As our Privacy Policy explains, we treat a valid GPC signal as a request to opt out of the sale or sharing of personal information about you. Because we do not set cookies that sell or share personal information, and nothing collected through your browser is sold or shared, honoring the signal requires no change to which cookies are set or how that information is handled. Do Not Sell or Share requests can be sent to privacy@contentsclaims.com as described in our Privacy Policy.
6. Cookie Consent — California and Other State Residents
Residents of California, Colorado, Connecticut, Virginia, and other states with applicable privacy laws have the right to opt out of cookies and tracking technologies used for targeted advertising. ContentsClaims currently sets only strictly necessary cookies (session management, security, and Stripe payment processing), which are required for the Service to function; we do not set analytics or advertising cookies.
7. Do Not Track
The World Wide Web Consortium (W3C) has not established universal technical standards for a legacy "Do Not Track" (DNT) browser signal. ContentsClaims does not currently respond to the DNT signal as a standalone mechanism. Because we do not use tracking or advertising cookies, DNT would not change which cookies are set. See §5 for Global Privacy Control.
8. Updates to This Cookie Policy
ContentsClaims may update this Cookie Policy periodically to reflect changes in the cookies we deploy, updates to third-party services, or changes in applicable law. The "Last Updated" date at the top of this page indicates when the Policy was last revised. Material changes will be communicated consistent with our Privacy Policy's notice provisions. We encourage you to review this Policy periodically.
9. Contact Us
If you have questions about our use of cookies or tracking technologies, or to exercise any privacy rights related to cookie data, contact us at:
ContentsClaims LLC — Privacy Officer
privacy@contentsclaims.com
401 Ryland Street, Ste 200-A, Reno, NV 89502