Law enforcement guidelines

How to make a request, what process we need before we answer it, and — just as important — what does not exist to be handed over.

Last updated 4 September 2026.

Where to send a request

Write to support@daxone.app with "Law enforcement request" in the subject line. It reaches a person.

Carino is operated by the operator of Carino. The registered entity and its address are being added here before public launch.

Please include the legal process itself, the account you are asking about — an email address or a profile link is enough to identify one — and the narrowest description of the records you need. A request for everything about an account takes longer to answer than a request for the two things the investigation actually turns on.

What we need before we disclose anything

We disclose member data only on valid legal process. A request from an official email address is not legal process, and we do not act on one.

Subscriber records — the email address on an account, when it was created, and when it was last used — on a subpoena or its equivalent under the law that binds us.

Stored content — profile text, photos, room posts, and the messages held in a match conversation — on a search warrant or a court order of equivalent standard.

Requests from outside the jurisdiction we are established in should come through a mutual legal assistance treaty, a letter rogatory, or the equivalent route, unless there is an emergency as described below.

What we actually hold

An account is an email address, a hash of a password, whatever the member wrote on their profile, the photos they uploaded, the questions they answered, who they said yes or no to, what they posted in the rooms, the messages in their match conversations, and any reports or blocks involving them.

We run no analytics, advertising, or third-party tracking of any kind. There is no browsing history, no device fingerprint, no advertising identifier and no data-broker record to produce, because none of it is ever collected.

Card details are held by Stripe and never by us. A request for payment records should be served on Stripe.

What we cannot produce

The contents of an end-to-end encrypted private chat. Those messages are encrypted in the member's own browser with a key we never receive, and they are never written to our database. We hold no copy and no key. That is a property of how the system is built rather than a policy we could be ordered to reverse — there is nothing on our side to decrypt and nothing to hand over.

Anything belonging to a deleted account. Deletion is immediate and there is no grace period. An account deleted before a request reaches us cannot be produced, and there is no backup from which to reconstruct one.

Preservation requests

We will preserve the records of an identified account for 90 days pending service of legal process, and renew that once on request. Ask in writing, identify the account, and say that preservation is what you are seeking.

Preservation is not disclosure. Preserved records are still released only on the process described above, and preserving them does not stop the member deleting their account — it stops us from being the reason the records are gone.

Emergencies

Where we believe in good faith that there is an imminent risk of death or serious physical injury, we may disclose the information needed to prevent it without waiting for process.

Mark the subject line "Emergency disclosure request", and say what the danger is, who is in it, and what you need from us to stop it. We would rather read one of these that turns out to be unfounded than miss one that was not.

Telling the member

Our default is to tell a member that their data has been asked for, and to give them a chance to object before we hand anything over. Somebody should know when the state asks about them.

We will not tell them where a court has ordered us not to, where the law forbids it, or where we believe notice would put somebody in danger or lead to evidence of harm to a child being destroyed.