EddieRod.com policy

Do Not Sell or Share My Personal Information

Privacy choices, Global Privacy Control handling, and how to submit a qualifying request.

Version 1.0 Effective 2026-07-25

DMCA & Copyright Policy

Complete publication candidate for attorney approval

Document key: dmca

Version: 1.0

Effective date: July 27, 2026

1. Respect for copyright

EddieRod.com respects copyright and expects users to do the same. This Policy explains how to report material you believe infringes copyright and how a user may dispute a removal.

2. Designated copyright agent

Send copyright notices and counter-notices to:

DMCA Agent: Copyright Agent, EddieRodLLC

Operator: EddieRodLLC, doing business as EddieRod.com

Address: 3816 South Lamar Blvd, Building 22, Austin, Texas 78704, United States

Phone: 512-387-0093

Email: focus@eddierod.com

EddieRod.com intends to maintain matching agent information in the U.S. Copyright Office DMCA Designated Agent Directory.

3. Copyright notice

A notice should include:

1. your physical or electronic signature;

2. identification of the copyrighted work claimed to be infringed, or a representative list if multiple works are covered;

3. identification of the material claimed to be infringing and information reasonably sufficient for us to locate it, including the URL;

4. your name, mailing address, telephone number, and email address;

5. a statement that you have a good-faith belief that the disputed use is not authorized by the copyright owner, its agent, or law; and

6. a statement, under penalty of perjury, that the notice is accurate and that you are the copyright owner or authorized to act for the owner.

A notice that does not substantially include this information may be delayed or rejected. Knowingly making a material misrepresentation may create liability.

4. What we do with a notice

When we receive a substantially valid notice, we may remove or disable access to the identified material, notify the user who posted it, preserve relevant records, and take other appropriate action. We may forward the notice, including contact information, to the user or a transparency service where lawful.

We may also remove material when we have actual knowledge or become aware of facts making infringement apparent, even without a formal notice.

Automated filters may help identify duplicate or apparently infringing material, but a filter does not replace review of a properly submitted notice.

5. Counter-notice

A user who believes material was removed because of mistake or misidentification may send a counter-notice containing:

1. the user’s physical or electronic signature;

2. identification of the removed material and where it appeared before removal;

3. a statement under penalty of perjury that the user has a good-faith belief the material was removed or disabled because of mistake or misidentification;

4. the user’s name, address, telephone number, and email address;

5. consent to the jurisdiction of the federal district court for the user’s address, or, if outside the United States, the federal judicial district where EddieRodLLC is located; and

6. agreement to accept service of process from the person who submitted the original notice or that person’s agent.

6. Restoration after counter-notice

We may send the counter-notice to the original claimant. Unless the claimant notifies us that a court action has been filed seeking to restrain the allegedly infringing activity, we may restore the material not less than 10 and not more than 14 business days after receiving a valid counter-notice.

7. Repeat infringers

We maintain a policy of terminating, in appropriate circumstances, users who repeatedly infringe copyright. We may consider valid notices, counter-notices, court findings, repeated removals, obvious infringement, and attempts to evade enforcement. We may act sooner for deliberate, large-scale, or dangerous conduct.

8. Other rights complaints

Trademark, privacy, publicity, impersonation, defamation, and other rights complaints may be sent to focus@eddierod.com. A DMCA notice should be used only for copyright claims.

9. Misuse

Do not submit a notice or counter-notice containing knowingly false statements. We may suspend accounts that abuse the process and may disclose information when required by law.

10. Contact

Email: focus@eddierod.com

Phone: 512-387-0093

Mail: 3816 South Lamar Blvd, Building 22, Austin, Texas 78704, United States

EddieRod.com Legal Review Package • Page of

ATTORNEY REVIEW COPY | FACTUAL FIELDS COMPLETED

EDDIE ROD.COM / LEGAL DOCUMENT

Data Retention Schedule

Complete publication candidate for attorney approval

Status: Internal legal and operational annex

Version: 1.0

Effective date: July 27, 2026

This schedule supports the Privacy Policy and deletion, export, anonymization, suppression, licensing, security, and legal-hold workflows. “Anonymize” means removing direct identifiers and retaining only what remains necessary. A hash may still be personal or pseudonymous data.

1. Operating principles

• Keep personal information only as long as reasonably necessary for a documented purpose.

• Delete information when no longer needed, unless law, security, fraud prevention, licensing, suppression, accounting, or a dispute requires retention.

• When deletion would destroy evidence of a contract, license, consent, suppression request, or abuse decision, retain the minimum record and remove direct identifiers where practical.

• Restrict access to retained records and prohibit unrelated use.

• Apply deletion to active systems promptly and allow backups to expire through normal rotation.

• Place a documented legal hold on relevant records when a dispute, investigation, or preservation duty arises.

• Use automated deletion where implemented and documented manual review for remaining categories.

2. Schedule

Data

System

Retention period

Account-erasure treatment

Purpose or trigger

Account profile, email, locale

Auth

Life of account + 30 days

Delete

Account operation and recovery window

Password hash and two-factor secret

WordPress / Security

Life of account

Delete promptly

Authentication

Onboarding progress

Auth

Life of account + 30 days

Delete

Operational state

Legal acceptance records

Theme Core / Auth

7 years after later of acceptance, account closure, or related transaction end

Anonymize where possible; preserve document, version, time, surface, and locale

Contract evidence

Email subscriber and preferences

Mailer

Life of subscription or account + 30 days

Delete except suppression evidence

Communications

Email suppression list

Mailer

Indefinite while the address must remain suppressed

Retain hashed or minimum matching value

Prevent unwanted re-contact

Email send, open, click, bounce, and complaint events

Mailer

24 months

Delete or aggregate

Delivery operations and measurement

Consent event log

Mailer / Theme Core / Security

7 years after event or related relationship

Anonymize; preserve version, surface, time, locale, and minimum evidence

Proof of consent and withdrawal

Topic, source, interest, and saved-item preferences

Feed / Vault

Life of account + 30 days

Delete

Personalization

Engagement events

Feed

24 months, then aggregate or delete

Delete

Personalization, digest selection, and performance

Attribution, UTM, and advertising-campaign data

Feed / Members / Advertising

24 months

Delete or aggregate

Measurement and attribution

Unpublished User Content

Bulletins

Life of account + 30 days

Delete unless legal hold

User workspace

Published Bulletins, riffs, and comments

Bulletins

While published or needed for community context

Retain with identifying account information removed after account deletion; remove for valid legal, safety, privacy, or moderation reason

Publishing and dependent works

Moderation reports and decisions

Bulletins

3 years after closure

Anonymize reporter where practical

Safety, abuse, and repeat-offender evidence

Vault entitlements and frozen license receipts

Vault

Life of license + 7 years; minimum records for perpetual grants may be retained indefinitely

Restrict or anonymize only if the license remains provable

Both parties’ evidence of rights

Vault download audit

Vault

24 months

Delete

Abuse detection and support

Stripe customer, subscription, payment, refund, and transaction records

Members / Advertising

7 years after transaction or account closure

Anonymize or restrict; retain accounting minimum

Tax, accounting, refunds, and chargebacks

Membership state and history

Members

Life of account + 24 months

Delete except transaction evidence

Account and support

Coupon redemptions

Members

3 years

Anonymize

Reconciliation and abuse prevention

Referral fraud evidence and actor hash

Members

24 months after decision

Anonymize or restrict

Prevent repeated abuse

Referral reward ledger

Members

7 years after grant or reversal

Anonymize

Reconciliation and disputes

Age-verification audit

Security

365 days unless law requires longer

Anonymize

Eligibility evidence

Hashed birth-date or age input

Security

User: up to 365 days; guest: up to 30 days

Delete

Age verification

Security logs and hashed IP

Security

180 days; longer under legal hold or active investigation

Anonymize or restrict

Security and incident response

Cookie-consent and GPC audit

Security / Theme Core

5 years after event

Anonymize

Proof of consent and opt-out state

Advertising-selection and measurement decisions

Advertising

14 to 90 days according to configured inventory setting; aggregate reporting may remain longer

Delete direct decision records; retain aggregates

Delivery, debugging, and reconciliation

Privacy requests and identity-verification records

Theme Core / WordPress

3 years after closure

Anonymize or restrict

Proof of response and appeal

Support, corrections, and legal correspondence

Support

3 years after closure; longer for active dispute

Delete or redact when no longer needed

Service history and disputes

DMCA notices, counter-notices, and repeat-infringer records

Legal / Bulletins

7 years after closure or last relevant action

Restrict; remove unnecessary direct identifiers where possible

Takedown evidence and repeat-infringer policy

Hosting backups

Hostinger

Up to 90 days

Expire through rotation; reapply deletion after restoration

Disaster recovery

3. Deletion workflow

1. Authenticate the request using proportionate information.

2. Locate data across registered subsystems.

3. Delete ordinary account, preference, engagement, and workspace records.

4. For retention-bound records, remove direct identifiers, restrict access, and record the retention basis.

5. Preserve content or evidence under a documented legal hold.

6. Record completion, partial denial, and appeal instructions.

7. Ensure deleted data is not reintroduced from backups except during a necessary restore, after which the deletion request must be reapplied.

4. Special operating rules

4.1 Published content after account deletion

Published Bulletins, riffs, and comments may remain while the account identity is removed. This preserves links, community context, and dependent riffs. A valid copyright, privacy, safety, court, or legal removal requirement overrides ordinary retention.

4.2 Perpetual Vault licenses

A licensee and EddieRod.com may need the frozen receipt many years later. If de-identification would make the license impossible to prove, the record is restricted rather than destroyed.

4.3 Acceptance and suppression evidence

Legal acceptance and suppression records remain after account deletion because deleting them can destroy proof of agreement or cause renewed unwanted email. Their use remains limited to those purposes.

4.4 Hashes

IP and birth-date hashes may be susceptible to matching or enumeration and are treated as pseudonymous personal data unless a documented assessment establishes otherwise.

4.5 Manual and automated enforcement

Some categories are automatically deleted, expired, anonymized, or rotated. Other categories require documented manual review. The public Privacy Policy describes the intended periods; operations must not claim automatic enforcement where only a manual process exists.

5. Review cycle

Review this schedule at least annually and whenever a new processor, data category, advertising method, AI use, subscription model, age rule, or legal regime is introduced.