Closed dphillipsatzipline closed 4 years ago
Hi.
Domain part is stored, yes. Purely for statistics/analytics. Nothing is being leaked or shared elsewhere. If you are concerned about privacy you can always use "domain" end-point. Currently it uses same validation methods as using "email" end-point. In future I plan to implement additional check for SMTP response, and it will require mailbox of course, but this feature probably will be available through account registration and some limitations - because providing such service for free can easily lead my API to be blacklisted for some email providers.
Regarding terms and conditions. There are none for currently available free API, you can use it however you want. However, I am monitoring API traffic and any suspicious requests might be blocked without warning.
Is the source code available for us to host this on our own?
From: Kristaps Jaremčuks notifications@github.com Sent: Thursday, January 9, 2020 3:14 PM To: CodeKJ/DISIFY DISIFY@noreply.github.com Cc: Dave Phillips dphillips@zipline.biz; Author author@noreply.github.com Subject: Re: [CodeKJ/DISIFY] Data Sharing Concerns? (#2)
Hi.
Domain part is stored, yes. Purely for statistics/analytics. Nothing is being leaked or shared elsewhere. If you are concerned about privacy you can always use "domain" end-point. Currently it uses same validation methods as using "email" end-point. In future I plan to implement additional check for SMTP response, and it will require mailbox of course, but this feature probably will be available through account registration and some limitations - because providing such service for free can easily lead my API to be blacklisted for some email providers.
Regarding terms and conditions. There are none for currently available free API, you can use it however you want. However, I am monitoring API traffic and any suspicious requests might be blocked without warning.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCodeKJ%2FDISIFY%2Fissues%2F2%3Femail_source%3Dnotifications%26email_token%3DAOHRBYK5LO2A3B2UD4N6VPDQ46ARRA5CNFSM4KE5P3BKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIRUAJI%23issuecomment-572735525&data=02%7C01%7Cdphillips%40zipline.biz%7C24c78be613544f482c2708d795408158%7C7e7a3729108e44d697a90932341c66df%7C0%7C1%7C637141976599797706&sdata=pPVCzSPwCnQP0YXq5A%2Bxx%2BTfmsfcPST4RAWLK3LlKCo%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOHRBYIIGIYS3RZR4J4Z5GLQ46ARRANCNFSM4KE5P3BA&data=02%7C01%7Cdphillips%40zipline.biz%7C24c78be613544f482c2708d795408158%7C7e7a3729108e44d697a90932341c66df%7C0%7C1%7C637141976599807659&sdata=Ke4V3PXn1o9ePhOM%2FdPs%2F%2B8ff11DKg%2Bjd5FI3VTtDec%3D&reserved=0.
In future I might share source for some validation methods used, so you can implement it yourself. But don't expect project code to be publicly available, I plan to extend it with other services and would like to keep it as my intellectual property.
Can you share the validation methods you used?
From: Kristaps Jaremčuks notifications@github.com Sent: Thursday, January 9, 2020 3:23 PM To: CodeKJ/DISIFY DISIFY@noreply.github.com Cc: Dave Phillips dphillips@zipline.biz; Author author@noreply.github.com Subject: Re: [CodeKJ/DISIFY] Data Sharing Concerns? (#2)
In future I might share source for some validation methods used, so you can implement it yourself. But don't expect project code to be publicly available, I plan to extend it with other services and would like to keep it as my intellectual property.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCodeKJ%2FDISIFY%2Fissues%2F2%3Femail_source%3Dnotifications%26email_token%3DAOHRBYK765CDK5AF3WFXNOTQ46BSZA5CNFSM4KE5P3BKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIRUY7I%23issuecomment-572738685&data=02%7C01%7Cdphillips%40zipline.biz%7C4ea4002e6eb0429534fa08d79541be19%7C7e7a3729108e44d697a90932341c66df%7C0%7C0%7C637141981900770361&sdata=R8YIcwumfamIuDASU8mjnWWLUhpJod5%2B3yu5cSNJ0DQ%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOHRBYPSHOAPFE75G7X55O3Q46BSZANCNFSM4KE5P3BA&data=02%7C01%7Cdphillips%40zipline.biz%7C4ea4002e6eb0429534fa08d79541be19%7C7e7a3729108e44d697a90932341c66df%7C0%7C0%7C637141981900780358&sdata=xB%2BUiv%2FXDnydBNv%2BmOQlT%2FtnJAO4qLc9BkIEOQWXUkE%3D&reserved=0.
Not atm. I need to prepare it first, its not something I can simply copy/paste. I will make separate documentation with all API methods, functionality and back-end source for some validations used.
Are the e-mail addresses that are sent in, stored anywhere? Is there any type of terms and conditions users of your API are agreeing to?