Privacy Policy

Claim 50 free spins now!

Introduction

This privacy policy took effect on March 31, 2026. It describes data handling practices for the Retro tapes website, an independent informational project I run alone. I am Murray, a data enthusiast with network administration experience and interest in sequence logging. The site operates from my home office in New Zealand using basic automation scripts to scrape and archive my personal session data. No gambling services appear here. Expect factual details on what data enters the picture, how it gets processed, and your options.

retrotapes.nz serves up information without collecting much from visitors. Server logs capture basics for functionality. Emails you send provide contact details. I do not sell data or run ads. This document covers key areas like collection, use, storage, and rights. Questions go to [email protected].

Data I Collect

Collection stays minimal. Server access logs record IP addresses, timestamps, user agents (browser details), and requested pages. These help diagnose issues or spot unusual activity. No names, emails, or identifiers tie to individuals unless you provide them. For example, form submissions or email inquiries yield name, email, and message content.

Cookies store session info like preferences or login states if applicable, though logins do not exist here. Analytics tools do not track behavior across sites. My scripts focus on my own session sequences from network logs, unrelated to visitor data. Think packet captures or timing logs from personal tools, kept private.

If you comment on posts (future feature), display name, email, and comment text store temporarily. IP logs with comments for moderation. Images upload with metadata stripped. Overall, expect technical necessities only, no profiling.

How Data Gets Collected

Automatic methods dominate. Web server software logs every request passively. No active scanning occurs. HTTPS encrypts transmissions, so data in transit stays protected. Scripts run locally on my setup to parse personal archives, pulling timestamps, sequence IDs, and log entries from my devices.

Voluntary submissions happen via email or contact forms. Browser fingerprinting avoids deliberate use; standard headers suffice for logs. No SDKs or trackers embed in pages. JavaScript runs minimally, avoiding storage APIs. Collection aligns with site operation basics.

Third-party services like hosting providers log at their end, covered by their policies. I select NZ-based hosts respecting local laws. Data flows one-way into my controlled environment.

Reasons for Using Data

Logs diagnose errors, like failed page loads from bad IPs. Timestamps track site uptime. User agents inform compatibility fixes. Email responses handle inquiries directly. My session archives fuel personal research on logging patterns, improving my scripts.

No data fuels marketing or ads. Analysis stays aggregate; no individual tracking. Security reviews scan logs for threats. Retention policies clear old entries routinely. Use cases tie directly to maintenance and curiosity-driven logging.

Future expansions might add stats pages from anonymized aggregates, always opt-out friendly. Purposes remain narrow and transparent.

CTA

Ready for retro action? Check out offers on classic slots.

Sharing and Disclosure

I share nothing. Solo operation means no partners or vendors access raw data. Hosting providers see logs but anonymized. Legal demands compel disclosure only under court order, rare for this scale. No sales, rentals, or trades occur.

Service providers like email hosts process transmissions per their terms. I review them yearly. Aggregates might inform public posts, stripped of identifiers. Emergencies like hacks prompt authorities if needed, with notification where possible.

Transparency rules: any sharing logs in updates here. Expect zero routine outflows.

Cookies and Similar Tech

First-party session cookies last visit duration, clearing on close. No persistent trackers. Essential ones enable navigation; disable at browser risk to function. No analytics cookies currently; plans use server-side if added.

Local storage avoids for now. Third-party none. Cookie banner appears on first visit listing types. Consent stored simply. EU/UK visitors get granular controls per regs. Details:

Session ID: navigation.
Preferences: dark mode if implemented.

Clear via browser settings anytime.

Data Storage and Retention

Data lives on secure home servers or NZ cloud with encryption at rest. Backups rotate weekly, encrypted. Logs retain 12 months, then purge unless needed. Emails keep until resolved, then archive indefinitely for records.

Personal session data persists longer for research, my own only. Access logs rotate monthly. Deletion automates via cron jobs. Storage uses RAID for redundancy. No offshoring; all NZ-based.

Volume stays low; scripts compress efficiently. Audits confirm compliance quarterly.

Security Practices

Home office setup includes firewall, fail2ban, and regular updates. HTTPS everywhere with strong ciphers. Passwords hash with salts. Scripts run non-root. Intrusion detection scans logs daily.

Physical security locks servers. Backups offsite encrypted. Incident response plan tests yearly. Vulnerability scans via open tools. Least privilege principle applies throughout.

Breaches trigger notifications within 72 hours per law. Mitigation first.

Your Rights and Choices

Request access, correction, deletion via email. Response within 30 days. NZ Privacy Act covers locals; GDPR for EU if applicable. No automated decisions affect you.

Withdraw consent anytime; impacts future collection. Opt-out of non-essential cookies. Portability for emails provided. Complaints direct to me or NZ Privacy Commissioner.

Verification via email confirmation. Rights exercised free unless excessive.

Children's Privacy

Site targets adults; no kid content. No known under-16 collection. Parents contact for removal. COPPA compliance assumed.

Policy Updates

Changes post here with date. Major ones email subscribers if any. Continued use signals acceptance. Review annually.

Contact Information

Reach Murray at [email protected]. No physical address public for security. Responses prompt.