Privacy policy

Effective and last updated: November 6, 2026

Who we are

Babynamed is run by SADIK SEFA ASLAN, a private individual, not a company.

Address: Uğurmumcu mh. Nakkaş sk. Pınar sit. B blok. Daire 15 KARTAL/ISTANBUL, Türkiye

In this policy, “we” and “us” mean the person named above.

What this policy covers

This policy explains what Babynamed collects, why, how long we keep it, and who can see it. If you use Babynamed in Turkish, a separate notice written for Turkish data protection law is at /tr/gizlilik/.

What we collect and why

Using Babynamed as a guest

You can create or join a room without an account. As a guest, we do not ask for your email address. Our system creates an internal placeholder address for your guest record; it is not shown anywhere and is not used to contact you. Your guest access lives in a cookie in your browser (see “Cookies and browser storage”).

Rooms, votes and shared names

When you create or join a room, we store the display name you type (up to 24 characters), the room’s name preference (girl names or boy names) and the country the names come from. We store every vote you give, both the names you like and the names you skip. We also keep a list of the names you have voted on until you delete your account, so the same name does not come up again for you and your partner, even after the room closes. When you both like a name, it is added to each of your “My names” lists, together with your partner’s display name in that room and the room code. That list stays after the room closes. We do not ask whether you are the mother or the father.

Signing in with Google

Signing in is optional; you only need an account to buy credits. If you sign in with Google, we receive and store your name, your email address, whether Google has confirmed that address, and the web address of your profile picture. We do not display the picture anywhere. We also store your Google account ID and the sign-in tokens Google issues, until you delete your account. We do not ask Google for a refresh token, and we request nothing beyond your basic profile and email address. The sign-in page itself belongs to Google and is covered by Google’s own privacy policy. We use this information to run your account and to keep your names, reports and credits attached to it.

Signing in with X

If you sign in with X, we receive and store your name, your X account ID and the web address of your profile picture. We do not display the picture anywhere. If X gives us a confirmed email address for you, we receive and store that address too. If it does not, our system creates an internal placeholder address for your account; it is not shown on any screen you see and is not used to contact you. We also store the sign-in token X issues, until you delete your account. We do not ask X for a refresh token. We ask X only for the permissions we need to read your profile and email address; we do not use them to read your posts, and they do not let us post or read your direct messages. If an account with the same email address already exists, for example one you opened with Google, signing in with X takes you to that account. The sign-in page itself belongs to X and is covered by X’s own privacy policy. We use this information in the same way as for Google sign-in.

Full Analysis

Full Analysis is a paid report about one name. Before your first report we ask for your last name once; we write it to every name in your list and store it with every report. You can also type a name that is not in our list (up to 4 words); we store it like any other name. We keep each report — the name, your last name, meanings, origin, nicknames, the comment on how the name sounds with your last name, and the result of the domain and username checks — until you delete your account. Failed attempts are also kept with the name and last name until you delete your account.

The part of a report that depends only on the first name (meaning, origin and nicknames) is stored indefinitely, without any link to you or your last name, and is shown to other people who analyze the same name. This includes names you typed yourself, so do not type a name you want to keep private. Where the name and your last name go during the analysis is explained under “Full Analysis: where your name goes”.

Credits and purchases

Credits are sold by Lemon Squeezy, not by us; see our Purchase terms. When you open the payment page, we send Lemon Squeezy the package you chose, your Babynamed user ID and the page to return you to; we do not send your name or email address. Your card details do not reach us. Lemon Squeezy’s payment notification to our server carries its order details, including your name and email address, but our server does not use, log or store them. Our server uses only the order number, your Babynamed user ID, the package, the amount, the currency and whether it was a test order. It saves these as your purchase record, with the number of credits, whether the order was refunded and the time the notification arrived. Lemon Squeezy also makes your name, email address, city, region and country visible to us in its seller account; our application does not store them. Every day, our server also reads Lemon Squeezy’s recent orders, going back at least 14 days, to check that each payment added its credits and each refund was processed. That list carries buyers’ names and email addresses, but our server does not use, log or store them. From each order it uses only the number, status, refund amount, package, whether it was a test order and the dates; it saves nothing from the list in our database. We keep the purchase records and your credit balance until you delete your account.

Emails with us

If you email support@babynamed.com, Cloudflare’s email routing passes your message to our Gmail mailbox in real time. Cloudflare says it does not read, queue or store the emails themselves, but it records each message’s sender, recipient and subject line; its documentation says this routing data is retained for 31 days. Gmail is a Google service, and Google handles the mail in our mailbox under its own terms and privacy policy (Google LLC, United States). We email you only to reply to a message from you, or to notify you of a security breach if we have your address; Babynamed sends no newsletters or notifications on its own. Our replies go out through Brevo (Brevo SAS, France), an email delivery service that processes them for us. Brevo keeps a record of each email we send — the date and time, the recipient and the subject — and it may record whether the email was delivered, opened or a link in it was clicked, with the time and IP address. We turn off Brevo’s option to keep a preview of each email we send, but Brevo’s terms say it stores messages sent through its service on our behalf, so a copy may remain with Brevo under those terms. Brevo stores the data mainly in France and Belgium; other Brevo companies in Germany, the United States and India, and some of its US service providers, may access it. We delete conversations in our mailbox within two years after the last message, and Brevo’s sending records are deleted automatically after 12 months. If you write to us by post, we keep your letter, and any scanned copy, for at most two years after we answer, then destroy them. We keep this correspondence for that long so that we can show what we answered and when if there is a dispute or a complaint to an authority.

Technical data: IP address and logs

Your IP address reaches us through Cloudflare, which carries all traffic to our site. We use it only in the server’s memory to limit abuse, for example 20 invite-code attempts per minute or 60 new guests per hour from one address. We do not write it to our database or to our application log. Memory entries are not wiped the moment a limit’s time window ends; they can stay until the server restarts or the entry buffer (5,000 per limit) fills up.

Our application log records errors and warnings, plus one technical line for each AI call. It does not record your IP address, the pages you request, your name or your email address; in rare error cases, a line from our sign-in software may include a random user ID. A warning about a payment that needs checking may include the order number. For each AI call we log technical measurements such as duration, model and token counts, without the name being analyzed. The server software in front of our application (Caddy and the Cloudflare tunnel) may include request details in its error lines. All of these lines go to Fly.io’s log system, which Fly.io currently keeps for about seven days. Fly.io may use its own support tools, including AI-based ones, on those log lines. Cloudflare keeps its own records of traffic through its network for a period consistent with its business purposes, or as long as it needs them to meet its legal obligations; it does not publish a fixed period.

What we do not collect

We do not ask for or store health information, pregnancy information, due dates, or whether you are the mother or the father. We use the room’s girl or boy names preference only to filter the name list. Babynamed is not a health or pregnancy app and gives no medical advice. We do not ask for your age or date of birth. We do not use analytics, advertising or tracking cookies, and our pages load no outside scripts, fonts or pixels. Babynamed sends no newsletters or notifications; we email you only to reply to you, or to notify you of a security breach. We do not sell your data, and we do not share it for advertising. We do not use your data to train AI models, and Anthropic does not use it to train theirs (see below).

What your partner sees

Your partner sees the display name you typed for the room, the names you both liked, whether you have finished the round, whether you have asked for a new round, and — after finishing their own round — how many names you have voted on. Your partner does not see your individual votes, the names you skipped, your email address, your last name, your reports or your credits. Room members can also see each other’s random user ID; it contains no personal details. Your partner’s “My names” list keeps your display name next to each shared name, and that entry stays even if you delete your account, because it is part of their record.

Invite links and codes

A room has a six-character invite code and an invite link that contains it. Anyone who has the code or the link can open the invite page without signing in and see the display name of the person who created the room, the room’s name preference (girl or boy names) and whether the room is full. Treat the link like a key: share it only with your partner. A room holds two people; once your partner has joined, nobody else can join. The link’s preview in messaging apps is the same for everyone and does not include your name.

Shared report links

Your reports are private to you unless you share one. If you tap “Share report” and send the link, anyone who has it can open the full report without signing in. They will see the name, your last name, the comment on the name with your last name, and the domain and usernames derived from your name and last name. They will not see your partner’s name or the date you both liked the name.

The link is practically impossible to guess: it is a random 128-bit code. The page is marked “noindex” for search engines and is not in our sitemap, but anyone who has the link can forward it, copy it or screenshot it. The link stays open until you tap “Stop sharing” under the report or delete your account; it has no time limit. After “Stop sharing”, the old link no longer opens; if you share again, a new link is created. We keep the closed link’s code and closing time for about 30 days (and in backups until they are deleted), so we can close it again if we ever restore a backup. The preview card that messaging apps show contains only the first name; we ask apps to keep it for no more than a day, but some may keep it longer, including after you stop sharing.

Full Analysis: where your name goes

Anthropic (Claude)

When you start a Full Analysis, we send the name and your last name (each cut to 120 characters) to Anthropic, which runs the Claude AI model that writes the report. Anthropic processes this data for us as our service provider. For the meaning and origin sections, we send only the first name and our short note on its meaning and origin, plus, for the meaning section, any entry in our slang list that is spelled the same as the name; your last name is not included in those calls. For the origin section, Claude may run at most one web search per request, limited to wikipedia.org and wiktionary.org; Claude writes the search query itself, and its input contains only the first name. Anthropic runs these searches, and it may use search subprocessors to do so.

We do not send Anthropic your display name, your partner’s name, your email address, your user ID, your room code or your votes. Under Anthropic’s commercial terms, this data is not used to train Anthropic’s models. Anthropic deletes it within 30 days, unless its automated systems flag it for a usage-policy review (then up to two years) or the law requires longer. Anthropic may also keep safety classification scores about requests for up to seven years. Anthropic stores this data in the United States, but processing may take place in other countries. If you delete your account while an analysis is running, it stops, and no new request is sent to Anthropic, Verisign, GitHub or X.

Verisign, GitHub and X

To show whether the .com domain and usernames based on your name are taken, our server joins your first name and last name into one plain-letter string (for example, aysegundogdu). It asks Verisign’s public .com registration service (RDAP) about that .com domain, GitHub’s public API about that username, and X’s API about that username. These requests use our server’s own keys, not anything of yours, and they go from our server, so these companies do not see your IP address. Verisign, GitHub and X handle the string under their own terms and privacy policies. From their answers we keep only the status — registered or not, in use or not, or “couldn’t check”; we do not store any other person’s account details. We cache definite answers (not “couldn’t check”) for up to about 48 hours, without recording who asked, so the same string is not queried again within a day.

Service providers

These are the outside services that handle your data, what they do, and where.

Fly.io (United States, Virginia) hosts our application and database and processes this data for us. It currently keeps our server logs for about seven days and a snapshot of our disk for 14 days.

Cloudflare delivers all traffic to our site, protects it from attacks, stores our backups, and routes email sent to support@babynamed.com to our mailbox. To do this, it processes your IP address and request data, and it also uses data derived from traffic on its network for its own security and service-improvement purposes. Our nightly backups are encrypted on our server before upload. The continuous copy of our database is not encrypted by us; Cloudflare encrypts it when it is stored, using keys that Cloudflare manages. Both are stored in the United States.

Google provides the sign-in as a separate company under its own privacy policy. Your browser goes to Google’s sign-in page directly; we receive the profile details listed above. When you delete your account, we send Google one request to revoke the access you granted (see “Deleting your account”).

X provides the X sign-in as a separate company under its own privacy policy. Your browser goes to X’s sign-in page directly; we receive the profile details listed above. When you delete your account, we send X one request to revoke the access you granted (see “Deleting your account”).

Anthropic (United States) runs the AI model for Full Analysis as our service provider, as described above.

Verisign, GitHub and X receive the domain and username strings described above, under their own terms.

Lemon Squeezy sells the credits as merchant of record and handles payment, tax, invoices and refunds under its own privacy policy. We send it the package, your user ID and a return address; it sends us the order details listed above.

Google (Gmail) (Google LLC, United States) hosts the mailbox that receives your emails to us, under its own terms and privacy policy.

Brevo (Brevo SAS, France) sends our replies for us, as described under “Emails with us”; it stores the data mainly in France and Belgium, with possible access from Germany, the United States and India.

While it runs, our application sends data to no other outside service. We share data with public authorities only when the law requires it, and only to the extent it requires.

Cookies and browser storage

We set only strictly necessary cookies:

__Secure-better-auth.session_token keeps you signed in, whether you are a guest or signed in with Google or X. It is set only when you create a room, join a room or sign in with Google or X; browsing the information pages sets no cookie. It is HttpOnly, Secure and SameSite=Lax. It lasts 30 days, and each time you use the site (at most once an hour) it is renewed for another 30 days. As a guest, this cookie is your only way back to your room, so we keep it for the full 30 days.
__Secure-better-auth.state protects the Google and X sign-in flow and lasts 5 minutes.

Cloudflare may set a strictly necessary security cookie, such as cf_clearance, if it needs to check that a visitor is not a bot. Google’s and X’s sign-in pages may set their own cookies on their own domains.

In your browser’s local storage we keep your language choice (babynamed-dil) and which tips you have already seen (babynamed-ipucu-…). In session storage we keep, during a purchase, the name whose analysis you will return to and a list of the purchases already on your account when you started checkout (their order IDs and the time) (babyname-kredi-donus-isim, babyname-kredi-onceki-bakiye). Deleting your account clears the session storage entries; the language and tip entries stay until you clear this site’s data in your browser. We do not use analytics, advertising or tracking cookies.

How long we keep your data

Session: stops working after 30 days without use. An expired session record (a random code and dates, with no IP address or browser details) can stay until you delete your account; for guests, it is deleted with the guest record.
Guest data: if you do not open Babynamed for 30 days, or if you tap “Sign out”, your guest record is deleted within about one day, through the same path as account deletion. As a guest, “Sign out” has no way back.
Google and X account data: kept until you delete your account; it is not deleted for inactivity.
Rooms: a room is deleted after 90 days with no vote and no new round; a room with no votes at all, including one nobody joined, is deleted after 14 days. Shared names stay in your lists.
Votes: until the room is deleted or you delete your account.
List of names you have voted on: until you delete your account.
My names list, reports, purchase records and credits: until you delete your account.
Shared report links: until you tap “Stop sharing” or delete your account; after “Stop sharing”, the closed link’s code and closing time stay about 30 days longer.
Name-only part of reports: indefinitely, with no link to you.
Domain and username check cache: up to about 48 hours.
Backups: a continuous copy of our database in Cloudflare R2 is normally updated within seconds of each change and keeps earlier versions for up to about 30 days. A backup is also taken every night at 03:00 UTC; it is kept about 7 days on our server and up to about 30 days, encrypted, in Cloudflare R2. Before maintenance, we may take another backup, kept about 7 days on our server. Fly.io keeps a snapshot of our disk for 14 days. Backups are deleted on a rolling basis, so deleted data drops out of them within 30 days. If we ever restore a backup, we repeat the account deletions and link closures (“Stop sharing”) made after that backup was taken. If our live database itself were lost or damaged, we could miss a deletion or closure made after the copy we restore. This can also happen if we restore Fly.io’s disk snapshot, because that path does not repeat deletions or closures. If you then see your data or a closed link again, you can delete or close it again yourself, or email us.
Emails with us: conversations in our mailbox, up to two years after the last message; Brevo’s sending records, 12 months; Cloudflare’s email routing record, 31 days according to Cloudflare.
Letters sent to us by post: at most two years after we answer, then destroyed.
Server logs at Fly.io: currently about seven days.
Rate-limit entries in memory: until the server restarts or the buffer fills.
Deletion records: a daily count of what kinds of data we deleted and how, with nothing that shows whose data it was; kept for 3 years, then deleted.

Deleting your account

On the Account screen, “Delete my account and data” (as a guest, “Delete my data”) deletes your data right after you confirm; it cannot be undone. In one step this deletes your names list, your reports, your share links, your votes, your remaining credits, your purchase records, your sessions and your Google or X link, and your room closes. Your partner sees a one-time “room closed” note and keeps the shared names in their own list. We send Google, or X, one request to revoke the access you granted; deletion completes even if that request fails. You can also remove Babynamed’s access yourself in your Google Account settings, or on X’s connected apps page. A running analysis stops. Remaining credits are not refunded.

What stays after deletion:

your display name and the room code next to shared names in your partner’s list;
the “room closed” note shown to your partner, until they close it;
the name-only part of reports, which has no link to you;
anonymous usage counters;
the cached domain and username status, for up to about 48 hours;
backups, until they are deleted on their rolling schedule, within 30 days;
your random user ID and the time of deletion, without your name or email, for about 30 days (and in backups until they are deleted), so we can delete your account again if we ever restore a backup;
Lemon Squeezy’s own order records, which carry your Babynamed user ID;
the order numbers of purchases you made in the 14 days before deleting, which our daily payment check may write to our log, where they can stay for up to about three weeks after you delete;
the order number in any payment or refund notice for your account that arrives after you delete, which our server may write to our log, and for a payment our daily payment check may write again until the order is 14 days old; Fly.io keeps each log line about seven days, so the number can stay up to about three weeks after you delete;
data already sent to Anthropic, Verisign, GitHub and X, under their own retention rules;
the report preview card in messaging apps’ caches, which we ask them to keep for no more than a day (some may keep it longer).

There is no “download my data” button; email us for a copy.

Your rights

Wherever you live, you can ask us to tell you whether we hold data about you and what it is, send you a copy, correct it, delete it, or stop a particular use of it. Email support@babynamed.com. We answer within 30 days, free of charge. If you signed in with Google, write from the Google email address on your account so we can link the request to you. If you signed in with X, write from the email address X gave us; if X gave us none, we may not be able to link an emailed request to your account. As a guest, you have not given us an email address, so we may not be able to link an emailed request to your data; you can delete all of your guest data yourself from the Account screen at any time. If you signed in with Google or X, you can delete your Babynamed account yourself at any time, too. If you believe we have handled your data wrongly, you can complain to the data protection authority where you live. If you are in Türkiye, the Turkish notice at /tr/gizlilik/ explains your rights under KVKK and how to apply.

Age

Babynamed is for adults: you must be 18 or older to use it. We do not knowingly collect data from children under 13; if we learn that we have, we delete it. We do not ask for your age on any screen. The names you consider for a baby are not linked to any real child.

Where your data is stored

We are based in Türkiye. Our application and database run on Fly.io servers in the United States (Virginia). The continuous copy of our database and our encrypted nightly backups are stored with Cloudflare in the United States. Anthropic stores analysis data in the United States and may process it in other countries. Cloudflare, Google, Verisign, GitHub, X and Lemon Squeezy process the data described above in their own locations, under their own policies. So your data may be processed outside the country you live in. The countries where it is processed include the United States and Türkiye, where we are based. For emails with us, they also include France and Belgium, with possible access from Germany, the United States and India.

Security

All traffic to Babynamed uses HTTPS; the connection ends at Cloudflare, which forwards requests to our server through a private tunnel. The session cookie cannot be read by scripts and is sent only over HTTPS. Nightly backups are encrypted on our server before they are uploaded; the continuous copy of our database is encrypted by Cloudflare when stored. Card details are handled by Lemon Squeezy and do not reach us. We check that payment notifications really come from Lemon Squeezy before adding credits. No method of storage or transmission is completely secure, so we cannot promise absolute security. If a security breach affects your data, we will tell you as soon as we can — by email if we have your address, otherwise with a notice on this site.

We do not sell your personal data. You can still email support@babynamed.com to ask us not to sell it. We do not share it for targeted advertising, and our pages use no advertising or analytics pixels. Our pages load no third-party scripts, so no advertiser collects data about you through them. Cloudflare also handles traffic for many other websites that use its services, and it uses data derived from that traffic for its own purposes, such as security, under its own privacy policy. If you sign in with Google, Google may collect information about your activity on sites and apps that use its services. Depending on your Google Account settings, Google may link that activity to your personal information. We do not track you across other websites ourselves, so there is nothing on our side for a “Do Not Track” or Global Privacy Control signal to switch off; our site does not read these signals and does not change its behavior when they are present.

Changes to this policy

We will post changes on this page and update the date at the top. We do not send notification emails, so this page is where you will see changes. If a change would let us use data we already hold in a new way, we will not do that without asking you first.

Contact us

SADIK SEFA ASLAN
Uğurmumcu mh. Nakkaş sk. Pınar sit. B blok. Daire 15 KARTAL/ISTANBUL, Türkiye
support@babynamed.com