`Rubicon Project` ‧ `Trackers Policy` ‧ not tracked anymore

OTA-Bot commented 1 year ago

No version of the `Trackers Policy` of service `Rubicon Project` is recorded anymore since 18 October 2023 at 15:07:06 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

What went wrong

Received HTTP code 404 when trying to fetch 'https://rubiconproject.com/privacy-policy/website-cookie-statement/'

How to resume tracking

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

[ ] https://rubiconproject.com/privacy-policy/website-cookie-statement/

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 2023-10-18T15:07:06Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2023-10-18T15:07:06Z 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

OTA-Bot commented 5 months ago

No version of the `Trackers Policy` of service `Rubicon Project` is recorded anymore since 10 June 2024 at 12:43:19 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

What went wrong

Fetch failed: Timed out after 30 seconds when trying to fetch 'https://rubiconproject.com/privacy-policy/website-cookie-statement/'

How to resume tracking

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

[ ] https://rubiconproject.com/privacy-policy/website-cookie-statement/

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-06-10T12:43:19Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-06-10T12:43:19Z 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

OTA-Bot commented 4 months ago

No version of the `Trackers Policy` of service `Rubicon Project` is recorded anymore since 3 July 2024 at 18:12:25 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

What went wrong

Fetch failed: Received HTTP code 404 when trying to fetch 'https://rubiconproject.com/privacy-policy/website-cookie-statement/'

How to resume tracking

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

[ ] https://rubiconproject.com/privacy-policy/website-cookie-statement/

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:12:25Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-07-03T18:12:25Z 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

OTA-Bot commented 3 months ago

No version of the `Trackers Policy` of service `Rubicon Project` is recorded anymore since 6 August 2024 at 18:13:20 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

What went wrong

Fetch failed: Timed out after 30 seconds when trying to fetch 'https://rubiconproject.com/privacy-policy/website-cookie-statement/'

How to resume tracking

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

[ ] https://rubiconproject.com/privacy-policy/website-cookie-statement/

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-06T18:13:20Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-08-06T18:13:20Z 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

OTA-Bot commented 3 months ago

No version of the `Trackers Policy` of service `Rubicon Project` is recorded anymore since 7 August 2024 at 6:13:08 UTC

The source document has not been recorded in a snapshot, thus no version can be extracted.

What went wrong

Fetch failed: Received HTTP code 404 when trying to fetch 'https://rubiconproject.com/privacy-policy/website-cookie-statement/'

How to resume tracking

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

[ ] https://rubiconproject.com/privacy-policy/website-cookie-statement/

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-07T06:13:08Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-08-07T06:13:08Z 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

OTA-Bot commented 2 weeks ago

No version of the `Trackers Policy` of service `Rubicon Project` is recorded anymore since 23 October 2024 at 18:11:39 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

Extract failed: The provided selector ".page-header,.content" has no match in the web page at 'https://rubiconproject.com/privacy-policy/website-cookie-statement/'

How to resume tracking

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

[ ] https://rubiconproject.com/privacy-policy/website-cookie-statement/

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-10-23T18:11:39Z as the validUntil value.
If the service has closed, move the entire contents of the declaration to its history file, using 2024-10-23T18:11:39Z 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.

OpenTermsArchive / contrib-declarations