Privacy

No user accounts No public profiles Permission matters

What Double-D does with your information.

Double-D should collect as little as possible and explain plainly when a visitor sends a note.

Field Notes and contact drafts are meant to help people send corrections, questions, and field lessons. They should not become public stories unless permission is clear.

Current handling

What happens today, what does not, and what requires permission.

Privacy should be understandable in one pass. Double-D should never hide data collection inside confusing platform language.

True Today

What can appear in a note

  • Name, page, correction, question, and next-step notes can be typed into Field Notes.
  • The note should be handled as private unless you give permission to reuse it anonymously.
  • The goal is improving a page, not collecting customer profiles.
Not Used Today

What Double-D is not using today

  • No production user accounts or saved profiles.
  • No public submission database or live newsletter signup.
  • No automated support inbox pretending to be a human relationship.
Policy Update Required

What would require a policy update

  • A real contact destination with clear response expectations.
  • An approved decision on analytics, retention, and hosted form handling.
  • A policy that matches any new account, analytics, email, or submission system before it is used.

Choose the right path

Use the lightest feedback route that fits the job.

The clearest privacy experience is also the simplest one: share only what is needed to solve the problem.

I found a page issue

Use Field Notes when the job is a correction, trust concern, confusing next step, or missing explanation on a specific page.

Open Field Notes

I want to understand what Double-D is

Open About and Contact for the plain-English version of the mission, contact routes, and correction path.

Open About and Contact

I need an account, newsletter, or public submission process

If Double-D adds accounts, newsletters, analytics, or public submissions, this privacy page should explain that before those systems collect information.

Open Terms and Safety

Public basics

Open the other public-basics pages.

Terms and Safety

See the verification, field-responsibility, and no-commerce boundary that sits beside privacy on every planning page.

Open Terms

Accessibility

See the readability, keyboard, mobile, and recovery promises these pages are expected to keep.

Open Accessibility

Need a page corrected?

Use Field Notes when the issue is accuracy, trust, confusion, or a missing next step on a specific page.

Open Field Notes