Privacy Policy

This policy describes what data may be processed when you use spec-coding.dev and how we handle it.

Data Controller

The data controller for this website is the Spec Coding editorial team. For privacy-related inquiries, contact [email protected].

Information We Collect

Cookies and Advertising

This site uses Google AdSense to display advertisements. Google AdSense uses the DoubleClick DART cookie to serve ads based on your prior visits to this site and other sites on the internet. The DART cookie enables Google and its partners to serve ads based on your visit to this site and/or other sites on the internet.

Third-party advertising partners, including Google, may place or read cookies, use device identifiers, or use web beacons and similar technologies as a result of ad serving on this site. These technologies help with ad personalization where allowed, non-personalized contextual ads, fraud prevention, frequency capping, and ad measurement.

Cookie types used on this site:

You may opt out of the use of the DART cookie by visiting the Google ad and content network privacy policy. You can also opt out of personalized advertising entirely at Google Ads Settings or through the Network Advertising Initiative opt-out page.

If you prefer not to receive personalized ads, Google may still show you non-personalized ads based on contextual signals such as page content and general location.

Our ad placement rules and editorial independence disclosures are documented in the Advertising Policy.

Newsletter and email subscriptions

If you subscribe via the newsletter form in the site footer, we collect your email address for the sole purpose of sending occasional updates about new articles and resources on Spec Coding. Submissions are processed through Formspree, a third-party form service. We do not sell, rent, or share your email address with any other party.

You can unsubscribe at any time by emailing [email protected] with the subject line "Unsubscribe." We will remove your address within five business days.

Legal Basis for Processing

Third-Party Services

Data handling by third-party services is governed by their own privacy terms. We do not share your personal data with third parties beyond what is required for these services to function.

Data Retention

Server logs are retained for a maximum of 90 days. Analytics data is retained according to the default Google Analytics retention period. Local storage preferences (theme and cookie consent) persist until you clear your browser data.

Local Drafts and Generator Inputs

Some tools may store temporary draft values in your browser so you can recover a form after refresh. These values stay on your device unless you submit a contact form or use a third-party service outside this site. You can clear local drafts by resetting the tool or clearing browser site data.

Avoid entering production secrets, credentials, private customer data, or confidential incident details into public web forms. Use representative examples when drafting specs for sensitive systems.

If you use a shared or managed device, remember that browser sync, extensions, device management software, or organizational logging may affect how local data is stored. Those controls are outside Spec Coding and should be reviewed under your own organization policy.

For sensitive specs, prefer placeholder values that preserve structure without exposing real customer names, internal hostnames, access tokens, project codenames, or unreleased pricing.

Use the same caution before sharing generated output with external tools, contractors, or public issue trackers.

Practical Review Before Sharing a Spec

Before copying a generated spec into an external chat tool, public issue tracker, contractor handoff, or community forum, scan it for identifiers that are easy to overlook: customer IDs, internal table names, incident timestamps, unreleased feature names, private repository paths, auth headers, and environment-specific URLs. Replace them with representative values that preserve the shape of the problem without exposing the underlying system.

If a spec must include sensitive operational detail, keep that version inside your approved company workspace and share a sanitized summary externally. Spec Coding can help with structure, but it cannot determine your organization's data classification rules.

Data Minimization in Practice

When using a generator, enter only the information needed to describe behavior. Replace customer names, secrets, internal domains, exact incident timestamps, production IDs, and unreleased product names with placeholders. Keep the structure of the problem, but remove identifiers that would create avoidable privacy or security exposure.

If you later paste generated output into another tool, review that destination's privacy policy separately. Spec Coding can keep local drafts in your browser, but it cannot control how third-party tools process text after you copy it away from this site.

Your Rights

Contact

Questions about this policy: [email protected].

Effective date: February 25, 2026 · Last updated: April 29, 2026