Privacy Policy

Effective date: 22 July 2026

This Privacy Policy explains how MediaPuller.com collects, uses, discloses, stores, and protects information when you visit or use the MediaPuller website, its online media downloader, anonymous story viewers, generated media pages, and related interfaces (together, the "Service"). Because MediaPuller depends on changing third-party platforms and service providers, we may update this Policy when our data practices change.

Please read this Policy together with the MediaPuller Terms of Service. If you do not agree with the processing described here, do not submit a URL, username, profile identifier, file, or other information to the Service. This Policy does not govern the privacy practices of a source platform, content-delivery network, search engine, analytics provider, hosting provider, comments provider, or other third party. Their own notices apply to their processing.

1. Definitions

In this Policy:

  • "MediaPuller," "we," "us," or "our" means the operator of MediaPuller.com.
  • "Personal Data" means information relating to an identified or identifiable natural person. Depending on the context, an IP address, cookie identifier, username, profile name, email address, source URL, or public profile metadata may be Personal Data.
  • "Technical Data" means information generated when a browser, device, application, or server communicates with the Service, including an IP address, request time, HTTP method, requested address, referrer, User-Agent, response or error information, and security or rate-limit events.
  • "Request Data" means a URL, username, profile identifier, platform choice, API parameter, or file that you submit to request a downloader, story-viewer, API, or related function.
  • "Public Metadata" means information obtained from or associated with a source page or public profile, such as a title, description, author name, account username, avatar, thumbnail, caption, publication time, duration, media type, media dimensions, format, or source address.
  • "Source Platform" means the third-party website, application, API, media host, social network, or content-delivery network from which MediaPuller attempts to obtain metadata or media delivery information.
  • "Processing" has the meaning given by applicable data-protection law and includes collecting, accessing, organising, storing, using, transmitting, displaying, deleting, or otherwise handling information.

2. Data Controller and Contact Information

The controller for processing carried out for MediaPuller's own purposes is the operator of MediaPuller.com, operating under the MediaPuller name from Ukraine.

For privacy questions, requests, or complaints, contact mediapuller@gmail.com. Please write "Privacy Request" in the subject line and describe the information or page concerned. Do not send passwords, platform session cookies, authentication tokens, identity documents, or other secrets unless we specifically request a proportionate method of verification.

A Source Platform or other third party is normally a separate controller for information it receives and processes under its own purposes and rules. MediaPuller does not control that third party's privacy practices.

3. Scope and Summary of the Service

MediaPuller is a browser-based media-resolution service. A user may submit a source URL to discover available video, audio, image, or related media options, or submit a username or profile address to request active stories from a supported platform. The Service may communicate with a Source Platform, use authorised service access, call a third-party API, or provide a media address that the user's browser requests from the source or its CDN.

MediaPuller generally does not download a requested media file to permanent server storage merely because a user asks to view or download it. Most results are source or CDN links. Certain features temporarily proxy or stream media, and limited result data is retained for the period reasonably necessary to provide the requested functionality. Submitted URLs and associated metadata may nevertheless be stored in the MediaPuller database and may create public result pages. Successful story searches retain a profile identifier and platform as part of the Service history.

The public downloader and story-viewer interfaces currently do not require a consumer account. Restricted administrator accounts and authenticated API capabilities do exist. Different data practices apply to those restricted functions.

4. What Data We Collect

The categories collected depend on the feature used. MediaPuller may process:

  • Request Data: submitted URLs, usernames, profile identifiers, platform selection, route and query parameters, and API request fields;
  • Public Metadata: titles, descriptions, captions, author or profile names, usernames, avatars, thumbnails, publication dates, duration, media characteristics, format addresses, and source identifiers;
  • Technical Data: IP address, request time, HTTP method, content type, requested URL, referrer, User-Agent, operating or browser details inferred from that string, response status, processing stage, rate-limit state, and error details;
  • Usage Data: page views and interaction information received through Google Analytics, counters associated with generated pages, and whether a request produced an existing or newly generated result;
  • Administrator Data: login name, password hash, first and last name, email address, roles, authentication state, account timestamps, and audit-relevant actions;
  • Security and recovery data: authentication and anti-forgery values, password-reset identifiers, creator and approver IP addresses for password-reset records, CAPTCHA values kept in memory, API bearer tokens, and application error records;
  • Communication and notification data: email address, email recipients, CC or BCC fields, subject, body, delivery attempts, failure information, and any information included in a message;
  • Uploaded data: a file, original filename, generated server filename, size, MIME type, associated user identifier, and timestamps where an upload-capable API or restricted administrative feature is used; and
  • Operational metadata: generated page name, platform type, processing result, created, updated, hidden or deleted dates, and view or search counters.

Do not submit sensitive Personal Data, private content, confidential information, unlawfully obtained credentials, or a URL whose processing would violate another person's rights. MediaPuller does not need special-category data to provide its public downloader or story-viewer features, but a submitted URL, public profile, title, caption, image, or file could incidentally contain such information.

5. Information About Other People and Public Metadata

A downloader or story request can concern a creator, account holder, performer, person depicted in media, or another third party. Public availability does not necessarily make that information non-personal or remove legal protections. MediaPuller may obtain Public Metadata from the relevant source and display it in a request result or generated page.

If you submit information about another person, you are responsible for having a lawful basis and respecting that person's privacy, publicity, confidentiality, copyright, and other rights. MediaPuller uses this information to resolve the request, display the result, maintain supported functionality, prevent abuse, and, for eligible downloader results, operate public generated pages. A person who believes that a MediaPuller page or record relates to them may request review, correction, objection, restriction, or removal by contacting us.

6. Cookies and Similar Technologies

The Service uses or may cause the following cookies to be used:

  • Administrator authentication cookie. Restricted administrator authentication uses a first-party cookie that carries protected authentication information rather than the administrator's plain-text password. It may persist when an authorised administrator selects a remember-me option; otherwise browser-session behaviour applies.
  • Security cookie. Essential security technology may place a cookie and pair it with a form token to help reject cross-site request forgery on protected forms.
  • Site message cookie. A first-party session cookie may temporarily carry user-interface messages or actions between requests and is removed after use.
  • Language cookies. The Service may use cookies or a language address in the URL to remember or apply a selected language.
  • Google Analytics cookies or identifiers. Google Analytics 4 may set or read analytics identifiers and receive browser and usage data as described in Section 23.
  • Third-party media or embedded-service cookies. When your browser requests media, an image, a comments widget, or another resource from a third party, that party may read or set cookies under its own domain and policy.

MediaPuller does not require visitors to provide their own Source Platform credentials for the public downloader or story-viewer workflow. Any technical access information used by MediaPuller to operate an integration is kept separate from the visitor's browser.

7. Browser Storage and Device Storage

MediaPuller does not intentionally store public downloader or story-viewer Request Data in browser local storage or IndexedDB. Restricted administrator editing features may use browser storage for preferences or autosave. A browser, media player, third-party script, or source CDN may also maintain its own cache or storage under its rules.

If you download a file, your browser or device controls the destination, download history, cache, recently used files, and any cloud backup or synchronisation. MediaPuller cannot delete a copy stored by your browser, operating system, device, backup provider, or another application.

8. Server Logs and Error Logging

MediaPuller maintains application, security, and error logs to operate, secure, diagnose, and improve the Service. Depending on the event, a log may contain an authenticated identity, content type, HTTP method, requested address, referrer, User-Agent, connection IP address, message, and error details.

Submitted URLs, usernames, profile identifiers, query values, source responses, or other Request Data can appear in a log message or error record when a request fails or diagnostic information is necessary. MediaPuller does not intentionally record every POST form body in its ordinary application logs.

The web server, reverse proxy, operating system, hosting provider, security service, and network provider may produce their own access, error, or security logs independently of MediaPuller. Their privacy notices and retention practices apply to their processing.

9. IP Addresses, User-Agent, and Referrer

IP address. The Service uses the connection IP for application logging, rate limiting, security investigation, and restricted-account recovery records. Ordinary downloader and story history records are not designed as a per-visitor IP history, although a related application log may contain both an IP address and request information.

User-Agent. The User-Agent may be logged and is examined to distinguish mobile devices and recognised automated crawlers. This affects presentation and some view-count behaviour. It can reveal browser family, operating system, device category, and automation indicators.

Referrer. The HTTP referrer may be included in application logs and may also be available to analytics or an external resource requested by the browser, subject to browser referrer policy. A referrer can disclose the address of the previous page. MediaPuller does not require a referrer to provide the public downloader.

Where MediaPuller uses a reverse proxy or comparable network service, the address available to the Service may be a proxy-supplied address. MediaPuller applies technical safeguards intended to use connection information for security and abuse prevention appropriately.

10. Download Requests and Download History

When you submit a downloader URL, MediaPuller validates it, identifies the likely platform, and sends all or part of the URL or source identifier to the source website, its API, a platform-specific intermediary, or third-party extraction software that communicates with the source. The returned information may include Public Metadata and one or more media format addresses.

For eligible successful results, MediaPuller stores the submitted source URL and associated metadata, such as a generated page name, title, author, description, duration, thumbnail, platform, available format information, dates, and counters. This information can support a public page and can appear in sitemaps or result lists. Some results are not retained. There is no general per-consumer account to which this history is attached, and this record is not designed as a per-visitor IP history.

Following a media link may cause your browser to communicate directly with the Source Platform or CDN. That third party will then receive at least the network data required to deliver the resource and may receive the media address, request headers, cookies for its domain, referrer, and device information. In certain integrations, MediaPuller instead acts as a temporary intermediary and the source sees MediaPuller's server connection while MediaPuller receives your media request.

The database record is a history of processed source items, not proof that a visitor completed a download. MediaPuller does not reliably know whether a browser saved, opened, abandoned, or later deleted the media.

11. Story Viewer Requests and Story History

When you submit a story-viewer request, MediaPuller processes the username or profile address and selected platform. Depending on the platform, the Service may use authorised service access, a third-party API, or temporary automated processing. The requested platform or intermediary may receive the requested username or source identifier and MediaPuller's service context necessary to provide the feature.

After a successful story lookup, MediaPuller stores the normalised username or profile identifier, the selected platform, and relevant operational dates in its story-viewer history. It does not retain returned story media as part of that history, and the history is not designed as a per-visitor IP record. Authorised administrators can manage these records.

Story metadata and delivery information are retained only for a limited operational period reasonably necessary to provide the requested functionality. Where a story requires temporary streaming, MediaPuller does not intentionally save the streamed media as a permanent media file.

The term "anonymous story viewer" means that a visitor does not authenticate to the Source Platform with their own account through MediaPuller. It does not mean that the visitor is anonymous to MediaPuller, its hosting or analytics providers, a CDN contacted by the browser, or every Source Platform. Technical Data can still be processed as described in this Policy.

12. Public Generated Pages and Search Engines

An eligible successful downloader request may generate a public page using the source URL, generated slug, thumbnail, title, description, author, duration, formats, and related metadata. These pages are not private storage. They may be linked on MediaPuller, included in a sitemap, indexed by a search engine, cached by a browser or search provider, shared on social networks, or archived by an independent service.

Removing a MediaPuller database record or hiding a page does not automatically remove copies from a Source Platform, search index, CDN cache, browser cache, social share, or archive. If a public page contains Personal Data about you and you wish to object or seek removal, send the page address and the reason for your request to the contact email. MediaPuller may preserve limited evidence where necessary to resolve legal claims, enforce its Terms, or comply with law.

13. Accounts, Authentication, and API Access

Public downloader and story-viewer use currently does not require consumer registration. Restricted administrator records can include a login, password hash, first name, last name, email address, roles, creation and update dates, and deletion status. Passwords are verified against a hash; MediaPuller should not need to know an administrator's reusable plain-text password after it is set.

Administrator sign-in uses security measures including CAPTCHA and an encrypted authentication cookie. Password-recovery records may include a reset identifier, relevant IP address information, and operational dates.

An authenticated API can issue a bearer token after valid credentials are supplied. Tokens have a limited lifetime. A client is responsible for storing a token securely and not placing it in a URL, log, public location, or untrusted browser storage.

14. Uploaded Data, Communications, and Notifications

Content-management and upload features may store news images, managed assets, or files submitted through an available upload interface. Where used, an upload can be stored with related attachment metadata, including file name, size, MIME type, associated identifier, and relevant dates. This is different from ordinary media downloading: an uploaded file may be retained until removed under the applicable retention process.

If you contact MediaPuller, we process your email address and the content and metadata of your message to answer it, maintain a record, prevent abuse, and handle legal or privacy requests. Notification records may include recipients, message content, delivery attempts, error details, and relevant dates. Do not include unnecessary Personal Data.

15. How We Use Data

MediaPuller uses information to:

  • receive, validate, route, and process a downloader, story-viewer, streaming, or API request;
  • obtain and display Public Metadata and available media options;
  • temporarily proxy or stream media where direct delivery is not technically available;
  • create, maintain, count, organise, and display eligible public generated pages;
  • maintain story lookup history by username and platform;
  • authenticate administrators, issue authorised API tokens, and recover restricted accounts;
  • operate language, message, CAPTCHA, caching, and content-management functions;
  • measure website usage and understand aggregate traffic through Google Analytics;
  • diagnose errors, maintain compatibility, monitor performance, and improve reliability;
  • detect automation, spam, fraud, excessive traffic, unauthorised access, and other abuse;
  • apply request limits, concurrency controls, blocks, suspensions, and legal restrictions;
  • respond to support, privacy, copyright, court, regulatory, and law-enforcement matters;
  • establish, exercise, or defend legal claims and enforce the Terms of Service; and
  • comply with applicable legal obligations.

MediaPuller does not use downloader or story history to build a consumer advertising profile. MediaPuller does not currently use an artificial-intelligence provider to process Request Data or Personal Data. This Policy will be updated before either practice changes.

16. Legal Bases Under the GDPR

Where the GDPR, UK GDPR, or a similar law applies, MediaPuller relies on a legal basis appropriate to each purpose:

  • Performance of a contract or steps requested before a contract: to process the URL or profile identifier you submit and return the downloader or story-viewer result you request; to authenticate an authorised administrator; and to provide requested support.
  • Legitimate interests: to operate and secure the Service, prevent fraud and abuse, apply rate limits, diagnose faults, maintain short-lived caches, measure operational performance, enforce the Terms, preserve evidence, and defend legal claims. MediaPuller also relies on legitimate interests for eligible generated pages and the processing of relevant Public Metadata, subject to a balancing assessment and your right to object.
  • Consent: where required for non-essential analytics cookies, similar tracking, or a particular voluntary communication. In jurisdictions where prior consent is required before non-essential analytics is activated, such analytics should not be activated until a valid choice has been obtained. This Policy is not itself a consent mechanism. Withdrawal does not affect processing already lawfully carried out.
  • Legal obligation: to comply with a binding law, court order, valid regulatory request, accounting requirement, or lawful rights request.
  • Vital interests or public task: only in the exceptional circumstances where applicable law permits and the relevant conditions are met; these are not normal bases for the public Service.

Where legitimate interests are relied upon, the relevant interests include providing a functional, secure, sustainable service; protecting users, creators, infrastructure, and the operator; understanding faults; and handling claims. You may object where the law gives you that right. MediaPuller must stop unless it demonstrates compelling legitimate grounds or needs the information for legal claims.

17. Data Retention

MediaPuller retains different categories of information for different periods, taking account of the purpose of processing, the sensitivity of the information, security needs, the nature of the Service, legal obligations, and the need to establish, exercise, or defend legal claims:

  • Temporary caches and proxy state: retained only for a limited operational period reasonably necessary to process a request, reduce repeated source requests, protect the Service, or complete temporary delivery.
  • Authentication and security information: retained for the duration needed to administer access, secure the Service, investigate abuse, and meet legal or claim-related obligations.
  • Downloader records, public pages, story history, administrator accounts, recovery records, notification records, attachments, and managed content: retained for as long as reasonably necessary for the purposes described in this Policy, including until removal, deletion, or a retention decision under applicable procedures.
  • Application logs: retained for an operational and security period reasonably necessary to diagnose issues, protect the Service, and meet legal obligations.
  • Google Analytics data: retained in accordance with MediaPuller's analytics settings and Google's applicable controls and policies.

Some records may be retained in restricted form after deletion or removal where necessary for security, fraud prevention, compliance, legal claims, or backup integrity. Search indexes, browser caches, Source Platforms, and other third parties may retain independent copies under their own policies.

18. Temporary Caching, Proxying, and Media Storage

Temporary caching helps reduce repeated source requests, improve response time, and protect the Service from abusive load. Cached information may include submitted URLs, usernames, source identifiers, returned metadata, media addresses, and temporary delivery information. Such entries are retained only for a limited operational period and can expire or be removed earlier.

For most downloader results, MediaPuller returns a source or CDN URL and does not store the media bytes. Some features use temporary proxying or streaming where necessary to provide delivery. Those processes use transient memory and network buffers while the request is handled, but MediaPuller does not intentionally save the requested media as permanent downloader files.

This statement does not apply to files deliberately uploaded through an upload-capable endpoint, restricted administrator content, application logs, database metadata, platform session files, or a visitor's own browser and device storage.

19. Security, Fraud Prevention, and Abuse Detection

MediaPuller uses technical and organisational measures intended to protect the Service, including secure transport, protected authentication state, password hashing, role-based restricted areas, form-security controls, input and platform validation, log-based diagnostics, and request-limiting controls. No Internet service can guarantee absolute confidentiality, integrity, or availability.

The Service examines connection information, request route, request rate, concurrent activity, User-Agent, validation results, authentication state, and error patterns to prevent automation, credential attacks, scraping, spam, denial of service, and misuse. It may refuse a request, return a rate-limit response, temporarily restrict an address, suspend a feature, or permanently block abusive activity. MediaPuller applies technical rate-limiting and concurrency controls to protect the Service; those controls may change for security or capacity reasons.

Security records may be retained beyond a normal cache period where reasonably necessary to investigate an incident, prevent recurrence, comply with law, or establish or defend claims. MediaPuller will not disclose details that would materially weaken its controls.

20. Third-Party Services and Recipients

Information is disclosed only as needed for the feature, for security and operations, or as required by law. Recipient categories include:

  • Source Platforms, their APIs, media hosts, and CDNs needed to resolve or deliver submitted content;
  • platform-specific intermediary services used by certain integrations;
  • website hosting, network, DNS, reverse-proxy, and infrastructure providers;
  • Google Analytics and related Google delivery infrastructure;
  • the comments-widget provider on pages where comments are enabled;
  • email delivery and mailbox providers used for support or notifications;
  • professional advisers, courts, authorities, complainants, and counterparties where necessary for legal compliance or claims; and
  • a successor or proposed successor in a lawful reorganisation, financing, sale, or transfer, subject to appropriate safeguards.

MediaPuller does not disclose a visitor's reusable platform password because the public Service does not ask the visitor to provide one. MediaPuller's own technical platform credentials and sessions are operational secrets. Users must never submit their own platform cookies, bearer tokens, or passwords in the ordinary URL or username fields.

21. Source Platforms, External APIs, and Intermediaries

MediaPuller can communicate with Source Platforms displayed through the Service's supported-site and downloader interfaces. Those platforms include social networks, video hosts, music services, image hosts, messaging services, and their associated APIs and CDNs. Support changes over time. Each recipient processes information under its own privacy policy and terms.

Certain integrations use third-party intermediary providers, including image-proxy providers and media-delivery services, where necessary to obtain metadata, previews, delivery options, or requested functionality. Such providers may receive a source-media address and ordinary browser or server request data. HyperComments receives browser data on pages where its comments widget loads. MediaPuller may also use third-party extraction software that communicates with the relevant Source Platform and its CDN.

A server-side request normally exposes MediaPuller's server IP to the Source Platform rather than the visitor's connection IP, unless information is deliberately forwarded. A direct media or image request from the browser exposes the visitor's IP and browser request data to the third party. MediaPuller does not control whether a Source Platform associates that request with cookies already present in the visitor's browser.

22. Hosting, Edge, Reverse-Proxy, and CDNs

MediaPuller may use an edge, reverse-proxy, or security provider. Where used, that provider may process connection information, including IP address, request headers, requested URL, security signals, response details, and cookies, as necessary to deliver and protect the Service.

Hosting provider. The Service uses third-party hosting and network infrastructure. The provider may process connection data, stored application files, database data, backups, and operational logs within the permissions of the hosting arrangement.

CDNs and media hosts. Source Platforms commonly deliver thumbnails, images, audio, and video through separate CDN domains. When the browser receives a direct address, the corresponding CDN processes the network request under the platform's policy. MediaPuller may not be able to identify the final CDN in advance because signed URLs and delivery hosts change dynamically.

23. Google Services, Analytics, and Fonts

The Service uses Google Analytics 4. Google can receive page address, referrer, IP-derived location, browser and device information, language, timestamps, interaction and campaign information, and analytics identifiers. Google may set analytics cookies. MediaPuller uses analytics to understand traffic, popular pages, and technical performance.

Google Analytics settings and controls govern its retention and certain processing choices. In jurisdictions where prior consent is required before non-essential analytics is activated, such analytics should not be activated until a valid choice has been obtained.

MediaPuller may also contact YouTube or Google APIs to resolve supported media, and may use Google-hosted fonts. Those requests can provide Google with the relevant source identifier or ordinary network and browser information. Other technology providers may process information only where necessary to operate, secure, support, or improve the Service.

24. Advertising, Comments, Embedded Content, and External Links

MediaPuller does not currently operate third-party advertising scripts on its public pages. If advertising or another advertising-related provider is introduced, MediaPuller will update this Policy and implement any notice, consent, opt-out, and contractual measures required by applicable law before or when that change takes effect.

News detail pages load a HyperComments widget. When it loads, the provider can receive IP address, User-Agent, page address, referrer, cookies, and any information a visitor submits to the widget. Comments are governed by the provider's notice as well as applicable MediaPuller rules.

Pages can contain direct media, thumbnails, social-share buttons, or outbound links. Loading an external image or media element may contact its host automatically. Clicking a share or external link can disclose the current or selected address to services such as Facebook, WhatsApp, Viber, Telegram, X, LinkedIn, or VK. MediaPuller is not responsible for their subsequent processing.

25. International Data Transfers

MediaPuller operates from Ukraine, while Source Platforms, hosting infrastructure, analytics providers, CDNs, technical intermediaries, and visitors may be located worldwide. A request can therefore involve a transfer to a country with different privacy laws. The destination depends on the requested source, CDN routing, provider infrastructure, and visitor location.

Where GDPR transfer restrictions apply, MediaPuller uses an available lawful transfer mechanism, such as an adequacy decision, appropriate contractual clauses, or another permitted mechanism, and applies supplementary safeguards where required.

26. Your GDPR and Related Privacy Rights

Subject to applicable law and exceptions, you may have the right to:

  • obtain confirmation whether MediaPuller processes your Personal Data and receive access to it;
  • correct inaccurate or incomplete Personal Data;
  • request erasure where there is no overriding lawful reason to retain the data;
  • restrict processing in specified circumstances;
  • object to processing based on legitimate interests, including the publication of Public Metadata relating to you;
  • receive Personal Data you provided in a structured, commonly used, machine-readable format where portability applies;
  • withdraw consent at any time for future consent-based processing;
  • object to direct marketing; and
  • complain to the competent data-protection supervisory authority, including an authority in the EEA or UK where applicable.

To exercise a right, email mediapuller@gmail.com with enough information to identify the relevant record, such as the exact MediaPuller page, submitted source URL, username, date range, or administrator account. MediaPuller may ask for proportionate verification, redact information belonging to others, and refuse or charge for a manifestly unfounded or excessive request where law permits. We aim to respond within the time required by applicable law.

27. California Privacy Rights

If the California Consumer Privacy Act, as amended by the California Privacy Rights Act, applies to MediaPuller and to you, California residents may have rights to know the categories and specific pieces of Personal Information collected, know the sources, purposes, and recipient categories, request deletion, request correction, opt out of sale or sharing, limit certain uses of Sensitive Personal Information, and receive equal service without unlawful discrimination.

The categories described in this Policy can include identifiers, Internet or electronic-network activity, account or profile information, user-provided content, and inferences limited to device or bot classification. MediaPuller does not currently sell Personal Information for monetary consideration or operate targeted advertising. The use of analytics may be regulated as "sharing" in some circumstances. Where applicable law provides an opt-out right, you may submit a request through the privacy contact above.

Submit a California request through the privacy contact above. MediaPuller will verify and honour the request to the extent the law applies. An authorised agent may submit a request where legally permitted, subject to proof of authority and verification. MediaPuller will not discriminate against you for exercising an applicable right.

28. Children's Privacy

The Service is not directed to children under 16, and MediaPuller does not offer public child accounts. The Service does not perform age verification. Because users can submit public source URLs and profiles, returned or generated metadata could incidentally relate to a child even though MediaPuller does not seek that information.

A child must not use the Service where they cannot lawfully consent or enter the applicable Terms without a parent or guardian. If you are a parent, guardian, or affected person and believe that MediaPuller unlawfully processes a child's Personal Data, contact us with the relevant page or identifier so that we can investigate and take appropriate action.

29. Automated Processing and AI-Assisted Processing

MediaPuller uses automated systems to validate submitted values, classify platforms, contact sources, parse metadata, select media formats, generate page names, detect known bots, count requests, apply rate limits, cache results, and return errors or results. A request may be automatically refused because it is invalid, unsupported, too frequent, unavailable, or exceeds a concurrency limit. These operational decisions do not ordinarily produce legal or similarly significant effects on an individual.

MediaPuller does not currently send Request Data or Personal Data to an artificial-intelligence or generative-AI provider. Media extraction and classification use automated technical processes. If MediaPuller introduces AI-assisted processing, it will assess the purpose, provider, data categories, retention, legal basis, safeguards, and user rights, and update this Policy before or when that processing begins.

30. Cookie and Analytics Management

You can use browser controls to inspect, block, or delete cookies and site data. Blocking essential authentication or anti-forgery cookies can prevent restricted functions or protected forms from working. Browser privacy settings, content blockers, or DNS tools may block Google Analytics and third-party resources, but MediaPuller does not guarantee compatibility with every browser setting.

At the effective date, MediaPuller does not provide a separate on-site cookie preference centre. Browser settings alone may not control all third-party processing. In jurisdictions where non-essential tracking requires a prior consent, an appropriate consent and withdrawal mechanism must be made available before that tracking is activated. You should also review the privacy choices made available by relevant third parties.

31. Data Deletion, Objection, and Public-Page Removal Requests

Send deletion or objection requests to mediapuller@gmail.com. Include the exact MediaPuller URL, source URL, username or profile identifier, platform, approximate request date, and an explanation of your relationship to the information. For an account record, use the email associated with the account where possible. Do not send more identity evidence than necessary.

MediaPuller will assess whether the record is Personal Data relating to you, whether you are authorised to act, whether an exception applies, and whether the record should be hidden, corrected, soft-deleted, permanently deleted, or retained in restricted form. We may retain limited information needed for security, fraud prevention, compliance, legal claims, or to record an honoured opt-out. Deleting a public page does not control the Source Platform or third-party caches and indexes.

32. Changes to This Policy

MediaPuller may update this Policy when the Service, law, providers, data practices, or risk profile changes. The revised version will be posted at https://mediapuller.com/privacy with a new effective date. If a change materially affects how Personal Data is used, MediaPuller will provide additional notice where reasonably possible or legally required and will seek consent where a new consent-based purpose requires it.

You should review this page periodically. Continued use after an update does not replace consent where the law specifically requires consent.

33. Contact

Privacy questions, GDPR or California requests, objections to a public generated page, and deletion requests may be sent to:

MediaPuller Privacy Contact
Email: mediapuller@gmail.com
Website: https://mediapuller.com
Operating location: Ukraine