Skip to main content
replaced http://crypto.stackexchange.com/ with https://crypto.stackexchange.com/
Source Link

For those interested, here is the full text of the email that the Stack Exchange legal folks sent to me (and, I assume, to all other users who had posted answers). It describes how to send a counter-notification. I encourage everyone who posted an answer to read carefully and decide whether you want to send a counter-notification.

Dear Member:

This is to notify you that we have removed or disabled access to the following material as a result of a third-party notification by CipherCloud claiming that this material is infringing:

How is CipherCloud doing homomorphic encryption?: How is CipherCloud doing homomorphic encryption?How is CipherCloud doing homomorphic encryption?

Please Note: In order to avoid future strikes against your account, please delete any text to which you do not own the rights, and refrain from uploading additional text that infringe on the copyrights of others.

For more information about Stack Exchange's copyright policy, please read http://stackexchange.com/legal

If you elect to send us a counter notice, to be effective it must be a written communication provided to our designated agent that includes substantially the following (please consult your legal counsel or see 17 U.S.C. Section 512(g)(3) to confirm these requirements):

(A) A physical or electronic signature of the subscriber.

(B) Identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled.

(C) A statement under penalty of perjury that the subscriber has a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled.

(D) The subscriber's name, address, and telephone number, and a statement that the subscriber consents to the jurisdiction of Federal District Court for the judicial district in which the address is located, or if the subscriber's address is outside of the United States, for any judicial district in which the service provider may be found, and that the subscriber will accept service of process from the person who provided notification under subsection (c)(1)(C) or an agent of such person.

Such written notice should be sent to our designated agent as follows:

DMCA Complaints Stack Exchange, Inc. One Exchange Plaza 26th Floor New York, NY 10006 Email: [email protected]

Please note that under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability.

Sincerely,

Stack Exchange Inc.

Update: I've posted a copy of the takedown notice from CipherCloud, separately.

For those interested, here is the full text of the email that the Stack Exchange legal folks sent to me (and, I assume, to all other users who had posted answers). It describes how to send a counter-notification. I encourage everyone who posted an answer to read carefully and decide whether you want to send a counter-notification.

Dear Member:

This is to notify you that we have removed or disabled access to the following material as a result of a third-party notification by CipherCloud claiming that this material is infringing:

How is CipherCloud doing homomorphic encryption?: How is CipherCloud doing homomorphic encryption?

Please Note: In order to avoid future strikes against your account, please delete any text to which you do not own the rights, and refrain from uploading additional text that infringe on the copyrights of others.

For more information about Stack Exchange's copyright policy, please read http://stackexchange.com/legal

If you elect to send us a counter notice, to be effective it must be a written communication provided to our designated agent that includes substantially the following (please consult your legal counsel or see 17 U.S.C. Section 512(g)(3) to confirm these requirements):

(A) A physical or electronic signature of the subscriber.

(B) Identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled.

(C) A statement under penalty of perjury that the subscriber has a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled.

(D) The subscriber's name, address, and telephone number, and a statement that the subscriber consents to the jurisdiction of Federal District Court for the judicial district in which the address is located, or if the subscriber's address is outside of the United States, for any judicial district in which the service provider may be found, and that the subscriber will accept service of process from the person who provided notification under subsection (c)(1)(C) or an agent of such person.

Such written notice should be sent to our designated agent as follows:

DMCA Complaints Stack Exchange, Inc. One Exchange Plaza 26th Floor New York, NY 10006 Email: [email protected]

Please note that under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability.

Sincerely,

Stack Exchange Inc.

Update: I've posted a copy of the takedown notice from CipherCloud, separately.

For those interested, here is the full text of the email that the Stack Exchange legal folks sent to me (and, I assume, to all other users who had posted answers). It describes how to send a counter-notification. I encourage everyone who posted an answer to read carefully and decide whether you want to send a counter-notification.

Dear Member:

This is to notify you that we have removed or disabled access to the following material as a result of a third-party notification by CipherCloud claiming that this material is infringing:

How is CipherCloud doing homomorphic encryption?: How is CipherCloud doing homomorphic encryption?

Please Note: In order to avoid future strikes against your account, please delete any text to which you do not own the rights, and refrain from uploading additional text that infringe on the copyrights of others.

For more information about Stack Exchange's copyright policy, please read http://stackexchange.com/legal

If you elect to send us a counter notice, to be effective it must be a written communication provided to our designated agent that includes substantially the following (please consult your legal counsel or see 17 U.S.C. Section 512(g)(3) to confirm these requirements):

(A) A physical or electronic signature of the subscriber.

(B) Identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled.

(C) A statement under penalty of perjury that the subscriber has a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled.

(D) The subscriber's name, address, and telephone number, and a statement that the subscriber consents to the jurisdiction of Federal District Court for the judicial district in which the address is located, or if the subscriber's address is outside of the United States, for any judicial district in which the service provider may be found, and that the subscriber will accept service of process from the person who provided notification under subsection (c)(1)(C) or an agent of such person.

Such written notice should be sent to our designated agent as follows:

DMCA Complaints Stack Exchange, Inc. One Exchange Plaza 26th Floor New York, NY 10006 Email: [email protected]

Please note that under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability.

Sincerely,

Stack Exchange Inc.

Update: I've posted a copy of the takedown notice from CipherCloud, separately.

replaced http://meta.crypto.stackexchange.com/ with https://crypto.meta.stackexchange.com/
Source Link

For those interested, here is the full text of the email that the Stack Exchange legal folks sent to me (and, I assume, to all other users who had posted answers). It describes how to send a counter-notification. I encourage everyone who posted an answer to read carefully and decide whether you want to send a counter-notification.

Dear Member:

This is to notify you that we have removed or disabled access to the following material as a result of a third-party notification by CipherCloud claiming that this material is infringing:

How is CipherCloud doing homomorphic encryption?: How is CipherCloud doing homomorphic encryption?

Please Note: In order to avoid future strikes against your account, please delete any text to which you do not own the rights, and refrain from uploading additional text that infringe on the copyrights of others.

For more information about Stack Exchange's copyright policy, please read http://stackexchange.com/legal

If you elect to send us a counter notice, to be effective it must be a written communication provided to our designated agent that includes substantially the following (please consult your legal counsel or see 17 U.S.C. Section 512(g)(3) to confirm these requirements):

(A) A physical or electronic signature of the subscriber.

(B) Identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled.

(C) A statement under penalty of perjury that the subscriber has a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled.

(D) The subscriber's name, address, and telephone number, and a statement that the subscriber consents to the jurisdiction of Federal District Court for the judicial district in which the address is located, or if the subscriber's address is outside of the United States, for any judicial district in which the service provider may be found, and that the subscriber will accept service of process from the person who provided notification under subsection (c)(1)(C) or an agent of such person.

Such written notice should be sent to our designated agent as follows:

DMCA Complaints Stack Exchange, Inc. One Exchange Plaza 26th Floor New York, NY 10006 Email: [email protected]

Please note that under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability.

Sincerely,

Stack Exchange Inc.

Update: I've posted a copy of the takedown notice from CipherClouda copy of the takedown notice from CipherCloud, separately.

For those interested, here is the full text of the email that the Stack Exchange legal folks sent to me (and, I assume, to all other users who had posted answers). It describes how to send a counter-notification. I encourage everyone who posted an answer to read carefully and decide whether you want to send a counter-notification.

Dear Member:

This is to notify you that we have removed or disabled access to the following material as a result of a third-party notification by CipherCloud claiming that this material is infringing:

How is CipherCloud doing homomorphic encryption?: How is CipherCloud doing homomorphic encryption?

Please Note: In order to avoid future strikes against your account, please delete any text to which you do not own the rights, and refrain from uploading additional text that infringe on the copyrights of others.

For more information about Stack Exchange's copyright policy, please read http://stackexchange.com/legal

If you elect to send us a counter notice, to be effective it must be a written communication provided to our designated agent that includes substantially the following (please consult your legal counsel or see 17 U.S.C. Section 512(g)(3) to confirm these requirements):

(A) A physical or electronic signature of the subscriber.

(B) Identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled.

(C) A statement under penalty of perjury that the subscriber has a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled.

(D) The subscriber's name, address, and telephone number, and a statement that the subscriber consents to the jurisdiction of Federal District Court for the judicial district in which the address is located, or if the subscriber's address is outside of the United States, for any judicial district in which the service provider may be found, and that the subscriber will accept service of process from the person who provided notification under subsection (c)(1)(C) or an agent of such person.

Such written notice should be sent to our designated agent as follows:

DMCA Complaints Stack Exchange, Inc. One Exchange Plaza 26th Floor New York, NY 10006 Email: [email protected]

Please note that under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability.

Sincerely,

Stack Exchange Inc.

Update: I've posted a copy of the takedown notice from CipherCloud, separately.

For those interested, here is the full text of the email that the Stack Exchange legal folks sent to me (and, I assume, to all other users who had posted answers). It describes how to send a counter-notification. I encourage everyone who posted an answer to read carefully and decide whether you want to send a counter-notification.

Dear Member:

This is to notify you that we have removed or disabled access to the following material as a result of a third-party notification by CipherCloud claiming that this material is infringing:

How is CipherCloud doing homomorphic encryption?: How is CipherCloud doing homomorphic encryption?

Please Note: In order to avoid future strikes against your account, please delete any text to which you do not own the rights, and refrain from uploading additional text that infringe on the copyrights of others.

For more information about Stack Exchange's copyright policy, please read http://stackexchange.com/legal

If you elect to send us a counter notice, to be effective it must be a written communication provided to our designated agent that includes substantially the following (please consult your legal counsel or see 17 U.S.C. Section 512(g)(3) to confirm these requirements):

(A) A physical or electronic signature of the subscriber.

(B) Identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled.

(C) A statement under penalty of perjury that the subscriber has a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled.

(D) The subscriber's name, address, and telephone number, and a statement that the subscriber consents to the jurisdiction of Federal District Court for the judicial district in which the address is located, or if the subscriber's address is outside of the United States, for any judicial district in which the service provider may be found, and that the subscriber will accept service of process from the person who provided notification under subsection (c)(1)(C) or an agent of such person.

Such written notice should be sent to our designated agent as follows:

DMCA Complaints Stack Exchange, Inc. One Exchange Plaza 26th Floor New York, NY 10006 Email: [email protected]

Please note that under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability.

Sincerely,

Stack Exchange Inc.

Update: I've posted a copy of the takedown notice from CipherCloud, separately.

added 134 characters in body
Source Link
D.W.
  • 36.7k
  • 16
  • 28

For those interested, here is the full text of the email that the Stack Exchange legal folks sent to me (and, I assume, to all other users who had posted answers). It describes how to send a counter-notification. I encourage everyone who posted an answer to read carefully and decide whether you want to send a counter-notification.

Dear Member:

This is to notify you that we have removed or disabled access to the following material as a result of a third-party notification by CipherCloud claiming that this material is infringing:

How is CipherCloud doing homomorphic encryption?: How is CipherCloud doing homomorphic encryption?

Please Note: In order to avoid future strikes against your account, please delete any text to which you do not own the rights, and refrain from uploading additional text that infringe on the copyrights of others.

For more information about Stack Exchange's copyright policy, please read http://stackexchange.com/legal

If you elect to send us a counter notice, to be effective it must be a written communication provided to our designated agent that includes substantially the following (please consult your legal counsel or see 17 U.S.C. Section 512(g)(3) to confirm these requirements):

(A) A physical or electronic signature of the subscriber.

(B) Identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled.

(C) A statement under penalty of perjury that the subscriber has a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled.

(D) The subscriber's name, address, and telephone number, and a statement that the subscriber consents to the jurisdiction of Federal District Court for the judicial district in which the address is located, or if the subscriber's address is outside of the United States, for any judicial district in which the service provider may be found, and that the subscriber will accept service of process from the person who provided notification under subsection (c)(1)(C) or an agent of such person.

Such written notice should be sent to our designated agent as follows:

DMCA Complaints Stack Exchange, Inc. One Exchange Plaza 26th Floor New York, NY 10006 Email: [email protected]

Please note that under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability.

Sincerely,

Stack Exchange Inc.New

Update: I've posted a copy of the takedown notice from CipherCloud, separately.

For those interested, here is the full text of the email that the Stack Exchange legal folks sent to me (and, I assume, to all other users who had posted answers). It describes how to send a counter-notification. I encourage everyone who posted an answer to read carefully and decide whether you want to send a counter-notification.

Dear Member:

This is to notify you that we have removed or disabled access to the following material as a result of a third-party notification by CipherCloud claiming that this material is infringing:

How is CipherCloud doing homomorphic encryption?: How is CipherCloud doing homomorphic encryption?

Please Note: In order to avoid future strikes against your account, please delete any text to which you do not own the rights, and refrain from uploading additional text that infringe on the copyrights of others.

For more information about Stack Exchange's copyright policy, please read http://stackexchange.com/legal

If you elect to send us a counter notice, to be effective it must be a written communication provided to our designated agent that includes substantially the following (please consult your legal counsel or see 17 U.S.C. Section 512(g)(3) to confirm these requirements):

(A) A physical or electronic signature of the subscriber.

(B) Identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled.

(C) A statement under penalty of perjury that the subscriber has a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled.

(D) The subscriber's name, address, and telephone number, and a statement that the subscriber consents to the jurisdiction of Federal District Court for the judicial district in which the address is located, or if the subscriber's address is outside of the United States, for any judicial district in which the service provider may be found, and that the subscriber will accept service of process from the person who provided notification under subsection (c)(1)(C) or an agent of such person.

Such written notice should be sent to our designated agent as follows:

DMCA Complaints Stack Exchange, Inc. One Exchange Plaza 26th Floor New York, NY 10006 Email: [email protected]

Please note that under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability.

Sincerely,

Stack Exchange Inc.New

For those interested, here is the full text of the email that the Stack Exchange legal folks sent to me (and, I assume, to all other users who had posted answers). It describes how to send a counter-notification. I encourage everyone who posted an answer to read carefully and decide whether you want to send a counter-notification.

Dear Member:

This is to notify you that we have removed or disabled access to the following material as a result of a third-party notification by CipherCloud claiming that this material is infringing:

How is CipherCloud doing homomorphic encryption?: How is CipherCloud doing homomorphic encryption?

Please Note: In order to avoid future strikes against your account, please delete any text to which you do not own the rights, and refrain from uploading additional text that infringe on the copyrights of others.

For more information about Stack Exchange's copyright policy, please read http://stackexchange.com/legal

If you elect to send us a counter notice, to be effective it must be a written communication provided to our designated agent that includes substantially the following (please consult your legal counsel or see 17 U.S.C. Section 512(g)(3) to confirm these requirements):

(A) A physical or electronic signature of the subscriber.

(B) Identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed or access to it was disabled.

(C) A statement under penalty of perjury that the subscriber has a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled.

(D) The subscriber's name, address, and telephone number, and a statement that the subscriber consents to the jurisdiction of Federal District Court for the judicial district in which the address is located, or if the subscriber's address is outside of the United States, for any judicial district in which the service provider may be found, and that the subscriber will accept service of process from the person who provided notification under subsection (c)(1)(C) or an agent of such person.

Such written notice should be sent to our designated agent as follows:

DMCA Complaints Stack Exchange, Inc. One Exchange Plaza 26th Floor New York, NY 10006 Email: [email protected]

Please note that under Section 512(f) of the Copyright Act, any person who knowingly materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability.

Sincerely,

Stack Exchange Inc.

Update: I've posted a copy of the takedown notice from CipherCloud, separately.

Source Link
D.W.
  • 36.7k
  • 16
  • 28
Loading