Auto Archiver
Bellingcat's tool to automatically archive social media posts, videos, and images. Free and Open-Source.
URL
https://github.com/bellingcat/auto-archiver
Official documentation: https://auto-archiver.readthedocs.io/en/latest/
PyPI package: https://pypi.org/project/auto-archiver/
Current version checked: v1.2.7, released 2026-04-27. Last checked: 2026-06-18.
Description
Auto Archiver is an open-source Python tool from Bellingcat for archiving URLs in a repeatable, verifiable way. It is designed for researchers who need to process many links, preserve content before it disappears, and keep useful metadata about what was archived, when, and how.
Auto Archiver can take URLs from the command line, a CSV file, Google Sheets, Atlos, or API-based/shared-instance workflows. Depending on the configured modules, it can archive webpages, social media posts, images, videos, screenshots, metadata, hashes, timestamps, and links to third-party archive services.
Inputs: URLs supplied through CLI, CSV, Google Sheets, Atlos, or API/shared-instance workflows.
Outputs: archived files and metadata, usually saved locally or to configured storage such as Google Drive, S3, or Atlos; status and metadata can be written back to CSV, Google Sheets, console output, API/database modules, or reports.
Most individual users will run Auto Archiver through Docker or the command line. Bellingcat also maintains API and web-interface components for team or shared-instance deployments, but those require additional setup and administration.
An archiving tool for open source researchers
Use Auto Archiver when you have more than a few URLs to preserve, when several people are collaborating from a shared list such as Google Sheets, or when you need a repeatable workflow that records hashes, timestamps, screenshots, metadata, and storage locations.
For a small number of public webpages, tools such as the Wayback Machine or archive.today may be quicker. For video-only workflows, yt-dlp may be simpler. For manual browser-session capture or replayable WACZ archives, ArchiveWeb.page, Browsertrix, or Hunchly may be more appropriate depending on the case. Auto Archiver is strongest when you need batch processing, structured outputs, and configurable modules.
Bellingcat and others in the OSINT community have actively used Auto Archiver in fast-moving crises and major conflict investigations (for example, during Russia’s invasion of Ukraine) to save evidence that might disappear (gijn.org). It has also been adopted by organizations like the Centre for Information Resilience and OSR4Rights to systematically archive content from conflict zones (bellingcat.com). In practice, once the tool is set up, an investigator can simply copy-paste links of interest (from Telegram, TikTok, Twitter, etc.) into the designated sheet or interface, and the Auto Archiver will quickly preserve the content – a process described as “a life-saver for investigators” when dealing with volatile information (gijn.org).
Getting Started
To run Auto Archiver locally, some technical knowledge is needed for the initial setup. The easiest method is using Docker, which bundles all dependencies and simplifies the installation process.
Notable instances and case studies:
Russia-Ukraine War: Bellingcat used the Auto Archiver to systematically capture social media posts from platforms like Telegram and X, creating a permanent record of military movements, civilian harm, and other evidence.
Human Rights in Myanmar: The tool has been used to document social media posts related to human rights violations during the 2021 military coup, preserving evidence of protests and crackdowns.
Election Violence Evidence: The Global Investigative Journalism Network (GIJN) highlighted the Auto Archiver as a critical tool for preserving video evidence of election-related violence, naming it one of its "Top 10 Investigative Tools of 2023."
Misinformation Campaigns: Researchers use the tool to save posts from coordinated disinformation campaigns before they are removed, allowing for later analysis of tactics.
Environmental Disasters: Firsthand accounts from events such as the 2020 wildfires in Australia or the 2023 earthquakes in Turkey and Syria, have been archived to serve as evidence for response analysis and historical documentation.
Usage of Auto-Archiver
Supported Platforms
Auto Archiver works by sending each URL through the modules enabled in your configuration. Coverage depends on the URL, the extractor module, whether the content is public or login-restricted, and whether a platform blocks automated access. Treat the table below as a practical guide, not a guarantee.
General webpages
antibot_extractor_enricher, wacz_extractor_enricher, wayback_extractor_enricher, ghostarchive_enricher
Public pages may work without login. Login-restricted pages may need cookies or browser profiles.
Dynamic pages, paywalls, CAPTCHAs, and heavy JavaScript can reduce capture quality.
Video platforms supported by yt-dlp, including YouTube and some social platforms
generic_extractor
Public videos may work without login. YouTube or X/Twitter may require cookies or Proof of Origin Token handling in some cases.
Coverage follows yt-dlp support and can break when platforms change. Comments, subtitles, and livestream handling depend on settings.
X/Twitter
twitter_api_extractor and/or generic_extractor
Structured API capture requires X/Twitter API credentials. Cookies may be needed for some web-accessed content.
The current docs prefer bearer_tokens over the older singular bearer_token setting. Access depends on the user’s API tier and platform restrictions.
Telegram public message links
telegram_extractor
No login required for public t.me message links.
Best for simple public message/media links.
Telegram channels, groups, private channels, or invite links
telethon_extractor
Requires Telegram API ID/hash and usually a logged-in session. First login may prompt for a phone number/code.
Use only accounts with legitimate access to the channel/group. Bot tokens have limitations for private-channel archiving.
antibot_extractor_enricher LinkedIn drop-in
Authentication is required for most content. First login from a new IP may trigger email verification.
Antibot extraction is still described as trial/development-stage; expect failures.
antibot_extractor_enricher Reddit drop-in
Can work without authentication until Reddit flags the IP; authentication is advised.
Rate limits and anti-bot measures may affect reliability.
VKontakte
antibot_extractor_enricher VK drop-in
Some public content may work without authentication.
Login may be needed for restricted or media-heavy content.
TikTok
generic_extractor; TikTok drop-in exists under Antibot
Public content may work without login.
Official docs say the TikTok Antibot drop-in is susceptible to TikTok bot detection and recommend the Generic Extractor for TikTok.
Instagram-related extractor modules
May require configured credentials/API-related setup depending on workflow.
Unauthenticated access is often limited; verify outputs carefully.
Archiving is not the same as verification. Auto Archiver can preserve a copy, metadata, hashes, timestamps, and archive links, but researchers still need to assess authenticity, context, source reliability, and whether the archived material is complete.
Core Engine Deep Dive
Input Feeders: The tool is designed to ingest lists of URLs from a variety of sources, which it refers to as "feeders". The most common and well-documented method is using a Google Sheet, where a user simply pastes URLs into a designated column. This method requires the user to create a Google Cloud Service Account, generate a JSON credentials file, and share the target Google Sheet with the service account's unique email address, granting it editor permissions. The tool also supports simpler feeders, such as local CSV files or direct URL input from the command-line interface (CLI).
Modular Extractors: A key strength of the Auto Archiver is its modular design for handling different platforms. Upon receiving a URL, the tool intelligently routes it to a platform-specific "extractor" module designed to handle the unique structure and characteristics of that site. For example, a TikTok URL will be processed by the TikTok extractor, a YouTube link by the YouTube extractor, and a Telegram post by the Telegram extractor. This modularity allows the tool to be flexible and extensible, with the community able to contribute new extractors or update existing ones as platforms change.
Underlying Dependencies: The core engine's power comes from its integration with other robust open-source libraries. For downloading videos from a vast array of sites, it leverages the industry-standard
yt-dlplibrary. For interacting with Telegram, it utilizes libraries such as Telethon. To capture screenshots and render complex, JavaScript-heavy webpages, it employs a headless browser, such as an integrated version of Google Chrome.Configurable Storage Backends: The user has complete control over where the archived data is stored. The configuration file allows for specifying a storage backend, which can be a folder on the local machine, a cloud-based object storage bucket compatible with the Amazon S3 API (such as Digital Ocean Spaces or AWS S3), or a folder within the user's Google Drive.
Feedback Loop: One of the tool's most user-friendly features, particularly when using the Google Sheets feeder, is its ability to provide real-time feedback. As it processes each URL, the tool writes the status of the job—such as "in progress," "success," or a specific error message—back into the adjacent columns of the same spreadsheet. Upon successful archival, it populates these columns with valuable information, including a direct link to the archived content in the configured storage location, a link to the screenshot, and any extracted metadata like the post's title or duration
Installation methods: Choose one of the following setups:
Option A: Docker (simplest)
Docker is the easiest installation route for most users because it packages more dependencies and is the recommended path for WACZ/Browsertrix-related workflows.
To run with a configuration file:
Option B: Python/Pip
For local installation, use Python 3.10 or newer. PyPI currently lists support for Python >=3.10,<3.13.
This adds an auto-archiver command to your system path. You can check it by running auto-archiver --help for available options. (Advanced users can also clone the GitHub repo and install manually, but pip is easier.)
Local installs may require extra dependencies for some modules. For example, WACZ/Browsertrix workflows need Docker or Browsertrix support, and some YouTube workflows may need additional token/POT handling unless you use the Docker image.
Configuration
Auto Archiver is highly configurable via a YAML file (often named orchestration.yaml or config.yaml). You can create this by hand or use the tool’s built-in configuration editor for guidance.
orchestration.yaml (step 1), then tick or drag modules—Feeders, Extractors, Enrichers, Databases, Storages, Formatters—to build a custom archiving pipeline before saving the new YAML or copying it to your clipboard (steps 2-4).Key settings in the config include:
Input source (Feeder): Decide how you will supply URLs. Common options are Google Sheets (you’ll provide the Sheet ID and your Google credentials file path in the config), or CSV/Console (for a local CSV file or manual input). For Google Sheets, ensure the service account email is given edit access to the sheet. For a CSV, prepare a CSV with at least a “URL” column and any other optional columns (the tool will append results to this file).
Output storage: Choose where archived data will be saved. By default, it can save to a local folder (on disk). You can also configure cloud storage: e.g. an Amazon S3 bucket, Google Drive, or others. If using local storage, you might specify an output directory. The tool will organize archived files (videos, images, HTML, etc.) in that location, usually grouped by date or task.
Modules to enable: Auto Archiver has modular “extractors” (for pulling content) and “enrichers” (for extra data). By default, it decides automatically, but you can toggle some. For example, a screenshot module can capture a PNG image of the page or even save the page in a WACZ archive, a hashing module can record cryptographic hashes of files for integrity, a transcription module can attempt to transcribe video/audio (using Whisper AI) etc. In the config YAML, you might see sections like
enrichers:orextractors:where you can enable/disable these. If you leave them on, be sure to have the required dependencies (e.g. Whisper for transcripts).Credentials: In the config (or in a separate
.envfile that the config references), you’ll plug in any API keys or login info needed. For instance, to use the Twitter API method, put your Bearer token; for Telegram, your API ID/hash and bot token; for Reddit/LinkedIn, you might provide a session cookie string. All of these are optional – the tool will try to work without them – but providing credentials improves success.
Make sure to keep this config file secure (don’t share it publicly) since it contains your secret keys.
Usage Examples
Once everything is installed and configured, using Auto Archiver is straightforward. You typically run it via the command line. Common use cases include:
Archiving from a Google Sheet
If you set up a Google Sheet with URLs, just run the tool and point it to your config. For example:
Upon running, Auto Archiver will connect to the Google Sheet you specified. It will read each new URL in the sheet and begin archiving them one by one. You can watch the progress in the terminal. For each URL, the sheet will get updated with new data columns, such as an “Archive Status” (e.g. ✅ Archived or ❌ Failed) and links to the archived results. For instance, the sheet might show the direct URL to an archived video file, a link to a screenshot image, a hash value, or a timestamp of when it was archived. This gives you an easy overview within the spreadsheet itself of what’s been captured.
Using a CSV or list of URLs
If you prefer not to use Google Sheets, you can supply a simple CSV file. Put your URLs under a header (e.g. URL) in the CSV. Adjust your config to use the CSV feeder (point it to the file path). Then run:
The tool will read the CSV and process each link similarly. It can either update the same CSV with results or output a new report CSV. This is handy for one-off batches of links. (You can also run a single URL directly via the console feeder, or even script multiple auto-archiver calls for individual URLs. In general, it’s designed to handle a list rather than one URL at a time, but nothing stops you from making a CSV with just one link
Downloading from social media
You don’t need separate commands for each platform – just put the links in your input, and Auto Archiver picks the right approach. You just drop the links into your input source (for example, the “URL” column of a Google Sheet configured with the gsheet_feeder_db module). Auto Archiver’s orchestrator checks each link, chooses the matching extractor, runs it, then writes the results back to the sheet.
For example: to save a Telegram post (or an entire public channel’s history), you might paste the Telegram message URL or channel URL in the sheet. The archiver will download the text of the post, any images or video in it, and even stickers or files if possible. If you provided Telegram API credentials, it can retrieve a long history of a channel more reliably via Telethon, including content that a simple scraper might miss.
As another example, to archive a Twitter/X post, you’d put the tweet URL. With a Twitter API key set, the tool will fetch the tweet data (text, author, timestamp) through the API; if no key, it will try to scrape the tweet from the web or rely on a Wayback snapshot. In both cases, if the tweet has a video, Auto Archiver uses yt-dlp (or a similar downloader) to grab the video file for you. All of that gets saved and logged without you having to run separate download commands.
Capturing screenshots
By enabling the screenshot module in your config, the tool will save a full-page screenshot of webpages or posts as it archives them. This is useful for visual evidence.
For instance, when archiving a Facebook post (note: Facebook support is experimental and may require cookies), the archiver might save the HTML content and also generate a PNG image showing how the post appeared in the browser. Auto Archiver treats Facebook links just like any other platform: you paste the URL into your input (Google Sheet, CSV, CLI list) and the orchestrator routes it to the facebook extractor module. The screenshot file will be stored in your output (e.g. local folder or Drive) and a reference to it (filename or link) will appear in the sheet/CSV log. The same goes for tweets or Telegram messages: a screenshot of the post/chat can be captured in addition to text and video.
Keep in mind that to take screenshots, a headless browser is used; the new Antibot Extractor module in v1.1 handles this more robustly, even navigating login or cookie walls in many cases. (Facebook rate-limits datacenter addresses; the devs recommend running from a local connection, also referred to as a residential IP.) If a site is very hostile to automation (using CAPTCHAs), the screenshot might show a login or challenge page; in such cases, you might need to provide your login or skip the screenshot for that site.
Saving to cloud or remote storage
By default, archives save to your local disk (or wherever you run the Docker container). But you can configure remote storage. For example, if you set up Google Drive storage in the config, the tool will upload each archived file to a specified Drive folder. So if you’re archiving from a newsroom computer, everyone with access to the Drive can instantly see the saved videos/images there. Another advanced option is saving each page as a WARC/WACZ file (Web Archive Format) for forensic archiving purposes. It preserves full fidelity (headers, payloads, redirects), supports deduplication via “revisit” records, and is recognised by national libraries as a preferred preservation format. If enabled, the archiver will produce a .wacz web archive that you can later open with tools like Webrecorder. This can capture interactive page elements and scripts better than a simple HTML. Such advanced use is optional – for most users, having the screenshot plus the raw media files and a link to a Wayback snapshot covers the bases.
Cost
Level of difficulty
Requirements
You can run Auto Archiver on Windows, macOS, or Linux. You’ll need either Python 3.10+ (if installing as a Python package) or Docker installed. In addition, some system tools are recommended for full functionality:
FFmpeg – required for processing/downloading videos and audio.
Web browser engine – for capturing complex pages or screenshots. By default the tool used headless Firefox (with Geckodriver), but newer versions use an integrated headless Chrome solution for many tasks (so installing Firefox is no longer strictly necessary in v1.1+, especially if using the Docker image). If running locally without Docker, having Firefox + Geckodriver available is still suggested as a fallback.
(Optional) Google Cloud Service Account – needed only if you plan to use Google Sheets as your URL input. This is a special Google account for apps: you create it in Google Cloud, enable the Sheets API, and get a JSON key file. (You’ll share your Google Sheet with the service account’s email so the Auto Archiver can read/write it on your behalf.)
(Optional) Platform credentials – not required for basic use, but to archive certain content, you may need to supply API keys or login cookies. For example: a Twitter API Bearer token, Telegram API ID & hash (and bot token), or your own logged-in session cookies for sites like Reddit or LinkedIn. You can run the tool without these, but providing them can bypass rate limits and access protected content
Stable Internet connection – required for the tool to access and archive online content.
(Most platform credentials are only needed if you intend to archive from that platform and the content isn’t publicly accessible. Public content from many sites – e.g. YouTube, Facebook, TikTok – can often be archived without logging in, thanks to the integrated yt-dlp backend.)
Limitations
Initial Setup Complexity: While improved, the setup can be complex for first-time users. It involves configuring cloud credentials, API keys, and installing system dependencies. The new configuration wizard and Docker images have reduced this burden, but a basic technical proficiency is still necessary to get the tool running correctly (gijn.org). Users may need to troubleshoot environment issues or adjust configurations for their specific use case.
Platform & API Dependence: The Auto Archiver relies on third-party platforms’ APIs and front-end structures, which are subject to change. If a social media platform alters its URL format, API access, or introduces new anti-scraping measures, some extractor modules might break until updated. The tool’s maintainers actively push updates (and the tool can auto-update its yt-dlp component) to adapt to changes, but there may be short lapses in functionality for certain sites. Additionally, some platforms (e.g. Instagram, Facebook) do not provide easy methods for third-party archiving of content, meaning the Archiver might not capture those perfectly without an authorized session or may require workarounds like providing your login cookies.
Archiving Gaps for Certain Content: The Wayback Machine fallback does not fully preserve videos or interactive media. While the Auto Archiver attempts to download media content directly (using platform APIs or scraping) so that videos are saved, if all automated methods fail and only a Wayback snapshot is taken, the result may be a page without the actual video or dynamic elements. Highly dynamic or encrypted content (such as livestreams, ephemeral stories, or posts behind certain paywalls) may not be captured completely. Furthermore, very large files or high volumes of links may exceed rate limits or cause timeouts on some services. Users should be aware of these edge cases and, when possible, manually verify that critical videos and images have been successfully saved (for example, by checking the output folder or cloud storage to confirm that media files are present).
Platform volatility: Site layout, rate‑limits and anti‑bot controls change frequently; success rates improve with valid cookies/API tokens. The Antibot Extractor/Enricher mitigates some blocks but does not guarantee access.
Scope: Private/geo‑restricted/age‑gated content may require logins; some dynamic elements or comments may be partially captured depending on the module and settings. • Web UI/API: Hosted UI availability can fluctuate; the API DB module requires an API instance and token. • Legal/ToS: Archiving must take platform terms and applicable law into account; some workflows (e.g., automated scraping) may breach site terms if misused.
Ethical Considerations
Select and Queue URLs Responsibly
Serve the Public Interest, use only what is truly public and news‑worthy. Ask first: Does archiving/publishing this URL, image, or video materially advance an investigation in the public interest?
Handle vulnerable subjects with extra care. If minors or at‑risk individuals appear in the footage, consider redacting faces or withholding the post after archiving.
Keep sensitive sheets private. When you use the Google Sheets Feeder share the sheet only with your service‑account email, not “Anyone with the link,” to avoid leaking raw evidence.
Import only the cookies you truly need. The “Logging in to sites” guide shows how to attach a single
cookies.txtper domain; don’t dump your whole browser profile.Use Auto Archiver lawfully and proportionately, obtain consent where appropriate, and minimize the collection of personal data not needed for your purpose. For investigations with potential legal or human rights implications, align collection, preservation, and chain-of-custody practices with the Berkeley Protocol on Digital Open Source Investigations (OHCHR/UC Berkeley).
Cookies, API keys and service-account files can expose you or your organisation.
Do not use personal accounts for high-risk archiving workflows. Use credentials that you are authorised to use, keep them outside public repositories, and limit them to the smallest scope needed for the task. If you use cookies, avoid exporting your everyday browser profile; use a separate browser profile or working environment and import only what the workflow requires.
Verify, don't assume.
Archiving ≠ verification. Treat every capture as potential evidence. After the run, treat each capture as unverified until you geolocate, chronolocate, and cross‑check it.
Preserve metadata. Keep timestamps, hashes, and context intact so future reviewers can retrace your steps.
Capture With Integrity - Let the Modules Do the Work
Tampering claims
Hash Enricher writes SHA‑256 hashes to your sheet
add hash_enricher to steps.enrichers (auto-archiver.readthedocs.io)
Timestamp disputes
Timestamping Enricher signs each file via OpenTimestamps
add timestamping_enricher; keep .ots files with media (auto-archiver.readthedocs.io)
Missing visuals
Screenshot Enricher grabs a full‑page PNG
set screenshot: true or include screenshot_enricher (auto-archiver.readthedocs.io)
Link rot
Wayback Extractor/Enricher saves a snapshot if primary download fails
enabled by default in the fallback chain (auto-archiver.readthedocs.io)
Context is non‑negotiable
Contextualise or withhold. A geotag without narrative can mislead; always explain what the material shows, what it doesn’t show, and any unanswered questions. Transparency sometimes means showing less.
Show restraint. If full disclosure endangers a source or civilian, publish a redacted version, or withhold entirely, after consulting peers.
Be Transparent but Not Reckless
Explain your method. Document how the file was found, downloaded, and verified so others can replicate the process (Bellingcat’s “radical transparency”).
No hidden edits. Do not crop, enhance, or subtitle in ways that could distort meaning; any necessary edits must be disclosed.
Comply with Law and Platform Rules
Review terms & local law. Many sites forbid automated scraping; weigh legal exposure against public‑interest value and seek permission or legal advice when needed.
Respect copyright. Archive for evidentiary use; if publishing excerpts, rely on fair‑dealing/fair‑use principles and credit the original creator.
Protect Sources, Researchers, and Data
Secure working copies, and keep originals immutable. Store raw archives and sensitive spreadsheets in access‑controlled drives; share only with partners who follow the same standards.
Anticipate retaliation. Geolocation or doxxing can endanger the uploader; weigh disclosure against possible harm, and anonymise when prudent.
Guides and articles
Ramalho, M. Clark, E. Robertson, P. (2025, August 13) The Open Source Tool That Has Preserved 150,000 Pieces of Online Evidence. Bellingcat. https://www.bellingcat.com/resources/2025/08/13/the-open-source-tool-that-has-preserved-150000-pieces-of-online-evidence/
Ramalho, M. (2022, September 22). Preserve Vital Online Content With Bellingcat’s Auto Archiver. Bellingcat. https://www.bellingcat.com/resources/2022/09/22/preserve-vital-online-content-with-bellingcats-auto-archiver-tool/
Bellingcat/auto-archiver. (2024). [Python]. Bellingcat. https://github.com/bellingcat/auto-archiver (Original work published 2021)
GIJN Article: New Reporting Tools to Archive Videos, Find QAnon Networks, and Track Targets via Online Reviews (Features the Auto Archiver as a key tool for journalists.)
Resources and Support
Current Version: Auto Archiver is under active development. As of July 2025, the latest version is v1.1.1 (released June 30, 2025).
Documentation: Official docs are available on ReadTheDocs (covering installation, modules, and usage in detail). The documentation includes a configuration guide and examples of advanced setups. (Note: The docs may lag a bit behind the very latest features, so community forums can help fill the gaps.)
GitHub: The source code is on GitHub at bellingcat/auto-archiver. The README there provides installation instructions and links to the docs. Check the GitHub issues page if you encounter bugs – you might find that others have reported the same, along with fixes or workarounds. You can also open a new issue to ask questions or report problems. The project is open-source (MIT License) and welcomes contributions.
Community & Support: For direct support, consider the following:
Bellingcat occasionally provides guidance through Bellingcat’s online channels. Keep an eye on the Bellingcat website’s Guides section or their Twitter/Mastodon for any updated tutorials.
The Bellingcat online community (on Twitter, Reddit, or Discord groups) can be helpful – many researchers use Auto Archiver, so if you ask in a forum like the r/OSINT subreddit or the GIJN mailing list, someone might have an answer.
The GitHub repository has a Discussions tab where you can ask how-to questions outside of formal bug reports.
Similar tools
Wayback Machine Use for quick public snapshots and historical captures of webpages. It is fast for simple pages, but may miss videos, comments, interactive elements, or content behind login walls.
archive.today Use as a secondary public snapshot service for individual pages. Treat it as a third-party archive and manually review captures before relying on them.
yt-dlp Use when your main task is downloading video or audio from a supported platform. Auto Archiver may be more useful when you also need structured logs, hashes, screenshots, and storage routing.
ArchiveWeb.page Use when you want to capture pages manually while browsing and save replayable web archives.
Browsertrix Use when you need larger or scheduled browser-based crawls rather than a list of individual URLs.
Hunchly Use when you want browser-based case capture, tagging, timestamps, hashes, and an audit trail while manually browsing.
Tool provider
Developer: Bellingcat — repo & docs. GitHub
License: MIT (see LICENSE). GitHub
Advertising Trackers
Auto Archiver is usually run locally, in Docker, or on infrastructure controlled by the researcher or organisation. In that setup, it is not a tracking-based web service by default.
However, connected services may log requests or account activity under their own policies. This can include Google Sheets, Google Drive, S3 providers, X/Twitter, Telegram, proxies, Ghost Archive, the Wayback Machine, or any other third-party service configured in the workflow. Treat URLs, cookies, API keys, service-account files and archive logs as sensitive.
Martin Sona
Last updated
Was this helpful?