Law Enforcement Guidelines
Last updated 25 October 2026
This page is for law enforcement officers and agencies. It says where to send a request, what a request has to contain before we can act on it, and exactly what we can and cannot hand over. If you are a member looking for our rules, the Acceptable Use Policy is the page you want.
Not Pen Pals is a small dating app for adults, run by one business — NOTPENPALS LLC, which trades as Not Pen Pals and is organised under the laws of the State of Wyoming. There is no legal-response desk here and nobody working through the night: a person reads requests, in the order they arrive, and answers in writing. We are not a large platform with a team whose whole job this is, and we would rather tell you that plainly than leave you waiting on a service level we cannot keep.
Where to send a request
Email [email protected], with "Law enforcement request" in the subject line, and put your case or reference number in the body so it can be found again later.
Or send it by post to NOTPENPALS LLC, 30 N Gould St #70080, Sheridan, WY 82801.
One route is enough. Please do not send the same request to both — the mailbox and the post are the two places these are read.
What a request has to contain
A request we can act on arrives on official agency letterhead, or from an official agency email domain, and it contains all of the following:
- The agency you work for, and your name, rank or title, with the contact details we should answer to.
- A case or reference number we can quote back to you.
- A call-back number for the officer handling the case.
- The member or account the request is about — an account identifier, the email address on the account, or the name on the profile. We cannot work with a request that describes a category of members and names none of them.
- The date range you are asking about.
- Exactly what you are asking for: which records, and what you expect them to show.
- The legal process you are relying on — a subpoena, a court order or a warrant — with the issuing court and jurisdiction, and a copy of it attached. Tell us what it compels, and whether anything in it stops us telling the member.
If something is missing we will write back and ask for it rather than guess at what you meant. Without legal process that authorises disclosure, we can tell you what we hold and what process would be needed — not the records themselves.
Emergency requests
If there is an imminent risk of death or serious physical harm, put "Emergency" as well as "Law enforcement request" in the subject line, and describe the risk and why you believe it is imminent. Those go to the front of the queue, ahead of everything else in the mailbox.
Where the law allows it and the risk is real, we will act on what we can without waiting for a court order. We will still confirm who you are and which agency you are with before anything is handed over, and we will provide only what the emergency actually calls for.
The legal process that covers what we provided is still expected afterwards.
Child safety
Apparent child sexual exploitation or abuse goes to law enforcement and, as required, to the National Center for Missing & Exploited Children's CyberTipline, and we close the account. There is no warning, and we do not handle it quietly. The rules themselves are in our Acceptable Use Policy; this page does not restate them.
We do not automatically scan photos or messages, so on this service a report is usually how we find out. If you are an officer telling us that content of that kind is on Not Pen Pals, send it as an emergency request, with "Emergency" in the subject line, and say what you have and where you saw it.
We do not investigate these matters ourselves, and we do not wait to be satisfied that a report is well-founded before passing it on.
What we can provide, if the legal process supports it
This is the whole of it. If something is not on this list, we do not hold it:
- Account: the email address on it, the date it was created, its status — active, suspended or deactivated — when the member was last active in the app, and when they accepted the terms.
- Profile: the name the member goes by, their date of birth and age, their gender, their height, their photos, the country they declared they were in — accepted only as the United States, and not checked — the race or ethnicity they gave for themselves — a value they picked from a list, which we never check — whether they have children and whether they want more, which they also picked from a list and we never check — how often they drink and smoke, which they also picked from a list and we never check — the short written answers on their profile, what they said they were looking for, and when they said they were available.
- Their preferences: who they said they were open to meeting, the age range, height range and distance they set, and the races they said they wanted to see, the children answers they said they wanted to see, and the drinking and smoking answers they said they wanted to see, if they narrowed any of them. Each of these is a choice the member made about which people to be shown — a height range, a race preference, a children preference or a drinking or smoking preference is what they asked for, never a fact about anyone else.
- The location we hold for them: the point on their profile, snapped to a grid of approximately 1 mile before it was saved, and any place label they typed for themselves. Their coordinates are never turned into an address, and there is no history of where they have been — only that one current snapped point.
- Matches: who the member matched with and when each match was made, and any plan for a meet either of them proposed with a match — including plans that never became a meeting — with who proposed it, when it was planned for, how long it was to last, whether they both confirmed it, the place name, address and map point they entered for it, and anything either of them wrote in the plan's notes or with a confirmation.
- The extension of a match's clock: who asked for it, who accepted or declined it, and when. Only one can exist per match.
- Messages: the messages a member sent and received in a match, with the time each was sent.
- Likes and passes: who the member liked, and who they passed on.
- Blocks and reports: who blocked whom, who reported whom, and when; the reason chosen for it, anything written in the free-text detail a member may add, and — once a reviewer has acted — the decision they reached and their short note. A report hides the two members from each other by default, and that change is visible in the data.
- Subscription: whether it is trialling, active, paused or cancelled, and the event records our processor sends us about the subscription and its payments, kept as they arrived — those records can carry the email address the member gave the processor. The payment card is held by our payment processor and never by us — we hold no card number, no expiry date and no security code.
- Phone number: if the member set one up so they could be reached on a masked call, the number they gave us, stored as they typed it. We do not verify it by text message, so we cannot tell you it is theirs.
- Calls: that a masked call was asked for, who asked for it, when, and whether it connected. We hold no recording and no audio from the call itself.
- Verification: whether the member sent a selfie, what a reviewer decided, and their short note. The selfie image itself is deleted on a clock that runs about 30 days from when it arrives, once a reviewer has decided on it — whichever way that decision went. If no reviewer has decided by the time those 30 days are up, we keep the image while the review is open, because the review needs it, and it is deleted at the next daily cleanup after the decision. It does not stay with us indefinitely.
- The early-access list: if someone joined the list on our website rather than creating an account, the email address they typed and when it was added.
- Technical and connection records: which requests our own API answered for that account, when, and with what status — and only within the retention of our service records.
That last one is the honest one. Those records exist only within the retention of our service records, and we do not control that window; we are not going to quote you a period we have not confirmed. They are a record of requests, not a history of anyone's movements. If what you asked for is already gone, we will tell you that rather than send you something that looks like more than it is.
What we cannot provide
Some of what gets asked for does not exist here. It is not being withheld — we never had it:
- No real-time location and no location history. A member's own location is used only as an approximately one-mile grid, so the app can work out a rough distance between two people, and a precise position for the member is never stored. There is no background tracking: coordinates are only sent while someone is using the app. The one precise point we may hold is a venue's — the map point of a place entered for a date plan — and it describes the place, not the member.
- No card numbers, expiry dates or security codes. The member's payment card is held by our payment processor, not by us.
- No passwords. Sign-in is handled by our authentication layer, and we never see a password.
- No contents of a call. Masked calls connect two members through a number we own: we record that a call was asked for, who asked, when, and whether it connected, and we never listen to or record the call itself.
- Nothing on a verbal, informal or off-the-record request. A phone call is not legal process — the emergency route above is the one exception, and it is for danger, not for convenience.
Notice to the member
We tell the affected member that a request has arrived, and give them a chance to object — unless a court order or the law forbids it, or unless telling them would risk someone's safety.
If your order is sealed, or carries a non-disclosure requirement, say so on its face and tell us how long it runs for. We will follow it, and no further than it goes.
If you think notice would tip off the person the request is about, or put someone in danger, say so in the request and tell us why. We would rather weigh that with your reason in front of us than guess at it.
Preservation
Ask us in writing — from an agency email domain, or on letterhead — and we will preserve existing records while you obtain legal process. Say what you want held, and for how long.
In practice this is done by hand: a person keeps the records you have named out of routine deletion for as long as your request says, and takes them off any deletion clock of ours they sit on. There is no automated hold. It does not create anything we did not already have, and it is not disclosure: nothing is handed over until legal process arrives. One limit, stated plainly: if the member deletes their own account, that deletion takes their profile, photos and conversations with it — deleting an account is theirs to do, at any time, and we cannot hold it back. A report row that has been preserved is held for as long as the request or the open matter runs. A report row that was never preserved is not held out of anything by this process — but the member's own deletion does not take it either: a case stays after the account it names is gone, on purpose, so a reviewer can still read it. A case about a meet, a match, a picture or a message stays after the thing it is about is gone. What a reviewer decided on a case, and the note with it, is added to and never rewritten — a correction is recorded as a new entry beside it — and we keep report records for as long as we operate the service.
Cost
We do not charge law enforcement agencies for answering these requests. There is no fee schedule, and asking us to preserve records costs nothing.
A last word
This page describes how we handle requests. It is not legal advice, and it is not a promise that we hold anything we do not.
A request from outside the United States may need to come through the official mutual legal assistance route — from your country's central authority to ours. We will cooperate where the law requires it, but a request that arrives directly and has no legal effect here is not one we can act on.
If our practice changes, this page changes with it and the date at the top changes too. If anything here is unclear, ask us before you send it: [email protected].
Talk to a person
None of these pages is meant to be a maze. If anything here is unclear, or you want something changed about your own data, write to [email protected].