Proposal data notice

Last updated June 17, 2026 · IDCO / idcoapp research program

Share with contributors

Copy the message below when asking friends or colleagues for sample proposals:

Hi — I'm building proposal review and fee-benchmark tools for interior designers at IDCO (idcoapp). I'm collecting a small set of real proposals from trusted designers to calibrate the system.

Before you share anything, please read how we handle proposal data:
https://idcoapp.vercel.app/legal/proposal-data

Short version:
• Voluntary — only share if you're comfortable.
• Please keep project city and state in the document — we use location for localized benchmarks.
• Redact client names, street addresses, and contact details if you can.
• We use proposals to improve benchmarks and review checklists — not for marketing or resale.
• You can ask us to delete your contribution at any time.

Happy to answer questions before you send anything.

Purpose

Interior Design Collective (IDCO) is developing member tools — including AI-assisted proposal review and fee benchmarking — for residential interior designers. To make those tools accurate, we are collecting a limited set of real proposals from volunteer contributors (including friends, colleagues, and family in the design community).

This notice explains what we collect, how we use it, and what choices you have. It applies whether you upload through idcoapp, paste text into the proposal review tool, or send materials to us directly (email, shared drive, etc.).

What you might share

A proposal may include fee schedules, scope of work, procurement language, payment terms, and sometimes client or project identifiers. PDFs and pasted text are both in scope.

We do not need client contact information for this research. Please redact or remove client names, street addresses, phone numbers, and email addresses before sharing when you can. Please leave project city and state in the document — we use location for localized fee benchmarks and do not ask you to remove them.

How we use your proposal

What we store

Proposal documents (full text and PDFs) are not saved in our application database. Content is transmitted to our server for analysis, processed in memory, and sent to our AI provider to generate a report. The report is returned to your browser session.

To improve fee benchmarks and proposal review over time, we store anonymized structured signals in our database when you use the fee calculator or proposal review tool while signed in. These rows do not include your proposal text, uploaded PDFs, finding prose, or client-identifying details.

Member save history vs benchmark telemetry

idcoapp treats these as two separate product tracks. They use different storage, privacy expectations, and future features — and must not be conflated in implementation or copy.

For implementers: see docs/member-history-vs-telemetry.md in the idcoapp repository.

Service providers

Proposal content is processed using third-party infrastructure we rely on to operate idcoapp:

We choose providers with standard security practices. We do not authorize them to use your proposal for their own model training beyond what their published API/data policies describe.

Retention

Benchmark limitations

Benchmarks and review scores reflect IDCO’s corpus and member usage patterns. They are calibrated toward upscale residential interior design and skew toward designers who choose to use idcoapp — not a representative sample of the entire industry or every market.

Localized market tags (US and Canadian metros) help us research regional patterns, but published benchmarks may still blend national defaults until we have enough anonymous events in a market to report localized bands responsibly.

Your choices

Contact & changes

Questions, deletion requests, or concerns: Quinn Casey — quinn@idco.studio.

We may update this notice as the product evolves. The "Last updated" date at the top reflects the current version. Material changes will be communicated to active contributors when practical.