Privacy & cookies

Last updated: 25 August 2026

This notice explains what personal data AI Daddy collects, why, how long it is kept, who it is shared with, and the rights you have. Most of the site can be read with no account and no tracking.

Who is responsible

AI Daddy (aidaddy.tech) is the data controller. For any privacy request, use the contact page.

What we collect and why

• Account data (only if you create an account): your email address, and optionally a name and phone number you provide, plus your marketing-email choice. Used to sign you in and to give you access to member content. Lawful basis: performance of a contract (your account) and, for marketing email, your consent.
• Reading meter: for readers without an account we count how many articles you have opened in a rolling window to apply a free-reading limit. Your IP address is turned into a one-way salted hash and the raw IP is never stored. Lawful basis: our legitimate interest in offering a sustainable freemium model.
• Analytics & advertising (only with your consent): if you accept cookies, Google Analytics and Google AdSense set cookies and receive usage data to measure traffic and fund the content. Nothing loads or is sent to Google until you accept. Lawful basis: consent.

Payments

A paid PDF guide is processed by a payment gateway (Razorpay) in a window it renders. Card, UPI, and bank details are entered there and never reach this site or its servers, and we never store or see your raw IP address on a purchase. What we store about a purchase: the email you gave at checkout, the product bought, the amount and currency, and the gateway's order and payment identifiers. That record is what makes the guide available to download from the account that signs in with the same email, and what a refund request is checked against; see the refunds and cancellations policy. Purchase records are kept as our financial record of the sale even after an account is deleted; the buyer email on a kept record is due to be anonymized automatically once that part of our deletion process is built, and until then can be anonymized sooner on request. The entitlement created by the purchase (your access to the guide) is kept until that same deletion process ships, at which point it is removed along with the account; until then it can also be removed sooner on request. Either request can be made using the contact page. Purchase and access records are not used for marketing and not shared beyond the gateway, which has its own privacy policy for the data it collects to process the payment. Lawful basis: performance of a contract (fulfilling your purchase) and our legal obligation to keep financial records.

When you download a PDF guide you have purchased, we record the email and product it was for and the time of the download, plus a one-way IP hash and a coarse browser family (never your raw IP address or full browser identifier). This is the evidence we rely on for the no-refund-once-downloaded rule in the refunds and cancellations policy. The stamped copy generated for you expires and is deleted within 2 days; downloading it again issues a fresh copy. Lawful basis: performance of a contract and our legitimate interest in preventing abuse of the refund policy.

In-app activity (signed-in accounts)

When you are signed in, the site records which chapters you open, so the maintainer can see what is read and when an account was last active. Each record holds your account identifier (which resolves to your email), the chapter path, and the time you opened it. Your sign-ins and sign-ups are recorded the same way (just the event and its time). It does not record your IP address, your browser, a device fingerprint, a referrer, or anything you do on a page beyond opening it. Signed-out reading is never recorded this way (that is the separate, anonymous reading meter described above), and this activity is never joined with it. Records are deleted after 180 days by an opportunistic cleanup. Lawful basis: our legitimate interest in understanding how the guide is used. Because the data is tied to your account it is personal data: you can request a copy or its deletion using the contact page. Activity older than 180 days is deleted automatically, and an erasure request removes it sooner.

Cookies

We use a small amount of local storage that is essential to run the site (for example, your sign-in session and your cookie choice). Non-essential analytics and advertising cookies load only after you accept them. You can withdraw consent at any time:

Change cookie preferences

How long we keep it

• Reading-meter hashes: deleted after about 35 days.
• In-app activity for signed-in accounts: deleted after 180 days.
• Account data: kept until you delete your account, which you can do from your account page.
• Purchase records (PDF guides): kept as our financial record of the sale even after account deletion, with the buyer email anonymized once our deletion process supports it (sooner on request). The entitlement created by a purchase is kept until that same process ships, or removed sooner on request.
• Download records (email, product, time of download, a one-way IP hash, and a coarse browser family): kept as the evidence behind the no-refund-once-downloaded rule for as long as the purchase record they relate to, and anonymized on the same plan as that purchase record.
• Analytics/advertising data: retained by Google per their policies.

Who we share it with, and where

We use processors to run the service. Account sign-in and the reading meter run on Amazon Web Services in India (the ap-south-1 region). Analytics and advertising, when you consent, are provided by Google LLC in the United States. Payments are processed by Razorpay Software Private Limited in India. These transfers rely on the providers' standard contractual clauses and equivalent safeguards. We do not sell your personal data.

Your rights

Subject to applicable law you can request access to your data, ask us to correct it (you can edit your profile on the account page), ask us to delete it (you can delete your account yourself from the same page), object to or restrict processing, withdraw consent, and lodge a complaint with your local data-protection authority. To make a request, use the contact page.

Changes

We may update this notice; material changes will be reflected in the date above.