5 ms·

This is a more general question, but: What company would be comfortable with giving out schematics, source code, etc... to third parties like this or AI Model

This is a more general question, but: What company would be comfortable with giving out schematics, source code, etc... to third parties like this or AI Model providers like Anthropic, etc... Privacy policy aside, this just seems like a statistical guarantee at some point to leaks sensitive IP (not specifically pointing at this company, but in this space in general). Or does nobody care?

etgibbs 1y ago
great question. we've found most code/docs are offline in the embedded space (for good reason) so our approach going forward is going to be more FDE/on-prem for enterprise users. they asked for self-hosted, BYOK, local indexing, etc. and I think this is something that can differentiate us for consumer users we have a zero-retention policy with the model providers, and we use repo mapper to index your code locally, but as you pointed out these APIs are a black box so no guarantees
- Terretta 1y ago
  Your policy and this comment conflict.
  - etgibbs 1y ago
    need to update the policy, this was for the original version of the app, which used a deterministic algorithm to generate driver code, which we stored on cloud so you could download the files. thanks for pointing this out.
NotBoolean 1y ago
Embedder’s privacy policy is very clear that they keep your information. https://embedder.dev/privacy-policy https://embedder.dev/privacy-policy “Content Data When you use our services, we collect: Any files or data you upload Any generated code or data”
- etgibbs 1y ago
  we store the files you upload for indexing we don't store generated code / data, but it does pass through our API to the model provider. we store the usage meta data for billing purposes
  - tensility 1y ago
    "we store the files you upload for indexing" Screw that. No way.
- Catbert59 1y ago
  > Any files or data you upload Any generated code or data” That renders it entirely unusable for us :-( We work a lot with heavily NDA'ed datasheets/sources.

etgibbs 1y ago

great question. we've found most code/docs are offline in the embedded space (for good reason) so our approach going forward is going to be more FDE/on-prem for enterprise users. they asked for self-hosted, BYOK, local indexing, etc. and I think this is something that can differentiate us for consumer users we have a zero-retention policy with the model providers, and we use repo mapper to index your code locally, but as you pointed out these APIs are a black box so no guarantees

Terretta 1y ago
Your policy and this comment conflict.
- etgibbs 1y ago
  need to update the policy, this was for the original version of the app, which used a deterministic algorithm to generate driver code, which we stored on cloud so you could download the files. thanks for pointing this out.

NotBoolean 1y ago

Embedder’s privacy policy is very clear that they keep your information. https://embedder.dev/privacy-policy https://embedder.dev/privacy-policy “Content Data When you use our services, we collect: Any files or data you upload Any generated code or data”

etgibbs 1y ago
we store the files you upload for indexing we don't store generated code / data, but it does pass through our API to the model provider. we store the usage meta data for billing purposes
- tensility 1y ago
  "we store the files you upload for indexing" Screw that. No way.
Catbert59 1y ago
> Any files or data you upload Any generated code or data” That renders it entirely unusable for us :-( We work a lot with heavily NDA'ed datasheets/sources.