Skip to content

Google copyright removals

Account
dmcalens

Privacy policy

What DMCALens collects, why, who processes it for us, how long each item is kept, and how to have it removed.
Effective
13 October 2026
Cookies
One, for sign-in
Advertising
None
Usage analytics
Microsoft Clarity, without cookies
Requests answered within
30 days
Contact
[email protected]

1. Who is responsible

DMCALens (dmcalens.com) is run by its operator, referred to here as “we”. We decide what personal data the service processes and why, which makes us the controller of that data. Every privacy question or request goes to [email protected]. We answer requests ourselves.

This policy covers the website, accounts, alert emails and payments for paid plans. It does not cover the notice records republished on the site, which come from Google; section 9 explains how those are handled.

2. What we collect and why

Visitors without an account. Reading the site needs no account. We do not ask for any personal data and do not set a cookie. Every request reaches our server with your IP address, the page asked for, the time and your browser's user agent. We use these to deliver the page, to apply rate limits and to block abusive traffic. They are not combined into a profile of what you read.

Account holders. An account consists of:

  • your email address, used to send sign-in links, the alerts and summaries you ask for, and service messages about your plan;
  • your plan (Free, Pro or Business) and, for a paid plan, the date the paid period ends;
  • the date the account was created and the date of your last sign-in;
  • sign-in links and sessions, stored only as hashes, so a copy of our records cannot be used to sign in as you;
  • the IP address that requested each sign-in link, kept with that link to stop people from flooding an address with links;
  • your watchlist: the domains, agencies and rights holders you watch;
  • your alert history: which notices were included in which email to you, and when, so each notice is sent to you once;
  • a log of your CSV exports (what was exported and when), used to apply the daily export limit.

Paying subscribers. For each order we keep the plan, number of months, amount and currency of the price, the invoice and payment IDs issued by the payment provider, the payment status, and the crypto currency and amount you actually paid. We also keep the status messages the payment provider sends us about each order. We never receive wallet keys, seed phrases or card details.

People who write to us. If you email [email protected] or use the contact form, we receive your email address, the page you name and whatever you put in the message, and use them to answer you. Form messages are kept with the IP address they came from, for up to two years. If you ask for a refund, we also receive the wallet address you give us and use it only to send that refund.

The only emails we send are sign-in links, the alerts and summaries for your watchlist, notices about your paid period (a reminder before it ends and a notice when it has ended), notice of material changes to our terms if you are a paying user, and replies to your messages. We send no advertising and do not sell, rent or share personal data for anyone's marketing.

Where the EU or UK General Data Protection Regulation applies, we rely on these bases:

  • Performance of a contract (Article 6(1)(b)): the account, sign-in, watchlist, alerts, exports, payments for paid plans and the emails about your plan. Without your email address we cannot provide an account.
  • Legal obligation (Article 6(1)(c)): keeping order records for as long as tax and accounting rules require.
  • Legitimate interests (Article 6(1)(f)): server logs, rate limits and the sign-in IP address, to keep the service available and stop abuse; answering messages sent to us; and republishing Google's public notice records, in the interest of transparency about copyright removal requests (see section 9). You can object to processing based on legitimate interests at any time.

Usage analytics (section 5) also rest on legitimate interests: seeing which pages are used and where they fail, so the site can be fixed. We do not rely on consent for anything, because we do nothing that would require it: no tracking cookies, no advertising, no profiling.

4. Cookies and browser storage

  • Session cookie (named “__Host-dl_session”): set only when you sign in. It keeps you signed in for 30 days, is sent only over HTTPS to dmcalens.com, and cannot be read by scripts on the page. It is strictly necessary for the account, so it needs no consent banner.
  • Theme preference (“dl-theme” in your browser's local storage): set only if you choose light or dark mode with the header control. It never leaves your browser.
  • Home chart shown (“dl-pulse” in your browser's session storage): remembers that the home page chart has already played its opening animation in this browser session. It holds no data about you, never leaves your browser and is gone when the session ends.

There are no analytics, advertising or tracking cookies. The one third-party script is Microsoft Clarity (section 5), which runs without cookies; on the sign-in, account and contact pages everything it would record is masked.

5. Providers that process data for us

These providers process personal data on our behalf, only for the purpose listed:

  • Cloudflare: content delivery and protection against attacks. Every request passes through it, so it sees IP addresses and request data.
  • Cloudflare Email Service: delivers our emails. It receives your email address and the content of each email we send you.
  • NOWPayments: processes crypto payments for paid plans. You pay on NOWPayments' own payment page, where NOWPayments' terms and privacy policy apply to what you enter there. It tells us the payment status and the amount and currency received.
  • Microsoft Clarity: usage analytics. It records how pages are used (page views, clicks, scrolling, and replays of a visit with typed text and email addresses masked) together with the browser, device, country and IP-derived region. It sets no cookies, so visits to different pages are not linked. Microsoft's privacy statement applies to its processing.
  • Our hosting provider: the virtual server that runs the site and stores the account data and logs described here.

Some of these providers process data outside the EU and EEA. You can ask at [email protected] which provider handles your data where.

6. How long we keep it

  • Sign-in link (stored only as a hash) and the email it was sent toKeptValid for 20 minutes; deleted one day after it expires
  • IP address that requested a sign-in linkKeptDeleted with the link, one day after it expires
  • Session (stored only as a hash)Kept30 days from sign-in, or until the account is deleted
  • Email address, plan and account datesKeptUntil you delete the account
  • WatchlistKeptUntil you remove the watch or delete the account
  • Alert history (which notices were emailed to you, and when)KeptUntil you delete the account
  • CSV export log (what was exported, and when)KeptUntil you delete the account
  • Orders and payment status recordsKeptAs long as tax and accounting rules require, up to 10 years; the link to your account is removed when you delete it
  • Contact form messages, with the sender's IP addressKeptUp to two years, then deleted
  • Server logs with IP addressesKept14 days
  • Theme preferenceKeptIn your own browser, until you clear it
  • Home chart shown (session storage)KeptIn your own browser, until the browser session ends

Deleting your account (section 7) removes your email address, watchlist, alert history, export log and sessions at once. Order records stay, without any link to you, because they are the record of a payment.

7. Your rights and how to use them

Depending on where you live, you have the right to:

  • get a copy of the personal data we hold about you (access);
  • have inaccurate data corrected (rectification);
  • have your data deleted (erasure);
  • have its use restricted while a complaint or correction is being dealt with (restriction);
  • receive the data you gave us in a machine-readable format (portability);
  • object to processing based on legitimate interests (objection);
  • complain to the data protection authority where you live or work.

Delete your account yourself: sign in, open your account and use Delete account. The deletion takes effect immediately and cannot be undone.

Everything else: write to [email protected] from the address on the account, or tell us which address the request is about so we can confirm it is yours before acting. We answer within 30 days, the time limit the GDPR sets.

8. Security

There are no passwords to leak: you sign in through a single-use link sent to your inbox, valid for 20 minutes. Sign-in links and sessions are stored only as hashes. All traffic is encrypted with HTTPS. Anyone who can read your mailbox can sign in as you, so keep that mailbox secure.

9. People named in Google's records

The notice records on DMCALens are republished from Google's public copyright removal data. They name the organisations that sent notices, the rights holders they acted for and the domains and URLs reported. Sometimes a sender or rights holder is a person rather than a company. We do not add personal data to these records and do not judge whether a notice or a site is lawful.

Pages of rights holders whose notices mostly concern adult sites, and pages of adult domains, are kept out of search engines, and their names are not printed on pages that search engines index.

If a record names you as a person and you want it reviewed, write to [email protected] with the address of the page and what you are asking for. We review every such request ourselves and answer within 30 days. We cannot change or remove a record at Google; a request to Google has to go to Google.

10. Children

DMCALens is a tool for site operators and rights professionals and is not directed at children. If you believe a child has opened an account, write to [email protected] and we delete it.

11. Changes to this policy

When this policy changes, we publish the new version on this page with a new effective date.

12. Contact

Privacy questions and requests: [email protected]. The terms that govern use of the service are on the terms page.