Privacy Policy

Last updated: 09 December 2025

The Daydreamverse Blog is a personal publishing project run by me, Aleks D. It is a simple, static website where I write about addiction, recovery, neurobiology, harm reduction, prevention, and rebuilding a life. This page explains what personal data is collected when you visit this site or interact with me, and how I handle it.

1. Who is responsible for this site?

The Daydreamverse Blog is created and maintained by Aleks Dubowski as a personal project, connected with my broader creative and AI studio, DeDynamics.

If you have questions about privacy on this site, you can contact me via the contact page.

2. What kind of data I collect

This site is intentionally minimal. I only collect the information that is necessary for basic functionality and communication:

  • Newsletter subscriptions: If you subscribe to the newsletter, you provide your email address and optionally your name. This data is used only to send you newsletter emails or important updates related to The Daydreamverse Blog.
  • Contact messages: If you contact me via a form or by email, I receive the information you choose to send (such as your name, email address, and message content).
  • Server and security logs: Like most websites, infrastructure providers may automatically collect technical information such as IP address, browser type, device information, and timestamps for security, performance, and abuse prevention.

3. How I use your data

I use the data mentioned above only for the following purposes:

  • To send you emails you explicitly subscribed to (newsletter or similar updates).
  • To reply to messages you send through contact forms or directly by email.
  • To keep the site secure and running reliably (for example, monitoring abuse or errors).

I do not sell your personal data and I do not use it for advertising profiling.

4. Services and processors I rely on

The Daydreamverse Blog is hosted and delivered via third-party infrastructure. This means some personal data is technically processed by these providers:

  • Cloudflare: Used for hosting, DNS, and content delivery. They may process technical data such as IP addresses and request metadata for security and performance.
  • Resend: Used to send newsletter emails. When you subscribe, your email address (and optional name) is sent securely to Resend in order to deliver the email.
  • Email provider: Incoming messages you send may be stored in my email inbox so I can read and reply to them.

I choose tools that offer strong security and a clear approach to privacy, and I only send them the minimum data necessary for their function.

5. Cookies and analytics

At this stage, The Daydreamverse Blog does not intentionally use invasive tracking cookies or third-party marketing trackers. If I decide to add privacy-respecting analytics in the future, this policy will be updated to reflect that change.

6. How long data is kept

I keep your data only for as long as it is reasonably necessary for the purpose for which it was collected:

  • Newsletter data is stored while you remain subscribed.
  • Contact messages are kept as long as needed to handle the conversation or for legitimate record-keeping.
  • Technical logs are kept according to the retention policies of the infrastructure providers and for security/debugging purposes.

7. Your choices and rights

You can unsubscribe from newsletter emails at any time using the link in the email (when available) or by contacting me directly and asking to be removed.

If you want to know what personal data I have about you in the context of this project, or if you want it corrected or deleted, you can reach out via the contact page and I will do my best to respond within a reasonable time.

8. Changes to this policy

As The Daydreamverse Blog and its infrastructure evolve, this privacy policy may change. When that happens, I will update the "Last updated" date at the top of this page and, where appropriate, mention it in a blog post or newsletter.

9. Not legal advice

This privacy policy is written in clear, human language and reflects how I actually run this project. It is not a formal legal document and does not replace professional legal advice.