Privacy Policy.

1. Who we are

TechReaderDaily ("we", "us", "the site") publishes daily technology journalism at www.techreaderdaily.com. We are the data controller for the personal data described in this policy. For data-protection inquiries, use the contact form at /contact.

2. What we collect

Information you give us directly

• Newsletter subscriptions: the email address you submit, the source page, and the timestamp.
• Contact form submissions: your name, email, optional subject, your message, and the IP address the submission came from.
• Account credentials (staff only): username and an argon2id password hash. We do not store plaintext passwords.

Information collected automatically

• View counters: when you load an article, we record the slug, a one-way SHA-256 hash of your IP scoped to that calendar day, and the referring host (e.g. google.com). The IP hash exists only to deduplicate within a 24-hour window; we cannot reverse it to identify you.
• Server access logs: the Cloud Run platform records standard HTTP access information (timestamp, path, status, user-agent, IP) for operational and abuse-prevention purposes. Logs are retained for 30 days.
• Cookies: see Cookies and similar technologies.

What we do NOT collect

• We do not require an account to read the site.
• We do not run our own behavioural advertising trackers.
• We do not store credit card information.
• We do not sell personal data to anyone, for any purpose, ever.

3. Why we collect it

• To deliver the service — serving articles, managing newsletter subscriptions, responding to messages you send via the contact form.
• To understand traffic patterns — anonymous, deduplicated view counters and referring-host classification, used to choose what surfaces on the homepage and to spot abuse.
• To run advertising — see Advertising partners.
• To comply with legal obligations — for example responding to lawful requests.

Our legal bases (where the EU GDPR applies) are: contract (delivering content you requested), legitimate interest (anonymous analytics and abuse prevention), consent (newsletter sign-up and non-essential cookies), and legal obligation (responses to lawful requests).

4. Cookies and similar technologies

We use a small number of cookies. The complete list, what each cookie does, and how to opt out of optional ones live on our Cookie preferences page. In summary:

• Essential: a session cookie (trd_session) used only when staff sign in to the admin area.
• Advertising: cookies set by Google AdSense for ad delivery and measurement. See the next section.

We do not run a separate analytics product (no Google Analytics, no Plausible, no Matomo). The view counter described above is server-side and uses no cookies.

5. Advertising partners

We display advertising via Google AdSense. Google and its partners may set or read cookies on your device to serve and measure ads, including personalised ads where you have consented (or non-personalised ads where applicable law requires).

• Google's privacy practices for advertising: policies.google.com/technologies/ads.
• You can opt out of personalised advertising in your Google account at myadcenter.google.com.
• For aggregate ad-industry opt-outs: aboutads.info/choices (US) or youronlinechoices.eu (EU).

Where we are required to obtain consent for personalised ads (e.g. in the EEA, UK, or Switzerland), we will surface a consent banner before personalised-ad cookies are set. Until consent is given, only non-personalised ads are served.

6. Who we share data with

We share data only with the small set of service providers that make the site work. Each is bound by their own privacy terms.

• Google Cloud (Firestore, Cloud Run, Cloud Build, Cloud Scheduler, Secret Manager): hosting and storage. Data is processed in Google's US data centres.
• Google AdSense: ad serving (see above).
• Bing / IndexNow: we ping search engines with new article URLs so they can crawl them; only the article URLs and our IndexNow key are sent.

We do not sell, rent, or trade personal data. We may disclose data if required by law, a binding court order, or to protect against fraud, abuse, or security threats to the service.

7. How long we keep it

• Newsletter subscriptions: until you unsubscribe.
• Contact messages: up to 24 months after the conversation closes.
• View counters: the deduplication row contains only a daily IP hash and rolls forward; aggregate counts are retained indefinitely for traffic statistics.
• Access logs: 30 days.

8. Your rights

Depending on where you live, you may have the right to access, correct, delete, port, or object to processing of your personal data. To exercise any of these rights, use the contact form. We respond within 30 days. We may need to verify your identity before fulfilling certain requests.

If you are in the EEA, the UK, or Switzerland, you also have the right to lodge a complaint with your local data-protection authority.

9. Children

The site is not directed at children under 13, and we do not knowingly collect personal data from children. If you believe a child has submitted personal data to us, contact us and we will delete it.

10. Changes to this policy

When we make material changes, we update the effective date at the top of this page and post a brief note on the homepage. The previous text is preserved in our public Git history.

11. Contact

For any privacy-related question, including data-access or deletion requests, write to us via /contact. Messages land directly in the newsroom inbox and are read by a human.