D1 ReimaginedExplore the project
Join DiscordView on GitHub
The preservation journal

Find an update.

Project policies

Privacy Policy.

How D1 Reimagined handles website and connected publishing information.

Effective 26 October 2026

Scope and contact

This policy covers the D1 Reimagined website and the project’s connected video publishing application. Privacy enquiries and rights requests can be sent to privacy@d1reimagined.com.

No accounts

The website has no sign-in, membership or registration. Everything it publishes is public, and no personal profile is created when you read it. The earlier private member accounts have been retired; contact the privacy address to confirm removal of any former account record.

Website visitors

The site does not use cookies, advertising trackers or behavioural analytics. The hosting service processes network information such as IP addresses, request details and security events to deliver and protect the site. Operational records are used for security and troubleshooting.

Visit counts

To learn where people find the project, the site counts page views per day by source and landing page. The source is a link tag such as ?ref=youtube, or otherwise the name of the referring website (for example youtube or google). Only these totals are stored: no IP address, cookie, device details or other identifier, so a count cannot be linked to a person. Counts are kept for up to 13 months.

Community services

Links to Discord, GitHub and YouTube take you to services with their own privacy policies and rules. Joining the Discord server, opening a GitHub issue or watching a video is governed by those services; the project does not receive your credentials from them.

Video embeds and external links

A video player is loaded only when you choose to play an embedded video. The video platform then receives network and device information under its own privacy policy.

YouTube API Services

The project’s account-connection service uses YouTube API Services to verify an authorised channel and support permitted publishing actions. The Google Privacy Policy describes Google’s handling of information. You can revoke access at any time through Google account permissions, or use Disconnect in the project publishing application. No Google account password is collected by this service.

Connected publishing accounts

The publishing application is used by authorised project channel owners. Depending on the permissions granted, it processes platform account identifiers, basic profile information, published video information, upload permissions and access or refresh tokens. It also handles project video files, captions, titles, descriptions and publishing status.

Purpose and legal basis

Information is used to connect authorised accounts, prepare and submit project videos, retrieve publishing status, manage project content, respond to requests and protect the service. Account access is based on the channel owner’s authorisation; website security and operational processing support the project’s legitimate interests. You can withdraw platform authorisation at any time through that platform’s settings.

Storage and sharing

Access credentials are protected and are not served by this website. Publishing information is shared with the relevant video platform only as needed for authorised actions. Hosting and email providers process information needed to operate the website and handle enquiries. Personal information is not sold or shared for advertising.

Contact mail

General contact messages are screened in a private encrypted quarantine. Messages are retained for up to 30 days, with a maximum of 100 messages and 500 KB per message. Messages exceeding these limits are rejected rather than silently discarded. Remote email images and attachments are not opened automatically. Privacy and security reports are delivered separately to the project operator.

Retention and deletion

Connection credentials are retained only while the authorised connection is needed. Cached YouTube channel information is checked and refreshed daily while the application is running, and removed from the displayed cache after 30 days without a refresh. A confirmed invalid grant removes the local credentials and cached channel information. Disconnect immediately stops local API access, requests revocation from Google and removes cached channel information and connection copies from local recovery bundles. If Google cannot be reached, revocation is retried; the interface shows that it is pending and links to Google’s permissions page. A token retained only to retry revocation is discarded within seven days. A verified deletion request can be sent to privacy@d1reimagined.com and is handled within seven days. Deleting local connection data does not delete videos or account data held by YouTube. Operational security records are retained for up to 30 days where controlled by the project; service providers may apply their own retention periods. Videos remain on the relevant platform until removed there.

Your rights

Where applicable, you may request access, correction, deletion, restriction or portability, object to processing, withdraw authorisation and complain to your data protection authority. Identity may need to be verified to protect account data.

Children and changes

The account connection service is not intended for children. This policy may change as the project develops; the effective date above identifies the current version.