Privacy policy

This privacy policy explains what information Freelance Codex collects, why it is collected, how it is used, and what choices you have.

We aim to keep this plain-language and practical. If you have questions, or you want to request access/deletion of information you submitted, contact us:

• Contact

This policy complements:

• Cookie policy (how cookies and analytics preferences work)
• Terms (use of the site and disclaimers)

Summary (the short version)

• We collect information you submit through forms (for example, Ask the Codex) or by emailing us, plus basic site usage data if you opt into analytics.
• We use collected information to respond to messages, operate the site, improve content, and keep the site secure.
• We do not sell personal data or build advertising profiles.
• You can control optional analytics via cookie preferences. See: Cookie policy
• You can request access, correction, or deletion of information you submitted by contacting us: Contact

What counts as “personal data” here

“Personal data” (or “personal information”) generally means information that identifies you, directly or indirectly. We treat user-submitted information and identifiable technical data carefully.

On Freelance Codex, personal data can include:

• direct identifiers you provide, like an email address (if you include one)
• the content of messages you submit, if it includes identifying details
• technical identifiers in server logs, like an IP address or user agent string
• analytics identifiers and usage data, if you opt into analytics (where applicable)

Some information becomes identifying when combined with other information. That’s one reason we keep optional analytics under consent controls (where required).

What we collect

We collect information in a few categories. The specifics depend on how you use the site.

1) Information you submit (forms and messages)

If you submit a form (for example, via Ask the Codex) or send us a message, we may collect:

• your email address (if provided)
• the content of your message or question
• any contextual fields you submit (for example, country, freelancing stage, or other details you choose to include)

Important: you control what you submit. If you want to keep something private, don’t include it. Avoid sharing sensitive personal information that is not needed to answer your question.

2) Communication metadata

If you contact us, we may retain metadata such as:

• date/time of your message
• delivery status
• and basic email headers (as typical with email communication)

3) Site usage data (analytics, optional)

If you opt into analytics cookies (where applicable), we may collect usage data such as:

• pages visited
• approximate device/browser details
• general referrer information (for example, direct vs search)
• aggregate engagement signals

We use this data to improve navigation and content quality (for example, making it easier to find the right Codex page quickly).

Analytics are optional where consent is required. For details and controls, see:

• Cookie policy

4) Server logs (security and operations)

Like most websites, our servers may log basic request information for security and performance, such as:

• IP address
• user agent (browser type)
• request timestamps
• requested URLs
• error logs

These logs help us:

• detect abuse and attacks
• debug performance issues
• keep the site reliable

This is standard operational logging and is not used to build advertising profiles.

5) Cookies and local storage

We may use cookies and similar storage (for example, local storage) for:

• essential site functionality (security, preference storage)
• optional analytics (if enabled with consent)

See: Cookie policy

How we use information

We use collected information for the following purposes.

1) Responding to requests and messages

If you submit a question or contact us, we use your information to:

• read your submission
• respond or follow up
• clarify details if needed
• and (in some cases) improve public content based on recurring questions

If you submit via Ask the Codex, we may use your question to create a public page (anonymized) if it is common and high-stakes. We do not publish identifying details.

2) Improving content and site usability

Freelance Codex is designed as a maintained reference system, not a one-off blog. To improve it, we may:

• track which pages are most visited (aggregate)
• identify confusing navigation paths (aggregate)
• refine internal linking between related pages

This is part of keeping the site useful over time. If you want the editorial trust model, read:

• Editorial standards
• Review policy

3) Operating and securing the site

We use operational data (including server logs and essential cookies) to:

• keep the site functional and secure
• prevent spam and abuse
• maintain performance and availability

What we do not do

To be explicit:

• We do not sell personal data.
• We do not build advertising profiles.
• We do not “track you across the internet” for ad targeting.

If we ever recommend tools or partners, we disclose relationships transparently:

• Disclosure policy

Legal bases and jurisdiction notes (plain-language)

Privacy obligations vary by jurisdiction (for example, the EU/UK, US states, and others). We are not providing legal advice here. Instead, we describe our practical approach.

Depending on applicable laws, we may rely on:

• consent (for optional analytics cookies, where required)
• legitimate interests (operating and securing the site, improving content)
• contractual necessity (responding to a request you initiate)
• legal obligations (where applicable)

If you have jurisdiction-specific questions, contact us:

• Contact

Data sharing and third-party services

We may use third-party services to operate the site. Depending on the service, some information may be processed by those providers on our behalf.

Examples of service categories:

• hosting and content delivery
• form processing and spam protection
• analytics (optional, based on consent)
• email service providers (for handling messages)

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

We do not allow third-party services to use data for their own advertising purposes on our behalf (where we have control of the configuration), and we do not sell personal data to them.

If you want details about a specific provider used at a point in time, contact us:

• Contact

Publishing submissions (Ask the Codex) and anonymization

If you submit a question via Ask the Codex, your question may influence public content in one of three ways:

1. We answer privately (no publication).
2. We publish an anonymized Codex page based on the question.
3. We improve an existing page or tool based on the question.

If we publish:

• we remove identifying details (names, company identifiers, unique project markers)
• we do not publish your email address
• we do not publish private documents or sensitive personal data

However, anonymous does not mean “impossible to infer” in all cases. If your situation is uniquely identifiable, avoid sharing details you wouldn’t want public.

If you want something removed later, contact us:

• Contact

Data retention: how long we keep information

We aim to keep information only as long as needed to:

• respond to requests
• maintain site operations
• comply with legal obligations (if applicable)

We do not list fixed retention periods here because needs vary. We keep data only as long as necessary for the purposes described above.

Retention principles

Our retention approach is:

• purpose-limited: kept only for the reason it was collected
• data-minimizing: we avoid collecting extra details and encourage you not to submit unnecessary sensitive information
• access-controlled: we limit who can access submissions and operational logs
• reviewable: we may delete or anonymize older material when it no longer serves a clear purpose

If you request deletion, we generally focus on removing data from active systems where feasible. Some copies may persist in logs or backups for a period; access is restricted and systems overwrite data as they cycle.

Form submissions and emails

We may retain submissions and email correspondence for a reasonable period to:

• respond to your request
• identify recurring questions to improve the Codex
• maintain a record of corrections and update history

Deletion requests work best when you share enough context to locate the right submission (for example, which message or related page). For published content, we may remove, edit, or further anonymize it depending on the request.

If you want your submission deleted (where feasible), contact us:

• Contact

Analytics (if enabled)

Analytics data is typically retained in aggregated form to detect trends and improve content. Exact retention may vary by analytics provider configuration. You can opt out of analytics cookies via:

• Cookie policy

Disabling analytics cookies stops future analytics collection on this device/browser. It may not remove past analytics events that were already included in aggregated reporting.

Server logs

Operational logs are usually retained for a limited period for security and debugging purposes. Retention length may vary depending on operational needs and hosting configurations.

Security

We use reasonable safeguards to protect information, such as:

• access controls
• secure hosting practices
• spam/abuse protections on forms (where configured)

No system is perfectly secure. If you believe you’ve found a security issue, report it responsibly:

• Contact

Your choices and rights

Your rights depend on your jurisdiction, but we support reasonable requests related to data you submit.

Common requests include:

• access: “What information do you have from me?”
• correction: “This information is wrong.”
• deletion: “Please delete my submission.”
• consent control: “I want to disable analytics cookies.”

1) Control analytics cookies

Use cookie preference controls (where available) or browser settings:

• Cookie policy

2) Request access, correction, or deletion

Contact us with:

• the email address you used (if applicable)
• the URL or context (what you submitted)
• what you want (access/correction/deletion)

We may need to verify the request to prevent unauthorized changes.

What happens after you contact us (in general):

1. We locate the relevant information (and may ask clarifying questions).
2. We may take steps to verify the request, especially for deletion or correction.
3. We fulfill the request where feasible, or explain practical limits.

We may keep a minimal record that a request was handled (for example, to prevent abuse), but we try to keep it limited.

Contact:

• Contact

FAQ

Do you sell personal data?

No. We do not sell personal data, and we do not build advertising profiles.

Do you use targeted advertising or “track me across the internet”?

We do not configure Freelance Codex to track you across other websites for ad targeting. Some third-party services may process limited data to provide infrastructure, but they are used to operate the site, not to build advertising profiles.

Can I use Freelance Codex without optional analytics?

Yes. Where consent is required, analytics are optional and are controlled via cookie preferences. Essential cookies (and basic operational logging) may still be used for security and basic site functionality.

To learn more or change your settings, see the Cookie policy.

What should I avoid submitting in a form or message?

Avoid sharing sensitive personal information that is not needed to answer your question. If you’re asking about a situation involving a client or employer, consider removing or generalizing details that could identify them (or you).

If I submit a question, will it be published?

Not necessarily. If you submit a question via Ask the Codex, we may answer privately, publish an anonymized page based on a common question, or use the submission to improve existing content. If we publish, we remove identifying details and do not publish your email address.

How do you handle requests to remove published content?

If a published page appears to include identifying details or you want it removed, contact us with the URL and context. Depending on the situation, we may remove the page, edit it, or further anonymize it. If search engines have cached older versions, we may not control how quickly those caches update.

How do I make a privacy request (access, correction, deletion)?

Use the contact page and include the email address you used (if any) and enough detail to find the relevant information. We may ask follow-up questions to verify the request or locate the right submission.

Children’s privacy

Freelance Codex is intended for adults and professional use. We do not intentionally collect personal information from children. If you believe a child has provided personal information, contact us and we will address it:

• Contact

International users

Freelance Codex may be accessed from multiple countries. Depending on where services are hosted and where you are located, information may be processed in different jurisdictions.

If you have a question about cross-border data handling, contact us:

• Contact

Changes to this policy

We may update this privacy policy as the site evolves. When we make material changes, we will update the policy and its “last reviewed” date.

For how we handle content maintenance generally, see:

• Review policy

Questions or requests

For any privacy question or request, contact:

• Contact