DeepInfra Terms of Service

DeepInfra · Official agreement

Read the agreement

5 of 81 cards in Retention & Deletion

Retention & Deletion · Company commitment

The Zero Data Retention commitment overrides the Privacy Policy and other Provider documents; the DPA only adds to it

The Terms say the Zero Data Retention commitment in Section 7(b) controls over the Privacy Policy and any other Provider policy, webpage or documentation. The DPA supplements, and does not narrow, that commitment, which this section says "applies to all Customer Data". Section 7(b) itself states that Zero Data Retention applies to models hosted by Provider.

Supporting quotations

Notwithstanding the foregoing, the Zero Data Retention commitment in Section 7(b) controls over the Privacy Policy and any other Provider policy, webpage, or documentation, and the DPA supplements, and does not narrow, that commitment, which applies to all Customer Data.
Provider will not retain, store, or log any Customer Data submitted to or generated by the Services beyond the period strictly necessary to process and return the applicable request

Qualifications & exceptions

  • Section 7(b) lists exceptions (support retention, operational metadata, legal and abuse records, features Customer elects) and limits the commitment to models hosted by Provider.

Not stated here

  • The text does not say whether "applies to all Customer Data" here is meant to include Customer Data sent to third-party models, which Section 7(b) says is governed by Section 18 and the third party's terms.

Cross-references

Also annotated in the same passage (6)

Retention & Deletion · Company commitment

Zero Data Retention: DeepInfra will not keep or log Customer Data beyond what is needed to process the request

Provider says it will not retain, store or log any Customer Data submitted to or generated by the Services beyond the period strictly necessary to process and return the applicable request. After that the data is deleted from Provider's systems in the ordinary course of operations ("Zero Data Retention"). Key-value and prefix cache state derived from Customer Data is held temporarily in memory solely to serve requests and is not used for any other purpose.

Supporting quotations

Provider will not retain, store, or log any Customer Data submitted to or generated by the Services beyond the period strictly necessary to process and return the applicable request, after which such Customer Data is deleted from Provider's systems in the ordinary course of operations ("Zero Data Retention").
Key-value and prefix cache state derived from Customer Data is held temporarily in memory solely to serve requests and is not used for any other purpose.

Qualifications & exceptions

  • Deletion happens "in the ordinary course of operations"; no deletion deadline is given.
  • Four exceptions follow in the same section, and the commitment is stated to apply to models hosted by Provider.

Not stated here

  • "The period strictly necessary to process and return the applicable request" is not defined in time.

Cross-references

Also annotated in the same passage (5)

Retention & Deletion · Restriction or exception

Zero Data Retention excludes support copies, operational metadata, legal and abuse records, and features Customer elects

The Zero Data Retention commitment does not apply to four things: (i) Customer Data Provider keeps at Customer's written request or with its prior written authorization to diagnose or resolve a support or Service issue, deleted within 30 days after the issue is resolved; (ii) non-content operational metadata such as request counts, timestamps, latency and billing data, which does not include Customer Data submitted to or generated by the Services; (iii) records Provider must keep to comply with law, or to detect, investigate or respond to fraud, security incidents or abuse of the Services; and (iv) Customer Data kept for a feature or Service Customer elects to use, such as batch requests, asynchronous media outputs, third-party integrations or paid cache retention, for no longer than the retention period stated in the documentation for that feature.

Supporting quotations

(i) Customer Data that Provider retains at Customer's written request, or with Customer's prior written authorization, to diagnose or resolve a support or Service issue, which Provider will delete within thirty (30) days after the issue is resolved
(ii) non-content operational metadata, such as request counts, timestamps, latency, and billing data, that does not include Customer Data submitted to or generated by the Services
(iii) records Provider is required to retain to comply with applicable laws or to detect, investigate, or respond to fraud, security incidents, or abuse of the Services
(iv) Customer Data that Provider retains for a feature or Service that Customer elects to use, such as batch requests, asynchronous media outputs, third-party integrations, or paid cache retention, for no longer than the retention period stated in the documentation for that feature or Service

Qualifications & exceptions

  • Item (i) requires Customer's written request or prior written authorization, and deletion is due within 30 days after the issue is resolved.
  • Item (iii) covers records required for legal compliance or for fraud, security incident or abuse detection, investigation or response; no retention period is stated.
  • Item (iv) applies only to features or Services Customer elects to use, for no longer than the documented retention period.

Not stated here

  • The documentation that sets the retention periods for item (iv) features is not part of this document.
  • Item (iii) states no retention period for fraud, security or abuse records.

Cross-references

Also annotated in the same passage (5)

Retention & Deletion · Restriction or exception

Zero Data Retention covers models DeepInfra hosts; data sent to third-party models follows the third party's terms

Zero Data Retention applies to models hosted by Provider. Customer Data that Customer elects to submit to a third-party model made available through the Services is governed by Section 18 and the applicable third party's terms. Section 18 says use of Third-Party Content is governed exclusively by the applicable third-party license, terms of use and privacy policies, and that Customer agrees to be bound by them.

Supporting quotations

Zero Data Retention applies to models hosted by Provider; Customer Data that Customer elects to submit to a third-party model made available through the Services is governed by Section 18 and the applicable third party's terms.
governed exclusively by the applicable third-party license, terms of use, and privacy policies

Qualifications & exceptions

  • The third-party carve-out applies where Customer elects to submit data to a third-party model made available through the Services.

Not stated here

  • The Terms do not say which available models are Provider-hosted and which are third-party models, or what any third party's terms say about retention.

Cross-references

Also annotated in the same passage (6)

Retention & Deletion · Restriction or exception

Confidentiality obligations last three years after termination, and for trade secrets as long as they stay trade secrets

The confidentiality obligations in Section 17 continue for three years after the Agreement terminates. For Confidential Information that is a trade secret under applicable law, they continue for as long as it remains a trade secret.

Supporting quotations

their obligations under this Section 17 shall continue in effect for three (3) years after the termination of this Agreement; provided, however, that with respect to any Confidential Information that constitutes a trade secret under applicable laws, the obligations under this Section 17 shall continue for so long as such information remains a trade secret under applicable laws

Qualifications & exceptions

  • The trade-secret extension applies only to information that constitutes a trade secret under applicable laws.