Cookie policy

We use essential cookies to keep the site reliable. With your OK, we also run lightweight analytics to learn what helps readers most.

This page explains how Freelance Codex uses cookies (and similar technologies), what categories exist, and how you can manage your preferences.

We are aiming for practical and plain-language. The goal is that you understand:

what cookies are doing on this site,
what is essential vs optional,
what data may be collected (and what is not),
how to change your choice,
and what to do if your browser settings get in the way.

For the broader data policy (beyond cookies), read Privacy policy.

If you have questions or requests, use Contact.

Quick summary

Essential cookies keep the site secure and functional. They are always on because the site cannot work properly without them.
Analytics cookies are optional. If enabled, they help us understand what content is useful so we can improve it.
We do not sell personal data or build ad profiles.
Your cookie choice is stored for up to six months, unless you reset it or clear cookies in your browser.

What cookies are (and why you should care)

A cookie is a small piece of data stored in your browser that a site can read later. Many cookies are harmless and purely functional. Some cookies are used for tracking across multiple sites.

Freelance Codex tries to keep this simple: we use essential cookies by default, and optional analytics only if you consent.

Common cookie uses

remembering your preferences,
keeping forms secure,
supporting site stability,
measuring usage (analytics),
and other basic functionality.

Helpful terms (first-party, third-party, session, persistent)

Cookies are often described using a few basic terms. These are not "good" or "bad" by themselves, but they help explain what is going on.

First-party: set by Freelance Codex.
Third-party: set by a service we use (if applicable).
Session: generally lasts only while your browser is open.
Persistent: stays until it expires or you delete it.

The same website can use a mix of these. For example: a site might set a first-party cookie to remember a preference, and it might also load an analytics tool that sets its own cookies (which would be third-party in some setups). That is why categories and consent matter more than the vocabulary.

Cookie categories on Freelance Codex

We group cookies into two categories. This makes the choice straightforward: use the site with only what is required to operate it, or additionally opt in to analytics to help us improve.

1) Essential cookies (always on)

Essential cookies support core site functionality and security. Without them, the site may not work reliably.

Essential cookies may be used for things like:

security protections (for example, protecting forms from abuse),
maintaining your cookie preference choice,
routing and performance stability,
protecting against certain common web attacks.

Because essential cookies are required for the site to function, you cannot opt out of them via our cookie preference tool.

If you want to block all cookies, you can do so in your browser settings, but parts of the site may not work. In practice, the most common issues are:

forms that do not submit reliably,
security features that become overly strict,
being asked for preferences repeatedly.

2) Analytics cookies (optional)

Analytics cookies are optional. When enabled, they help us understand how people use the site so we can improve content and navigation.

We aim for "lightweight analytics" that are:

aggregated (we care about totals and patterns, not stalking individuals),
used for site improvement,
not sold to advertisers.

Analytics data may include:

which pages are viewed,
approximate device/browser information,
general referral source (for example, direct vs search),
broad engagement patterns (for example, whether people find the right page).

Analytics cookies are off by default unless you opt in (depending on how the site is configured). If you opt in, you can also opt out later by resetting your preferences.

If you want to understand the editorial motivation here (why we care about what people find useful), see:

What we do not do

To be explicit:

We do not sell your personal data.
We do not build ad profiles.
We do not use cookies to follow you around the internet for advertising.

Many sites use additional cookie categories such as "marketing" or "targeting" cookies designed for advertising and cross-site profiling. Freelance Codex is not doing that.

This is consistent with the broader commitments in our:

How consent and preference storage work

If you make a cookie choice on Freelance Codex, we store that choice for up to six months. The point is to avoid making you decide on every visit.

Two practical details that surprise people:

The choice is stored in your browser. If you use multiple browsers or devices, you may need to set it more than once.
If you clear cookies or site data, the stored choice may be removed, which can cause a consent prompt to appear again.

Your cookie preference choice is stored for up to six months, unless:

you reset your cookie preferences on this page,
you clear cookies/site data in your browser,
or the site configuration changes in a way that requires new consent.

Manage your preferences

Change your preference on this site

You can change your cookie preference choice at any time by resetting your cookie settings using the preference controls on this page (if available on your current build).

Resetting your preference typically removes the stored choice so the site can ask again (or revert to defaults, depending on the configuration).

If you do not see a preference panel (for example, in some development environments), you can still manage cookies using your browser settings.

Manage cookies in your browser (generic steps)

Browser menus change over time, but the options are usually in a place labeled "Privacy" or "Site settings." In most browsers you can:

view and delete cookies,
block cookies entirely,
block third-party cookies,
set rules per-site.

Be aware: blocking all cookies can break essential site functionality. If your goal is simply "no analytics," it is usually easier to keep cookies enabled generally and opt out of analytics on this page.

Common situations (and what to do)

People manage cookies in different ways depending on their setup. Here are common scenarios and the least-annoying way to handle each one.

You are on a shared/public computer. Consider using a private browsing window so data is less likely to persist. If you do sign in to anything anywhere, sign out and close the browser when finished.
You use private/incognito mode a lot. Some browsers do not persist cookies in those sessions, or they clear them when you close the window. That can make consent prompts reappear.
You clear cookies regularly. If you auto-delete cookies on exit, your stored preference may be removed and you may see the prompt again. Consider setting a per-site exception if you want your preference to stick.
You block third-party cookies. This can reduce cross-site tracking broadly. It may also affect some third-party tools. Freelance Codex still categorizes cookies as essential vs analytics, and we aim to keep third-party usage minimal.
You use privacy extensions/ad blockers. Some extensions block scripts or storage they consider "tracking." That can be compatible with using the site, but it can also cause repeated prompts or unexpected behavior if the extension blocks the preference storage.
You are in an in-app browser. Links opened inside social apps or email clients sometimes have stricter privacy settings and may not store preferences the same way as your normal browser.

"Do Not Track" (DNT)

Some browsers include a "Do Not Track" preference. There is no universal industry standard for DNT responses. We primarily rely on our cookie categories and opt-in approach for analytics, rather than interpreting DNT as a legally binding signal.

Cookies vs other tracking technologies

Some technologies behave like cookies without being "cookies" in a strict browser sense. The key point is that they can also store preferences or measure usage.

local storage
session storage
pixel beacons
server logs

Freelance Codex may use standard server logs for security and performance monitoring (a normal part of operating a website). These logs typically contain information like:

IP address,
request timestamps,
and requested URLs.

If you want details on what we store and why, see: Privacy policy.

Third-party services

Freelance Codex may use third-party services to support:

form protection (anti-spam),
analytics (if enabled),
or site performance and hosting.

If third-party services set cookies, those cookies are governed by the relevant category (essential vs analytics) and by your consent settings.

We aim to keep third-party usage minimal and to prefer services that are privacy-conscious and easy to explain.

If you have a question about a specific service used on the site, contact: Contact.

Why we use optional analytics at all

A maintained reference system is only useful if people can find the right page quickly.

Optional analytics helps us answer practical questions without guessing. For example: if we publish a page and readers consistently bounce, we may need to clarify the first paragraph, tighten the structure, or change how it is linked.

Analytics can help us answer questions like:

Are people landing on the right page for "getting paid on time"?
Are readers dropping off because a page is confusing?
Which tools are actually used (so we maintain the right ones)?
Which internal links help readers move from "confusion" to "action"?

We use those signals to improve:

navigation (for example, Start here and The Codex),
content updates (via Review policy),
and tool usability (via Tools & templates).

If you opt out of analytics, you still get the same content. We will simply have less feedback about what is working.

Troubleshooting

If something feels off, it is usually a browser setting or an extension.

The consent prompt keeps showing up

This usually happens when the browser is not saving the preference. Common causes include:

you cleared cookies/site data,
you are in private/incognito mode,
your browser deletes cookies on exit,
a privacy extension is blocking storage or scripts.

If you want the prompt to stop repeating, allow essential site data for this site and avoid settings that auto-delete cookies.

I opted in/out but nothing seems to change

First, make sure your browser is not blocking cookies entirely. If your preference is stored, you should not be asked again for up to six months (unless you clear data or reset). If you still see the prompt, check extensions and privacy settings.

Frequently asked questions

"Are cookies required to read the site?"

Essential cookies may be required for core functionality and security. You can usually read most content without opting into analytics cookies.

"Can I opt out of analytics and still use the site?"

Yes. Analytics cookies are optional. You can still browse the Codex, Radar, and tools without analytics enabled.

"Does opting into analytics identify me personally?"

We aim to use analytics in an aggregated, privacy-conscious way. If you want details on data handling, read: Privacy policy.

"What happens if I clear my cookies?"

Your stored preferences may be reset. You may be prompted again for consent (depending on site configuration).

"Why am I seeing the consent prompt again?"

Usually one of these is happening:

your browser cleared cookies/site data,
you are using a mode that does not persist cookies,
an extension blocked the preference storage,
or the site configuration changed in a way that requires new consent.

"Can I block all cookies and still use the site?"

Sometimes, but it is not guaranteed. Blocking all cookies can break essential functionality. If your goal is to avoid analytics, it is usually better to allow cookies generally and opt out of analytics on this page.

"Do you use cookies for advertising?"

No. We do not use cookies to follow you around the internet for advertising, we do not build ad profiles, and we do not sell your personal data.

"I have a privacy request or question."

Use: Contact.

Updates to this page

We may update this cookie policy from time to time, for example to clarify wording, reflect changes in how the site works, or explain new features. The last reviewed date and change log below summarize recent updates.