Share → Bond → Receive

Pandemology Privacy and Cookie Policy with Educational Dicta

Responsible Party

Jason Spangehl

Document Purpose

Compliance with Laws Governing how Social Media Companies Can Use Your Data

Benefitting Party

Social Media Companies Who Don't Want to Provide Integration Without Collecting Your Data

Cookie Policy for Pandemology

This is the Cookie Policy for Pandemology, accessible from

What Are Cookies

As is common practice with almost all professional websites this site uses cookies, which are tiny files that are downloaded to your computer, to improve your experience. This page describes what information they gather, how we use it, and why we sometimes need to store these cookies. We will also share how you can prevent these cookies from being stored; however, this may downgrade or 'break' certain elements of the sites functionality.

For more general information on cookies see the Wikipedia article on HTTP Cookies.

How We Use Cookies

We use cookies for a variety of reasons detailed below. Unfortunately, in most cases, there are no industry standard options for disabling cookies without completely disabling the functionality and features they add to this site. It is recommended that you leave on all cookies if you are not sure whether you need them or not in case they are used to provide a service that you use.

Disabling Cookies

You can prevent the setting of cookies by adjusting the settings on your browser (see your browser Help for how to do this). Be aware that disabling cookies will affect the functionality of this and many other websites that you visit. Disabling cookies will usually result in also disabling certain functionality and features of this site. Therefore it is recommended that you do not disable cookies.

The Cookies We Set

Account related cookies 

If you create an account with us, then we will use cookies for the management of the signup process and general administration. These cookies will usually be deleted when you logout; however, in some cases, they may remain afterwards to remember your site preferences when logged out.

Log-in related cookies 

We use cookies when you are logged in so that we can remember this fact. This prevents you from having to log in every single time you visit a new page. These cookies are typically removed or cleared when you log out to ensure that you can only access restricted features and areas when logged in.

Email newsletter related cookies: 

This site offers newsletter or email subscription services and cookies may be used to remember if you are already registered and whether to show certain notifications which might only be valid to subscribe/unsubscribed users.

Orders processing related cookies

This site offers e-commerce or payment facilities, and some cookies are essential to ensure that your order is remembered between pages so that we can process it properly.

Surveys related cookies

From time to time, we offer user surveys and questionnaires to provide you with interesting insights, helpful tools, or to understand our user base more accurately. These surveys may use cookies to remember who has already taken part in a survey or to provide you with accurate results after you change pages.

Forms related cookies

When you submit data to through a form such as those found on contact pages or comment forms, cookies may be set to remember your user details for future correspondence.

Site preferences cookies

In order to provide you with a great experience on this site, we provide the functionality to set your preferences for how this site runs when you use it. In order to remember your preferences, we need to set cookies so that this information can be called whenever you interact with a page is affected by your preferences.

Third Party Cookies

In some special cases, we also use cookies provided by trusted third parties. The following section details which third party cookies you might encounter through this site.

This site uses Google Analytics which is one of the most widespread and trusted analytics solutions on the web for helping us to understand how you use the site and ways that we can improve your experience. These cookies may track things such as how long you spend on the site and the pages that you visit so we can continue to produce engaging content.

For more information on Google Analytics cookies, see the official Google Analytics page.

Third-party analytics are used to track and measure usage of this site so that we can continue to produce engaging content. These cookies may track things such as how long you spend on the site or pages you visit which helps us to understand how we can improve the site for you.

From time to time, we test new features and make subtle changes to the way that the site is delivered. When we are still testing new features, these cookies may be used to ensure that you receive a consistent experience whilst on the site whilst ensuring we understand which optimisations our users appreciate the most.

If we sell products, it's important for us to understand statistics about how many of the visitors to our site actually make a purchase and as such this is the kind of data that these cookies will track. This is important to you as it means that we can accurately make business predictions that allow us to monitor our advertising and product costs to ensure the best possible price.

We also use social media buttons and/or plugins on this site that allow you to connect with your social network in various ways. For these to work the following social media sites including;
Linked In
will set cookies through our site, which may be used to enhance your profile on their site or contribute to the data they hold for various purposes outlined in their respective privacy policies.

More Information

However if you are still looking for more information then you can contact us through one of our preferred contact methods:

By visiting this link:


In Sam’s corner of the net, Facebook beckoned with a grin, "Share your life!" they said, but forgot to mention the bin, Where every like, every post, every bit of his whim, Goes to a database, neatly tucked in.

Sam quipped, “Tried Twitter, for a change of scene, But before I knew it, they knew where I'd been. ‘Just share your thoughts, keep it brief and lean’, While they mined my data, oh, so unseen.”

Instagram told Sam, “Show your life’s highlights!” But between the filters and the copyrights, Sam thought, “It’s not my life they want in the lights, It’s my data, my habits, my sleepless nights.”

“Join LinkedIn,” they said, “build that network bond!” But with every connection, of him they grew fond, Sam laughed, “They don’t care about my job or my pond, Just my contacts, connections, and the magic wand of my card.”

Snapchat promised ephemeral, a momentary glee, But Sam mused, “Do those snaps ever truly flee? In the age of the screenshot, nothing’s truly free, Every fleeting moment, stored eternally.”

“Pinterest!” Sam exclaimed, “Just a board, a pin!” But even there, algorithms play to win. “Show me DIYs, recipes, the latest sin,” But in exchange, they know his every kin.

Sam sighed, “Remember when sharing was simply divine? Now, with every post, I toe a fine line. YouTube, TikTok, even Spotify's chime, All want a piece of my digital time.”

In the world of retweets, shares, and viral tags, Where giants vie for our time, wrapped in rags of terms. Sam declares, “It’s not just a platform, but a digital drag, Where every share is worth its weight, in virtual terms.”

I.        Pandemology’s Use of Data

Stabilization (A → B) ∧ (B → C) ∧ (C → A)

Dominant Legal Interpretation:

  • Object A: Service: The Service refers to the website provided by the company. The Service is designed to facilitate specific functionalities and services.
  • Object B: Personal Data: Personal Data encompasses any information that can identify an individual, gathered while using the Service.
  • Object C: Company: The Company refers to Pandemology, which owns and operates the Service.
  • Service → Personal Data: The Service collects Personal Data for its functioning.
  • Personal Data → Company: The Personal Data is used by the Company to improve and provide the Service.
  • Company → Service: The Company maintains and offers the Service to users.

In this Stabilization, it's clear that there's a cyclical relationship. The Service collects data, which then is utilized by the Company to further improve the Service, creating a feedback loop. For users, this implies that their data is integral for the provision and improvement of the Service.

Competing Legal Interpretations:

  • Object A: Service: The Service could also be seen as a platform for data collection for purposes beyond providing the said Service.
  • Object B: Personal Data: Personal Data may include data that the user is unaware is being collected.
  • Object C: Company: The Company could be part of a larger network of organizations sharing data for varying purposes.

The competing legal interpretations suggest a level of ambiguity in terms of the exact boundaries of data use, potential risks of data sharing, and scope of the Service’s functionalities. Users should exercise caution and demand transparency.

Dicta Counterbalance (¬B → ¬A) ∧ (¬C → ¬B) ∧ (¬A → ¬C)

  • ¬Object A: Lack of Service: Absence of access to the Service, possibly due to restrictions or unavailability.
  • ¬Object B: Absence of Personal Data: Situations where Personal Data isn't collected because the Service isn't accessed.
  • ¬Object C: Absence of Company’s Role: Scenarios where the Company isn't collecting, storing, or utilizing data because there's no Service being offered.
  • ¬Personal Data → ¬Service: If no Personal Data is collected, the Service isn't being used.
  • ¬Company → ¬Personal Data: If the Company isn't operational, then no Personal Data is collected.
  • ¬Service → ¬Company: If the Service isn't available, the Company has no role.

In this negation layer, the absence of one element leads to the absence of the other, indicating a counterbalance. If users don't use the Service, their Personal Data is not collected. Similarly, if the Company is not in operation, the Service will not function. This layer reinforces the interconnected nature of the original triad, warning users of the impacts of the absence of any object in the layer.

II.      Types of Data Collection

Causal (A → B) ∧ (B → C) ∧ (¬A → ¬C)

Dominant Legal Interpretation:

  • Object A: Usage of Service Here, the act of using the Service is described in greater detail, highlighting the types of data that are collected, including usage data and personally identifiable information.
  • Object B: Types of Personal Data The types of Personal Data refer to the specific categories of information collected, like email address, name, phone number, and Usage Data such as IP addresses and browser types.
  • Object C: Data Collection Mechanisms These are the processes or methods employed to collect various types of Personal Data, such as automatic collection for Usage Data or prompted input for personally identifiable information.
  • Usage of Service → Types of Personal Data: When the Service is used, various types of Personal Data are collected.
  • Types of Personal Data → Data Collection Mechanisms: Different types of Personal Data are collected through different mechanisms.
  • ¬Usage of Service → ¬Data Collection Mechanisms: If the Service is not used, data collection mechanisms are not activated.

In this Causal chain, it is clear that the types of data collected are directly linked to how one uses the Service. The complexity of data collection also becomes evident, emphasizing the need for user awareness and literacy regarding data privacy.

Competing Legal Interpretations:

  • Object A: Usage of Service The Service could potentially collect data without clear user consent or knowledge.
  • Object B: Types of Personal Data The data collected might be used for different undisclosed purposes.
  • Object C: Data Collection Mechanisms The mechanisms may be invasive, possibly collecting more data than what is outlined.

The competing legal interpretations raise concerns about transparency and data use ethics. It suggests the need for more stringent data collection limitations and user notifications.

Dicta Reversion (¬B → ¬A) ∧ (¬C → ¬B) ∧ (C → A)

  • ¬Object A: Non-Usage of Service Absence of access or usage of the Service, resulting in no data collection.
  • ¬Object B: Absence of Types of Personal Data No specific categories of Personal Data are being collected because the Service is not in use.
  • ¬Object C: Inactive Data Collection Mechanisms Data collection mechanisms aren't activated as there's no usage or Personal Data being gathered.
  • ¬Types of Personal Data → ¬Usage of Service: Absence of types of Personal Data indicates the Service is not being used.
  • ¬Data Collection Mechanisms → ¬Types of Personal Data: If the mechanisms are inactive, it implies that no data categories are being collected.
  • Data Collection Mechanisms → Usage of Service: Active data collection methods indicate the Service is in use.

Implications and Warnings: This layer warns that if data collection mechanisms are active, the Service is most likely in use even if one isn't aware, highlighting the need for vigilance. On the flip side, inactive data collection mechanisms and absence of types of Personal Data are good indicators that the Service isn’t in use.

III.    Social Media Integration

Association ((¬B → ¬A) ⊻ C) ∧ ((¬B → ¬C) ⊻ A) ∧ ((A ∧ C) → B)

Dominant Legal Interpretation:

  • Object A: Third-Party Social Media Services Platforms like Google, Facebook, Instagram, Twitter, and LinkedIn that allow a user to create an account and log into the Service.
  • Object B: Granting Access to Personal Data The act of the user giving permission to collect personal data upon using Third-Party Social Media Services for account creation or login.
  • Object C: Company's Use of Data How the company uses, shares, and stores the Personal Data collected from Third-Party Social Media Services.
  • ((¬B → ¬A) ⊻ C): Either not granting access negates the use of Third-Party Social Media Services or the company will use the data.
  • ((¬B → ¬C) ⊻ A): Either not granting access negates the company's use of data or Third-Party Social Media Services will be used.
  • ((A ∧ C) → B): Using Third-Party Social Media Services and the company's use of data implies granting access.

The Decision Layer suggests that the act of granting access to data (Object B) is influenced by the interplay between the usage of Third-Party Social Media Services (Object A) and the Company's use of the data (Object C). This layer highlights the conditional relationships that exist and can help users make more informed decisions.

Competing Legal Interpretations:

  • Object A: Third-Party Social Media Services The platforms may gather more data than explicitly outlined in the Privacy Policy.
  • Object B: Granting Access to Personal Data The scope of access granted may be wider than the user is aware of.
  • Object C: Company's Use of Data The Company may use the data for unspecified purposes.

Competing interpretations present concerns that the decision to grant access to data may be fraught with hidden implications, requiring users to critically evaluate the scope and intent behind such permissions.

Dicta Discrimination ((A → B) ⊻ ¬C) ∧ ((C → B) ⊻ ¬A) ∧ (¬B → (¬A ∧ ¬C))

  • ¬Object A: Non-Usage of Third-Party Services Not using any Third-Party Social Media Services for login.
  • ¬Object B: No Granting of Access No permissions are given for Personal Data access.
  • ¬Object C: Company's Non-Use of Data The Company is not using, sharing, or storing Personal Data from Third-Party Services.
  • Triad Relationship:
  • ((A → B) ⊻ ¬C): Either using Third-Party Services leads to granting access or the Company won't use the data.
  • ((C → B) ⊻ ¬A): Either the Company's use of data leads to granting access or Third-Party Services won't be used.
  • (¬B → (¬A ∧ ¬C)): Not granting access leads to both non-usage of Third-Party Services and the Company's non-use of data.

Discrimination serves as a cautionary guideline, stressing that the failure to grant access (¬B) directly impacts both the usage of Third-Party Services (¬A) and the Company's use of data (¬C). It implies a need for a transparent opt-in system and raises concerns about the indirect consequences of data-sharing decisions.

IV.    Cookie Policy

Coexistence (A ↔ B) ∧ (B ↔ C) ∧ (A ↔ C)

The coexistence of A, B, and C ensures the functionality and user experience of the website. One type of cookie often relies on the other to make the overall service seamless.

  • A: Necessary / Essential Cookies
  • B: Cookies Policy / Notice Acceptance Cookies
  • C: Functionality Cookies
  • ¬A: Absence of Necessary / Essential Cookies
  • ¬B: Absence of Cookies Policy / Notice Acceptance Cookies
  • ¬C: Absence of Functionality Cookies

Dominant Legal Interpretation

  • A ↔ B: Necessary cookies (A) coexist with acceptance cookies (B). Necessary cookies often need user consent, flagged by acceptance cookies.
  • B ↔ C: Acceptance cookies (B) coexist with functionality cookies (C). If a user has consented through acceptance cookies, functionality cookies usually operate seamlessly.
  • A ↔ C: Necessary cookies (A) coexist with functionality cookies (C). Both types often work together to make essential website features available.

Under a dominant legal interpretation focused on coexistence, each type of cookie complements the others in terms of functionality and compliance. All must be present for optimal website operation and user experience. Companies should ensure proper implementation and notification about all types of cookies to comply with regulations.

The argument can be made that the absence of one cookie type doesn't necessarily affect the other types' functionality. Therefore, they might not coexist in a strict sense but operate independently under certain conditions.

If the cookies don't have to coexist, the legal interpretation could be that users should have more granular control over which cookies they accept, potentially affecting how cookies should be presented in compliance with laws like GDPR.

Dicta Equilibrium (¬A ↔ ¬B) ∧ (¬B ↔ ¬C) ∧ (¬A ↔ ¬C):

This deals with the absence or negation of each object and their equilibrium in non-existence.

  • ¬A ↔ ¬B: The absence of necessary cookies (¬A) often correlates with a lack of acceptance cookies (¬B), making it hard to gain user consent.
  • ¬B ↔ ¬C: Without acceptance cookies (¬B), functionality cookies (¬C) are often also absent, affecting website functionality.
  • ¬A ↔ ¬C: The absence of necessary cookies (¬A) usually means an absence of functionality cookies (¬C), impairing basic website functions.

In a legal framework that understands these objects in a state of equilibrium in their absence, a company failing to implement one may likely fail to implement the others, potentially leading to non-compliance with laws and poor user experience.

By understanding the importance of each type of cookie and their coexistence or equilibrium, companies can better navigate the legal landscape around user data and consent.

V.      Data Retention, Transfer, and Deletion

Coexistence (A ↔ B) ∧ (B ↔ C) ∧ (A ↔ C)

Dominant Legal Interpretation and Implications

  • A: Retention of Personal Data by the Company
  • B: Transfer of Personal Data by the Company
  • C: User’s Right to Delete Personal Data
  • ¬A: No Retention or Immediate Deletion of Personal Data
  • ¬B: No Transfer or Restricted Movement of Personal Data
  • ¬C: No Right or Inability to Delete Personal Data

Under this layer, all objects coexist in a balanced state. In the dominant legal interpretation, each object is seen as mutually influential and interdependent.

The dominant legal interpretation would focus on the reciprocal obligations and rights between the user and the Company. While the Company can retain and transfer data, the user has the right to delete data. All three are implemented under the umbrella of legal obligations, security concerns, and user consent.

  • A ↔ B: The Company retains personal data (A) while also having the capability to transfer this data (B). Both exist together under the Privacy Policy.
  • B ↔ C: The Company's ability to transfer personal data (B) coexists with the user's right to delete personal data (C).
  • A ↔ C: Retaining personal data (A) coexists with the user's right to delete it (C).

Dicta Equilibrium (¬A ↔ ¬B) ∧ (¬B ↔ ¬C) ∧ (¬A ↔ ¬C)

  • ¬A ↔ ¬B: The non-retention or immediate deletion of data (¬A) is likely tied to scenarios where the data is not transferred to other locations (¬B).
  • ¬B ↔ ¬C: If the data is not transferred (¬B), it is also likely that the user has either chosen or is unable to delete it (¬C).
  • ¬A ↔ ¬C: If data is not being retained (¬A), it might be due to the user's decision or inability to request retention (¬C).

In the negations, we observe that an absence in one dimension likely implies an absence in the other dimensions. For example, if data isn't being retained, it may also imply that the Company isn't transferring it, which could mean the user has deleted or can't delete it. This equilibrium serves as a cautionary note on the complexities of data management and user rights.

These dicta emphasize that both parties should be fully aware of the intertwined nature of data retention, transfer, and deletion, as they are often linked in ways that might not be immediately apparent.

Disclosure of Personal Data

  • A: Disclosure of Personal Data in Business Transactions
  • B: Disclosure of Personal Data to Law Enforcement
  • C: Disclosure for Other Legal Requirements
  • ¬A: Non-disclosure or Restricted Disclosure in Business Transactions
  • ¬B: Non-disclosure or Restricted Disclosure to Law Enforcement
  • ¬C: Non-disclosure for Other Legal Requirements

Stabilization (A → B) ∧ (B → C) ∧ (C → A)

  • A → B: Disclosure in the context of business transactions (A) sets a precedent for disclosure to law enforcement (B).
  • B → C: If data can be disclosed to law enforcement (B), it reinforces the likelihood of disclosure for other legal requirements (C).
  • C → A: Disclosing data for other legal requirements (C) could potentially make it easier for the Company to disclose data in future business transactions (A).

The dominant legal interpretation here sees the various types of disclosure as mutually reinforcing, creating an environment where if one type of disclosure is permissible, it increases the likelihood of others.

Dominant Legal Interpretation

Under this dominant interpretation, each form of data disclosure supports and justifies the others. If the Company discloses information for one reason, such as a business transaction, it sets a precedent that might make other forms of disclosure more acceptable or even expected.

Dicta Counterbalance Analysis (¬B → ¬A) ∧ (¬C → ¬B) ∧ (¬A → ¬C)

  • ¬B → ¬A: If the Company resists disclosing to law enforcement (¬B), that might make it less likely to disclose during business transactions (¬A).
  • ¬C → ¬B: If the Company avoids disclosure for other legal requirements (¬C), this could inhibit disclosure to law enforcement (¬B).
  • ¬A → ¬C: If there are restrictions or hesitance in disclosing for business transactions (¬A), this could potentially impact the likelihood of disclosure for other legal requirements (¬C).

In a counterbalancing logic, avoiding one form of disclosure makes it more likely that other forms will be avoided as well. This may involve invoking user consent, data minimization principles, or other legal arguments to counteract disclosure requirements.

This dicta suggests a note of caution: if the Company or the user is concerned about privacy and wants to minimize disclosure, they must consider how each form of permitted disclosure can influence others.

VI.    Security and Additional Features

Causal Analysis (A → B) ∧ (B → C) ∧ (¬A → ¬C)

  • A: Security of Personal Data
  • B: Children's Privacy
  • C: Links to Other Websites
  • ¬A: Inadequate Security Measures
  • ¬B: Non-Compliance with Children's Privacy
  • ¬C: Unchecked Third-Party Interactions

Dominant Legal Interpretation and Implications

The dominant legal interpretation here posits that adequate security measures not only protect user data but also serve as a critical factor in ensuring compliance with regulations like children's privacy. Any failure in one aspect could significantly affect the others.

  • A → B: Proper security measures (A) are critical to ensuring children's privacy (B).
  • B → C: Upholding children's privacy (B) is in line with ensuring that third-party links (C) are also safeguarded or at least appropriately disclaimed.
  • ¬A → ¬C: A failure in data security (¬A) would naturally lead to a lack of trust or control in third-party interactions (¬C).

In a causally connected triad, the objects are reliant on one another for proper function. Adequate security measures are foundational, affecting both children's privacy and the safety of third-party links. Inadequate measures in any of these areas could lead to cascading legal and ethical issues.

Dicta Reversion (¬B → ¬A) ∧ (¬C → ¬B) ∧ (C → A)

  • ¬B → ¬A: Failure to comply with children's privacy regulations (¬B) could potentially lead to broader security issues (¬A).
  • ¬C → ¬B: Lack of oversight on third-party interactions (¬C) could result in non-compliance with children's privacy (¬B).
  • C → A: Ensuring oversight or disclaimers for third-party websites (C) actually reinforces the general security measures (A).

In the reversion logic, the absence of compliance in one area may lead to a collapse in others. For example, if the Company fails to properly curate or warn about third-party links, it could open a gateway for issues concerning children's privacy, which in turn could undermine general security.

This dicta highlights the precarious nature of these interlinked responsibilities. Each area of compliance or non-compliance influences the others, either buttressing the Company's legal standing and ethical responsibilities or eroding it. Therefore, a holistic approach to these concerns is crucial for both the Company and the user.

VII. Additional Provisions of the Agreement

Changes and Contact

Object Identification

  • A: Changes to Privacy Policy
  • B: User Notification
  • C: Contact Information
  • ¬A: Lack of Policy Updates
  • ¬B: Inadequate User Notification
  • ¬C: Unreachable Contact Information

Stabilization (A → B) ∧ (B → C) ∧ (C → A)

  • A → B: Any change to the Privacy Policy (A) will trigger a user notification process (B).
  • B → C: User notification (B) is valid and effective only if there is accurate and accessible contact information (C).
  • C → A: Availability of accurate contact information (C) allows users to inquire about or discuss changes to the Privacy Policy (A).

The dominant legal interpretation underscores the stability between updating the Privacy Policy, notifying users, and having available contact information. Each serves as a stabilizing factor for the other.

Dominant Legal Interpretation and Implications

In a stabilization triad, each object helps sustain the others. Changes to the Privacy Policy (A) require effective notification to users (B), which is dependent on valid contact information (C). This results in a virtuous cycle that stabilizes the user's trust and the company's integrity.

Dicta Counterbalance (¬B → ¬A) ∧ (¬C → ¬B) ∧ (¬A → ¬C)

  • ¬B → ¬A: Inadequate user notification (¬B) might imply that the Privacy Policy is not updated frequently or transparently (¬A).
  • ¬C → ¬B: Unreachable or incorrect contact information (¬C) negates the efficacy of user notification (¬B).
  • ¬A → ¬C: If there are no updates or changes to the Privacy Policy (¬A), it may indicate that the contact information provided may not be regularly checked or updated (¬C).

In counterbalance logic, the absence of one object destabilizes the others. Inadequate user notification can be symptomatic of a lack of regular policy updates, and both of these are dependent on the availability and accuracy of contact information.

This dicta underlines the importance of balance and stability among these elements. Failing in one aspect could cause a counterbalancing negative effect on the others, thereby eroding the user's trust and possibly inviting legal scrutiny.

If you have any questions about this Privacy Policy, You can contact us:

By visiting this page on our website: