Legal
Cookie Policy
Effective date: May 31, 2026 Last updated: May 31, 2026
This Cookie Policy explains what cookies and similar technologies are, what types we and our service providers use on the getFIXLY services (the websites at https://www.getfixly.app, https://www.getfixly.app/blog, https://community.getfixly.app, any associated apps, and any other features and functionality, collectively the "Services"), and the choices available to you. It supplements our Privacy Policy.
You can change your cookie choices at any time by clicking the "Cookie preferences" link in the footer of any page.
1. What are cookies?
A cookie is a small text file that a website places on your device to help the site work, remember your preferences, and understand how you use it. Cookies set by the site you're visiting are called "first-party cookies." Cookies set by a different domain (e.g., embedded videos, analytics, fonts) are called "third-party cookies."
We also use similar technologies that have similar functions, including:
- Local and session storage (data stored by your browser, similar to cookies);
- Pixels / web beacons (tiny images that record activity, often for analytics or email open rates);
- Software development kits (SDKs) in mobile apps;
- Server logs (which record IP addresses and request data without setting cookies).
For brevity, we use "cookies" to refer to all of these.
2. Categories of cookies we use
We organize cookies into four categories. The exact list of cookies, vendors, and purposes is available in the Cookie preferences panel in the footer; the categories below describe how we think about them.
(a) Strictly necessary cookies
Required for the Services to function. They cannot be turned off. Examples:
- Session cookies that keep you signed in to your forum or app account;
- Cookies that remember items in a checkout flow;
- Security cookies and bot-detection cookies (e.g., Cloudflare Turnstile challenges that protect waitlist forms from spam);
- Load-balancing cookies that route requests to the right server;
- A consent cookie that records your cookie choices.
(b) Functional cookies
Help the Services remember choices you make to give you a better experience. Examples:
- Language and time-zone preferences;
- Forum display preferences (light/dark mode, post density);
- Whether you've dismissed a banner.
Disabling these may cause some features to behave inconsistently across sessions.
(c) Analytics / performance cookies
Help us understand how the Services are used so we can improve them. Examples include cookies set by analytics tools we may use (such as a privacy-respecting analytics platform on the marketing site, server-side analytics on the blog, or similar tools on the forum and the paid app). These cookies generally measure things like:
- Pages visited and time spent;
- Where users come from (referrers, campaigns);
- Errors encountered;
- Aggregate device, browser, and location (city/region-level) information.
Where we use analytics that depend on consent under applicable law, those analytics will not run until you accept analytics cookies in the consent banner.
(d) Marketing / targeting cookies
Used (only if and when we run advertising campaigns) to measure the effectiveness of marketing and to show you relevant content on third-party sites. Examples might include conversion-tracking pixels for ad platforms or social-media retargeting cookies. These cookies are loaded only after you give consent in the consent banner. Some uses of marketing cookies may qualify as a "sale" or "sharing" of personal information under U.S. state privacy laws; you can opt out via the same controls.
3. Cookies in the current stack
For transparency, the cookies and similar technologies we currently use (or expect to use as the Services launch) include:
| Source | Purpose | Category |
|---|---|---|
| getFIXLY (first-party) | Session, authentication, CSRF protection, consent record, language, theme | Strictly necessary / Functional |
| Cloudflare (CDN, security, bot challenge) | Performance, security, Turnstile challenge for waitlist forms | Strictly necessary |
| NodeBB (forum at https://community.getfixly.app) | Forum session, login, draft autosave, user preferences, anti-CSRF | Strictly necessary / Functional |
| Ghost (blog at https://www.getfixly.app/blog) | Authentication for staff, member subscriptions (if enabled), comment session | Strictly necessary / Functional |
| Stripe (payments, when paid plans launch) | Fraud detection, payment session | Strictly necessary |
| Privacy-respecting web analytics (e.g., Plausible / PostHog / similar) | Aggregate site analytics | Analytics |
| Email-marketing platform (when newsletter launches) | Email open / click tracking | Functional / Analytics |
| Ad-platform pixels (only when paid campaigns launch) | Conversion measurement, retargeting | Marketing |
The exact list will be kept current in the Cookie preferences panel. If you don't see a vendor listed there, we're not using it.
4. Your choices
- Cookie banner. When you first visit the Services from a region that requires consent (such as the EU or UK), you'll see a banner that lets you accept or reject categories of cookies. You can change your choices any time using the "Cookie preferences" link in the footer.
- Browser settings. Most browsers let you block or delete cookies; consult your browser's help. Be aware that blocking strictly necessary cookies will break parts of the Services.
- Mobile-device controls. On iOS and Android, you can reset advertising identifiers and limit ad tracking in your device settings.
- Do Not Track / Global Privacy Control. We honor the Global Privacy Control (GPC) signal as a request to opt out of "sales" and "sharing" / targeted advertising under applicable U.S. state privacy laws. We do not separately respond to legacy "Do Not Track" headers, which are not consistently interpreted across the industry.
- Opt-out at the vendor. Most analytics and ad vendors offer their own opt-outs (e.g., the Network Advertising Initiative's opt-out at optout.networkadvertising.org).
5. Children
The Services are not directed to children under 16, and we do not knowingly use cookies to collect data from children under 16.
6. Changes to this Policy
We may update this Cookie Policy from time to time as we add or remove technologies. The "Last updated" date at the top tells you when the Policy was last revised.
7. Contact
Questions about this Cookie Policy: privacy@getfixly.app.