Twitter ‧ Data Processor Agreement ‧ not tracked anymore

[OTA-Bot]

No version of the Data Processor Agreement of service Twitter is recorded anymore since 3 July 2024 at 18:16:37 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

• Fetch failed: Received HTTP code 503 when trying to fetch 'https://help.twitter.com/en/rules-and-policies/data-processing-legal-bases'

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

• https://help.twitter.com/en/rules-and-policies/data-processing-legal-bases

If the source documents are accessible through a web browser

Edit the declaration:

• Try updating the selectors.
• Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

• If the source documents have moved, find their new location and update it.
• If these terms have been removed, move them from the declaration to its history file, using 2024-07-03T18:16:37Z as the validUntil value.
• If the service has closed, move the entire contents of the declaration to its history file, using 2024-07-03T18:16:37Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

• Latest declaration
• Latest version
• Latest snapshot

[OTA-Bot]

Tracking resumed

No changes were found in the last run, so no new version has been recorded.

[OTA-Bot]

No version of the Data Processor Agreement of service Twitter is recorded anymore since 3 August 2024 at 6:15:47 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

• Fetch failed: Received HTTP code 403 when trying to fetch 'https://help.twitter.com/en/rules-and-policies/data-processing-legal-bases'

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

• https://help.twitter.com/en/rules-and-policies/data-processing-legal-bases

If the source documents are accessible through a web browser

Edit the declaration:

• Try updating the selectors.
• Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

• If the source documents have moved, find their new location and update it.
• If these terms have been removed, move them from the declaration to its history file, using 2024-08-03T06:15:47Z as the validUntil value.
• If the service has closed, move the entire contents of the declaration to its history file, using 2024-08-03T06:15:47Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

• Latest declaration
• Latest version
• Latest snapshot