Contact
Contact Freelance Codex
Want to suggest a topic, report a correction, or submit a question you'd like answered publicly? This page routes you to the right place, tells you what to include, and shows examples so we can act quickly.
Freelance Codex is meant to be maintained. That only works if readers can tell us when something is wrong, missing, confusing, or newly relevant.
This page is the “how to reach us” hub for:
- corrections and factual issues,
- topic suggestions and questions,
- privacy/cookie requests,
- security issues,
- partnership inquiries,
- and general site feedback.
Quick routing (pick the fastest path)
If you're not sure where to start, use this decision list. It reduces back-and-forth and helps us respond (or update the Codex) faster.
- A question you want answered publicly (anonymized): use Ask the Codex.
- A correction, broken link, or outdated page: email [email protected].
- A privacy or cookie request: email [email protected] (and see Privacy policy / Cookie policy).
- A security issue: email [email protected] with steps to reproduce.
- A partnership or tool suggestion: email [email protected] and be explicit about any commercial relationship.
- General site feedback: email [email protected].
Two ways to contact us
We keep contact intentionally simple. There are only two routes: submit a question via the form, or email us directly.
Ask the Codex (best for questions)
If you want to submit a question that might become a public Codex page, use Ask the Codex. The form is designed to capture the context we usually need to answer well: constraints, where you are in your freelance journey, and what decision you're actually trying to make.
Use this route when you're asking something that could help other freelancers too: pricing, scope, contracts, client management, late-payment workflows, positioning, and similar repeatable problems.
If your question is sensitive or you'd prefer it to stay private, email instead. In general, assume anything submitted via Ask the Codex could be paraphrased into an anonymized, maintained answer. If you include identifying details (names, email threads, contract scans), we may not be able to use the submission as-is.
Email (best for corrections, policies, and everything else)
For corrections, privacy/cookie requests, security issues, tool and collaboration outreach, or general feedback, email [email protected].
A specific subject line helps us route your message quickly. Examples: “Correction: [page title]”, “Privacy request”, “Cookie question”, “Security report”, or “Partnership inquiry”.
Prefer to browse before you write?
If you think your question might already be covered, these pages are the fastest “start points”:
What to contact us about (and what to include)
To keep responses fast and useful, route your message to the right category and include the minimum details needed to act. You do not need to write a novel. You do need to be specific.
1) Report a correction (factual error, outdated info, broken link)
Email us at [email protected]
Include (copy/paste friendly):
- the URL of the page
- what is wrong (quote the exact line if possible)
- what the correct information should be
- a source that supports the correction (primary sources preferred)
- why it matters (what a reader might do incorrectly)
Not sure whether something is “wrong” or just unclear? That's still useful. If a section is confusing, missing context, or easy to misread, email us the URL and tell us what you assumed it meant.
If you can include a primary source (official docs, statutory text, vendor documentation, or the original announcement), that's ideal. If you only have a secondary source, include it anyway and tell us what you want verified.
This is the fastest way to improve the Codex reliably, and it helps us keep pages maintained over time.
Related policies:
2) Suggest a new topic (or request a missing page)
If you have a topic idea, the best format is a question (even if you already have opinions). Questions force clarity, and clarity is what turns a “post idea” into something we can maintain.
Example topic requests that tend to be useful:
- “How do I structure milestones for a 6–8 week project?”
- “What’s a sane way to handle Net 60 clients as a solo freelancer?”
- “How do I write a change request without sounding hostile?”
- “How do I raise rates for existing clients without blowing things up?”
Send your suggestion by email, or submit it as a question via Ask the Codex.
If you want your suggestion to be easy to evaluate, include a sentence on who it's for (industry, stage, region) and what the stakes are (what mistake you're trying to avoid).
3) Submit a question you want answered publicly (anonymized)
Use Ask the Codex.
That form is designed to capture the context needed to answer precisely (country, stage, constraints). “Good questions” often become maintained pages, which means you may see an answer show up as a Codex entry later even if you don't receive a long private reply.
4) Partnership inquiries (tools, collaborations, media)
Freelance Codex sometimes references tools and templates. If you represent a tool and want to suggest it, please include:
- what the tool does (one sentence)
- what problem it solves for freelancers
- pricing model
- what makes it reliable over time
- any affiliate or partnership proposal (be explicit)
Important: we do not accept “pay-to-rank” arrangements. If money is involved, we disclose it clearly. See:
When we evaluate a tool suggestion, we care less about marketing claims and more about long-term usefulness: stable pricing, clear documentation, obvious limitations, and whether a freelancer can reasonably adopt it without getting locked into surprises.
For media and citations, include:
- deadline
- what you're writing
- what kind of quote or contribution you need
- and any constraints (jurisdiction, industry, stage)
5) Privacy requests, data questions, cookie preferences
If you have a privacy request, data question, or need help with cookie preferences, email [email protected].
To help us handle your request, include what you want done (for example: question, correction, removal request, or clarification), plus any relevant URLs. If your request is about something you submitted via a form, describe what you submitted and when, so we can locate it.
Relevant pages:
6) Security issues
If you believe you've found a security vulnerability (for example, a form issue or exposure risk), email us and include:
- the affected URL
- steps to reproduce
- what you observed
- screenshots or logs if helpful
Please avoid posting vulnerabilities publicly before we can investigate.
7) General site feedback (bugs, UX issues, confusion)
If something on the site is confusing, broken, or just harder than it should be, email [email protected] and include enough context for us to reproduce it.
- what you expected to happen
- what actually happened
- the page URL (or the step right before it broke)
- your browser + device (approximate is fine)
How to write a message that gets a fast, useful response
Freelancing questions can be conditional. Corrections can be subtle. Security reports can be hard to reproduce. The fastest way to get a useful response (or a fast fix) is to include constraints and specifics.
For corrections
- URL + the exact line/section
- what should be changed
- supporting source
For topic suggestions
- the exact question you want answered
- who it's for (stage, industry, country if relevant)
- why it matters (what failure mode it prevents)
For “help me” questions (private or public)
Include:
- your stage (Start / Run / Grow)
- your country and your client's country (if relevant)
- what you do (one sentence)
- what you've already tried
- what outcome you want
If you're unsure, use the guidance on Ask the Codex.
Examples of good submissions
These examples show the level of detail that tends to be “just enough.” You don't need perfect wording. You do need to make it actionable.
Example: Correction email
Subject: Correction: [page title] has outdated info
Message: URL: [paste URL]. The section that says“...” appears to be outdated. Suggested change: replace it with“...”. Source: [link to primary source or official doc]. Why it matters: a reader following the current version might [describe the mistake].
Example: Topic suggestion
Question: “How should I structure a deposit + milestone schedule for a 2-month project?”
Context: Solo freelancer, [country], typical clients are small teams. The failure mode: I deliver work early, then the last invoice drags for weeks. I'd like a default structure that protects cash flow without being weird for clients.
Example: Ask the Codex submission
“My client wants to switch from fixed-scope to hourly mid-project. How do I propose a change that protects me and keeps trust?”
Include constraints like timeline, the current agreement, what has already changed, and what outcome you want (stay on track, renegotiate scope, reset expectations, etc.).
Example: Privacy/cookie request
Message: I have a privacy request related to [page URL or form submission]. I would like [describe the request clearly]. If you need additional details to locate it, tell me what to provide.
Example: Security report
Message: Potential vulnerability at [URL]. Steps:[1-2-3 reproduction steps]. Observed: [what you saw]. Impact:[what could happen if exploited]. Environment: [browser/device]. I have not shared this publicly.
Example: Partnership/tool suggestion
Message: Tool suggestion: [tool name]. One-line summary: [what it does]. Why it's relevant to freelancers:[specific workflow/problem]. Pricing model: [clear and current]. Reliability notes: [docs, export options, limitations]. Commercial relationship: [affiliate/partnership yes/no, and details].
Anti-spam and safety note
We keep this inbox usable by filtering obvious spam and automated outreach. If your message looks like a bulk template (especially if it's unrelated to the site), we may not reply.
For safety, avoid sending sensitive personal information you wouldn't want stored in an email thread. If you need to point us to something, a URL plus a clear description is usually enough.
What you can expect from us
We're building a maintained reference system, not an inbox that promises instant replies.
That said, we do read messages and we use them to drive what gets fixed, clarified, and expanded.
In general, we try to:
- respond as quickly as we can,
- prioritize corrections and high-stakes issues,
- and fold recurring patterns into maintained pages.
Response time varies based on volume and the kind of request. We can't promise a reply timeline, but messages that include the essentials (URL, constraints, sources, reproduction steps) are much easier to act on quickly.
If you don't hear back, it doesn't necessarily mean your note was ignored. Sometimes the right outcome is a quiet fix, a clarification added to an existing page, or a new page added to the backlog. For how we maintain and review pages, see Review policy.
If your message is:
- a clear correction with a source, or
- a specific, high-stakes question with context,
it is much easier to act on quickly.
Frequently asked questions
“Should I email or use Ask the Codex?”
If it's a question you want answered publicly, use Ask the Codex. If it's a correction, privacy/cookie request, security report, or general feedback, email [email protected].
“Will my question be published?”
Questions submitted via Ask the Codex are intended for potential public answers, with identifying details removed. If you want to keep the discussion private, email instead and share only what you're comfortable having in an inbox.
“Do you reply to every message?”
Not always. We prioritize corrections, security issues, and requests that are easiest to verify and act on. When a message points to a clear improvement, you may see it reflected in a page update even if you don't receive a long reply.
“Where should I start if I’m new to freelancing?”
Start with:
“I have a question about pricing or rates. Where do I go?”
Start with:
“I have a contract clause question.”
Start with:
“A client is paying late. Do you have scripts?”
Yes:
“Do you offer legal, tax, or financial advice?”
No. We provide educational information and templates, not legal, tax, or financial advice. For high-stakes situations, consult qualified professionals in your jurisdiction. See:
“Can I request removal of something I submitted?”
Yes. Email us with the details. See Privacy policy.