Difference between revisions of "Privacy issues"

From Project VRM
Jump to navigation Jump to search
 
Line 1: Line 1:
Very much a stub...
+
Very much a stub...sorry for stream of consciousness, will clean up as soon as possible.
 +
 
 +
Privacy issues relating to spamtastic potential and release of personal information are pretty clear, though requiring significant writeup.  Another privacy-related scenario to consider:
 +
 
 +
whitneymcn (the person) wants to put out RFPs for both Product A and Product B, but does not want vendors (or anyone else) to know that he is looking for both.  Alternate formulation, whitneymcn wants Product C, but does not want the request/acquisition associated with his public "history" (and that history could be build by any vendor, third party, or other seeker who monitors his RFPs).
 +
 
 +
What mechanism allows for anonymizing an RFP from a vendor/public perspective while still reliably linking it back to the seeker?

Revision as of 14:25, 19 December 2006

Very much a stub...sorry for stream of consciousness, will clean up as soon as possible.

Privacy issues relating to spamtastic potential and release of personal information are pretty clear, though requiring significant writeup. Another privacy-related scenario to consider:

whitneymcn (the person) wants to put out RFPs for both Product A and Product B, but does not want vendors (or anyone else) to know that he is looking for both. Alternate formulation, whitneymcn wants Product C, but does not want the request/acquisition associated with his public "history" (and that history could be build by any vendor, third party, or other seeker who monitors his RFPs).

What mechanism allows for anonymizing an RFP from a vendor/public perspective while still reliably linking it back to the seeker?