Cookie Policy
What we put on your device, why, and how to change your mind.
ProposalForge uses cookies and similar technologies (such as localStorage and SDK identifiers) to keep you signed in, prevent fraud, and — if you opt in — understand how the product is used so we can improve it.
Categories we use
- Necessary— required for the site to function (sign-in, security, billing). Always on.
- Analytics— aggregate usage measurement so we can see which features are valuable. Off by default; opt in via banner or preferences modal.
- Marketing— we do not currently run advertising or cross-context tracking. The category exists in the banner so we can transparently disclose if that ever changes.
Cookies we set
| Name | Purpose | Category | Expiry | Party |
|---|---|---|---|---|
| sb-* | Supabase authentication session | Necessary | 7 days (rolling) | First-party |
| pf-consent | Stores your cookie preferences | Necessary | 12 months | First-party |
| __cf_bm | Cloudflare bot management | Necessary | 30 minutes | Third-party |
| __stripe_mid, __stripe_sid | Stripe fraud detection on checkout | Necessary | 1 year / 30 minutes | Third-party |
| pf-anon | Privacy-respecting product analytics (no PII) | Analytics | 12 months | First-party |
Browser controls
You can clear or block cookies in your browser settings. Blocking Necessary cookies will break sign-in and billing. Most modern browsers also send a Global Privacy Control signal; we honor GPC for Analytics cookies in jurisdictions where it is legally required.
Other tracking technologies
We use limited localStorage entries to remember editor preferences and preview interactions. These are not cookies but they have similar privacy implications, so they are governed by the same consent choice.
Changes
We will update this list whenever we add a new cookie. The “Effective” date at the top reflects the latest version. Material changes will be announced in the cookie banner.
Questions: [email protected].