Who we are

digitalmediamarketing.ai

I am a guy who likes and is learning AI. I live in Portland Oregon.


Comments

I don't do comments



Who we share your data with

Google Analytics. Here is an AI description:


Google Analytics, as a web analytics service provided by Google, is designed to collect data on user interactions with websites and apps to help site owners understand usage patterns. Importantly, Google prohibits the collection of personally identifiable information (PII)—such as names, email addresses, or precise physical addresses—through its standard implementation. Instead, it focuses on anonymized or pseudonymous data. However, some collected data (like IP addresses) may be classified as personal data under privacy laws like GDPR, depending on the context and jurisdiction.Below is a breakdown of the main types of data collected, based on Google's official documentation. Note that the exact data can vary based on how a website owner configures Analytics (e.g., via tags, SDKs, or integrations with advertising features).Key Data Categories Collected:
  • Unique Identifiers:
    • Pseudonymous client identifiers stored in first-party cookies (e.g., a random number like 12345.67890) to recognize returning users across sessions.
    • App instance identifiers for mobile apps (a randomly generated number tied to the app installation; resets if the user clears their advertising ID).
  • Device and Browser Information:
    • Browser type and version.
    • Device model, operating system, screen resolution, and language settings.
    • This helps analyze how users access the site (e.g., mobile vs. desktop).
  • IP Addresses:
    • Temporarily collected to derive approximate geographic location (e.g., country or city level) and for security purposes.
    • In Google Analytics 4 (GA4), IP addresses are not logged or stored; they are used briefly and then discarded or anonymized.
  • Usage and Interaction Data:
    • Pages viewed, time spent on pages, and navigation paths.
    • Referral sources (e.g., how users arrived at the site, like from a search engine).
    • Events such as clicks, form submissions, or video plays (if tracked).
    • Search terms used on the site (if applicable).
  • Advertising-Related Data (if enabled):
    • Advertising identifiers (e.g., from Google Ads integrations) for features like remarketing or audience measurement.
    • This may include data on ad interactions, but only if the site owner enables it and obtains user consent where required.
Important Notes:
  • Anonymization and Privacy: Data is collected in a way that avoids direct PII. Identifiers are random and not tied to real-world identities without additional context from the site owner. Google uses secure transmission (HTTPS) and disperses data across systems for protection.
  • No Direct PII Collection: Site owners must ensure no PII is sent (e.g., via URL parameters). If PII is inadvertently included, it's the owner's responsibility, not Google's.
  • User Controls: You can limit or opt out of data collection by:
    • Installing the Google Analytics Opt-out Browser Add-on.
    • Managing cookie preferences in your browser.
    • Adjusting ad personalization settings in your Google account (e.g., via Ads Settings).
    • For apps, resetting your advertising ID.
For the most up-to-date details, refer to Google's official resources, as policies can evolve.

Google Analytics, as a web analytics service provided by Google, is designed to collect data on user interactions with websites and apps to help site owners understand usage patterns. Importantly, Google prohibits the collection of personally identifiable information (PII)—such as names, email addresses, or precise physical addresses—through its standard implementation. Instead, it focuses on anonymized or pseudonymous data. However, some collected data (like IP addresses) may be classified as personal data under privacy laws like GDPR, depending on the context and jurisdiction.Below is a breakdown of the main types of data collected, based on Google's official documentation. Note that the exact data can vary based on how a website owner configures Analytics (e.g., via tags, SDKs, or integrations with advertising features).

Key Data Categories Collected:

  • Unique Identifiers:
    • Pseudonymous client identifiers stored in first-party cookies (e.g., a random number like 12345.67890) to recognize returning users across sessions.
    • App instance identifiers for mobile apps (a randomly generated number tied to the app installation; resets if the user clears their advertising ID).
  • Device and Browser Information:
    • Browser type and version.
    • Device model, operating system, screen resolution, and language settings.
    • This helps analyze how users access the site (e.g., mobile vs. desktop).
  • IP Addresses:
    • Temporarily collected to derive approximate geographic location (e.g., country or city level) and for security purposes.
    • In Google Analytics 4 (GA4), IP addresses are not logged or stored; they are used briefly and then discarded or anonymized.
  • Usage and Interaction Data:
    • Pages viewed, time spent on pages, and navigation paths.
    • Referral sources (e.g., how users arrived at the site, like from a search engine).
    • Events such as clicks, form submissions, or video plays (if tracked).
    • Search terms used on the site (if applicable).
  • Advertising-Related Data (if enabled):
    • Advertising identifiers (e.g., from Google Ads integrations) for features like remarketing or audience measurement.
    • This may include data on ad interactions, but only if the site owner enables it and obtains user consent where required.
Important Notes:
  • Anonymization and Privacy: Data is collected in a way that avoids direct PII. Identifiers are random and not tied to real-world identities without additional context from the site owner. Google uses secure transmission (HTTPS) and disperses data across systems for protection.
  • No Direct PII Collection: Site owners must ensure no PII is sent (e.g., via URL parameters). If PII is inadvertently included, it's the owner's responsibility, not Google's.
  • User Controls: You can limit or opt out of data collection by:
    • Installing the Google Analytics Opt-out Browser Add-on.
    • Managing cookie preferences in your browser.
    • Adjusting ad personalization settings in your Google account (e.g., via Ads Settings).
    • For apps, resetting your advertising ID.
For the most up-to-date details, refer to Google's official resources, as policies can evolve.


Email News Letter.
I use Hostinger Reach Email Marketing tool. You can opt-out anytime. Here is an AI description of Hostinger information:

Data Collected by Hostinger Reach, Hostinger Reach is an AI-powered email marketing platform integrated into the Hostinger ecosystem. As such, its data collection practices are governed by Hostinger's overall Privacy Policy. Hostinger collects various types of personal data to provide services, including email marketing features like building contact lists, sending campaigns, and tracking results. Note that some data is provided directly by users (e.g., during signup or uploads), while other data is collected automatically (e.g., via logs or cookies).Below is a structured summary of the key data types collected, based on Hostinger's privacy practices. This includes data relevant to Reach users (e.g., account holders) and data processed on their behalf (e.g., subscriber lists). Purposes are tied to service delivery, compliance, security, and improvements. Hostinger does not store sensitive payment details itself but uses third-party processors.

1. Account and Signup Information
  • Email address and password (minimum required for signup).
  • First and last name, contact details (e.g., for domain-related services or support).
  • Identity verification documents (e.g., passport, ID card, or driver's license images) if needed for compliance (e.g., ICANN rules for domains, though less relevant for Reach alone).
  • How Collected: Directly from you during registration or account updates.
  • Purposes: User identification, access to the platform, providing services like email campaigns, support, fraud prevention, and sending updates.


2. Login and Authentication Data
  • Login scopes and email from third-party providers (e.g., Google or Facebook scopes).
  • How Collected: When logging in via social accounts.
  • Purposes: Authentication and seamless access to Reach features.


3. Payment and Billing Information
  • Financial details for processing payments (e.g., for premium Reach plans), including payment status and last 4 digits of credit cards.
  • Note: Full credit card info is not stored by Hostinger; handled by certified third-party processors.
  • How Collected: During subscription or purchase (e.g., Reach plans allow up to 200 emails/month and 100 unique subscribers for free tiers, with paid upgrades).
  • Purposes: Billing for services, including email marketing subscriptions.

4. Communications and Support Data
  • Details from inquiries, chats, messages, or support tickets, including account history.
  • How Collected: When you contact support or interact via the platform.
  • Purposes: Resolving issues, disputes, enforcing agreements, and improving services.

5. Usage and Interaction Data
  • Pages visited, content viewed, searches, actions (e.g., email campaigns created, sent, or tracked).
  • Reach-specific: Account overview stats (e.g., subscriber counts, email send metrics), synced subscribers from integrated sites (e.g., via WordPress plugin).
  • How Collected: Automatically through platform usage, often via Google Analytics (which uses permanent cookies).
  • Purposes: Analyzing usage to optimize features, improve email deliverability, and enhance user experience.


6. Log Data and Device Information
  • IP addresses, browser type, ISP, referring/exit pages, operating system, date/time stamps, clickstream data.
  • Device details (e.g., OS, phone model, device ID).
  • Approximate geo-location derived from IP.
  • How Collected: Automatically when accessing the platform.
  • Purposes: Diagnosing issues, optimizing services, security (e.g., detecting abuse), legal compliance (e.g., taxes or pricing).


7. Tracking Technologies and Cookies
  • Cookies, beacons, tags, scripts for tracking interactions.
  • Examples: Click tracking (CI codes), source tracking (ISC), item tracking (ITC).
  • Reach may use these for campaign performance (e.g., open rates, clicks).
  • How Collected: Automatically via browser or app.
  • Purposes: Monitoring activity, personalization, and analytics. See Hostinger's Cookie Policy for details.


8. Subscriber and User-of-User Data (Processed on Your Behalf)
  • Contact lists, email addresses, and other info uploaded for email marketing (e.g., subscribers synced from your website via forms or plugins).
  • Any personal data from visitors/users of your emails or linked sites.
  • How Collected: Uploaded by you (e.g., importing contacts) or via integrations (e.g., WordPress plugin auto-syncs new subscribers).
  • Purposes: Enabling email campaigns, segmentation, and tracking. Hostinger processes this as a data processor under your instructions, not for its own use (per Data Processing Addendum).

9. Other Data
  • Job applicant info (if applying via Hostinger).
  • Survey responses, forum posts, or promotional participation.
  • Aggregated or inferred non-personal data.
  • How Collected: Directly or indirectly through interactions.
  • Purposes: Market research, service improvements, business operations.
Key Notes on Hostinger Reach-Specific Practices
  • Reach is designed for collecting leads, segmenting audiences, and sending emails. It integrates with Hostinger tools (e.g., Business Email, Website Builder), so data like subscriber emails is synced automatically if enabled.
  • Limits on free plans (e.g., 100 unique subscribers/month) help manage data volume.
  • Hostinger emphasizes compliance with laws like GDPR and CCPA. You can opt out of marketing emails, disable cookies, or request data access/deletion via their support.
  • Data is not sold to third parties but may be shared with affiliates, service providers (e.g., for analytics or payments), or for legal reasons.
  • Retention: Data is kept as long as needed for services, then deleted (e.g., logs for 30 days, account data until deletion request).
  • Security: Encrypted transmission, access controls, and regular audits.
For the most accurate and current details, review Hostinger's Privacy Policy directly, as practices may update. If you're a Reach user, check your dashboard for data management options.

Let me know if I forgot anything.