Privacy Policy

Overview

This policy describes how Ranklog (“we”, “us”, “our”) collects, uses, and discloses information when you use Mickey Banks, the high school basketball scouting assistant you reach by iMessage, and the site at textmickey.com (together, the “service”). Ranklog operates the service and is the data controller for the personal information this policy describes. Ranklog is organized in [RANKLOG STATE OF INCORPORATION]. “You” means the person who uses the site or texts Mickey.

Please read this policy carefully. If you use the service, you agree to this policy. If you do not agree, do not use the site and do not text Mickey. What the service does is described in the Terms of Service.

Changes to this policy

We may update this policy. We will change the effective date at the top and post the new version on this page. If a change is material, this page is the notice. We do not have an email address for every person who texts Mickey. If you do not agree to an update, stop using the service. If you keep using it after the new date, the update applies to that later use.

Information we collect and why

We collect the information below to reply, to keep a thread coherent, to count free replies, to limit bursts, to avoid answering the same delivery twice, to review reply quality, to secure the service, to enforce the terms, and to respond if you email us.

We do not sell, rent, or share personal information or message content with third parties for their own purposes. We do not use it for advertising. We do not use it to train artificial intelligence models, and we do not let anyone else train on it.

What you give us. If you use the form on textmickey.com, you give us your first name, last name, and mobile number. We pass your name and number to the service provider that delivers iMessage, so that line can accept your texts. We do not write your name into our database. We do not ask you to create a password.

If you text Mickey, we receive the phone number or iMessage handle that sent the message, the time, and the content: the words you typed, or a voice note. We need the number in the moment to send a reply. In our database we do not store the number as digits. We store a one-way code of the handle. The same number always produces the same code, which is how a later text finds the same reply count and thread. Someone who sees only the code cannot read the number out of it. We can match a request to your records only if you give us the number you used, because we have to rebuild the code. We do not write that number into our application logs. Voice-note handling does not write the audio or the transcript into those logs.

A voice note is audio. We fetch it long enough to transcribe it into text, then we answer the transcript the way we answer a typed message. We do not store the audio file in our database. The transcript can be stored as the text of that turn, as described below. The service that delivered the voice note may still hold the original audio. We do not control that copy. If we cannot transcribe a note, we ask you to type instead.

If you email us, we have whatever you put in that email.

What we store about a thread. For each texter we store the coded handle, the time of the first text, the time of the latest text, a count of messages in the current short rate window, and how many replies you have used so the free replies can run out.

For each inbound message we store a delivery record: a delivery id, the coded handle, the time we received it, and whether the reply was sent, ignored, or failed. That record does not include the words you wrote.

When we successfully send a scouting reply, we store the text of your message, or the voice transcript, and the reply we actually sent. We also store how long the reply took and a short record of the scouting notes used to write it. A text that is too long to accept is dropped and is not stored. After the free replies are used up, further texts get a payment link. Those texts are not sent on to be drafted, and the words are not added to the stored thread. The delivery record for that text can still exist, without the words.

The drafter of a reply reads up to the last 20 messages of conversation context. That number is how far back a new reply looks. It is not a deletion schedule. If conversation storage is configured, we keep the text of the exchange, including your message and the reply we sent, so the next answer can follow the thread. If it is not configured, that context stays in the temporary memory of the server process that handled the text and is not written to the database. A first text that is only a greeting is not sent to the drafter. Later greetings are.

Reply quality. When reply review is turned on, we score delivered exchanges, either a sample or all of them, depending on a setting. A review record can include your message, our reply, the scouting notes used for that reply, a score, and a short explanation. We use this to see whether replies are holding up. We do not use it for advertising, and we do not let anyone train on it. Review does not run unless that part of the service is configured.

Scouting notes. Scouting notes are a separate store: players, schools, rankings, offers, visits, commitments, and what scouts wrote. Mickey reads them to answer. Your phone number is not written into that store. Naming a player in a text does not open an account for that player, and it does not make that player a user.

Payment. After the free replies, we text a link to a payment page. If you open it, the payment provider collects what it needs to charge the plan. We do not receive or store your card number. Our database does not store a customer id or a receipt. We do not send your phone number to the payment page from our code.

The site. textmickey.com does not set its own cookies, and it does not run advertising or analytics scripts. When you submit the signup form, we may hold your IP address for a short time in the memory of the server process handling that request, to slow repeated signups. We do not write that address into our database. A restart of that process clears it.

The host that serves the site and the text service may keep its own request logs. Those logs can include an IP address, browser type, and the time of a request. We use them to operate and secure the service, not to advertise. We do not set that host’s log schedule in this policy.

We do not collect precise location, and we do not buy personal information about you from data brokers.

Cookies and tracking

The public site does not use cookies, pixels, or similar tracking tools to follow you around the web or to advertise. The site is not built to respond to a browser do-not-track or opt-out signal, because we do not run that kind of tracking. Blocking cookies should not stop you from reading the site. The text service does not use a browser cookie to recognize you. It recognizes the coded handle of the number you text from.

Who we share it with

We disclose personal information to service providers who process data only on our behalf, under confidentiality and data-protection obligations, to operate the service. Those providers handle messaging delivery, hosting, artificial intelligence processing (to draft a reply and, when review is on, to score it), transcription of voice notes, and payment processing if you open a payment link. Your information is processed on our systems and on their systems. We do not authorize them to use it for their own purposes, for advertising, or to train their models.

We may also disclose information if the law requires it, to protect a person, to detect abuse of the service, or if the service is sold and the records move with it. We may disclose information to professional advisors, such as lawyers and accountants, when they need it to advise us and are required to keep it confidential.

We do not sell, rent, or share personal information or message content with third parties for their own purposes. We do not give it to data brokers or advertisers. We do not use it for advertising. We do not let anyone else train on it.

How long we keep it

We do not run an automatic deletion of the delivery record, the reply count, the stored thread, conversation memory, or review records. They stay until we delete them. The 20-message figure is only how far back a new reply looks. Older stored messages are not erased by that window.

Audio from a voice note is not kept in our database. The transcript can remain as text in the stored turn, with no set end date. The signup limit described above lives only in temporary server memory. Logs kept by a host follow that host’s own schedule, which we do not publish here.

Your requests

Email [RANKLOG CONTACT EMAIL] to ask what we have, to correct it, or to delete it. Include the phone number you texted from. We need that number to rebuild the coded id. There is no delete button on the site and no delete keyword in the thread.

When we can match the request, we will delete the coded user record, the reply count, the delivery log, stored turns, conversation memory, and review records tied to that code. We do not have an automated deletion tool that covers every store, so this is a manual step. We may keep a short note of the request itself, and we may keep what a law, a dispute, or a security incident requires. Deleting our copy does not delete a message still held by the messaging network, a payment provider, or another service provider under its own rules.

You may have other rights where you live, including the right to appeal a refusal. Email us and we will apply the law that covers you. We do not sell personal information, so there is no sale opt-out to switch on.

Other sites

We may send you a link to a payment page we do not control. If a reply points at a school or another site, that site is not ours. Read that party’s policy before you give them information. We are not responsible for their privacy practices. A link is not an endorsement.

Children

Mickey is not directed at children under 13, and the terms limit the service to people who are at least [MINIMUM AGE]. We do not knowingly collect personal information from a child under 13. We do not ask your age. Scouting notes describe high school players and can include school, class year, and what a scout wrote. We do not ask you for a player’s home address, phone number, health details, or family contacts. If you believe we have personal information from a child under 13, email [RANKLOG CONTACT EMAIL] and we will delete it.

Security

We take reasonable steps to protect what we store. The messaging tables are locked so the public database interface cannot read them. Incoming texts are accepted only when the delivery signature checks out. No method is perfect. A message travels on the messaging network until it reaches our line, and after that we process it as this policy describes, including through service providers. Do not send secrets you cannot bear to have processed that way.

Contact

Ranklog
[RANKLOG MAILING ADDRESS]
[RANKLOG CONTACT EMAIL]