This Cookie Policy explains how ProposalForge uses cookies and similar technologies when you visit or use our platform at forgeproposals.com. We believe in transparency and want you to understand exactly what technologies are at work when you interact with our Service.
1. Introduction
Cookies are small text files that are stored on your device (computer, tablet, or mobile phone) when you visit a website. They are widely used to make websites work more efficiently, provide a better browsing experience, and give site operators information about how visitors interact with their site.
This Cookie Policy covers all cookies and similar technologies (including local storage and device fingerprinting) used by ProposalForge in connection with our platform at forgeproposals.com. It applies to all visitors and registered users of the Service.
This policy supplements our Privacy Policy, which provides a comprehensive overview of how we collect, use, and protect your personal information. If there is any conflict between this Cookie Policy and the Privacy Policy regarding cookies or similar technologies, this Cookie Policy takes precedence.
2. Cookies We Use
ProposalForge uses only strictly necessary cookies. These cookies are essential for the basic functionality of the Service and cannot be disabled without preventing you from using core features such as signing in.
Cookie Name
Purpose
Description
Duration
Category
next-auth.session-token
Authentication
Keeps you signed in to your account
Session (expires when browser closes)
Strictly necessary
next-auth.csrf-token
Security
Prevents cross-site request forgery attacks
Session
Strictly necessary
__Secure-next-auth.session-token
Authentication
Secure variant of the session token used on HTTPS connections
Session
Strictly necessary
Important: We do NOT use any marketing, advertising, analytics, or tracking cookies. The cookies listed above are the only cookies set by ProposalForge.
3. Cookieless Analytics
To understand how visitors use our platform, we use Plausible Analytics — a privacy-focused, open-source analytics tool. Plausible is fundamentally different from traditional analytics platforms:
▸Cookieless by design — Plausible does not set any cookies on your device, ever
▸No personal data collected — it does not collect IP addresses, user agents, or any personally identifiable information
▸No cross-site tracking — it cannot and does not track you across different websites
▸No persistent identifiers — each pageview is treated independently with no user profiles built over time
▸All data is aggregated — only aggregate metrics (page views, referral sources, country-level location) are collected
Because Plausible does not use cookies and does not collect personal data, it is fully compliant with GDPR, CCPA, and PECR without requiring user consent. No cookie banner or consent mechanism is needed for Plausible to operate lawfully.
4. Local Storage
Local storage is a browser feature that allows websites to store small amounts of data on your device. Unlike cookies, local storage data is not sent to the server with each request.
ProposalForge uses a single local storage key:
cookie-consent
This key stores whether you have dismissed the cookie consent banner. It contains only the value "accepted"and no personal information. It persists until you clear your browser's local storage.
You can clear this value at any time through your browser's developer tools or by clearing site data in your browser settings. Doing so will cause the cookie consent banner to reappear on your next visit.
5. Device Fingerprinting
ProposalForge uses FingerprintJS to help detect and prevent multi-account abuse on our free tier. FingerprintJS collects certain browser characteristics to generate a unique visitor identifier:
▸Screen resolution and color depth
▸Installed fonts and browser plugins
▸Canvas and WebGL rendering characteristics
▸Timezone and language settings
▸Other browser configuration attributes
How We Handle This Data
The visitor ID generated by FingerprintJS is hashed using SHA-256 before storage. We never store the raw fingerprint or the raw visitor ID. The hashed identifier is used solely for detecting whether multiple free-tier accounts are being created from the same device.
Important Distinctions
▸This is not a cookie — no data is stored on your device by the fingerprinting process
▸The fingerprint cannot be used to track you across other websites
▸The raw fingerprint data never leaves your browser; only the hashed ID is transmitted to our servers
▸It is used exclusively for abuse prevention, not for advertising, analytics, or user profiling
For more details on how we process fingerprint data, see Section 2.2 of our Privacy Policy.
6. Third-Party Cookies
ProposalForge does not set any third-party cookies. We do not embed third-party advertising scripts, social media widgets, or tracking pixels that would place cookies on your device.
Stripe Payment Processing
When you interact with Stripe for payment processing (for example, when entering payment details or managing your subscription), Stripe may set cookies on its own domain (stripe.com) to facilitate secure payment processing and fraud detection. These cookies are governed by Stripe's own privacy and cookie policies, not ours.
▸Stripe cookies are set on stripe.com, not on our domain
▸We have no control over Stripe’s cookies and cannot access them
▸Stripe’s cookies are used for payment security and fraud prevention
You can control and manage cookies through your browser settings. Most browsers allow you to view, delete, and block cookies from specific or all websites. Here are some general steps:
▸Open your browser’s settings or preferences menu
▸Navigate to the privacy, security, or cookies section
▸Choose to view, block, or delete cookies for specific sites or all sites
▸You can also set your browser to notify you when a cookie is being set
Browser-Specific Guidance
For detailed instructions on managing cookies in your specific browser, consult your browser's help documentation. Most popular browsers (Chrome, Firefox, Safari, Edge) provide clear instructions in their settings under privacy or cookie management.
Please note: Since ProposalForge uses only strictly necessary cookies for authentication and security, blocking these cookies will prevent you from signing in to your account and using core features of the Service. We do not use any optional cookies (analytics, marketing, or preference cookies), so there are no non-essential cookies to opt out of.
8. Changes to This Policy
We may update this Cookie Policy from time to time to reflect changes in the technologies we use, legal requirements, or our business practices. When we make changes:
▸We will update the “Last Updated” date at the top of this page
▸For material changes (such as introducing new categories of cookies), we will notify you by email at the address associated with your account
▸The updated policy will be posted on this page and will take effect immediately upon posting
We encourage you to review this page periodically to stay informed about how we use cookies and related technologies. Your continued use of the Service after changes are posted constitutes your acceptance of the updated Cookie Policy.
9. Contact
If you have any questions about this Cookie Policy or the technologies we use, please contact us: