Restriction is a privacy job you can name

A privacy request that only waves at a statute is not a complete request. The privacy-requests guide on www.oernoe.com is blunt about that for a reason: vague messages that only say “GDPR” slows the reply because the team still has to guess the job. Restriction is one of the jobs you can name. It sits beside copy, correction, and deletion in the “what to send” list, and naming it is how you keep the inbox from turning into a support thread dressed up as law.

This essay is about that naming. Not about inventing faster statutory clocks. Not about turning privacy@oernoe.com into a product help desk. About writing a message that says which work you want done while a complaint is looked at, from the account email, with hostnames attached when you can.

## The four jobs, in plain language

The guide asks you to say which of these you want: a copy of the account data we hold, a correction of a specific field, a deletion of the account, or a restriction while we look at a complaint. If you want more than one, list them. That sentence is the whole process design. Copy is an export of the account record. Correction is a named field that is wrong. Deletion removes the account and the content attached to it after confirmation. Restriction is the temporary brake: keep processing limited while a complaint is examined.

People blur those jobs because privacy language on the open web is often a paste of rights labels without a concrete ask. “I want my data” might mean export, or it might mean delete everything, or it might mean stop using a field until a dispute ends. Anoepal’s privacy inbox is small. There is no overnight desk and no chatbot that closes the ticket to keep a metric down. A complete request that names the job gets acknowledged on the timeline the guide already publishes: a few working days for a complete request, with statutory deadlines, where they apply, living in the Privacy Policy rather than in a cheerleading number on the guide.

Restriction is useful precisely when you are not ready to delete and you are not only asking for a file. You believe something is wrong, or contested, and you want the account handled carefully while that is reviewed. Saying “restriction” does not replace evidence. It tells the operator which queue your message belongs in.

## Why vague statute words slow the reply

“GDPR” is a statute name, not a ticket type. The same is true of other privacy law labels people drop into a subject line. The inbox still has to decide whether you want a copy, a fix, a deletion, or a restriction. Guessing wrong wastes both sides: you get a question back, or you get the wrong job started, or the message sits while someone tries to infer intent from tone. Incomplete messages get a question back, not a refusal. That is already documented. The way to avoid the round trip is to name the job in the first message.

Write from the email address on the Oernoe account. That is how identity is checked without asking for a passport scan. If you no longer have that inbox, say so and describe another account fact that can be checked, such as a recent login time or a hostname you used. Do not send a password, a one-time code, or a screenshot of a session cookie. Those instructions are not bureaucracy for its own sake. They keep a privacy request from becoming an account takeover channel.

Name the hostnames you used if you can: Search, Health, Chat, AI, Docs, Drive, Tracker, or this publisher site. Health notes and Chat threads are not the same pile as a Search listing you submitted. Restriction on one surface may not be what you meant for another. Specificity is how the team avoids rummaging through the wrong store while a complaint is open.

## What restriction is not

Restriction while a complaint is looked at is not a silent promise that every log line on earth freezes. It is not a takedown of a third-party page that mentions your name in Search results. It is not Google Ads Settings. It is not a billing dispute ticket. It is not support for a product bug. Those neighboring jobs have their own doors: support@oernoe.com for product failures, legal@oernoe.com for legal threats, the DMCA packet for copyright notices, Google’s own tools for ad choices on publisher pages you once opened.

Deletion, for comparison, removes the account and attached content after a confirmation step, because people sometimes write in a hurry and then want a Drive folder back. Some records can still remain when law or security requires it: a truncated log that a deletion happened, a billing record if you paid for a labeled premium feature, a fraud note. Privacy says when that applies. Restriction is earlier in the timeline than deletion. It is the named pause, not the memory wipe people sometimes imagine when they only write a statute acronym.

An export is also a different job. An export is the account record held to run the product: identity fields, services attached to the account, and content stored in those services where it can be retrieved. It is not a dump of every request log ever seen, and it is not other people’s data that happens to sit next to yours. Search queries are not an advertising profile. Ordinary request data still exists to return a page and fight abuse. If a query log is retained for security, that belongs in Privacy’s description, not in a fantasy that every keystroke arrives in a zip file. Restriction does not substitute for export, and export does not substitute for restriction.

## How to write the restriction ask

A useful restriction message looks boring on purpose. It comes from the account email. It names restriction as the job. It states, in a few concrete sentences, what complaint is being looked at: which field, which service, which event, which date range if you know it. It names hostnames. It does not paste a password. It does not mix a copyright notice, a billing argument, and a privacy right into one paragraph. Mixing jobs is how replies get slower.

If you also want a copy of account data while the complaint is open, list both jobs. If you want a correction of a specific field and a restriction until that correction is confirmed, list both. The guide’s instruction to list multiple asks is there so the operator does not have to choose for you.

If the request needs a product change before it can be answered, the reply should say that in plain language, not hide behind a holding paragraph. That honesty rule is already in the privacy-requests guide. Restriction does not erase the need for product work when the underlying issue is a missing control or a bug. It names the privacy handling while that work is sorted.

## Distinct from the nearby essays

This piece is not Incomplete privacy request gets a question back, which is about the round-trip mechanic when detail is missing. It is not Privacy export is not a search diary, which is about what an export contains and what it refuses to pretend. It is not Product change before privacy reply, which is about cases where the answer waits on engineering. It is not Privacy request inbox is not support, which is about keeping privacy@oernoe.com from absorbing every product complaint. It is not Billing records can outlive a deleted account, which is about retention after deletion. Restriction is the named job itself: how to ask for limited processing while a complaint is examined, without hiding behind a statute label.

## Publisher ads and the privacy inbox

Selected finished pages on www.oernoe.com may load Google AdSense. That is not Search selling queries. Google may process cookies, IP address, device data, and page context on those pages. Oernoe can delete or restrict processing for the account it holds. Oernoe cannot reach into Google’s ad systems and erase a prior ad request. For ads choices, use Google Ads Settings and the industry opt-outs linked from the Cookie Policy. Login, signup, Account, Search, Health, Chat, AI, Docs, Drive, and Tracker do not load that ads script. If an ad unit appears inside those products, that is a bug for support, not a privacy setting to negotiate by statute name alone.

Restriction requests about account processing should still name the account and the hostnames. They should not be written as if the privacy inbox can rewire a third-party ad network by reply. Keeping those systems separate is part of the same clarity that makes “restriction” a useful word instead of a fog machine.

## What “looked at” implies for a small team

Oernoe is operated by Anoepal. The privacy inbox is privacy@oernoe.com. There is no form behind a login wall. Acknowledgement aims for a few working days on a complete request. Restriction while a complaint is looked at therefore implies a human review, not an instant automated freeze badge in the product UI. If you need a faster product-side lock—signing out sessions, changing a password, turning on two-factor when the setting is there—do those account security steps as well and say that you did. The privacy job and the security steps complement each other. One does not replace the other.

Pages in Search results that are not your account remain a different path: send the exact result URL and the reason. A listing you submitted about yourself is a product object. A listing someone else submitted still needs a check so the wrong row is not removed. Restriction of your account processing does not automatically retract a public web page someone else published.

## The habit worth keeping

Name the job. Restriction is allowed to be the word you use. Pair it with the account email, the hostnames, and a short description of the complaint under review. Leave passwords out. Leave statute-only subject lines for people who enjoy slower answers. When the complaint resolves, you can still ask for correction, export, or deletion as separate, named jobs.

That habit is how a privacy request stays a privacy request. It is also how restriction earns its place on the list next to copy, correction, and deletion: not as a mystical right label, but as work you can point at, in language the inbox can act on, without pretending the operator can guess what you meant from a single acronym.