JSON endpoint privacy

Hi Stiofan,

I’m most concerned about the personal data that is entered into listings, like email addresses, telephone numbers, and names.

Alex

Hi Stiofan,

I agree that making non-personal data public is expected, but as for names, telephone numbers, email addresses, and possibly addresses, I think these ought to be protected. A lot of sites assure their users that they will never display contact details publicly, or at least offer the option to keep them hidden.

Is there a way to hide the JSON endpoint pages? Or to protect them with a password, or something?

Alex

Hi Stiofan,

My site is a job and review site. My CPTS are farms, jobs, and resumes, where farms and jobs are linked. Like most job sites, when someone applies to a job the application is sent via a form to avoid displaying the email address publicly on the site. Workers can list resumes on my site and employers can pay to see their contact details, which are sent to them in an email (and not displayed publicly).

Although I’ve hidden all contact details on my site, I’m concerned about them being public in the JSON endpoints, partly because of the paying for contact details side of things, and partly because most people don’t want their contact details displayed publicly.

Alex

Ah cool, thanks 🙂

I know this might sound like a stupid question, but how do I know if I’m using the API or not?