What we collect,
and what we refuse to

The website

• Analytics: Ahrefs Web Analytics, which uses no cookies. Like any request, its script sends Ahrefs your network address. Ahrefs says it uses the address to find your location, no closer than your city, and to count a day's unique visitors by hashing it with your browser's user agent and a salt it deletes every 24 hours, and that it never stores the address itself. Ahrefs does store the user agent (which names your browser, operating system and device) and your language settings. The script is never loaded on the parent link page. We deliberately do not use Google Analytics. We see page counts, not people.
• Newsletter: if you subscribe, your email address goes to Beehiiv, our newsletter provider, and is used to send you the newsletter. Nothing else is done with it, and every email has an unsubscribe link that works immediately. If you never subscribe, the newsletter never has your email. Beehiiv also records which of our signup forms you used. Except on a live link page, it also records the page you signed up on and, unless you opened a live link page earlier in the same visit, the first page of ours you opened that visit, the site or app that linked you to us (its name only, for example google.com, never the full address or what you searched) and, if you arrived on a link tagged for one of our social channels, which network and which kind of post. A wrestler's profile is recorded as a profile, never by name. When you subscribe, the form uses Vercel BotID, from our host, to tell people from bots: your browser solves a small challenge without showing you anything, sends the answer with your sign-up, and Vercel checks that the answer is genuine. We use only this basic check, not Vercel's deeper analysis of browser signals, and we never use it to identify you. The form also turns away sign-ups from Tor exit relays and more than 20 from one network address in an hour, and tells you when it does.
• Adding a club: the add a club form sends us the club's details and your note. Your own email is optional. If you give it, we use it only to ask you about that club; we never publish it and never subscribe it to anything. Ask and we delete it sooner; otherwise the email is deleted within 12 months of submission.
• Affiliate links: some gear links go to Amazon with our affiliate tag. Amazon knows you clicked, the way it does for any link to Amazon; we see aggregate commissions, never who bought what.
• No ads, no ad trackers, no data sales. Ever.

The iOS app

• What you enter stays on your device, with exceptions you control: the live parent link and, from app 1.4.0, the answers you choose to send to the club and a creator code you add, and, from app 1.4.1, notes and votes you send to the club (below). Your assessment, weigh-ins, plan settings, meets, matches, starred colleges, and cycle dates are stored locally on your phone. The first-launch setup (your role, name, state, grade, team, and weight class) and an optional photo stay on the phone too and are never sent to us, except what a live parent link shows if you create one and, from app 1.4.0, the few answers Send carries if you tap it (below). From app 1.4.0, when an adult picks a state at setup, the app also asks our server for that state's club list, a plain request for public data (below). Delete the app and they are gone. From app 1.4.0, two small items are kept in your phone's Keychain, which iOS can keep after an app is deleted, so a reinstall finds them: your age range, the month it next changes and what Apple said about age laws (never your birth date), and, if you sent answers, the random key to them.
• Setup, your season plan and your week (app 1.4.1 and later). From app 1.4.1, setup asks a few more questions, and each one has an answer like Not sure yet. Everyone picks a role: wrestler, coach, parent or fan. A wrestler is then asked her grade, state, style, weight class, next meet, goals, and whether she wants weight tracking. A coach, parent or fan is asked their level, state and goals. Your name, how you found us and a creator code stay optional. Your grade, style, weight class, next meet and your weight tracking answer stay on your phone and are never sent to us. Your role, level, state, goals and how you found us stay on your phone too, unless you tap Send (below). Once you have sent them, tapping Start at the end of setup sends any change you made to them, as a change in About you does (below). None of your setup answers is given to RevenueCat. These also stay only on your phone and are never sent to us:
  • Your season plan, which the app works out on your phone each time you open it;
  • This week on Today: the list you tick off, and its count of what you did this week;
  • the reminders you turn on, which your phone sets for itself: the app has no push service, so nothing about them goes to us or to anyone else;
  • if you picked your club from our directory, its name (Send carries only the club's id, below);
  • your athlete card for the recruiting one-pager: your school, grad year, height, GPA, NCAA ID, film links, and the names, emails and phone numbers you add.
  The one-pager, its sample and every PDF are made on your phone. They leave it only if you share them yourself, from your phone's share sheet. Your next meet is one of your meets, so a live parent link shows it by name and date if you turn one on (below).
• Live parent links (app 1.2). This feature sends personal information from the app only if you turn it on. The app can then keep one web page current for a parent. What that page holds, and therefore what our server holds: the same words as the parent digest PDF (whether you are on plan for your target class, the class you are legal at for your next meet, your record, any safety flags in words, the fueling rule, your meets by name and date) and your first name if you entered one (app versions before 1.4.0 also send your last name). Never your daily weights, body fat percent, cycle dates, venues, or weigh-in times. The link is turned off from the app or by the parent on the page; the row is deleted then, a link the app has not refreshed for 30 days is deleted automatically, and so is a link no parent opened within 14 days (database backups keep deleted rows for up to 7 days). About the parent, besides the network address every request carries (used for the abuse limits and kept in our host's logs, below), we record only when the page was last opened and how many times. The first device that opens a link is the only one that can read it. Creating a link requires an athlete aged 13 or older.
• Cycle data especially. Period start dates never leave the device and are never attached to any analytics. This is a design commitment, not a settings toggle.
• No accounts. The app has no sign-up, login or password, and you never need an email to use it. A live link is a random key on your phone, not an identity, and so is the key to the answers you send (below).
• Purchases and RevenueCat. Membership is sold and paid for through Apple. RevenueCat, our subscription service, which handles this data for us, keeps the record of it. The app gives RevenueCat no name, no email and no account. From app 1.4.0, if you add a creator code, the app also gives RevenueCat that code (below). RevenueCat knows the install by a random id it makes for it (an anonymous id) and by Apple's identifier for vendor (IDFV), an id iOS gives one app maker's apps on one device, which RevenueCat's code sends with its requests along with the device model, the phone's languages and its App Store country. It also holds the purchase history Apple reports (which plan, and when it started, renewed or ended), with the App Store's ids for each purchase, among them the original transaction id, which stays the same across a subscription's renewals. The app checks with RevenueCat at launch whether Membership is active, so RevenueCat holds these even if you never buy, and like any server it sees the network address each request comes from. We never see your payment details; Apple keeps those.
• Creator codes (app 1.4.0 and later). From app 1.4.0, if the app knows you are 18 or older (below) and you use the US App Store, you may add a code a creator gave you, at setup or in About you. In 1.4.0 and later, anyone under 18, or whose age the app does not know, never sees the field. A code is optional and changes nothing about your price or what you get, and nothing is sent until you tap to add it. When you tap, our server checks the code against our list and answers only whether it is live; the check stores nothing except the abuse count described below. If it is live, the app keeps it on your phone and sets it at RevenueCat as a customer attribute named wwc_code, so that if you buy a Membership, we can pay the creator who gave it a share of what Apple pays us. If you also send us your answers, the code goes with them (below). The code carries nothing about you. Remove code, or Delete my data, clears it on your phone and at RevenueCat and cuts the link between you and that creator (below), so your later payments credit no one. To do that, the app sends our server RevenueCat's anonymous id for your install. We use it once to cut the link and clear the code, and never store it. A code saved in an earlier version stays on your phone and is never sent unless you choose to use it when the app asks. In versions before 1.4.0, a code is stored only on your phone and never sent.
• Sending your answers to the club (app 1.4.0 and later). From app 1.4.0, the app can send a few of your setup answers to our server, and only if you tap Send. On the Send screen, Keep on this phone sits beside it, the same size, and every question can be skipped; you can send later, or never. Send is offered only on the US App Store, and only to a user 18 or older, or 13 to 17 on iOS 26.2 or later when Apple tells the app that no app store age law covers the account, and not to an adult whose age is only self-declared on a covered account (below). It is never offered to anyone under 13, or whose age the app does not know. A teen can show a parent exactly what Send carries before sending. Send carries only:
  • from anyone who sends: how you are involved (wrestler, coach, parent or fan), your level (youth, high school, college or open), your state, up to three goals from our list, and how you found us;
  • from an adult only: your club, picked from our directory (or that it is not listed), and a creator code if you added one (above);
  • with every send: the random key to your answers (we keep only its hash), the app version, whether you are 13 to 17 or 18 or older (never your age or birth date), and RevenueCat's anonymous id for your install (above);
  • with the first send: Apple's id for this app on your Apple Account (the app transaction id), if the app can read it.
  Send never carries your name, photo, birth date, grade, school or team name, weight class, style, weigh-ins, assessment, period log, email or phone. Our server keeps your answers under a random key that stays in your phone's Keychain (the server stores only a one-way hash of the key) and a short reference shown in Profile, Your data. It keeps RevenueCat's anonymous id only encrypted and as a keyed one-way scramble (an HMAC), used only to clear a creator code at RevenueCat and cut any creator credit link when your answers are deleted, and to keep that working if RevenueCat moves your purchases to another install. It keeps Apple's app transaction id only as a keyed one-way scramble, used only to find your answers if a parent withdraws consent through Apple (below). When you change your answers in About you or, from app 1.4.1, in setup (when you tap Start), the app sends the new set, and about once a week, when you open the app, it sends them again so we know they are still in use; when you turn 18, the next send says so. If your answers carry a creator code, we also record once that the code was entered with them: the code and the week, linked to your answers until they are deleted.
• How the app knows your age (app 1.4.0 and later). On iOS 26 and later the app asks Apple for your age range; Apple shares a range, never your birth date, and on iOS 26.2 and later also says whether an app store age law covers the account. Otherwise the app asks your birth month and year once. Either way the app keeps only the range, the month it next changes and what Apple said about age laws, on your phone, and never sends them: our server is told only whether you are 13 to 17 or 18 or older, only with answers you send, and uses that only to apply the rules on this page (what each age may send).
• Deleting what you sent (app 1.4.0 and later). Profile, Your data shows what our server holds for your phone, with Delete my data. It deletes your answers from our server at once, clears your creator code at RevenueCat, and cuts the link between you and any creator (below). From app 1.4.1, it also deletes the notes and votes kept with your answers (below). You can also email us the reference shown there, and we delete them the same way. The app deletes them itself when you can no longer send: if its age answer goes down (for example, to under 13), if Apple tells it an app store age law now covers a teen's account, or if your phone leaves the US App Store. Answers not used for 400 days are deleted too (below). What stays after a delete: a deletion record (below); purchase events for a creator code, cut down to the code, the kind of event, the week and the plan (below); the records of what we paid creators, kept for up to 7 years with nothing that links them to you; notes and votes sent without your answers (app 1.4.1 and later), which nothing in our database links to you; RevenueCat's record of your purchases (below); copies in our database backups for up to 7 days; and your setup answers and the rest of what is on your phone (there, a delete clears only the creator code, the Keychain key to your answers and the phone's copy of what was sent). Membership billing is Apple's, so deleting your answers does not cancel it.
• Notes and votes for the club (app 1.4.1 and later). From app 1.4.1, the Club tab has Tell the club, a private note to us, and What should we build next?, a list we write that you can vote on. Both are optional, and nothing of yours is sent until you tap to send a note or to vote. A user under 18, or whose age the app does not know, or an adult whose age Apple has only from the adult's own say, can send one only where Apple tells the app that no app store age law covers the account, and anyone can read the list (below, App 1.4.1 and app store age laws). What each one carries:
  • if you have not sent your answers, in any country: a vote, which only adds one to that item's count, and a note made only of choices from our lists (what it is about and what fits), with the app version. Neither carries your name, a key, an account id of yours or words you type, so what we keep of it links it to no one, and we cannot tell who sent it;
  • if you sent your answers (above): your notes and votes go with the random key to your answers, and we keep them with your answers. You can take a vote back. A note sent this way also holds your role, your level and whether you are 13 to 17 or 18 or older, copied from your answers. An adult may also type up to 1,000 characters in a note. In app 1.4.1, a note from a user 13 to 17 has no typed words, only choices. Before we store typed words, we try to remove email addresses, phone numbers, @handles and web addresses. An adult who added a creator code can also send a note about the creator program, and we keep that code with it.
  Only we read the notes. We cannot reply in the app, and we never show a note to anyone else. A vote shows only as part of an item's total. Delete my data deletes the notes and votes kept with your answers, and so does every other way your answers are deleted (above). Each note and vote, like every request, carries your phone's network address (used for the abuse limits and kept in our host's logs, below).
• Reading the app's content. Events, clubs, camps, wrestlers, news, rankings and, from app 1.4.1, the list you can vote on come from our server as plain requests for public data, the same ones a web browser would make. Like every request on the internet, each one carries your phone's network address (IP address), which our host records in its request logs along with what was requested.

Notices about purchases

This section covers two kinds of automatic notice: RevenueCat's about Membership, and Apple's about the app. RevenueCat's purchase events reach our server today. Apple's App Store notices reach it today too, passed on by RevenueCat, under the rules below. Neither comes from your phone, and neither carries your name, email or payment details.

• RevenueCat's purchase events. RevenueCat tells our server when a Membership starts, renews, turns from a free trial into a paid one, is cancelled, expires, is refunded, or moves to another install when purchases are restored. We keep an event only when the subscriber carries a creator code, or has a credit from one (below). Only app 1.4.0 and later send a code to RevenueCat, and only for an adult. When we do keep one, it holds only the code, the kind of event, the week it happened (never the day), whether the plan is monthly or annual, whether it was a test purchase, a link to the creator credit it counts toward, and two keyed one-way scrambles (HMACs): one of RevenueCat's id for the event, so a repeat is not counted twice, and one of RevenueCat's anonymous id for the subscriber, so a renewal is credited to the code on the first payment. We discard the price, currency, country, store and transaction ids (the original transaction id among them): what a creator earns comes from a fixed table of what Apple pays us for each plan, never from the event. Every other event is answered and dropped. For some events we cannot credit (for example a code that is not live, or a Family Sharing purchase), and when Remove code cannot clear the code at RevenueCat, we add one to a weekly count of the reason, which holds no code and no scramble.
• Creator credits. When a member who carries a live creator code makes a first purchase, we open a credit: a random id that stands for that membership and names no one, with the creator, the code, the week it opened, and the rate and number of months the creator is paid on. Each payment adds a row holding what Apple pays us for that plan (from our fixed table), the creator's share, the Mondays that name the paid period and the day its refund window closes, and whether it has been paid out. A refund adds a row that reverses the payment. The credit holds no scramble of your RevenueCat id. The only link from you to it is on the purchase events above, and it is cut when you tap Remove code or Delete my data (app 1.4.0 and later), and for each event when its subscriber scramble is removed. Once the link is cut, the credit earns nothing more, and it keeps no id of yours: only the creator, the code, a week and the amounts. We never tell a creator who you are: a creator sees only dollar sums that come from 5 or more members, apart from the payments made when a creator stops working with us, which can come from fewer.
• Apple's App Store notices about the app. Apple sends them to RevenueCat, which passes them on to our server as Apple wrote them. They carry Apple's ids for the app and its purchases, among them the app transaction id and the original transaction id. We check Apple's signature on each one and store nothing from them. The one we act on is a parent withdrawing consent through Apple for a child's use of the app, where the law gives parents that step. If Apple tells us that a parent has withdrawn consent, we delete whatever our server holds that is tied to that Apple Account, from every device it was used on, as of Apple's notice. From app 1.4.0, that is the answers sent from the app on that account, found by the scramble of the app transaction id they carry (above). From app 1.4.1, the notes and votes kept with those answers are deleted with them. Answers sent when the app could not read that id are not tied to the Apple Account, and a parent can have them deleted by emailing us the reference shown in Profile, Your data. The app offers a creator code only to a user it counts as 18 or older, and a parent's withdrawal is not how a code is cleared: Remove code or Delete my data clears it (above). Below iOS 26 the app goes by the birth year the user gives (below). A live parent link is not tied to the Apple Account: one the app can no longer refresh is deleted after 30 days, as always.

Children under 13

Nobody has to give us a name, an email or an account to use the site or the app, at any age. A child under 13 cannot create a live parent link, and the app asks a child for nothing else that leaves the phone: from app 1.4.0, it never offers Send or a creator code to a user under 13, or whose age it does not know. From app 1.4.1, a child can vote on our list or send a note made only of our fixed choices only where Apple tells the app that no app store age law covers the account (below); neither carries a name, a key, an account id of the child's or words the child types (above). Three technical identifiers still reach a server, because the app cannot run without them. The federal children's privacy rule (COPPA, 16 CFR 312.4(d)(3)) asks us to name them, say what they are used for, and say how we keep them from being used for anything else:

• The phone's network address (IP address). Used to deliver the app's and the site's content, and to protect the service from abuse: our server counts requests per address, stored only as a one-way hash of it with a time window and a number, so one address cannot flood a feature. Our host also records the address in the request logs it keeps to run the service and keep it secure, and on the website Ahrefs uses it for its visit counts, as described above.
• RevenueCat's anonymous id for the install. Used to sell and restore Membership and to tell the app whether Membership is active. RevenueCat's purchase events (above) also bring it to our server, which uses it, as a keyed one-way scramble, only to look for a creator credit for that Membership. No version of the app sends a code for a user under 18, so a child's install has no credit and nothing from its events is kept. The app itself sends it to our server only to clear a code (below).
• Apple's identifier for vendor (IDFV). RevenueCat's code sends it with the same requests. Used, like the anonymous id, only to sell and restore Membership and to check it; our server never receives it, and we never use it ourselves.

From a child's phone, our server can also get a vote or a note made only of our fixed choices (app 1.4.1 and later; above), and requests to delete, and nothing else. The requests to delete: if answers were sent from it before the app learned the user is under 13, or by an earlier install whose key is still in the phone's Keychain, the app sends that random key so our server deletes those answers; and if a creator code was added on it before then, the app clears the code at RevenueCat and sends RevenueCat's anonymous id to our server so the code is cleared and its link cut there too (above). Neither carries anything else.

We use these three only for those purposes. We never use them to contact anyone, to build a profile of anyone, or for advertising, or to prompt anyone to use the app more: the app has no ads and no ad trackers, and the abuse counts are never joined to anything else we hold. We share them only with the providers listed below, who handle them for us, and we never sell them. They are kept only for the times listed below. The one exception is the live parent link, which only a user 13 or older can turn on, and which sends a first name (app versions before 1.4.0 also send a last name) and the parent summary described above.

Neither the app nor the site lets a child make personal information publicly available. There are no public profiles, posts, comments or messages, and nothing a user enters is published by us. A live parent link is private: only a user 13 or older can create one, and only the first browser that opens it can read it. What someone sends through the add a club form is read only by us; a club is listed from its own public pages, never from the note or the email. From app 1.4.1, notes sent to the club are read only by us too, and a vote shows only as part of a total. Share cards and PDFs leave the phone only through the user's own share sheet.

On the website, the newsletter is for readers aged 13 and up, and the optional email on the add a club form is for people aged 13 and up too. If we learn that a child under 13 gave us an email, we delete it.

A parent can ask what we hold about their child, ask us to delete it, or tell us to stop: email the operator, Joe Spisak, at joe@spisak.co. For a purchase, include the order ID from Apple's receipt email (it is also in the App Store purchase history), so we can find the RevenueCat record and have it deleted; nothing else there identifies the child to us. Deleting the app stops all collection.

App 1.4.0 and app store age laws

Texas's app store law (Senate Bill 2420, section 121.053), and laws like it, ask an app maker to treat some updates as a significant change, which for a minor can need a parent's consent, through the app store, before the minor uses the changed part. Our written determination for app 1.4.0: the change is the new ways data leaves the phone, Send and creator codes (above), and in 1.4.0 no user the app counts as 13 to 17 can use either on an account Apple marks as covered, or where the app cannot tell. A user the app counts as 13 to 17 can send only when Apple tells the app that no such law covers the account, and never sees a code. An adult whose age Apple has only from the adult's own say, on a covered account, cannot send or add a code either. Their answers stay on their phone, as before. Below iOS 26, Apple gives the app no age signal, so the app goes by the birth month and year the user gives; a user who gives an adult birth year there is treated as an adult. Where Apple asks the app to tell an adult about a significant update, the app shows Apple's notice once, before that adult first sends answers or adds a code. This is our own written determination as the app's maker, not legal advice and not a ruling by a court or an agency; if the law, a court or Apple's rules require more, we will change the app and this page.

App 1.4.1 and app store age laws

Our written determination for app 1.4.1: the change is notes and votes sent to the club (above), a change in the kinds of data we receive (Texas Senate Bill 2420, section 121.053(b)(1); Louisiana R.S. 51:1771(17)(a)). In 1.4.1 a user the app counts as under 18, or whose age it does not know, can send a note or a vote only when Apple tells the app that no app store age law covers the account: not on an account Apple marks as covered, not where the app cannot tell, and not below iOS 26.2, where Apple cannot say. An adult whose age Apple has only from the adult's own say is treated the same way. Where the app does not let a user send, it says why, and the user can still read the list and its counts. A note or vote sent without your answers carries no name, key or account id of yours, only, like every request, your phone's network address, handled as described above; one sent with your answers is kept with them and deleted with them (above). Where Apple asks the app to tell an adult about a significant update, the app shows Apple's notice, naming notes and votes, once, before that adult's first note or vote, even if the adult confirmed the 1.4.0 notice; until the adult confirms it, no note or vote is sent. Nothing else new in 1.4.1 changes the kinds of data we receive: the rest stays on the phone, and setup sends a change to answers you already sent, as About you already does (above). This is our own written determination as the app's maker, not legal advice and not a ruling by a court or an agency; if the law, a court or Apple's rules require more, we will change the app and this page.

How long we keep things

Each item below says what is kept, why, and when it is deleted. Deleting means removing it from the live database or service; a deleted database row can remain in our database backups for up to 7 days.

• Our host's request logs (the network address, the time, and what was requested). Kept by Vercel, our host, to run the site and the app and keep them secure. Deleted after 30 days.
• Abuse counts (a one-way hash of the network address, a time window and a number). Kept to stop one address from flooding a feature. Deleted by a nightly sweep once more than 1 day old.
• A live parent link (the words and the name above). Kept to show a parent what the athlete chose to share. Deleted when it is turned off, after 30 days without a refresh from the app, or after 14 days if no parent ever opened it.
• Answers sent from the app (app 1.4.0 and later; above), with the hash of their key, their reference, the two scrambles and the encrypted RevenueCat id. Kept so the app can restore them after a reinstall, and so we learn who the club is and what to build for it. Deleted at once when you delete them or the app can no longer send, and otherwise deleted by a nightly sweep after 400 days without use.
• Notes sent to the club (app 1.4.1 and later; above). Kept so we can read them and fix or build what they ask for. The words typed in a note are deleted by a nightly sweep after 365 days, unless we hold them. We hold a note's words when we mark it as telling us someone may be in danger, and our admin page lets us hold any note's words without giving a reason. Held words are deleted when the note is, or, once we release the hold, by the nightly sweep on the clock above. Every note is deleted after 24 months, or sooner, with your answers, if it was sent with them.
• Votes (app 1.4.1 and later; above). A vote sent with your answers is kept until you take it back or your answers are deleted. In our database, an anonymous vote is only a number on the item, with nothing about who cast it.
• The RevenueCat record (the anonymous id, the IDFV and device details its code sends, the purchase history with the App Store's ids for each purchase, and from app 1.4.0 any creator code you added, which Remove code or Delete my data clears). Kept by RevenueCat, as our processor, to sell, restore and check Membership, for as long as we sell Membership; it has no fixed end date today. To have it deleted, email us the order ID from Apple's receipt email and we have RevenueCat delete it. An install that never bought anything has no order ID and carries no name or email, so we have nothing to look its record up by; deleting the app means that record is never added to again. For an install that never bought anything we are setting a shorter deletion time, and this page will print it.
• Purchase events for a creator code (above). Kept to credit the creator whose code it is. The subscriber scramble is removed by a nightly sweep once 400 days have passed since the event's week, and the event is deleted after 3 years. Test purchases are deleted 30 days after their week. The weekly counts of events we could not credit are deleted after 3 years, and so is the record that a code was entered with sent answers (above), which loses its link to the answers when they are deleted.
• Creator credits and payments (above). Kept to pay creators and for our tax records. Once a credit's paid months and their refund window are over and every payment on it has been paid out, a nightly sweep adds its payments to the creator's monthly total, which names no member, and deletes the credit and its payment rows. Anything left, and every payout record, is deleted 7 years after its week, or after the day its payout was sent. Test purchases are deleted 30 days after their week.
• Deletion records (app 1.4.0 and later). When we delete the answers an app install sent (a live parent link is simply deleted), or the app asks us to delete answers that have not reached us yet, we keep only a one-way hash of that install's random key, so the deleted record is refused instead of quietly re-created. Deleted by a nightly sweep after 13 months. If clearing a creator code at RevenueCat is still pending, the record also holds RevenueCat's anonymous id, encrypted, until the clear succeeds; if it keeps failing, the id is deleted after 7 days.
• Your email on a club submission. Kept only to ask you about that club. The club's details stay in our queue, but the email is deleted within 12 months of submission, by a nightly sweep, or sooner if you ask.
• A newsletter subscription. Kept by Beehiiv to send the newsletter. When you unsubscribe, the mailing stops at once, and Beehiiv keeps the address marked as unsubscribed for as long as we publish the newsletter, so it is never mailed again and no one else can sign it back up. Ask us and we will have Beehiiv delete it.

Who handles data for us

• Vercel hosts the website and our server, keeps the request logs, and runs the BotID check on newsletter sign-ups.
• Supabase runs our database: live parent links, abuse counts, club submissions, the answers, notes and votes sent from the app, and the purchase events and creator credits above.
• RevenueCat is our subscription service for Membership and handles its purchase records for us. We have turned on none of RevenueCat's third-party integrations or scheduled data exports, which would send those records on to other companies; it sends them for us only to our own server (above).
• Beehiiv sends the newsletter.
• Ahrefs counts the website's visits (above).
• Apple distributes the app and sells Membership, tells the app your age range on iOS 26 and later, and sends us its App Store notices through RevenueCat (above); what Apple collects is covered by Apple's own privacy policy.

How we protect it

Our server stores the keys to live links and to the answers you send only as one-way hashes, RevenueCat's anonymous id only encrypted or as a keyed one-way scramble, and Apple's app transaction id only as a keyed one-way scramble. It reaches the database over an encrypted connection, as a database role granted access only to this site's tables, and it never writes the contents of a request, a key or a token to its logs. We keep a written information security program and review it at least once a year; email us for a copy.

More about who runs this and how it is sourced: the about page.